Exchange: Outlook Providing Decommissioned Exchange Server
Outlook was not able to configure itself for the private cloud mailbox and it was giving old decommissioned Exchange server name.
This was happening in one of the private cloud’s source domain and I found it interesting issue so sharing.
Issue:
Customer has recently moved all mailboxes into a Private cloud. Mobile and OWA are working fine.
When the source domain users are trying to configure outlook they were getting old decommissioned Exchange server name.
Resolution:
Now customer told me that they are a very small org so when they moved to Private cloud, they just delete the server object from ADUC and Exchange ORG from ADSIEdit. It is not recommended but they had chosen this way because of any xyz reason.
So Exchange was not removed gracefully and exchange attributes were present in properties of the old user. New user outlook was not returning old server name but it was not configuring using autodiscover.
Tried to browse https://autodiscover.emaildomain.com/autodiscover/autodiscover.xml but I was unable to browse the website.
Review the dns and found DNS was not pointing to correct IP.
Fixed the IP in DNS and now I was able to get login prompt for
https://autodiscover.emaildomain.com/autodiscover/autodiscover.xml
Now reviewed few old and new user property in adsiedit.
Found old users have Exchange attributes configured and new users have no Exchange attributes. At this time new users should be able to configure outlook without any issue.
For the old user we ran the following command on a domain controller in elevated PowerShell to clear the Exchange attributes.
get-aduser -filter {msexchmailboxsecuritydescriptor -like “*”} | set-aduser -clear msExchMailboxGuid,msexchhomeservername,legacyexchangedn,mail,mailnickname,msexchmailboxsecuritydescriptor,msexchpoliciesincluded,msexchrecipientdisplaytype,msexchrecipienttypedetails,msexchumdtmfmap,msexchuseraccountcontrol,msexchversion,proxyaddresses,mDBUseDefaults,mDBOverHardQuotaLimit,mDBOverQuotaLimit,mDBStorageQuota,msExchMobileMailboxFlags,homemta,homemdb
Now all users were able to their cloud mailbox in the outlook.
Conclusion:
Always remove Exchange server gracefully else you may land up to an unexpected issue.
Join us and be part of Los Angeles Exchange User Groups. Launch of the Group: http://www.meetup.com/LAExUG/events/224726725/
Microsoft MVP | Exchange Server
Team@MSExchangeGuru
