Dynamic Environment Manager supports scenarios with multiple environments, such as different customers, development, testing, acceptance, production, and separately managed organizational divisions.
You can use the traditional mechanisms like Active Directory group policies and file services to make a design that accommodates the needs of your organization. If you are managing multiple Dynamic Environment Manager environments with a team of administrators, you can also configure these environments through a group policy, by using the DEM Management Console.admx template, available in the Dynamic Environment Manager download package. If environments are configured through a policy, the Configure Environments menu option and the Configure button in the ribbon are not available. If only a single environment is configured through a policy, the Switch Environment menu option is not available either.
For each environment that you define, a Dynamic Environment Manager configuration share needs to be created, as well as a group policy with the environment-specific paths configured. After that, you target the Dynamic Environment Manager group policies to the appropriate users, depending on which environment they belong to. For example, you can target the group policies based on an Active Directory organizational unit. You can use a single instance of the Dynamic Environment Manager Management Console to manage these environments. For information on configuring group policies, see Installing and Configuring Omnissa Dynamic Environment Manager.
When multiple environments are configured in the Dynamic Environment Manager Management Console, you can import and export Dynamic Environment Manager configuration items between environments.
Was this page helpful?