You must install User Environment Manager on your environment to manage personalization and application configuration settings. The User Environment Manager MSI consists of several installation features that you can install on your environment.

Table 1. User Environment Manager Installation Features
Installation Feature Description
VMware UEM FlexEngine

Client component that you must install on each desktop or Terminal Server that you want to manage by using User Environment Manager.

If you are deploying FlexEngine to physical machines, you can use any software deployment tool to perform batch deployment or use Active Directory Group Policy software deployment.

If you deploy FlexEngine in a VDI or RDSH environment, such as VMware Horizon, you can manually install FlexEngine in the template or parent virtual machines and then deploy pools and farms of VMware Horizon® View™ desktops and RDSH servers based on these templates.

Important: When you are deploying FlexEngine in virtual machines used in VMware Horizon® Cloud Service™, some differences apply, such as installation paths and other specifics related to use in the Horizon Cloud environment. For details about deploying FlexEngine when using a Horizon Cloud environment, see the administration documentation that is appropriate for your Horizon Cloud deployment mode. Horizon Cloud documentation is available from the Horizon Cloud documentation landing page.
VMware UEM Management Console Administration console that you can install on any desktop or Terminal Server where you want to manage User Environment Manager.
Application Migration Optional. You can install Application Migration on desktops or Terminal Servers if you want to migrate application settings across application versions. This feature depends on FlexEngine and cannot work standalone.
Self-Support Optional. You can install the Self-Support tool on desktops or Terminal Servers where you want users to support their application settings by themselves, without administrator intervention. This feature depends on FlexEngine and cannot work standalone.