Cloud Drive Mapper ( CDM ) is fully compatible within Citrix / RDSH environments and can be deployed relatively easily.
Follow link to see a short demo video of CDM within a Citrix environment, link here.
- Cloud Drive Mapper Licence Key ( Obtained via IAM Cloud Portal / Support Team )
- At least .net 4.6.2
- Webclient Service installed and running
- *.sharepoint.com within Trusted Internet Zone
On shared servers where multiple users run sessions at the same time
( Desktop Sessions / App Sessions ) then the following reg key is required within HKLM :-
MultipleInstanceOveride = true
REG ADD "HKLM\Software\IAM Cloud\CloudDriveMapper" /v "MultipleInstanceOveride" /t "REG_SZ" /d "true " /f
Installation of CDM
Download the msi from here
The MSI can be pushed via MSIExec / GPO / SCCM etc in the same manner as any other MSI installer.
No special keys need to be pushed with the msi.
Below is an example of the MSIExec install :-
msiexec /i "\\dc01\software\CDM\SetupCDMx64.msi" ALLUSERS=2 /qn
Once installed check the following location and delete any entries for Cloud Drive Mapper as we will need to start CDM as described further down.
If CDM is to be run on older systems you may also have to take the steps below( If applicable ) :-
a) Change startup type of wuauserv to automatic ( if it’s not running)
b) Install Windows6.1-KB2846960-x64.msu (If this affects you, you may receive an error when opening a SharePoint Document Library in Windows Explorer or map a network drive to the library after you install Internet Explorer 10 in Windows 7 or Windows Server 2008 R2 )
We have seen isolated faults here whereby the end user session wasn’t able to see the above key, a resolution to this was as follows:-
Registry Permissions: If the registry permissions on HKLM\Software\IAM Cloud were set to “Read” for host\Users (on the target RDS hosts), CDM would fail in the RDS session (and viewing the HKLM\Software within the RDS session showed registry key ‘IAM Cloud’ not present.
Setting Registry Permissions of HKLM\Software\IAM Cloud on the RDSH server to Full Control for host\Users resolved the issue.
Unlike most other software CDM is required to authenticate in order to correctly map a users drives. It is therefore imperative that CDM is started in user context and not at an elevated cmd level.
Where CDM is to be used in an "app front-end" environment the user will have no interaction with the CDM application, it is therefore imperative that SSO ( SIngle Sign On ) be fully working in order for CDM to auto authenticate the user and map any drives required during the "app session"
We have found there are four different methods of starting CDM, in order of success we have found these to be :-
- Manipulate the Userinit reg key ( by far the most successful and widely used method )
- Batch file but targeting a specific user group
- GPedit ( via script )
- GPO to HKCU/run ( Least used method )
In depth explanation of the options above :-
1) Userinit method
The userinit key is located in the following location :-
Here we will create a .bat file and refer to this from the UserInit key.
Normally the userinit key will have the following entry :- C:\Windows\system32\userinit.exe,
We will change this to be :- C:\Windows\system32\userinit.exe, "C:\Scripts\CDM\CDM.bat"
Within the cdm.bat file
:: Cloud Drive Mapper startup script Start "" "C:\Program Files\IAM Cloud\Cloud Drive Mapper\CloudDriveMapper.exe" -r exit 0
Where this is being run from a shared server and you do not wish for CDM to start for all users then IFMember can be used as per example below:-
N/B : for ifmember to work it must be accompanied by the ifmember.exe which can be obtained via IAM Cloud Support.
REM ===================================== REM Enable CDM for Certain Group Members REM CDM Access group = CDMGrp REM ===================================== :: Ifmember is part of 2k3 Rescue kit ( %0\ denotes running it from same location as .bat file (( else give it a path )) ) %0\..\ifmember.exe /v "CDMGrp" IF ERRORLEVEL 1 GOTO Enable_CDM goto end_EnableCDM :Enable_CDM Start "" "C:\Program Files\IAM Cloud\Cloud Drive Mapper\CloudDriveMapper.exe" -r goto end_EnableCDM :end_EnableCDM
2) Batch file via sched task
Where we do not want CDM starting for all users and the Ifmember section above isn't viable, then we can use a scheduled task to target our cdm.bat file, we will set the sched task to be run only for users of a specific security group.
See Images Below :-
Set the section "When running the task........" to be set against the specific security group.
At log on & Any User
Target our CDM bat file
Make sure to set " Run a new instance in parallel " <-- as we're running it for each user who logs on
3) GPedit Method
As above we will call the same cdm.bat file, except via the Logon/Logoff method as shown below:-
Note this is a LOCAL policy NOT GPO.
4) HKCU/Run GPO
Here we have created a security group CDMGrp and assigned the policy to that group with the following parameters :-
N/B :- Making sure to tick "Run in logged-on user's security context (user policy option)
Action :- Update
Hive :- HKCU
Key path :- Software\Microsoft\Windows\CurrentVersion\Run
Value Name :- Start-CDM
Value Type :- Reg_SZ
Value Data :- C:\Program Files\IAM Cloud\Cloud Drive Mapper\CloudDriveMapper.exe