Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Sunday, September 24, 2017 7:35 PM
We are moving mailboxes to EXO. Some the mailboxes fail with errors that force me to remove the migration user job and add a new one. I would like to add the new one to the existing migration batch. Is that possible?
For the new-migrationbatch cmdlet there are switches called userIDs and Users that the documentation says can be used to add migrationusers from other batches to the new batch, but I can't figure out how to get it to work. Has anyone gotten that to work?
All replies (11)
Tuesday, September 26, 2017 8:23 AM ✅Answered | 1 vote
Hi Matt,
I did some test on my labs and it works to use the UserIds and DisableOnCopy parameters with New-MigrationBatch to pull the mailboxes to the new batch from old batches. Here is the cmdlet I used to work.
New-MigrationBatch -Name TestBatch4 -UserIds [email protected],[email protected] -DisableOnCopy
After the batch is created, I can manually start it. As is shown in the screenshot, the mailboxes in the new batch is being migrated as normal.
To my experience, when a migration batch failed, we usually narrow down the root cause, fix the issue and then resume the migration batch for the failed mailboxes, or delete the failed batch and create a new one for the failed mailbox to do the job again.
Regards,
Alex Sun
Please remember to mark the replies as an answer if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Monday, September 25, 2017 5:34 AM
Hi
Get in detail here : https://technet.microsoft.com/en-us/library/jj898488(v=exchg.150).aspx
Regards,
Raj
________________________________________________________________________________
Please mark as an "Answer" and do "Vote",if my contribution or answer is useful
Monday, September 25, 2017 5:07 PM
Thank you. I understand the migration Batches can be managed in the EAC, but there is no way to add a user to an existing Migration Batch that way that I see. I'm asking specifically if there is any way to add a user to a existing migration batch. Documentation for the new-migrationbatch cmdlet states there are switches called userIDs and Users that can be used to do that, but I can't get it to work. Has anyone gotten that to work?
Tuesday, September 26, 2017 5:21 AM
Hi Matt
I'm not sure run following command.
New-MigrationBatch –Local –Name LocalMove3 CSVData ([System.IO.File]::ReadAllBytes(“C:Usersxxx.xxx.csv”)) –TargetDatabase Database12013 -Autostart -AutoComplete
Regards,
Raj
________________________________________________________________________________
Please mark as an "Answer" and do "Vote",if my contribution or answer is useful
Tuesday, September 26, 2017 6:32 AM | 1 vote
Thank you for responding. I'm looking to add users to an existing batch, not create a new batch with users.
Tuesday, September 26, 2017 7:36 AM
Hi
I suppose its not possible
Regards,
Raj
________________________________________________________________________________
Please mark as an "Answer" and do "Vote",if my contribution or answer is useful
Tuesday, September 26, 2017 4:21 PM
That's awesome to hear that work for you, for someone. I tried the UserIDs and Users switches before to bring in users in other batches, but it didn't work. I tried with Identity and migrationUser GUID. I did not try with the DisableOnCopy switch, and it may be that the error I got didn't like the parameter set I used. Now that I look at your cmdlet it may not have liked the autostart switch I had.
Tuesday, September 26, 2017 8:33 PM
I was able to add existing migrationusers to a new batch using cmdlet below, but they don’t actually show in the new batch even though it says it has 2 users. It may be linking back to them in the original batch where they are still reported to be, where their status is stopped. I don't understand what's happening with that.
New-MigrationBatch -Name "Batch_Test2" -userids $mv -DisableOnCopy -AutoStart
Friday, September 29, 2017 11:40 AM | 1 vote
Hi Matt,
I tried your command and it worked for me. The on-premises mailboxes are added to the batch and it starts automatically, and the mailboxes is moved to cloud successfully.
Back to your issue, are the mailboxes visible several minutes after the batch starts automatically? Do you have any error reports from the batch? Have they been moved to the cloud if you go back to the Recipients-> Mailboxes? It would be better for understanding if you could provide some screenshots.
Regards,
Alex Sun
Please remember to mark the replies as an answer if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Tuesday, October 3, 2017 1:46 PM
For my previous test, the Migrationusers always were visible in the original batch, even though the new one said it had 2, they never showed if you did a get-MigrationUser for that batchID. There were no error reports in the batch. I haven't had a chance to test anymore. I may try again over the next week. If I do I'll provide more detail or images.
Tuesday, October 3, 2017 11:01 PM
I was able to do another test, and it worked! The real test was to see that the original moveRequest stayed intact and was used for the move, rather than creating a new one and having to sync everything again. It appears that did happen, so that appears to solve my problem, and answer my questions. I'm going to test again with a larger production batch before marking it answered. Thank you!