V3.24 of OnedriveMapper is now available for download.
After months of beta-testing, no issues have been reported. Therefore, v5.07 of OnedriveMapper is now live.
The only change from v5.06 is that it now automatically updates the msEdge driver when the user has sufficient permissions.
You can now download and test OnedriveMapper 5, fully based on Edge and without any dependencies on Internet Explorer (to be deprecated August 17).
Installation instructions for V5 have already been updated on the OnedriveMapper page.
This August, the 17th to be precise, Microsoft 365 will stop supporting IE 11.
As OnedriveMapper 4.X uses Internet Explorer under the hood, there is a chance that functionality will break.
As Microsoft does not intend to actively block IE 11, there may be some lag until users actually begin experiencing issues with OnedriveMapper 4, and V3 may also continue to work properly as it does not use IE (in native mode).
But to ensure continuity I’ve begun testing with OnedriveMapper 5 using the Edge Webdriver and the WebView2 component.
I’m aiming to release an ‘Edge’ (Chromium) version of OnedriveMapper before August so you have ample time to test and upgrade. As always, this update will be free / open source.
ODM 5 will require Edge Chromium to be present on your endpoints.
Version 4.04 OnedriveMapper now automatically reconnects drives (of any type) when the cookie expires. No more ‘broken’ mappings! The script is smart enough to detect if its just a connectivity issue (= do nothing) or an actual drive issue.
All improvements since 4.00: