If you do not configure FlexEngine to run as a Group Policy client-side extension, you must configure FlexEngine to run from a logon script.
- You selected a different directory when you installed VMware Dynamic Environment Manager.
- VMware Dynamic Environment Manager was installed as part of another installation.
For example, if you used the Horizon Cloud Import Image workflow or the Horizon Agent Installer to install VMware Dynamic Environment Manager for a virtual machine located in Microsoft Azure, the installation path is different. For details, see Creating Desktop Images for a Horizon Cloud Pod in Microsoft Azure.
If VMware Dynamic Environment Manager is installed in a non-default directory, adjust the path accordingly.
If you configure FlexEngine to run as a Group Policy client-side extension, you do not need to configure FlexEngine to run from a logon script. See Configure FlexEngine to Run as Group Policy Extension Setting.
However, in case a computer is offline and a user logs in with cached credentials, Group Policy client-side extensions do not run. If FlexEngine is configured to run as a Group Policy extension, no import takes place. Therefore, configure a logon script with the -OfflineImport argument to enable importing of user settings at login even when the user's computer is offline.
You can add the FlexEngine logon command to an existing logon script or call it directly as a logon script. For this purpose, use User Configuration\Windows Settings\Scripts.
Configure the following command that runs during logon:
"C:\Program Files\Immidio\Flex Profiles\FlexEngine.exe" -r
This command reads the settings that are configured through the VMware Dynamic Environment Manager Group Policy Object and performs the path-based import accordingly.
To run FlexEngine as a logon script from a GPO, use the following settings.
| Option | Value |
|---|---|
| Script Name | C:\Program Files\Immidio\Flex Profiles\FlexEngine.exe |
| Script Parameter | -r |
VMware Dynamic Environment Manager manages profile information that often must be imported before the Windows shell is initialized. To make sure that the shell initialization waits until the logon script has completed, enable the Run logon scripts synchronously Windows Group Policy setting. This setting is located at User Configuration\Policies\Administrative Templates\System\Scripts.
