Topic Last Modified: 2005-11-18
The Microsoft® Exchange Server Analyzer Tool queries the Active Directory® directory service to determine if the Content Indexing Rebuild Schedule (msExchCIRebuildSchedule) attribute and the Content Indexing Rebuild Style (msExchCIRebuildStyle) attribute are present and set to anything other than 0. These are attributes of each public information store database.
If the Exchange Server Analyzer finds that both of these attributes are present and set to anything other than 0, a non-default configuration message is displayed.
When these two attributes are both set to 1, it indicates that full-text indexing has been enabled for the information store database. Full-text indexing enables powerful and fast searches by indexing every word in a specified database. When you deploy full-text indexing, you select an individual public folder or mailbox store to be indexed. Users can then conduct full-text searches on the messages and attachments contained in the public folder or mailbox store.
By default, the index contains the subject and body of a message, along with names of the sender and recipient and any names that appear in the Cc and Bcc fields. The index also includes text from the following types of attachments: .doc, .xls, .ppt, .html, .htm, .asp, .txt, and .eml (embedded Multipurpose Internet Mail Extensions (MIME) messages) files. Binary attachments, such as pictures and sounds, are not indexed.
Search results are only as accurate as the last time the index was updated. As the content of public folders or mailbox stores changes, the index must be updated to reflect the new content. Index updates can be performed manually or automatically on a schedule.
There are four major categories of full-text indexing files. You can optimize the performance of full-text indexing by arranging the disk location of these files as follows:
- Catalogs Catalogs are the main indexes.
There can be one catalog for each Exchange store. Place your
catalog on a RAID-0+1 array. You can specify the catalog location
in Exchange System Manager when you create the catalog.
- Property store This is the database
containing various properties of items indexed in the catalog.
There is only one property store per server. Place the full-text
property store on the RAID array. By default, the files are
installed on the same drive as Exchange Server.
- Temporary files These files contain
temporary information used by the Microsoft Search service. Place
the full-text index temporary directory on the RAID array. By
default, these files are installed on the system drive, which
typically does not have the I/O throughput of the RAID array.
- Gatherer logs These files contain log
information for the indexing service. One set of logs exists for
each catalog. The gatherer logs can remain in their default
location, or you can move them if you choose.
To enable or
disable full-text indexing
-
Open Exchange System Manager.
-
Expand Servers, expand an Exchange server, and then expand the storage group containing the public folder store you are working with.
-
Right-click the public folder store and select Properties.
-
Select the Full-Text Indexing tab.
-
Edit the Update interval field as desired.
-
Click OK to save the changes and exit the public folder store Properties.
For more information about full-text indexing public folders, see the Microsoft Knowledge Base article 319433, "HOW TO: Configure Full-Text Indexing on Public Folders" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=319433).
For more information about configuring and troubleshooting full-text indexing on mailbox stores, see the following Knowledge Base articles:
- 822932, "HOW TO: Configure Full-Text Indexing on Mailbox Stores
in Exchange 2003" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=822932)
- 319436, "HOW TO: Configure Full-Text Indexing on Mailbox Stores
in Exchange 2000" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=319436)
For information about full-text indexing in a multi-language environment, see the Knowledge Base article 325624, "XGEN: Full-Text Indexing with Multiple Languages" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=325624).
For more information about full-text indexing best practices, see the Knowledge Base article 326186, "XADM: White Paper - The Best Practices for Deploying Full-Text Indexing" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=326186).