Issues with OneDrive post migration

I've seen this discussed a couple different times but have not seen a resolutions…..does anyone have a fool proof way to QMM process a profile (CCU) which will properly updates OneDrive for use post Migration. (I imagine BT has the same challenges) 

Post migration with CCU, OneDrive tries to reestablish its connection but fails with Access Denied type errors. Seems the root of the issue is that the non-synced on-demand junction files do not process by vmover and so the owner is not changed properly. IF you force Ownership through Windows Explorer post migration then OneDrive starts working.

 Support even has an article saying OneDrive is not supported and there is an enhancement request open.

 I was able to make this work with one customer where we forced 20 seconds of a full Sync of OneDrive by changing the registry, re-launching OneDrive, pausing for 20 seconds then killing OneDrive and letting vmover run but this isn’t working for another customer.

 Forcing all OneDrive to sync before migration might solve this but it might also cause issues on the desktopswith diskspace .

  • Does AD Pro handle these issue better?
  • Do we know if any enhancements have been logged to have the products handle all the various Office challenges properly instead of piecing together scripts
  • Do these same challenges happen with BT re-acl?


  • Based on the information provided, it appears that there are challenges with using Quest Migration Manager (QMM) to properly update OneDrive for use post-migration. OneDrive tries to reestablish its connection but fails with Access Denied errors, which may be related to non-synced on-demand junction files that are not processed by vmover, resulting in the owner not being changed properly.

    According to the support article provided, OneDrive for Business is not currently supported by QMM resource processing. Therefore, it may be challenging to find a foolproof way to process a profile (CCU) that will properly update OneDrive for use post-migration using QMM.

    Regarding AD Pro, it is unclear if this product handles these issues better or if any enhancements have been made to address these challenges. It may be worth contacting the vendor or researching further to determine if AD Pro is a suitable solution for the specific migration requirements and challenges.

    It is also unclear if these same challenges happen with Binary Tree re-acl. It may be worth investigating further or reaching out to the vendor for clarification on their product's support for OneDrive for Business migration.