Version 1.8 of OneDriveMapper will now automatically detect your OneDrive URL, instead of using your login name. This is useful in scenario’s where someone’s username changes. Microsoft does not change the OneDrive for business URL when the username changes, which would cause mappings made based on the login to fail. This often happened when IT staff changed a usename because a user got married.
The login detection and process has also been made more efficient, and broken driveletters are now automatically deleted.
I often hear customers who run an onpremises Exchange 2010 or 2013 environment in Hybrid mode with Office 365 complain about their Shared Mailboxes not appearing in Office 365 when using AADSync (or AADConnect).
This is important for mail routing if they don’t exist as contacts, or if you are using Exchange Online Protection for these mailboxes.
If you’re using OneDrive for Business to store a large amount of company and / or personal files, you’re like me.
And you’ve probably been frustrated running into issues using the OneDrive for Business client. It really hates it when you have over 5000 items in your account. This is annoying, because Microsoft gives us unlimited storage space in our OneDrive for Business account. But if you go over 5000, you’ll see an error message if you go into the library settings and the trouble starts.
OneDrive for Business may stop syncing files, or start eating 100% CPU capacity and simply not responding to anything. Files may never upload, or may end up in a cache where you will have no idea where it is.
Version 1.6 of OneDriveMapper will now persistently label your drive, previously it would not remember the label if the registry keys for this setting did not roam with your profile.
Thanks to Mark R, who reported the issue, the script can now also properly show popups requesting a password when run as a hidden window by Group Policy.