Cloud Drive Mapper now detect the username in AzureAD Domain Joined scenarios automatically

Issue where browser was suspending at a white screen when logging in has been resolved

An issue where the drive converge process failed when the name contained a non ASCII character has been resolved

An issue where the drive converge feature was failing due to non-handling of unexpected results from Graph has been resolved

A bug has been fixed where incorrect browser disposal was causing some memory leaks

An issue has been resolved where drives incorrectly registered as blocked and didn’t show correctly in File Explorer

Improvements:

We have implemented a new solution to better handle GraphAPI’s throttling that was occurring in customers with large numbers of users, and/or lots of SharePoint sites and libraries. This has notably increased the reliability that drives will correctly map. NB: For organizations with large numbers of users (>5,000) or SPO libraries (>50): this improvement may lead to a small delay mapping the drives on the first time Cloud Drive Mapper runs after you upgrade. On subsequent logins it will become significantly faster. Please note, this change will also disproportionately affect pilots/tests where the majority of your users are still using an older version. So the test will be slower than the live experience once all users are upgraded. This is because the overall throttling of the MS Graph API will have significantly reduced once you’ve upgraded to 2.4+

We have significantly improved caching to minimise the calls to Graph and speed up the startup process

We’ve upgraded to Chromium NETBrowser 1.21.0.0

Verbose mode now shows us browser logs for quicker and more in-depth response to issues

]]>changelog – June 2019https://www.iamcloud.com/changelog/june-2019/?utm_source=rss&utm_medium=rss&utm_campaign=june-2019
Wed, 19 Jun 2019 22:10:20 +0000https://www.iamcloud.com/changelog/may-2019-copy/Our June 2019 major release contains new features for Cloud Drive Mapper, including our new converged SharePoint Drive plus a number of bug fixes and improvements.

Cloud Drive Mapper 2.3.6

Following the success of our Teams Drive feature in 2.3.3, we’ve now developed a SharePoint Drive on the same basis. SharePoint Drive is a single drive letter that dynamically maps all of the SharePoint document libraries you’re permitted to access into it. For the latest version of the Cloud Drive Mapper client, download it here.

]]>changelog – May 2019https://www.iamcloud.com/changelog/may-2019/?utm_source=rss&utm_medium=rss&utm_campaign=may-2019
Fri, 31 May 2019 11:56:00 +0000https://www.iamcloud.com/changelog/late-april-2019-copy/Our May 2019 major release contains new features for Cloud Drive Mapper, including our new integration with MS Teams.

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.

Features:

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.

Bugs:

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

Improvements:

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

]]>changelog – late-April 2019https://www.iamcloud.com/changelog/late-april-2019/?utm_source=rss&utm_medium=rss&utm_campaign=late-april-2019
Mon, 29 Apr 2019 11:10:24 +0000https://www.iamcloud.com/changelog/april-2019-copy/Our late-April 2019 major release contains a number of bug fixes, new features and performance improvements to our authentication service and API.

Authentication Service (version 33)

This release of our Authentication Service and API is a major release and contains three months of improvements across a range of authentication features. This release has paralleled some important changes we’ve made to our Azure infrastructure following changes to Microsoft’s Azure Global Traffic Managers. In summary, we’ve redesigned the high-level topology of our cloud infrastructure to make better use of Azure’s GTMs in our A/B release process. Now this work is completed we expect to resume our 2 to 3-weekly sprint cycles.

This authentication release is a pre-cursor to a further major service upgrade of our password service scheduled to be released in 2 weeks.

Authentication Service

Bug fixes:

An issue when password reset link is showing but having trouble after returning

An issue preventing a number of users from accessing custom password reset interfaces have been resolved

An issue with IMAP has been resolved

An MFA issue where the internal IP is not preserved when detecting MFA on Outlook 2010 has been resolved

An issue with App ID saving on SSGUI has been resolved

An issue with a duplicate UI when resending SMS/Emails has been resolved

New Authentication Features:

ResetPasswordOnNextLogon is preserved and forces the user through the flow

Allow different UI per application

Support IP detection on SOAP requests from Office365 by using x-msclient-ip as an option to pass in

Public logs now being stored for authentication with relevant header information meaning all authentication requests are fully tracked without IIS Logs into our own persistent table storage

Full support for Multi-Language, detected by the accept-language header in browser request

April 2019 – Minor Release

Cloud Drive Mapper (version 2.3.1.1)

Cloud Drive Mapper 2.3 brought in a large number of improvements and a major upgrade to our authentication and cookie system. Cloud Drive Mapper 2.3.1.1 has some further enhancements and fixes for SharePoint permissions, and improved re-try logic for when Office 365 doesn’t successfully provide a refresh token when requested.

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.

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.

Fixed “<null>” issue when Office 365 failed to re-issue a refresh token during the ADAL process

Added ability to DisablePermissionCheck. This is a regkey which can be set to true/false. This is useful for cases whereby the customer is not able to grant permissions to Cloud Drive Mapper in Azure AD. By default the following behaviours when mapping SharePoint are as follows:

If it IsTrial and the key is not set it will NOT do permission check when mapping SP Lib

If it IsTrial and the key is set to False it WILL do the permission check when mapping SP Lib

Outside of trial either no key or it set to False WILL perform permission check when mapping SP Lib.

If the key is True it will NOT do perm check

We have fixed an install issue preventing MSI to roll-over previous release correctly

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.

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.

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.

Fixed bug when validating the username response from Microsoft if it had non standard characters.

Fixed bug when CDM attempted to un-map drives when the machine was shutting down

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.

Removed dependency on the user needing access to the root SharePoint site when mapping sub-sites or separate sites entirely.

Significantly reduced the number of logons required in non single-sign on environments.

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.

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.

]]>changelog – November 2018https://www.iamcloud.com/changelog/november-2018/?utm_source=rss&utm_medium=rss&utm_campaign=november-2018
Tue, 13 Nov 2018 12:11:51 +0000https://www.iamcloud.com/changelog/late-october-2018-copy/Our November 2018 release has a minor upgrade to Cloud Drive Mapper, to improve cookie handling and to enable the ability to force users to login to map their drives.

]]>changelog – Late October 2018https://www.iamcloud.com/changelog/late-october-2018/?utm_source=rss&utm_medium=rss&utm_campaign=late-october-2018
Mon, 29 Oct 2018 16:56:11 +0000https://www.iamcloud.com/changelog/early-october-2018-copy/Our Late-October 2018 release has a major upgrade to Cloud Drive Mapper, which now has full ADAL support, meaning it can now support MFA and SSO from pretty much any provider

]]>changelog – Early October 2018https://www.iamcloud.com/changelog/early-october-2018/?utm_source=rss&utm_medium=rss&utm_campaign=early-october-2018
Fri, 05 Oct 2018 16:44:52 +0000https://www.iamcloud.com/changelog/september-2018-copy/Our Early-October 2018 release has a range of performance enhancements to Cloud Drive Mapper including support for Azure AD MFA with ADFS and an entirely new cookie handling system to address stability issues with certain users.

Cloud Drive Mapper v2.0

A new cookie-management system. Responding to reports that some users were experiencing intermittent failures of drive mapping, we discovered some issues affecting Office 365 cookies. These issues were happening outside of Cloud Drive Mapper, so there was no immediate remediation possible. Instead we rebuilt Cloud Drive Mapper’s cookie handling system to monitor and manage the cookies in real-time to ensure we eliminated the issues for users.