Mass deploying Cloud Drive Mapper (CDM)

Mass implementation of CDM is a two-step process that entails deploying the license key and then the software. Depending on your environment, you can deploy the CDM license key via Group Policy or Microsoft Intune and the software via Group Policy, Command-line Interface (msiexec), or Microsoft Intune. To mass deploy CDM via Group Policy, you must deploy the license key first.

License key deployment

• Deploying the license key for users via Group Policy

• Deploying the license key for computers via Group Policy

• Deploying the license key via Microsoft Intune

Software deployment

• Deploying CDM via Group Policy

• Deploying CDM via Command-line Interface (msiexec)

• Deploying CDM via Microsoft Intune

During installation, we establish communication between our service running on the host and the CDM component users see in the system tray. We add an entry to the Windows Firewall and target it to our specific application and the remote address of its local subnet. In doing so, we ensure that this doesn’t add any additional exposure from the external network or interfere with existing firewall rules.

When you use a silent proxy or firewall to protect local communication between services on the same host, you’ll need to permit CDMCore.exe (from within the installation path) to communicate with CloudDriveMapper.exe in the same location.

CDM uses the gRPC protocol and will work on ports 50000-50100 by default. These are configurable start and end ports. The range in ports is because we have several interfaces, and each user session concurrently consumes a unique port within this range. Other software operating within this range is detected and ignored to prevent interference.