FlexEngine supports the following command-line arguments to refresh settings or launch elevated tasks.
Tip: The example path to FlexEngine.exe is based on the default installation directory. The default directory does not apply in the following cases.
-
You selected a different directory when you installed Dynamic Environment Manager.
-
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 Dynamic Environment Manager for a virtual machine located in Microsoft Azure, the installation path is different. For more information, see Creating Desktop Images for a Horizon Cloud Pod in Microsoft Azure in the First-Gen Tenants - Horizon Cloud Administration Guide at Omnissa Product Documentation.
If Dynamic Environment Manager is installed in a non-default directory, adjust the path accordingly.
-DirectFlexRefresh
DirectFlex configuration is processed during logon. If you add Flex configuration files with DirectFlex enabled, or modify DirectFlex-related settings of existing files while a user is logged on, these changes are not automatically picked up during the session.
This behavior might not be a problem, but you can force an update by running the following command in the user's session:
"C:\Program Files\Immidio\Flex Profiles\FlexEngine.exe" -DirectFlexRefresh
-UemRefresh
User environment settings are applied at logon, while computer environment settings are applied at boot. For certain types of settings, you can perform a refresh while the user is logged in.
Refresh Operations
| Operation | Description |
|---|---|
-UemRefresh | Refresh the Dynamic Environment Manager file type associations, shortcuts, and printer mappings. |
-UemRefreshFtas | Refresh the Dynamic Environment Manager file type associations. |
-UemRefreshShortcuts | Refresh the Dynamic Environment Manager shortcuts. |
-UemRefreshPrinters | Refresh the Dynamic Environment Manager printer mappings. |
-UemRefreshADMX | Refresh the Dynamic Environment Manager ADMX-based user settings. |
-UemRefreshADMXComputerPolicy | Refresh the Dynamic Environment Manager ADMX-based computer settings. |
-UemRefreshDrives | Refresh the Dynamic Environment Manager drive mappings. |
-UemRefreshEnvVars | Refresh the Dynamic Environment Manager environment variables. |
-UemRefreshApplicationBlocking | Refresh the Dynamic Environment Manager application blocking settings. |
-UemRefreshHorizonPolicy | Refresh the Dynamic Environment Manager Horizon Smart Policies for user environment settings.
Note: You can refresh Horizon Smart Policies at any time. However, the Horizon remote desktop experience components determine if the changes take effect at that time. |
-UemRefreshHorizonComputerPolicy | Refresh the Dynamic Environment Manager Horizon Smart Policies for computer environment settings.
Note: You can refresh Horizon Smart Policies at any time. However, the Horizon remote desktop experience components determine if the changes actually take effect at that time. |
-UemRefreshTriggeredTasks | Refresh the Dynamic Environment Manager triggered tasks. |
-UemRefreshPrivilegeElevation | Refresh the Dynamic Environment Manager privilege elevation settings. |
-LaunchTask
With privilege elevation, you can define elevated tasks. You can launch elevated tasks with a command such as the following.
"C:\Program Files\Immidio\Flex Profiles\FlexEngine.exe" -LaunchTask "name-of-task"
For more information about elevated tasks, see the Omnissa Dynamic Environment Manager Administration Guide.
-ApplyNoADSettings
If NoAD mode is enabled, the settings defined in the NoAD.xml config file are applied to the registry when a user logs on. If there are network or timing related issues that are preventing the FlexEngine from applying NoAD.xml settings, you can use the -ApplyNoADSettings command to apply NoAD.xml settings on demand.
"C:\Program Files\Immidio\Flex Profiles\FlexEngine.exe" -ApplyNoADSettings
Note: All actions are performed in the context of the user running this command. If you are targeting NoAD settings based on group membership, the group membership of the user running this command is evaluated. For more information about user group membership, see Targeting NoAD Settings Based on Group Membership.
Was this page helpful?