Index Server uses IIS virtual directories to control indexing. To index a set of documents stored on the computer, the directory storing those documents must fall under an IIS virtual directory. This tour assumes familiarity with IIS. If you are unfamiliar with IIS and virtual directories, you should refer to the IIS documentation.
Index Server works best with disks formatted as Windows NT File System (NTFS). This format minimizes the impact of internal fragmentation due to large cluster sizes. Also, with an NTFS volume, you can experiment with the security features of Index Server.
This test drive takes you through three main steps in setting up a directory to search a group of documents.
The sample corpus contains four files and consumes 145 kilobytes (KB) of disk space.
File name | File type |
Ixserver.xls | Microsoft® Excel |
Ixserver.ppt | Microsoft® PowerPoint® |
Ixserver.doc | Microsoft® Word for Windows |
Ixgerman.doc | Microsoft® Word for Windows |
By default, these files are installed in the InetPub\IisSamples\IsSamples directory.
To create a directory for storing the sample corpus
A list of virtual directories appears.
To create a new virtual directory
The New Virtual Directory Wizard appears.
A list of access permissions for the directory appears, with Read and Script access selected by default. Read access allows users to search the directory and see documents that match their search. Script access allows users to execute any script files you may want to put into the directory.
The Corpus virtual directory appears in the list of virtual directories in the MMC. This virtual directory maps to the physical Corpus directory that you created earlier on this page.
As files are moved to the Corpus directory, change notifications are sent to Index Server, which then indexes the documents immediately.