If you follow the posts from Polina, not eta for the new logic/script (or whatever it will be)... ![🤷♂️]()
Only way right now, stop and disable job/schedule and then run the script with the move-vboentitiy cmdlets. It's working this way okeyish... Sometimes there are a few issues... Anotherthing I noticed sometimes there are groups moved, with the groups the member mailboxes are moved ,likewise in the backup there is a dependency... Afterwards when the user is moved (or vice versa) the move job generate a warning because either the object is currently still moved or it might be finished moving I ln the other move job and then it's complaining it doesn't find the object any more...
One more thing I did, after the move Jobe finished , I manually checked the jet repo with the get-vboentity cmdlets to see if there are any objects left in the repo! Happened once or twice that some objects where still in the jet according to the cmdlets..
Another important thing, don't run the job unless all move jobs are finished!
Also check the issue that arise with using the cmd, right now the moved restore points are not displaying in the (web) restore Portal...
Only way right now, stop and disable job/schedule and then run the script with the move-vboentitiy cmdlets. It's working this way okeyish... Sometimes there are a few issues... Anotherthing I noticed sometimes there are groups moved, with the groups the member mailboxes are moved ,likewise in the backup there is a dependency... Afterwards when the user is moved (or vice versa) the move job generate a warning because either the object is currently still moved or it might be finished moving I ln the other move job and then it's complaining it doesn't find the object any more...
One more thing I did, after the move Jobe finished , I manually checked the jet repo with the get-vboentity cmdlets to see if there are any objects left in the repo! Happened once or twice that some objects where still in the jet according to the cmdlets..
Another important thing, don't run the job unless all move jobs are finished!
Also check the issue that arise with using the cmd, right now the moved restore points are not displaying in the (web) restore Portal...
Statistics: Posted by DaStivi — Apr 06, 2025 7:51 am
