changelog – March 2019

By November 29, 2018changelog

March 2019 – Major Release

Cloud Drive Mapper (version 2.3)

We are really excited to announce the release of Cloud Drive Mapper 2.3. It has been a long time coming but the 2.3 release represents a major step forwards for Cloud Drive Mapper. This upgrade sees an array of significant improvements to the product as well as a completely re-built authentication and cookie-handling system. It provides a significantly more stable experience for all users, and completely eliminates a large number of edge-case scenarios that can affect the mapped drives’ persistence.

IMPORTANT NOTICE FOR ALL CLOUD DRIVE MAPPER CUSTOMERS: For existing customers who are upgrading from Cloud Drive Mapper 2.1 or below, as well as customers completely new to CDM, there is one small but very important one-off process that is required to implement Cloud Drive Mapper 2.3 and above. It involves registering the CDM client with Azure AD and granting your users’ permissions to access it.

Please read this step-by-step guide on how to grant AAD permissions before you upgrade.

IMPORTANT NOTICE FOR CUSTOMERS USING ADFS FOR OFFICE 356 SSO: Cloud Drive Mapper 2.3 now uses Chromium (the Chrome browser engine) as part of its authentication and cookie-handling system. In order for Cloud Drive Mapper to work with Single Sign-On via ADFS, you will need to have enabled support for the Chrome browser.

If you haven’t already enabled SSO for Chrome in ADFS, please read this quick guide on how to do it. 

Download the latest version of Cloud Drive Mapper (EXE/MSI) from our Resource Center (but please read the important notices above first)

 

Improvements in version 2.3

  1. Fixed bug when Cloud Drive Mapper tried to auto fix generic cookie issues, causing a fatal exception.
  2. Cloud Drive Mapper now validates permissions using the graph token, which brings a range of immediate and future improvements, including improving scenarios where CDM would map drives the user does not have access too.
  3. Fixed bug when validating the username response from Microsoft if it had non standard characters.
  4. Fixed bug when CDM attempted to un-map drives when the machine was shutting down
  5. Improved logging for diagnosing complex issues and added more knowledge base article references to the logs to provide administrators more information to self-diagnose issues.
  6. Improvements to the longevity cookie validation process to better ensure drives remain accessible whilst CDM is running.
  7. Removed dependency on the user needing access to the root SharePoint site when mapping sub-sites or separate sites entirely.
  8. Significantly reduced the number of logons required in non single-sign on environments.
  9. Improvements to OneDrive deep linking, including a bug-fix when using deep linking in conjunction with folder redirection which caused duplication of the folder structure in OneDrive.
  10. Significantly improved how the cookies are generated and handled by moving to Chromium WebKit

The greatest change in the list above is item 10, the integration with Chromium, represents the biggest change, and is where most customers will see major improvements to the reliability and persistence of CDM’s mapped drives.

2.3 is the biggest release we’ve ever done for Cloud Drive Mapper, and what is particularly important about this release is that it brings CDM in-line with Microsoft’s most recent standards/recommendations for working with Office 365. This opens the door to some very exciting new features that will be coming in the next few weeks and months.