asked on

New Exchange 2010 server lag issue

I have Exchange 2010, running on Windows 2008 domain controller. I added a new windows 2008 server to my network to replace the domain controller. I installed Exchange 2010 on the new server (with the old server still on the network). Everything replicated, I moved mailboxes, and all seemed good. I temporarily powered down the old server to make sure that everything was installed and configured correctly on the new server. **I have not done dc promo yet on old nor have I uninstalled Exchange - this is going to happen when schedule permits)** In the meantime, new server is running smooth EXCEPT - when users are in Outlook, they click on new email or reply to an email and outlook sits and "thinks" for 30-60 seconds. Its very annoying to users and with good reason. I believe that Exchange is looking for the first database (they are both still listed in my Exchange management console since I have not uninstalled the old one yet) and basically waiting for a timeout or something before going to the current database.

How can I quickly resolve this lag until I actually uninstall exchange from the old server? I was trying to find information on maybe making the new database primary or changing the timeout or something but am not having any luck.

Thanks for any suggestions.

Simon Butler (Sembee)

Start up the old Exchange server.
Exchange expects the other server to be there. Shutting down a server to see if something will break will not work - things will break.
Until you are ready to remove the server you should leave it running.

Installing Exchange on a domain controller is also not recommended. Ideally it should be on a member server. When Exchange is installed on a domain controller it changes the behaviour of Exchange. Exchange will only look to itself for DC functionality.

Simon.

ASKER CERTIFIED SOLUTION

ahyduk1

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ahyduk1

ASKER

I accepted my own comment as a solution because I found the solution myself. There were no other comments offering any suggestions. I wanted to post my solution in case someone else has this issue in the future.