How are most people managing configuration directories in User Environment Manager? Do you have one giant shared configuration directory with everything listed there? Or do you seperate the configuration directories into different use cases to prevent configuration errors from effecting all of your use
It probably depends on your situation and/or requirements. However, I normally just stick with the default layout and only group "Windows Settings", "Application Suites" like Microsoft Office, and "(Business) Applications" for overview and readability.
If you have departments for which you want to seperate configurations, because you want to have them managed seperately for instance, you may consider creating different environments.
To prevent "implementing" mistakes in a production environment, I would recommend to use a seperate environment for testing purposes. And follow change procedures before implementing changes in production.
VMware User Environment Manager 9.1 Documentation Center
Just to clarify Ivan's response a bit (as it may not be obvious unless you click that link), "environment" isn't used in the generic sense of the word, but refers to the UEM feature with that name:
UEM environments can be managed from within a single UEM management console. You can switch between environments, and you can import and export configuration files between them (to "promote" a config file from Test to Acceptance, for example).
More information can also be found on page 24 of the:
|VMware User Environment Manager Deployment Considerations|
Good addition Pim. I really like this document. Very helpful!!
Thanks, and good to hear.
And I need to thank you for your brilliant contributions to this community in that past couple of weeks. Keep up the good work!
We have a development environment, but we are trying to let different departments manage their own desktops, currently we have one configuration directory for about 12 diiferent desktop pools.We are trying to make everyone test their UEM changes in our development environment, but as we are using more advanced condition sets I'm worried about incorrect settings being available to the wrong desktops. One example is we had a printer show up in the incorrect desktop pool, when we tried to limit printers by the user accessing the pool. It was an attempt to make sure they get location specific printers but it failed because of one nested group in the OU we based it off of.
Thesse are all great suggestions, I have not seen the deployment consideration pdf yet, so thank you for that