This is a guide on how to deploy Cloud Drive Mapper (CDM) to devices via Microsoft Endpoint Manager, this can be easily deployed via Intune, and allows for simple integration into your Microsoft 365 environment.


To set this up you will need to download the CDM.msi here. Once this has been downloaded you will also need the IntuneWinAppUtil.exe which can be found here.

Once you have both of these downloaded, run the Util Tool. You will see the below:

From here, simply select the folder where the Cloud Drive Mapper.msi is and then specify the exe itself, then choose the output folder (i.e. where you want the Intune package to be)

Once this runs it will create an .intunewin version of the installer, this can then be used in the next step to create the app deployment.


Intune App Creation

Access your Intune environment and go to “Apps” > “All Apps” and select Add

It will them prompt to select an App Type, select “Windows App (Win32)”

From there select the app package file, this is the .intunewin file created in the first section of this guide.

From there fill in the information required and choose next.

Under “Program” settings select your preferred install behaviour. You can leave this as default if you have no preference.

The next section is specifying the minimum requirements of the machines the app will be deployed to, attune this to your environment and then select “Next”.

Under “Detection rules” you need to specify the conditions in which the app will deploy. One way to do this is to determine if the file is already installed, if it is then the app will not try to deploy, if it isn’t then the app will attempt to install.

Under “Rules format” select “Manually configure detection rules”, then select Add and use the below settings:

Simply make sure the “Value” field matches the version of Cloud Drive Mapper you are deploying


The next step of the deployment setup covers “dependencies”, feel free to skip this as Cloud Drive Mapper requires no pre-existing software to be installed.

You can also skip the Supersedence step as well.

The final step of the app setup is determining which user groups/devices the app will be deployed to, simply select the AAD user group you wish this to be deployed to or alternatively select “all devices” as a cover-all.

Once this is configured you should see the CDM app in the list of Apps within Intune, Intune will then attempt an installation after a short period of time.


Intune Script Deployment

The next step is to deploy the script we created that will add the registry keys that Cloud Drive Mapper will require, this will run in tandem with the app installation and then allow the app to deploy, install and licence without any need for intervention.


To do this you will first need to acquire the script which can be downloaded from here:

First the script defines your current execution policy and stores it as a variable, this means we can revert this back at the end of the script as the policy may need to be changed to allow the script to run without admin credentials.

The main section of the script creates the Registry keys for Cloud Drive Mapper within the HKEY_CURRENT_USER key.

The 2 keys present are standard, you can add any more relevant setting in this section of the script, to see a full list please click here

You will need to substitute the "LIC KEY (variable)" value with your CDM Licence key


Once this has been amended to include your licence key and any additional keys required save the script and then open your Intune management portal.


Navigate to “Devices” and then “Scripts”


Select “Add” > “Windows 10”


The first screen is simply naming the script package and adds the option to include a brief description of what the script does for future reference. 


Click “Next”


The next section is where you import the script itself, simply select this from where you saved the .ps1 file


Also make sure you select the script to run as the logged-on user and NOT the system:




Click “Next”

The final step is to determine who the script package is assigned to. It is strongly recommended to assign this to a user group rather than specific devices as this can create issues if the same device is used by multiple staff.

Click “Next” and review your settings and click “Save”

The script will now deploy to the assigned groups, this can take some time, if you need this deployed as quickly as possible one way to speed this up is to restart the “Microsoft Intune Management Extension” on the target device.

Updating the App via Intune 

The Cloud Drive Mapper will be updated as we add more features, you can update your existing installation of Cloud Drive Mapper by following the below steps.

The first step is to download the latest version of Cloud Drive Mapper, this can always be found here

Secondly, you will need to create the .intunewin package as per normal deployment, the steps to do this are outline under the “Prerequisites” section of this article.

Once this is created navigate to your O365 Endpoint Management console and got to “Apps” > “All Apps”. Open the existing Cloud Drive Mapper App, open “Properties” and select “edit” next to “App Information”.

Next to “Select file to update” you should see your current .intunewin file, click the link and navigate to where you have stored the updated .intunewin file.

This will replace the existing package with the new one, make a note of the new version number in the “App Version” field.

The next step is to navigate to “Detection Rules” and you should see the current detection rule listed, simply click the path and it will open the settings.

From here just update the version number to the new version and select “Review + save”

Intune will now do a check to all user groups/devices Cloud Drive Mapper is assigned to and detect that the current version is now outdated, it will then uninstall the old version and install the new version without any user intervention required.

Please note that, once installed, the application will have to be manually started the first time (Start Menu > Cloud Drive Mapper) or it will auto-run upon the machine being restarted. This is only the case upon the program being initially installed.