Exchange2007 Migration to Office 365

I performed a Cutover Migration from an OnPremise Exchange 2007 to Office 365 Successfully, but I cannot get the Outlook Clients inside the Domain where the old Exchange 2007 Server resides, it tries to go find the internal Exchange Server each time and I even used the Microsoft Setup Repair Tool and it will do the initial setup of the Profile but then it will not connect again after that. I added in the DNS Server a xxx.com Zone and added the CNAME: autodiscover and pointed it to autodiscover.outlook.com and I can ping it but I still cannot get the Outlook to communicate to Office365, anyone's input is appreciated as I am in the middle of the conversion.
dtssupportAsked:
Who is Participating?
 
Jose Gabriel Ortega CConnect With a Mentor CEO J0rt3g4 Consulting ServicesCommented:
Do the corrections for your domain.
Set-AutodiscoverVirtualDirectory -Identity "Autodiscover (default web site)" -ExternalURL https://autodiscover.erllc.com/AutoDiscover/AutoDiscover.xml -InternalURL https://autodiscover.erllc.com/AutoDiscover/AutoDiscover.xml

Open in new window

0
 
Jose Gabriel Ortega CCEO J0rt3g4 Consulting ServicesCommented:
Yeah, you missed a step in your 2007 infrastructure.

just run this:

Set-ClientAccessService -Identity $env:computername -AutoDiscoverServiceInternalUri https://autodiscover.outlook.com/Autodiscover/Autodiscover.xml

Open in new window


Some people set it to $Null
I personally tell him where it is directly

Here are the Microsoft references:
Base Cutover migration: https://support.office.com/en-us/article/Cutover-migration-to-Office-365-9496e93c-1e59-41a8-9bb3-6e8df0cd81b4

Here you move to the tab "Run a Cutover migration" (in 3rd line) and then go to "complete post-migration tasks. (you are in the step1), they set it to null.
0
 
dtssupportAuthor Commented:
Where do you run this script at and on, tried a computer workstation and it errors out?
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
Jose Gabriel Ortega CCEO J0rt3g4 Consulting ServicesCommented:
Of course, you need to run the script in the Exchange Server 2007,  (Exchange management shell in the start menu, run it in as an administrator)
https://technet.microsoft.com/en-us/library/2006.12.managementshell.aspx?f=255&MSPPError=-2147217396
0
 
dtssupportAuthor Commented:
Script doesn't work on Exchange 2007, does not like the Term 'Set-ClientAccessService"
0
 
Adam BrownSr Solutions ArchitectCommented:
To clarify, the answers given are scripts that are designed to change the Active Directory SCP for your on-prem Exchange server. If you have the users migrated, you can do this easily. https://acbrownit.com/2014/04/04/exchange-autodiscover-episode-2-attack-of-the-exchange-server/ explains what the SCP is and how to change it through AD Sites and Services, if you want to do it that way. The SCP is the first check done for domain-joined computers, so you have to make sure it's set to point to https://autodiscover.outlook.com/autodiscover/autodiscover.xml.
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.