Link to home
Start Free TrialLog in
Avatar of James Parsons
James ParsonsFlag for Canada

asked on

Outlook 2010 Hangs momentarily when sending first message after opening program

We recently migrated from Exchange 2007 (Small Business Server 2008) to Exchange 2013. After shutting down the old Exchange 2007 server, Outlook (2010) clients seem to hang for 60-120 seconds upon replying to, forwarding, or creating a message the first time after starting the program. Subsequent replies, forwards, or new messages happen instantly. This behavior is repeated, once, the next time Outlook has a fresh start. The issue disappears when the old server is back online. The issue is persistent even when Outlook is opened in Safe Mode.

It's evident to me that there is some remnant of Exchange still active on the old server which clients are looking for. The problem is that I have no idea what it might be because everything else functions normally when the old server is offline. I'm not sure where to look, or how to identify what might be causing this issue.
Avatar of James Parsons
James Parsons
Flag of Canada image

ASKER

The same behavior occurs when creating a new calendar appointment
ASKER CERTIFIED SOLUTION
Avatar of gilnov
gilnov
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of R. Andrew Koffron
a DNS change to look at new server might help,
My guess is there's still some Exchange features.
here's a link to removing exchange 2007 there's another link to completely remove Exchange 2007 in text, if you're keeping any part of the server and it's an SBS server, I'd do the minimum removing you can get away with.
https://technet.microsoft.com/en-us/library/aa998193%28v=exchg.80%29.aspx
Do you use cached or online Exchange mode in Outlook?
Adding a CNAME record in DNS that directs DNS lookups of the previous server name to the new server name solved the problem.
Excellent. Glad you got it fixed.