How to obtain Cloud Driver Mapper error logs for troubleshooting - V2 Print

Enabling error logs:

If Cloud Drive Mapper is failing to map a drive then the cause of this can usually be found by examining the error logs when verbose logging mode is enabled. CDM will need to be closed, then logs enabled, then once its started again the log file will be generated.

Note: If you are on version 2.8 or below then please contact support@iamcloud.com for details on verbose logging. 

In order to enable verbose logging mode close CDM, then add the registry key MasterSettings = 32 either via a CMD prompt (please note it cannot be run from an elevated command prompt as it needs to be run in the end user context) or by manually creating it in one of the following hives. The key type is a string value / REG_SZ:

Computer\HKEY_CURRENT_USER\Software\IAM Cloud\CloudDriveMapper - recommended to add here

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\IAM Cloud\CloudDriveMapper

To add via CDM prompt:

reg add "hkcu\software\iam cloud\clouddrivemapper" /v "mastersettings" /t "REG_SZ" /d "32" /f

Please note: If you have an existing value in MasterSettings, then you will need add the value of 32 to that, further details can be found here.

In this case the log will be written to the users %localappdata% (AppData\Local\IAM Cloud\CloudDriveMapper\log) and will create a new daily log file if left running, this keeps the log file to a reasonable size and is easier to work with.

Alternatively a specific log location can be set, however if left enabled this will cause the log file to continue to grow size and is difficult to work with. 

To add via CMD prompt:

reg add "hkcu\software\iam cloud\clouddrivemapper" /v "WritelogToFile" /t "REG_SZ" /d "C:\ExampleFolder\Log\cdmlog.txt" /f

Or it can be added manually to:

Computer\HKEY_CURRENT_USER\Software\IAM Cloud\CloudDriveMapper - recommended to add here

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\IAM Cloud\CloudDriveMapper

String value = WritelogToFile with value of location where you want the log file to save to, for example C:\Users\auser\desktop\cdmlog.txt

Please note - if you were previously using version 2.8.10.1 or below and have WriteLogToFile set with the value of true in the registry, then this will prevent logs from writing when mastersettings = 32 is set as a key. WriteLogToFile = true will need to be deleted for the logs to generate.

Acquiring error logs:

Once the registry keys have been added, reload CDM and it will generate the log file in the specified location. This can then be sent to IAM Cloud support for analysis.

Please note, if using a specified file location, we recommend to disable verbose logging once you have the logs as it will continue to populate the .txt file with data when CDM is running.

You can do this by removing the entries in the registry. 

In application logs:

Using the Control (CTRL) key and right clicking on CDM in the icon tray, it now brings up the ability to have direct access to logging options. This option can be disabled using the DisableUserLogMenu key.

You will first be prompted to enable logs as per the below screenshot. Choose the middle option (requires CDM restart). For troubleshooting, safe logs are required. Once CDM is restarted these will be generated in  %localappdata% (AppData\Local\IAM Cloud\CloudDriveMapper\log)

Logging can then be disabled from the same menu.

Acquiring logs for deployment via MS Endpoint Manager (formerly Intune)

Cloud Drive Mapper can be deployed via MS Endpoint Manager, details can be found in our guide here. If this process has either failed to deploy the msi or any of the required registry settings, then the log file can be obtained from:

C:\ProgramData\Microsoft\IntuneManagementExtension\Logs

If you need any assistance please do not hesitate to contact support@iamcloud.com