Removing first Exchange 2010 Server from a Domain Controller/Linking profiles with new secondary Exchange server
Posted on 2011-03-05
We have a single, multihomed Domain Controller that is running Exchange 2010 with about 25 users/mailboxes.
Before anyone goes on about this, yes I know what an awful setup this is. (it is a very powerful box so I thought it might handle it)
Due to the terrible performance we were getting (surprise surprise), I've commisioned a new server to move Exchange 2010 to (we'll address the multihome issue later, performance is more important).
That's all installed, which went fine and it recognises the first server properly. I've moved a handful of the mailboxes over via a local move request which as gone smoothly.
Now my understanding is those users that have been moved to server 2 should automatically start requesting information from server 2 and not server 1, however when I go into Outlook and click change on the Microsoft Exchange account settings, the server is still listed as server1. Naturally the performance is even worse for these users now. If I make a new profile in Outlook and go through the process of adding their user accounts again, it correctly links up with Server 2.
How long will it take for server 2 to be loading automatically into Outlook user profile account settings, or will I have to make these changes manually?
I am still getting some serious latency on these properly moved profiles, and still popup bubbles with "Microsoft exchange is try to get information from server2" etc etc, you all know the one I mean.
Is this because server1 is still overly occupied with exchange, delaying the Global Catalog requests? Will I have to remove exchange entirely to see benefits here? I was hoping to make the move slowly for a gradual increase in performance, and then eventually uninstall Exchange from server 1.
I have more questions about OWA and what I have to do to maintain access but I think I'll post that in another question.
Thanks in advance.