Traditionally you might map user network drives via a logon script or maybe a group policy preference. VMware’s User Environment Manager (UEM) gives you some other nice options in the fun filled world of drive mappings!
We can take a conventional approach by mapping a drive for all users or targeting by an AD object such as group or OU. OK, so far so group policy preferences!
Why don’t we map a drive on a per application basis? Using UEM we can associate the mapped drive with an app and set it to apply ‘on demand’ when said application is launched. This avoids the need for the drive mapping to happen at user logon but it is available when required.
But what about my power users that want to be able to manually map drives (and persist them across devices)? UEM does not capture these manually mapped drives by default but we can add the below registry location so this information is stored and reproduced in a different session
I’ve used network drives as an example here but by moving application settings into UEM we can optimise the logon process, provide a consistent user experience and control all relevant app settings in one place. Very Nice!
Leave a Reply