asked on Outlook 2007 won't connect to E2K10 after migration from E2K3
Two weeks ago our company was contracted to migrate a single Windows 2003 server (file & Exchange 2003) to a new single Windows 2008 server (file & Exchange 2010).
The 2K8 server was added to the domain as a DC & GC, shares were recreated, files were moved over, all without issue.
Exchange 2010 was installed, mailboxes were moved, and OWA works. After decommissioning the old server, mail processing stopped, OWA broke, and Outlook 2007 users were no longer able to connect, so we reestablished it as a DC & GC.
As luck would have it, the old server started shutting itself off during the workday (not hibernation, just turning off), so we left it turned off and were forced to remove all traces of it from AD now stored on the new server. No traces of it appear in ADD&T, ADU&C, ADS&S, DNS, or DHCP.
Email flow has resumed without a hiccup since the weekend, OWA works, but Outlook still won't connect, claiming "Cannot open your default e-mail folders. Microsoft Exchange is not available. Either there are network problems or the Exchange computer is down for maintenance."
We suspect this error has something to do with a setting that relates to the old server still being necessary for either Exchange or Outlook, but we can't find it.
What information can we provide to you to help diagnose this issue?
Thank you in advance,
Isaac
The 2K8 server was added to the domain as a DC & GC, shares were recreated, files were moved over, all without issue.
Exchange 2010 was installed, mailboxes were moved, and OWA works. After decommissioning the old server, mail processing stopped, OWA broke, and Outlook 2007 users were no longer able to connect, so we reestablished it as a DC & GC.
As luck would have it, the old server started shutting itself off during the workday (not hibernation, just turning off), so we left it turned off and were forced to remove all traces of it from AD now stored on the new server. No traces of it appear in ADD&T, ADU&C, ADS&S, DNS, or DHCP.
Email flow has resumed without a hiccup since the weekend, OWA works, but Outlook still won't connect, claiming "Cannot open your default e-mail folders. Microsoft Exchange is not available. Either there are network problems or the Exchange computer is down for maintenance."
We suspect this error has something to do with a setting that relates to the old server still being necessary for either Exchange or Outlook, but we can't find it.
What information can we provide to you to help diagnose this issue?
Thank you in advance,
Isaac
ExchangeActive Directory
Last Comment
isaacgrover
You need to enable Encrypt settings in Outlook.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
@loki_loki - We can't bring the old server back up because it won't stay up for any predictable amount of time. We've recreated profiles a number of times with no success. When creating the profile, 'servername' is entered for the Exchange server, the username is entered, and when 'Check Name' is clicked, 'servername' resolves to its correct internal FQDN, and 'username' expands to the AD description.
@amitkulshrestha - Encryption is enabled.
After running 'Test-servicehealth' in EMS, we found that MSExchangeRPC and MSExchangeSA weren't running; we've started these services manually even though they were set to start automatically, and will continue to monitor their status.
I'll split points since you were the two who replied. =)
@amitkulshrestha - Encryption is enabled.
After running 'Test-servicehealth' in EMS, we found that MSExchangeRPC and MSExchangeSA weren't running; we've started these services manually even though they were set to start automatically, and will continue to monitor their status.
I'll split points since you were the two who replied. =)