Cloud Drive Mapper versions 2.0-2.6 used a built in Chromium browser. If app locker is present on the device, then this can sometimes block it from running, resulting in no drives being mapped.
The recommended solution to this is to upgrade to the latest version of Cloud Drive Mapper, which does not have this problem.
However if that option is not possible for some reason, this following advice will help overcome this issues with versions 2.0-2.6.
An exception needs to be added to the app locker policies to allow chromium to be run, however the process for doing this can vary between networks.
When searching the app locker logs results may show for either chromium64.exe, dotnetbrowser-chromium, browsercore or other similar phrases. Below are some of the possible locations that need to be allowed through.
CHROMIUM64.exe is usually stored in a TEMP folder within the users profile. EXE files within profiles are not always permitted. Either the exe can be allowed through, or the Publisher details meaning that only Chromium64.exe published by that vendor will be permitted.
If you need any assistance please do not hesitate to contact firstname.lastname@example.org