I am trying to migrate over users to a new domain on windows server 2003 environment and have exchange server 2007 installed. To keep the transition as smooth as possible we have chosen to create the user in the new domain and disable the mailbox and attach it to the new profile. The problem with this, is that it takes a couple of hours for the new profile to log in. I am pretty sure that it is due to the information store cache. My question is, is there a way to speed this up, so that it happens a lot quicker? Thank you.

Hi, I understand that you want to migrate users and mailboxes to a new domain,is that right? Then I'd like to know how did you attach the mailbox to the new profile, linked mailbox?disconnect? How did you migrate mailbox? To keep the transition as smooth as possible we have chosen to create the user in the new domain and disable the mailbox and attach it to the new profile. Disable mailbox? From the old domain? How did you attach it to the new profile? Xiu

I disabled the mailbox for the said user, then did a mailbox cleanup; Went to the disconnected mailboxes and connected it to the user in the new domain. It works it just takes about two hours for the user to be able to log on. I think it was your article that i read about the age cache limit and editing the registry. I know not to set it below 20 minutes. Just wondering if that is the right solution for what I am trying to accomplish? I appreciate your help. dmg

Hi, I understand that you use Exchange in the old forest and AD account is in the new forest, is that ture? It will take two hours to allow users to access their mailbox? If that is the case, then I'd like to know how about to use OWA, Outlook to access mailbox? If both account and Exchange Servers are in the same forest, then I recommend you to restart Exchange Information Store Service and force DC replication and then check the issue again. Besides, please try to run ExBPA to have a health scan and then post the errror here. Please try to run DCdiag from your Exchange Server and then post the error part here. For the cache, I recommend you to keep with default value. By the way, do you have anti-virus application isntalled? Do you have exclude the Exchange related files? Xiu

Actually the old domain was a child of the domain that we are moving into. The exchange server has been set up in the parent domain, which is what we are moving towards. Whenever I would connect the mailbox, the log would say ' mailbox connected successfully, but the changes will not show until the next replication'. So when I try to connect the mailbox in OWA, within the two hours, I get an error stating that it could not open the mailbox. After about two hours it function normally. There is only one exchange server, probably hosting approximately 800 mailboxes. I realize that i can restart the information store and the changes will take. The changes show in the active directory instaneously, it has been tried. (the exchange tabs show up in active directory users and computers ) As far errors there are no errors in DCDiag or any of the tools for Exchange. Those were the first things I tried then I researched more and it sounded like the information store kept a cache of some changes. Also part of the reason for them wanting to change the default time has to do with the time it takes when raising the quota limit on mailboxes. They don't want to wait hours for someone to have access back to their mailboxes and do not want to have to restart the information store whenever a mailbox is altered. When running the tests, DCDiag and the exchange tools there are no errors. And yeah the antivirus is configured correctly. dmg