If you have read my previous post: Connect to All PowerShell Modules in O365 with one script<\/a><\/em><\/strong>
You should have all the settings needed to connect your PowerShell to O365. Note in this scenario, that all these cmdlets will be run from O365 PowerShell and will be monitored from O365 by either PowerShell or the Exchange Admin Center. You will not be able to monitor the moves from On-Premises.<\/p>\n\n\n\n
2. Provide your on premises Migration Administrator credentials as a variable for your cmdlet.<\/strong><\/p>\n\n\n 3.\u00a0Move\u00a0a\u00a0single\u00a0mailbox.<\/strong> Now with all migration projects, we expect to have to move multiple mailboxes in a single batch. The following will show the process for moving mailboxes in bulk from on premises to O365:<\/p>\n\n\n\n 1.\u00a0Connect\u00a0to\u00a0Exchange\u00a0Online\u00a0via\u00a0PowerShell<\/strong> 2. Provide your on premises Migration Administrator credentials as a variable for your cmdlet.<\/strong><\/p>\n\n\n 3.\u00a0Move\u00a0multiple\u00a0mailboxes in a single batch.<\/strong> Next you initiate the mailbox moves. When specifying the mailbox identity in the cmdlet, use the respective header in your variable declaration (either $user.EMailAddress<\/strong> OR $user.Alias<\/strong>) References:<\/em><\/strong> As many of you have knowledge, I am studying for my MS-202 Exam. And, part of the knowledge needed is to be<\/p>\n$OnPremCred = Get-Credential -Message \"Enter the On Premises Exchange Migration Admin account creds\"<\/pre>\n\n\n\n
In your hybrid configuration you should be doing directory sync with O365\/Azure and the accounts should be available in the cloud showing that they are synced with AD. This also assumes that you have your MRS Proxy endpoint enabled, which can be done by the HCW. Also, make sure you have your licensing available for your mailboxes. From my knowledge, you can assign your license to the account in the cloud before moving, especially if you have a particular license that you need to assign the account. Other than that, moving the mailbox will assign an existing license that is available that includes an Exchange Online mailbox feature when the mailbox is moved.
Now we initiate the move with the cmdlet. Similar to what you would do in the GUI, this simple mailbox move cmdlet initiates the move request. It has most of the same parameters as a local move request including BadItemLimit, LargeItemLimit, AcceptLargeDataLoss, etc…
\u00a0
Use the following LINK<\/a><\/strong><\/em>\u00a0for\u00a0documentation\u00a0on\u00a0the\u00a0New-MoveRequest\u00a0<\/strong>cmdlet.<\/p>\n\n\n#Set the identity of the mailbox being moved\n$user = Read-Host \"Enter the alias or E-Mail Address of the user being migrated: \"\n\n#Next Run the cmdlet for the New Mailbox Move Request\nNew-MoveRequest -Identity $user -remote -RemoteHostName (hybridURL) -TargetDeliveryDomain companyname.mail.onmicrosoft.com -RemoteCredential $OnPremCred -AcceptLargeDataLoss -BadItemLimit 500 -LargeItemLimit 100 -BatchName \"$user Mailbox Move to O365\"\n\n#Get the status of the mailbox move to completion\nGet-MoveRequest | ? {$_.alias -eq \"$user\"} | Get-MoveRequestStatistics | fl\n<\/pre>\n\n\n\n
If you have read my previous post: Connect to All PowerShell Modules in O365 with one script<\/a><\/em><\/strong>
You should have all the settings needed to connect your PowerShell to O365. Note in this scenario, that all these cmdlets will be run from O365 PowerShell and will be monitored from O365 by either PowerShell or the Exchange Admin Center. You will not be able to monitor the moves from On-Premises.<\/p>\n\n\n\n$OnPremCred = Get-Credential -Message \"Enter the On Premises Exchange Migration Admin account creds\"<\/pre>\n\n\n\n
In your hybrid configuration you should be doing directory sync with O365\/Azure and the accounts should be available in the cloud showing that they are synced with AD. This also assumes that you have your MRS Proxy endpoint enabled, which can be done by the HCW. Also, make sure you have your licensing available for your mailboxes. From my knowledge, you can assign your license to the account in the cloud before moving, especially if you have a particular license that you need to assign the account. Other than that, moving the mailbox will assign an existing license that is available that includes an Exchange Online mailbox feature when the mailbox is moved.
This time you want to create a CSV file using the alias or emailaddress<\/em> as your header and then list the appropriate value for all the users in your batch group. Save the file locally as MigrationBatch01.csv\u00a0<\/em>or\u00a0a\u00a0name\u00a0of\u00a0your\u00a0choice.
<\/p>\n\n\n\n![\"\"](\"http:\/\/itblog.ldlnet.net\/wp-content\/uploads\/2019\/02\/CSVCreation.png\")
\u00a0OR<\/strong>
\u00a0<\/strong>Alias\u00a0as\u00a0the\u00a0header<\/figcaption><\/figure><\/div>\n\n\n\n
Use the following LINK<\/a><\/strong><\/em>\u00a0for\u00a0documentation\u00a0on\u00a0the\u00a0New-MoveRequest\u00a0<\/strong>cmdlet. <\/p>\n\n\n#Import the CSV into the variable state\n$mailboxes = Import-CSV C:\\Migration\\MigrationBatch01.csv\n\n#Next Run the cmdlet for the New Mailbox Move Request to move each mailbox\nforeach ($user in $mailboxes) { New-MoveRequest -Identity $user.EMailAddress -remote -RemoteHostName (hybridURL) -TargetDeliveryDomain companyname.mail.onmicrosoft.com -RemoteCredential $OnPremCred -AcceptLargeDataLoss -BadItemLimit 500 -LargeItemLimit 100 -BatchName \"Migration Batch 01 Moves to O365\" }\n\n#Get the status of the mailbox moves in the batch to completion\nGet-MoveRequest | ? {$_.batchname -like \"Migration Batch 01 Moves to O365\"} | Get-MoveRequestStatistics | ft -a -wr\n<\/pre>\n\n\n\nGOOD LUCK WITH YOUR MIGRATIONS!
HAPPY TROUBLESHOOTING!<\/h2>\n\n\n\n
Moving Individual Mailboxes to O365<\/a><\/strong>
Move Mailboxes in Bulk to O365<\/a><\/strong>
PowerShell Mailbox Migration to O365<\/a><\/strong>
Connect to all PowerShell Modules in O365 with one script<\/a><\/strong>
New-MoveRequest Microsoft Document<\/a><\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"