Reply to Message

View discussion in a popup

Replying to:
DEMdev
VMware Employee
VMware Employee

Hi MikeC3964,

UEM is really intended to be used with much more granular configuration files. Instead of your big bang approach, the idea is to create per-application and per-Windows setting Flex config files, each covering just the registry and file system locations for that particular app or Windows component.

I appreciate that that takes a non-trivial amount of time to set up, but hopefully our built-in Application Templates and WIndows Common Settings (in the Create Config File wizard) help you get started for commonly used apps and settings.

In addition to that, we have the Application Profiler, which helps in creating Flex config files for applications, by monitoring where an application saves its settings.

Your approach basically mimics a standard roaming profile, by pretty much capturing all of the user's registry information (and also quite a bit of the file system, judging from the "Read 2504 entries from profile archive" log message). That's easy to configure, sure, but won't give you the benefits of UEM (faster logons, easier reset/restore of application settings, etc).

Reply
0 Kudos