Overwritting User Settings

[deep184]

Hello,

In our environment we have laptop\tablet users connecting to a pool of VMs. Both physical and virtual environments are managed with UEM with separate configuration shares and one central profile share. We are noticing that when users connect into a VM and makes changes (i.e. mapping network printer,drive) and logs out it writes to the profile share like it should. However, when the user logs out of their physical device it overwrites any of the changes that the user made while made in the VM. Is there anyway to prevent this?

Thanks in advance!

[Pim_van_de_Vis · Accepted solution]

UEM uses a 'last write wins' and therefor you see this behavior.

You can work around this by enabling DirectFlex for all applications. That way the settings are written to the UEM profile share at applicaiton close and not at logoff.

Only some Windows settings need to be exported at logoff (for instance the wallpaper).

If you also want to prevent this from happening on the physical endpoints, you could change the export behavior for those UEM Config Files, see the attached screenshot.

Configured like this, the wallpaper will 'import only' when user logs on to a computer with a hostname that start with 'physical'.

In any other scenario (logon to the VM), the wallpaper will import at logon AND export at logoff.

[deep184]

Thank you for the response!

I was looking for something for printers, mapped drives, etc...  that do not have associated executable that could be assigned to enable DirectFlex.

The second option would definitely considered and only have settings imported and exported when using VMs and only imported when users are logged into physical desktops.

I was investigating if using a post-export task to import user setting once the VMware Horizon Client is exited by using command C:\Program Files\Immidio\Flex Profiles\FlexEngine.exe -r.

Are you aware if this would work or of any concerns?

Thanks

[Pim_van_de_Vis]

Rrunning an import immediately after export-at-logoff is a bad idea, because timing will probably interrupt this.

The suggestion to use conditions and 'import only' is probably the best approach.

[deep184]

Sounds good!

Thanks for the quick responses!

[Ittybit]

Hello,

Wouldn't creating Silos prevent this issue from occurring if the silo specific config files and profile archives are located in sub folders in the main UEM config share and user profiles?

Just wondering trying to figure out the purpose of silos.

Thanks

[DEMdev]

Silos are a legacy feature – nowadays you use conditions to achieve the same functionality (and much more).