Cloud Drive Mapper 2.3.3
Following the major upgrades to our cookie and authentication systems in 2.2 and 2.3, this release has been able to capitalise on our improved integrations with Office 365. It sees the arrival of two new exciting features and a range of other smaller improvements. For the latest version of the Cloud Drive Mapper client, download it here.
Important note: Before your upgrade Cloud Drive Mapper across your IT infrastructure, we strongly recommend you to check our knowledge-base for updated documentation, and to briefly test the new client with a small subset of users before deployment. For this release, we specifically recommend you read this documentation on AAD permissions, and follow the instructions accordingly.
- Notifications will now pop-up when mapping process starts and finishes
- Admins now have the option to allow their users to manage their own drives in a UI (see documentation), the drive settings are stored in OD for persistence across machines.
- Teams Drive (see documentation). Our new converged drive for MS Teams. You can now map a drive that will contain all your users’ Teams libraries within a single drive letter.
- Ability to map a drive via an environment variable. For example, you would add [ENV:department] to the mapped URL e.g. https://example.sharepoint.com/[ENV:department]/Shared%20Documents – CDM would then pick-up the variable from the machine and interpret the full URL for the context of the given user.
- STA issue when loading UI from background thread
- Logic issue fixed with detecting permissions (referred to as “24-hour bug”) and moved to support 1000 sites.
- A bug that meant CDM was asking the user to log-in more often than required
- We have simplified the AzureApp for TeamSites by having an EnableAdvanceMode
- Auto-heal added when the permission context on the mapping process returns unauthenticated
- Improvements to the CPU usage and thread management to reduce lag on the UI screens