Forum Discussion
"NeedsApproval"
Hi All, So I have been migrating mailboxes from onprem to O365 in the hybrid config with no issues. Today I have two migration batch jobs that state "NeedsApproval", but everything migrated. Kind ...
Hi LED04,
We found that the "NeedsApproval" was not linked to a person, but a time when the migration would occur. For us, this was 11.30 PM every night. If we left it until this time, it would migrate at this time and show as Completed. For us, though we wanted to kick off the migration sooner, so we changed the migration time and it progressed.
I am unsure if we used PowerShell or through the GUI, but it showed as completed after this 🙂
Hope this helps!
We found that the "NeedsApproval" was not linked to a person, but a time when the migration would occur. For us, this was 11.30 PM every night. If we left it until this time, it would migrate at this time and show as Completed. For us, though we wanted to kick off the migration sooner, so we changed the migration time and it progressed.
I am unsure if we used PowerShell or through the GUI, but it showed as completed after this 🙂
Hope this helps!
I am really fedup of this "Need approval" thing almost on each batch. It is adding no value but eating time on each migration batch/moverequest. I am seeing this even when there are no Corrupt items on move request.
I have been working on migrations since decades and never seen such pathetic experience dealing with this "NEED APPROVAL" even no such bad experience when fixed many failed migration issues.
It became worst when I try to fix it through many appreciable solutions provided by community members, but it kicks out the commands with the below error:
Set-MoveRequest -Identity "Emailid" -SkippedItemApprovalTime $(Get-Date).ToUniversalTime()
Set-MoveRequest -identity "Emailid" -SuspendWhenReadyToComplete $False -PreventCompletion $False -CompleteAfter $CompletionDateTime
WARNING: The request is currently being managed as a part of a migration batch. Changes to the request may be overwritten by the Migration Service or could impact the status expressed by the migration batch or migration user.
WARNING: The command completed successfully but no settings of 'DB#GBRPxxxG002-dbxxxxxxxxxxx' have been modified.
WARNING: The request is currently being managed as a part of a migration batch. Changes to the request may be overwritten by the Migration Service or could impact the status expressed by the migration batch or migration user.is there a way I can Disable this Feature on the Migration Batches and make sure it will not eat unnecessary time on migration Completion?
