Migrating to new Exchange 2007 SP3 update rollup 6 mailbox servers
Environment:
Recently we built 2 new mailbox servers to replace our current mailbox servers.
Exchange is installed on Windows Server 2008 R2 SP1
We've set the Genertion Server for the OAB to be the new server
We've changed the client settings for the new databases to be the Public folder database on the new server.
We've configured replication between the old public folder database and new database.
We've migrated all users to the new mailbox servers.
Problem:
After a couple weeks of having a static environment we finally shutdown the 2 old mailbox servers.
Now we're getting reports from users with a negative outlook experience
Outlook will take 10-15 minutes to open
Outlook will hang when browsing email, creating meetings, and other general calendar task.
I see no errors on the servers or the clients.
We've placed the users in online mode and back to cached mode
Recreating the users profile doesn't fix the problem either.
Any suggestions on this issue would be much appreciated.
July 27th, 2012 5:22pm
Make sure that all public folders have replicas in the new public folder database, including the system folders under:
\NON_IPM_SUBTREE\SCHEDULE+ FREE BUSY
\NON_IPM_SUBTREE\OFFLINE ADDRESS BOOK
\NON_IPM_SUBTREE\EFORMS REGISTRY
Then remove all replicas from the old public folder server. Monitor the old server with Get-PublicFolderStatistics to make sure that all replicas go away. Then remove the old public folder database. See if that fixes your problem.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
Free Windows Admin Tool Kit Click here and download it now
July 30th, 2012 12:45am
Make sure that all public folders have replicas in the new public folder database, including the system folders under:
\NON_IPM_SUBTREE\SCHEDULE+ FREE BUSY
\NON_IPM_SUBTREE\OFFLINE ADDRESS BOOK
\NON_IPM_SUBTREE\EFORMS REGISTRY
Then remove all replicas from the old public folder server. Monitor the old server with Get-PublicFolderStatistics to make sure that all replicas go away. Then remove the old public folder database. See if that fixes your problem.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
July 30th, 2012 12:47am
Ed,
Thank you for the assist. You were correct.
I ran a powershell script to replicate all the public folders, but apparently only default public folders were copied and not system. Looks like the system folders had to be configured manually.
Free Windows Admin Tool Kit Click here and download it now
August 16th, 2012 1:15pm