we are in the process of moving mailboxes from one datacenter to a managed services datacenter. The new DC is considered an extension of the current. We have Exchange 2007 SP2 setup in both locations. for the mailboxes that have been moved, there are complaints that the search feature is now slower. especially the first on eof the day or searching after opeing a locked PC. Some users are using Outlook 2003 and some are using Outlook 2007. All have windows XP PC's and there isn't any hope of installing Win Search 4. any idea's would be greatly appreciated.

Are they in cache mode or online? Cache mode searches the local copy for most searches. http://technet.microsoft.com/en-us/library/bb232132(EXCHG.80).aspx

online

online Cache is the recommended and preferred mode. Is the slowness only observed during searches?

"Cache is the recommended and preferred mode" - Agreed but not the customers desire. it is only observered during searches only on mailboxes moved to new mailbox servers at a new DC. its sporadic and can happen at any time. But idol time seems to be a factor. Such as if the PC is locked or the last search was a couple hours ago.

Hi Cause Outlook was in online mode and the Mailbox size was huge which slowed down the search on Server. Resolution We put Outlook in Cached Exchange mode, got all the emails downloaded and indexed. After this, search was performing better.

Depending on the size of the mailbox and also how many mailboxes in each DB. From memory, the catalog search every 5 mins to index all emails in the DB. Can you provide the size of the DB and the mailboxes.

DB = 323 Megs - we havent moved many users there yet I have witnessed the issue on my mailbox which is only 9 megs. Not a typo. Megs. its new.

Try the following. 1. stop the Exchange search indexer service 2. go to the directory where the db reside and rename the Catelog***** folder (this folder will recreate after the service is started) 3. Restart the search indexer service Allow the indexer to finish the indexing before searching. 323MB will probably take 2-5mins. Give that a go

setup scom job to run against index every 9 minutes until the mailbox server is fully populated with users. once the server is populated and people are searching againast it, the search cache should always be ready to go.