Cutover migration | Migrate onpremise Exchange mailboxes to Office 365 using Cutover migration

hi guys i hope you all are doing well and welcome to the next video of this entire series of exchange server 2019 in the last video we talked about imap and pop protocols and we configured imap and pop services in on-premise exchange server in this particular video we will be talking about cut over migration we will understand what is cut over migration what is the process of cut over migration we will talk about the prerequisites those are required to be met before you perform cutover migration and then we will migrate on-premise mailboxes to office 365 using cut over migration cutover migration is the simplest migration type to implement using cutover migration you can migrate all your mailboxes groups contacts and calendars to office 365 in one go you can perform cutover migration if your on premise exchange server version is 2003 or later and you have less than 2000 mailboxes you can perform cutover migration when you are planning to move completely to office 365 you want to move all your on-premise recipients to office 365 and you want to decommission your on-premise exchange server in cutover migration the contents from on-premise exchange server are copied to office 365. cutover migration is not a cut and paste process when you start cut over migration it first provisions the on-premise accounts in office 365 and then it copies the contents of these accounts to office 365. so during the process of cutover migration there will be two mailboxes for one user at the same time the original exchange mailbox that is stored in on premise exchange and the copy of the user mailbox that is being migrated to exchange online let's take a look at cutover migration process first we need to meet all the prerequisites for cutover migration once you have met all the prerequisites we need to create an office 365 challenge and we need to verify the on premise domain in office 365 then we will create a migration endpoint to connect office 365 to our on-premise exchange server once migration endpoint is created we will create a migration batch and we will start the migration and once migration is completed we will create mx record in public dns and we will route all the emails directly to office 365 then we will delete the migration batch we will assign license to the users we will create other dns records in office 365 like cname record so that users can connect to their mailboxes using outlook client and finally we can go ahead and decommission on premise section so this is the process of cut over migration now let's talk about the prerequisites those are required to be met for cutover migration cutover migration use outlook anywhere to connect to your on-premise exchange server so you need to make sure that outlook anywhere is enabled and configured in your on-premise exchange server in exchange 2013 2016 and 2019 outlook anywhere is enabled by default but if you are using exchange 2003 2007 and 2010 you need to enable outlook anywhere manually you would require an ssl certificate from a third party certification authority and mail.domain.com and autodiscover.domain.com has to be added under subject alternative name of that certificate when we create migration endpoint in office 365 we specify on premise exchange administrator credentials this admin account should have full access permission or received as permission on the on-premise mailboxes that we are going to migrate to office 365. you need to make sure the mailboxes that you want to migrate to office 365 they should not be hidden from address list if any mailbox is hidden from address list cutover migration will skip that mailbox if you have azure ad connect deployed in on-premise you need to disable it before you start cut over migration now if you already have synchronized on-premise identities to office 365 using azure already connect you need to purge them because during cutover migration these identities will be provisioned automatically in office 365. so if you already have users synchronized to office 365 cut over migration will either provision duplicate accounts in office 365 or migration process will fail so that is the reason you need to disable azure ad connect before you initiate cutover migration if unified messaging is enabled in on-premise you need to disable it and if you are planning to migrate on premise security groups you need to create mail-enabled security groups in office 365. these groups will be empty mail-enabled groups and once migration is done the membership of the on-premise groups will be updated in office 365 security groups automatically we need to create empty security groups in office 365 because cut our migration cannot provision security groups in office 365. so we need to create these groups manually and the membership of these groups will be updated automatically during the migration process so let's move towards our lab and let's do cut over migration i assume you already have one office 365 tenant so i will not be able to show you how to create office 365 tenant so let's go ahead and let's add premise domain in office 365. i own a domain that i'm currently using in on-premise and that domain is offered 365 concepts.com i have purchased this domain from godaddy so i will have to manage all the dns records in gojadi as of now we are going to add only the txt record because we need to publish only this record in office 365. so let me create a new record and txt add paste the value and click add record so this dns record is not created let me save it again okay now it is created so now we have verified the domain in office 365 challenge as of now this cname record and mx record these two records are pointing to my on-premise exchange server here you can see mail.office365concepts.com and same for mx record mail.office365concepts.com so we have only verified this domain in office 365. let's click verify so the verification is done now office 365 will ask you to verify other records as well like mx spf and cname record you do not have to verify these records as of now so you can simply close the process and the domain is verified next we will check if our on-premise exchange server is reachable from internet through outlook anywhere i'm using exchange 2019 so outlook anywhere is enabled already and in one of the previous videos we have configured outlook anywhere for our exchange server now if you want to test outlook anywhere you need to go to powershell and first you need to connect with exchange online module and once you are connected i'm already connected here if i run get iphone mailbox i should see the result and i am connected so to test outlook anywhere from exchange online we need to run dollar credentials equal get iphone credential and here we will type the email address and password of our on-premise administrator and next we will run test hyphen migration server availability first we will use exchange outlook anywhere because first we have to we are going to perform cut over migration so cutover migration use exchange outlook anywhere so that is the reason we are going to test outlook anywhere plus you need to test auto discover service as well after that we will use email address email address will be the email address of the administrator account that we just used and credentials and here we will use the variable that we just define credentials so by running this command you can verify if exchange online can connect to your on-premise exchange server using outlook anywhere and auto discover so the result says success and it has tested the endpoint that is my on-premise exchange server mail.office365concepts.com and it says valid true so that means my on-premise exchange server is accessible from exchange online over outlook anywhere and autodiscover now the next prerequisite for cut over migration is ssl certificate we already have one ssl certificate from let's encrypt if you want to verify this certificate from exchange admin center you can go to servers and then click certificates and here we can see the ssl certificate that we have got from let's encrypt and domain.com dot mail.office365concepts.com and autodiscover.office365concepts.com are added under subject alternative names of this certificate if you want to verify the exchange certificates from exchange management shell you can run get iphone exchange certificate press enter and this will list all the certificates if you want to check more details you can copy the thumb print and you can type the same command cat iphone exchange certificate hyphen thumb print paste the value and then do pipefl it will give you all the details all the attributes of this certificate you can check from whom you have got the certificate validation date and you can check the services those are binded and you can check the domains as well now the next prerequisite for cutover migration is we will assign full access formation on on premise mailboxes for admin account that we are going to use in migration endpoint for migration purpose so in my on-premise exchange server i have few mailboxes and i have these mailboxes two three four five i have five mailboxes so i will have to assign full access formation on these four mailboxes so i will be running at hyphen mailbox permission iphone identity identity will be the user first i'm going to assign permission on user 2. then we will use hyphen user hyphen user will be the administrator account who needs permission on this mailbox access rights plexus hyphen inheritance type or press enter so this permission is assigned same way we will assign permission on user one for john smith as well i believe i have permission on john smith and bob ross okay it is john smith okay and then we have bob ross so that's done so we have assigned full access permission on the mailboxes as well next we need to make sure that the on-premise mailboxes or the on-premise recipients are not hidden from address list if you want to verify this attribute for mailboxes you can run get hyphen mailbox pipe fl then we will look for display name and hidden from address list press enter so here we can see all the mailboxes are not hidden it says hidden from address list enabled false that means these mailboxes or the recipients are not hidden from address list so this attribute is set to false for everyone this is set for discovery search mailbox we do not need this we do not want to migrate this mailbox for rest of the mailboxes this is set to false next prerequisite says you need to disable azure id connect if it is enabled in your on-premise as of now i do not have azurity connect deployed so we will skip this step and unified messaging is also not available in exchange 2019 so we will skip this step as well now let's go to office 365. and let's go to exchange admin center go to recipients and let's create migration endpoint go to recipients click on migration click on these three dots click on migration endpoints click on plus now here you need to select outlook anywhere because cutover migration use outlook anywhere to connect from exchange online to your on-premise so select outlook anywhere if you are doing cutover migration and then click next under email address you will type one of the on-premise mailboxes email address so here i will use bob ross at office365concepts.com account with privileges will be admin account of your on-premise exchange server so here the format will be office365concepts.com and then username and here we will type the password of this admin account so once you are done click next now if this exchange online tenant can connect to my on-premise exchange server on the next screen i should see my exchange server properties like the url that is mail.office365concepts.com so here we can see this migration endpoint wizard has automatically detected my exchange server url that is mail.office365concepts.com and the authentication is ntlm and mailbox permission is domain admin this is assigned to my administrator account now let's go next here we will type the endpoint name for this migration endpoint for example test cut over migration we can leave these values as it is and click new so the migration endpoint is created click close and if i go to active users so in active users in office 365 i do not see my on-premise users as of now in on-premise i have these many users admin bob ross john smith user 1 and user 2. but in office 365 i do not have any one of these accounts so let's create migration batch now go to recipients migration click on this drop down now here we will select migrate to exchange online because we are going to migrate the mailboxes from on-premise to exchange online you select migrate from exchange online when you do off-boarding in case of exchange hybrid so select migrate to exchange online here we will select cut over migration go next we can see all the details here already go next and this is the migration batch batch one click next no changes are required here we will select automatically start the batch click new and this will start the migration batch click ok on the right here you can see the type of the migration that you are performing we are doing exchange outlook anywhere that is for cut over and staged migration as well direction is on boarding we are migrating from on-premise to office 365. status is syncing here we can see status as well mailbox status synced mailboxes 0 out of 5 finalized 0 out of 5 and as of now there is no failed mailbox if you click on view details we can see the status is validating as of now this batch migration batch is validating the on-premise users once it will change to provision after that you should be able to see on-premise users here under active users so let's wait for some time now let's go to view details again and now we can see the status is changed to provisioning so let's close this and let me refresh the page so now here we can see the administrator account bob ross john smith test user one test user one is my in cloud user user two and we are left with user user1 so let me refresh it again and here we can see user1 and user2 bob ross john smith and administrator so these accounts are provisioned in office 365 let's go back to migration batch view details status is still provisioning no items are skipped so far more details as of not issuing anything so let's wait for a few minutes and after that we will check the status again now if you want to check the status of migration or migration batch from powershell make sure you are connected to exchange online module first and you can verify the batch by running get hyphen migration batch press enter and this will give you the details of batch name status of the batch type of the migration that you are running and how many mailboxes are within that batch if you want to check more attributes you can add pipe fl press enter and this will give you more details like the name of the batch status syncing state is waiting for the next process and you can see number of mailboxes within the batch date and time when this batch was created who created it this is the admin account of my office 365 tenant and here you can see the type of the migration that we are performing outlook any view batch direction is onboarding we are migrating users from on-prem to cloud and like this you can check all these details now if you want to check the migration statistics though it will not give you much details but still you can check so here it will show you the your default domain of your office 365 tenant total count active count active count is how many mailboxes are still active within the batch if any mailbox is failed it will not show you the exact number i mean the same value as total count again it will show you the type of the migration that you are performing now next you can check the users or the mailboxes who are within the migration batch and for that you can run get hyphen migration user press enter and this will list all the users or the accounts those are within the batch so i have five accounts and we can see five accounts here now if i want to check the properties or the values for particular user within the patch you can copy the email address run get hyphen migration user paste the email address and pipe apple so like this you can check the this is the email address batch name and recipient type says mailbox status is provision updating this is still showing syncing so here we can see the status provision updating next status summary says active migration type is exchange outlook anywhere state is waiting for the next process and so like this you can check the properties if you want to check properties for this account same way you can run the same command and here type the email address pipe apple so you can check properties for this particular user as well so like this you can verify the migration from powershell also so now the migration status is syncing earlier this was showing provision updating so this is changed to syncing for all five mailboxes cutover migration is a slow migration process though you can migrate 2000 mailboxes in one go to office 365 but this is recommended to add 100 mailboxes or 150 mailboxes in one batch because cut over migration will take time if you're going to migrate 2 000 mailboxes in one go and if migration is going to take time there will be delay or there will be down time for the on-premise mailboxes so once the migration batch is completed you can assign license for these users and click save like this you can assign license to all the users and after that you can go to public dns and you can modify the mx bracket as of now mx record is pointing to on-premise so we can modify this to office 365. for my domain mx bracket will be this one office 365 concept siphoncom.mail.protection.orglook.com and click save this is not saved properly so this is office 365 concept hyphen com dot mail dot protection.outlook.com click save and same way you can add cnn record as well for autodiscover profits365 it will be auto discover.outlook.com click save so the dns records are updated moreover you can add the spf record as well and once this is done you can go ahead and you can decommission your on premise section server so this is how you perform cutover migration from on premise to office 365 in the next video we will be talking about exchange hybrid deployment we will understand what is exchange hybrid deployment what are the components of exchange hybrid deployment we will talk about the different types of exchange hybrid deployment types and what benefits are provided by each deployment type of exchange hybrid so that is all for now i will see you all in the next video thank you guys thank you for your time take care

Channel: Office365Concepts

Views: 27,188

Keywords: migration, mailbox migration, what is cutover migration, staged migration, cutover migration, hybrid migration, what is staged migration, what is hybrid migration, how cutover migration works, how staged migration works, how hybrid migration works, cutover migration process, staged migration process, hybrid migration process, migrate onprem to office 365, migrate exchange server to office 365, mailbox migration step by step, how to, step by step, tutorials, videos

Id: 77yuocjjT84

Length: 26min 44sec (1604 seconds)

Published: Tue May 17 2022