Key differences

	CDM (Legacy)	CDM (V3)
Configuration & management	Our legacy admin portal (https://portal.iamcloud.net) was deprovisioned earlier this year.	CDM (V3) users get instant access to our new admin portal, Iris. Iris makes creating and managing even highly customized configurations quick and easy.
Licensing	In CDM (Legacy), each mapping group has its own license key, which binds users to their drive settings.	In CDM (V3), your software license key is associated with your organization. The same key applies to all users within your organization and has no impact on your mapping groups or drive settings within your mapping groups.
License key	Your existing CDM Legacy license key will only work on version 2.x. Additionally, the registry value name for the v2.x license key is LicenceKey.	CDM (V3) comes with its own license key. You can’t use your existing v2.x license key for CDM (V3). The registry value name for the CDM (V3) license key is LicenseKey.
Folder redirection	In CDM (Legacy), folder redirection can only be implemented using a bitmask-style registry key.	In CDM (V3), you can enable the folder redirection policy for a Direct: OneDrive mapping via Iris, then deploy it via your deployment orchestration method.
Advanced controls	In CDM (Legacy), advanced controls are configured via a bitmask-style registry key.	With CDM (V3), you can easily configure sophisticated controls, also known as policies, via the new Iris portal before passing them on to the CDM client via your deployment orchestration method.
Advanced drive settings	In CDM (Legacy), advanced drive settings for Converged drives are configured via a bitmask-style registry key called ListConvergeSettings.	With CDM (V3), you can easily configure advanced drive settings for Dynamic drives (formerly Converged drives) via Iris.
Local AppData folder reset	In CDM Legacy, resolving authentication or configuration issues meant rebuilding the Local AppData folder (%localappdata%\IAM Cloud\CloudDriveMapper).	This is no longer necessary or recommended in CDM (V3), as doing so can slow the startup flow, interfere with roaming support and throttling prevention, and cause potential data loss between sessions. You should only do this if and when instructed by a member of our support team.

Configuration & management

Our legacy admin portal (https://portal.iamcloud.net) was deprovisioned earlier this year.

CDM (V3) users get instant access to our new admin portal, Iris. Iris makes creating and managing even highly customized configurations quick and easy.

Licensing

In CDM (Legacy), each mapping group has its own license key, which binds users to their drive settings.

In CDM (V3), your software license key is associated with your organization. The same key applies to all users within your organization and has no impact on your mapping groups or drive settings within your mapping groups.

License key

Your existing CDM Legacy license key will only work on version 2.x. Additionally, the registry value name for the v2.x license key is LicenceKey.

CDM (V3) comes with its own license key. You can’t use your existing v2.x license key for CDM (V3). The registry value name for the CDM (V3) license key is LicenseKey.

Folder redirection

In CDM (Legacy), folder redirection can only be implemented using a bitmask-style registry key.

In CDM (V3), you can enable the folder redirection policy for a Direct: OneDrive mapping via Iris, then deploy it via your deployment orchestration method.

Advanced controls

In CDM (Legacy), advanced controls are configured via a bitmask-style registry key.

With CDM (V3), you can easily configure sophisticated controls, also known as policies, via the new Iris portal before passing them on to the CDM client via your deployment orchestration method.

Advanced drive settings

In CDM (Legacy), advanced drive settings for Converged drives are configured via a bitmask-style registry key called ListConvergeSettings.

With CDM (V3), you can easily configure advanced drive settings for Dynamic drives (formerly Converged drives) via Iris.

Local AppData folder reset

In CDM Legacy, resolving authentication or configuration issues meant rebuilding the Local AppData folder (%localappdata%\IAM Cloud\CloudDriveMapper).

This is no longer necessary or recommended in CDM (V3), as doing so can slow the startup flow, interfere with roaming support and throttling prevention, and cause potential data loss between sessions. You should only do this if and when instructed by a member of our support team.