You must configure User Environment Manager before you can use it to create smart policies for remote desktop features.
To configure User Environment Manager, follow the configuration instructions in the VMware User Environment Manager Administration Guide. The following configuration steps supplement the information in that document.
To configure User Environment Manager, follow the configuration instructions in the VMware User Environment Manager Administration Guide.
- When configuring the VMware UEM FlexEngine client component on remote desktops, create FlexEngine logon and logoff scripts. For multiple sessions. such as a RDSH desktop and RDSH application or a multiple RDSH application session for the same user on the same RDSH host, use the -HorizonViewMultiSession -r parameter for the logon script. For the logoff script, use the -HorizonViewMultiSession -s parameter.
Note: Do not use logon scripts to start other applications on a remote desktop. Additional logon scripts can delay remote desktop logon for up to 10 minutes.
- Enable the user group policy setting Run logon scripts synchronously on remote desktops. This setting is located in the folder User Configuration\Policies\Administrative Templates\System\Scripts.
- Enable the computer group policy setting Always wait for the network at computer startup and logon on remote desktops. This setting is located in the folder Computer Configuration\Administrative Template\System\Logon.
- For Windows 8.1 remote desktops, disable the computer group policy setting Configure Logon Script Delay. This setting is located in the folder Computer Configuration\Administrative Templates\System\Group Policy.
- To ensure that Horizon Smart Policy settings are refreshed when users reconnect to desktop sessions, use the User Environment Manager Management Console to create a triggered task. Set the trigger to Reconnect session, set the action to User Environment refresh, and select Horizon Smart Policies for the refresh.
Note: If you create the triggered task while a user is logged in to the remote desktop, the user must log off from the desktop for the triggered task to take effect.