After removing 2003 Exchange servers from 2003-2007 mixed environment Outlook 2007 fails to connect to Exchange 2007 on first attempt - "Exchange server is unavailable"

After removing 2003 Exchange servers from 2003-2007 mixed environment Outlook 2007 fails to connect to Exchange 2007 on first attempt - "Exchange server is unavailable"

We recently removed Exchange 2003 from our mixed 2003-2007 environment.  All servers are running
Exchange 2007 with SP2.  All clients use Outlook 2007.

Now whenever a user opens Outlook 2007 for the first time it fails to connect with "exchange server is unavailable".
When I check the control panel > Mail applet there is a profile named "Default Outlook Profile".  If I delete the
"Default Outlook Profile" and reopen Outlook it successfully connects, creating the "Outlook" profile.

It's not a showstopper, but very annoying and this behaviour just started after retiring the EXchange 2003 servers.

An nslookup of autodiscover resolves to our 2007 CAS server.

Any ideas why Outlook fails to connect to the Exchange 2007 server on the first attempt, but always
succeeds on the second attempt (after deleting the "Default Outlook Profile")
calljdubAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

AustinComputerLabsCommented:
Did you migrate their mailboxes or export and import?
0
calljdubAuthor Commented:
Migrated 2003 mailboxes to 2007 4 months ago.  This behaviour started in the last month.  Also happenning to (new) users who were never on 2K3 mailbox.
0
AmitIT ArchitectCommented:
Test the Exchange connectivity from below link
https://www.testexchangeconnectivity.com/
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

MegaNuk3Commented:
Open outlook with /rpcdiag and see if it is attempting to connect over HTTP

Where does the default Outlook profile come from? Are you sure you don't have a login script for new users that is creating this outlook profile that incorrectly points to the wrong server?
0
MegaNuk3Commented:
When you go into the default outlook profile does it list an old exchange server name?

A quick workaround would be to add the old server names to DNS and point them at your new servers
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
calljdubAuthor Commented:
meganuk3:

> When you go into the default outlook profile does it list an old exchange server name?

yes

> A quick workaround would be to add the old server names to DNS and point them at your new servers

Nice idea, but I'd like to clean this up.

How to I search ldap or adsiedit for any instances of the old-computer name?
0
AustinComputerLabsCommented:
See: http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_26932659.html

For instructions on removing an orphaned Exchange server from AD.
0
MegaNuk3Commented:
Have you tried EXPROFRE to sort out user registry entries?

Or for a user you can open the exchange profile through control panel and then put a space in the end of the exchange server name and press "check name", this will update the majority of the registry entries if not all of them. This is kind of what EXPROFRE does, but EXPROfre can be run from the login script
0
calljdubAuthor Commented:
Adding an alias for the (removed Exchange 2K3) and pointing it to the 2007 CAS server worked.  Outlook clients that were looking for <oldserver> now resolve and account settings come up clean with <2007 CAS server>.

Have exhausted looking at:

- Registry searches of all Exchange servers and DC for <oldserver>
- LDAP search of Exchange container for <oldserver>
- DNS search for <oldserver>
- network login scripts using <oldserver>
- Possible GPO conflicts

No instances of <oldserver> in the above.

"test-OutlookWebServices -identity:<username>" returns failure, so something is amiss.

This weekend we're rebooting all the DC and Exchange servers.  If problem continues will work with MS support.

DNS alias tip was a good one to buy time and please the guys at the help desk!
0
MegaNuk3Commented:
Try EXPROFRE (which is probably what MS will suggest)

Thanks for the points
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.