Deploying Cloud Drive Mapper (CDM)
The following video describes the essential steps for deploying CDM to multiple users and devices. This can be for a specific department or throughout your organization, on physical machines or virtual environments.
Prerequisites and compatibility
You can deploy CDM to multiple users and devices, in a specific department, throughout your organization, on physical machines, or in virtual environments. However, before you begin, ensure your environment meets its prerequisites.
Check that no firewalls, proxies, or web filters block CDM's traffic to Microsoft 365 or Bifrost (the IAM Cloud API). For more information, see Prerequisites and compatibility.
Granting admin consent to CDM
You might've already done this while setting up CDM for yourself. If not, see Granting admin consent to Cloud Drive Mapper (CDM) for more information, or if you already have Entra admin permissions, click here and follow the steps.
Mapping configurations
Complete your mapping configurations and settings in Iris by adding additional drives or updating the configuration for drives you've already added.
Getting a sign-off from testing and go-live planning
Before deploying CDM, we recommend you get a sign-off from testing and go-live planning to ensure that you've thoroughly validated CDM and that it meets your needs. Formal coordination with all stakeholders within your organization at this stage will help mitigate risks and ensure a smooth deployment process.
Deploying the installer specific to your environment
On the Downloads page, you'll notice that we've provided you with an EXE, MSI, and a packaged intunewin file. The MSI file is best for msiexec and GPO deployment and works well for other proprietary application deployment systems. The intunewin file is best for Microsoft Intune.
While you can theoretically use the MSI file in your VDI environment, we recommend using the EXE file for VDI and server deployments, as we've built additional VDI-specific controls in the EXE installer that might be helpful. Deploy the installer specific to your environment, including the license key, which you can deploy via GPO or Intune. For more information, see Deploying Cloud Drive Mapper (CDM).
Custom mapping groups and policy keys
Optionally, ensure that you've deployed any custom mapping groups and policy keys, which can either be embedded in the installer or deployed separately in the same way as your license key.
Once deployed, CDM will launch at startup – typically as part of the Windows startup programs or via a custom method if you've deployed CDM in a VDI environment.
Initially, CDM will attempt to authenticate a local user to their Microsoft 365 account. It uses the Microsoft Authentication Library (MSAL) to do this.
If you've set up Single Sign-on in your Microsoft 365 environment, CDM will attempt to authenticate the local user silently. Alternatively, CDM will display the standard Microsoft 365 login prompt if this isn't possible.
Contacting support
If you run into any issues, your trial comes with full support, so reach out to our help desk at support.iamcloud.com or by emailing support@iamcloud.com.
