On-premises SBS 2011 Partial emails migrate to O365--After Cutover Setup steps
I am in the process of migrate one particular domain emails from On-Premises to Office 365 using a third party tool of Skykick. The cutover date is in 2 days.
The scenario is this:
The On-premises server is SBS 2011 which is Exchange 2010. It hosts 30+ emails with 7 Authoritative domains (see the attached). Users login on their Terminal Server (Windows Server 2012) to access all the company resources and exchange emails.
The moving away domain is not the primary domain. All Users (including the users with the moving away domain) are still login to the Terminal Server to access all their resources.
My query is:
What are the steps for the After Cutover Migration on the On-premises server to properly remove the Moving Away Domain email settings so that the internal mail flow will have no issue?
I have no issues with update DNS and MX records etc. for the moving away domains. Email flow outside the company domain environment should be all OK I believe.
Accepted-Domains1.JPG
The scenario is this:
The On-premises server is SBS 2011 which is Exchange 2010. It hosts 30+ emails with 7 Authoritative domains (see the attached). Users login on their Terminal Server (Windows Server 2012) to access all the company resources and exchange emails.
The moving away domain is not the primary domain. All Users (including the users with the moving away domain) are still login to the Terminal Server to access all their resources.
My query is:
What are the steps for the After Cutover Migration on the On-premises server to properly remove the Moving Away Domain email settings so that the internal mail flow will have no issue?
I have no issues with update DNS and MX records etc. for the moving away domains. Email flow outside the company domain environment should be all OK I believe.
Accepted-Domains1.JPG
Edward van Biljon (MVP)
What email flow problems are you referring to? Will office 365 control the DNS etc? You then can switch the accepted domain from authoritative on Exchange to relay and mail should go out to the internet to Office 365?
O365 has an excellent set of migration wizards that allow the entire process to be staged. Everything is there for you making the cut-over to O365 painless.
What I need to do to avoid any possible internal mail flow problems after the Migration Cutover?Ideally, use a consultant who has a proven track record of sbs2011 to 0365 migrations.
if this isn't viable you could follow sbs2011 > o365 migration guides very carefully but the risk of mail flow issues may remain depending on your experience.
SBS is an odd little combination of Microsoft components that were never designed to share a server so consistency is key. if you have performed customization/fixes outside of the SBS wizards you may encounter issues not covered in guides.
ASKER
Thank you so much for all your help. The migration cutover date is 21 June. I just want to get some professional advice before the cutover. The company has multiple domain emails hosted in the On-Premises SBS 2011. Only one domain name is migrate to Office 365. If I remove this domain (in migration) from the OC-Hub Transport-Accepted Domains list, what could happen to the related user?
https://docs.microsoft.com/en-us/exchange/exchange-deployment-assistant?view=exchserver-2019
I recommend you to go through this
I recommend you to go through this
The O365 Guide will provide all of the needed steps prior to, during, and post cut-over. Please follow them.
Since this is Small Business Server, the next step once everything is migrated and the cut-over is successful is to remove Exchange properly from SBS. I suggest keeping a small domain controller on-premises as O365 user synchronization is a lot easier to manage that way.
Since this is Small Business Server, the next step once everything is migrated and the cut-over is successful is to remove Exchange properly from SBS. I suggest keeping a small domain controller on-premises as O365 user synchronization is a lot easier to manage that way.
ASKER
Thank you Philip. I appreciate that If I migrate the entire on-premises emails to O365 then decommission the Exchange server is the way to complete the post-migration tasks. But my situation is the company is still need the On-premises Exchange for all the other company emails. Only one group of user's emails with a particular domain name (currently is hosted as the server accepted authoritative domain) are migrating to O365. I could not find any Microsoft resource that is addressing this kind of scenario.
Think the process thru is the best advice. SBS2011 is no black magic and its no different to moving users from on Prem to Off Prem.
I've done a few of these now and the one thing that is the hardest - those little receipient suggestions in OLK. Sometimes they resolve to the username@domain.local and the users need reminding that they should delete these if the emails get rejected. I can't delete them via GP or login script so the users have to delete them themselves.
Edit the Autodiscover records for the doimain you are moving off prem, to reflect the new IP's or domain names and, delete the existing email profiles for each user. Being SBS2011 I dont imagine it will be too many users that you'll need to do this for.
I've done a few of these now and the one thing that is the hardest - those little receipient suggestions in OLK. Sometimes they resolve to the username@domain.local and the users need reminding that they should delete these if the emails get rejected. I can't delete them via GP or login script so the users have to delete them themselves.
Edit the Autodiscover records for the doimain you are moving off prem, to reflect the new IP's or domain names and, delete the existing email profiles for each user. Being SBS2011 I dont imagine it will be too many users that you'll need to do this for.
ASKER
Thank you all for your advice. There are a few more days before the cutover. I have also generated a support ticket to the Microsoft Support. I'll update my configuration results here in due time.
When the cut-over happens, if the default e-mail domain is the one moving to O365, then run the SBS Console setup wizard to change the default to one of the other domains.
Then, once that's done, remove the Service Connection Point (SCP) in Active Directory using PowerShell for the domain moved to O365 so that local user's Outlook doesn't keep looking to the local Exchange (this should be in the O365 Migration Guide).
Then, once that's done, remove the Service Connection Point (SCP) in Active Directory using PowerShell for the domain moved to O365 so that local user's Outlook doesn't keep looking to the local Exchange (this should be in the O365 Migration Guide).
ASKER
Thank you Philip. The moving email domain is not the default one. It is one of the Accepted Authoritative Domain in the Exchange 2010. Users with that email domain are still login to the On-premises terminal server for other activities. Currently any new user generated can choose any email domain for their landing account emails.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Philip--Thank you. Your comment pointed me to the more thorough understanding of the SBS Exchange services. My scenario is relatively simple but apparently requires some understanding of how the Exchange manage the inbound/outbound mail flows. Thanks again.
Also, many thanks to Edward, Steve, MAS and mbkitmgr. Your helps are all valuable.
Also, many thanks to Edward, Steve, MAS and mbkitmgr. Your helps are all valuable.