How to remove AutoDiscover from local Domain Controller after migration to Hosted Exchange?

We've migrated to a hosted Exchange environment, but users are still resolving through the internal Domain Controller's autodiscover address....which means that we can't send mail to internal addresses (the external Hosted account is trying to send to .local addresses).  Any idea how to remove the AutoDiscover address from the onsite Exchange so that resolution skips right to the internet?

We have a CNAME record set up for our Hosted provider for AutoDiscover already.
blueteamAsked:
Who is Participating?
 
Glen KnightCommented:
So you will have created an autodiscover record in your internal and/or external DNS, just point this to the IP of your hosting provider instead of your exchange server,
0
 
Glen KnightCommented:
You mean the autocomplete from previously used addreses?

If so if it's Outlook 2003 or 2007 you will have to delete the NK2 file in each users profile.
0
 
blueteamAuthor Commented:
Not auto-complete, though we had reset that as well.  Both auto-complete and the autodiscover record need to be reset.  I added in the auto-discover record on the domain controller a few months back - need to have it removed now so that the Outlook forwards resolution of our internal addresses to the Hosted Exchange autodiscover record.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
blueteamAuthor Commented:
Correct.  The external address is set up already on the service that hosts our domain.  The internal address just needs to be deleted, I guess if it's not there, then Outlook will forward the requests to the Internet by default.  

I'm in IIS, but I don't see where the URL is for AutoDiscover - that's what I'm looking for.
0
 
blueteamAuthor Commented:
I entered the following into Powershell, which resolved the OOF and OAB errors....

Set-ClientAccessServer -Identity ServerName -AutoDiscoverServiceInternalUri HostedExchangeURL

But I still can't email internally....not sure why.  An AutoConfiguration test brings up the new AutoDiscover address...but when I email internally, it's getting rejected and reporting back the old internal Exchange address still.
0
 
blueteamAuthor Commented:
Actually, I'm able to email from about half the internal users - but not the rest.  I thought maybe it takes a little for the DNS to update - but it's been a few hours and no additional users can email internally.
0
 
blueteamAuthor Commented:
Solved by recreating the remaining profiles....guess it was just a timing thing after I changed the record.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.