VMware Horizon Community
grahamp1981
Contributor
Contributor
Jump to solution

Horizon Non-Persistent Desktops with UEM and Roaming AppData

I am having real trouble understanding the concept of moving away from roaming profiles and using UEM instead to preserve user settings.

I have seen all the best practices about not using folder redirection for anything as it can slow down performance but then how do you preserve changes made by individual users especially changes that were kept in the roaming app data folder when using profiles?

I have users that log onto non-persistent desktops, makes changes to pin icons to taskbar, pin documents to office. They log off and the desktop is destroyed, they then log on again to a new desktop and all their changes are lost. How do individual users keep their settings saved using UEM?

I have seen things about adding the following as an example

pastedImage_0.png

but then where is it including these folder trees from? Surely a user must have to have an individual folder or place where their data is stored so that when they log back on, it writes it to their desktop session?

It all sounds very unclear and hoping someone can make me understand this better?

Tags (3)
1 Solution

Accepted Solutions
DEMdev
VMware Employee
VMware Employee
Jump to solution

Hi grahamp1981,

Can you double-check the configuration of your logoff script as per the Configure FlexEngine to Run From a Logoff Script topic in the docs?

View solution in original post

0 Kudos
7 Replies
ijdemes
Expert
Expert
Jump to solution

Hi grahamp1981​,

Do you have trouble understanding the UEM concept in general, the reasoning for using it, or a specific issue? Please let me know and I will help you out.

Maybe unneccesary to mention, but the introduction to UEM can be found here: Introduction to User Environment Manager


\\ Ivan
---
Twitter: @ivandemes
Blog: https://www.ivandemes.com
grahamp1981
Contributor
Contributor
Jump to solution

The problem I have is a specific issue as explained in my post above.

0 Kudos
sjesse
Leadership
Leadership
Jump to solution

The configuration files tells the uem agent where the settings are so at logoff it can create a zipfile based on those files and registry settings to be unzipped in the correct location on the next logon or direct flex trigger. In the uem configuration you specified a section for

archives, this these zip files are located this location, look at the below link for a reference

VMware User Environment Manager Deployed in 60 Minutes or Less | VMware End-User Computing Blog

If your asking what the appdata and localappdata tags are, these come from the user profile. Appdata is C:\users\<username>\appdata\roaming and localappdata is C:\users\<userdata>\appdata\local

For your specific issue, you should have a Taskbar configuration file under Windows Settings, in the Personalization setting. If its not there you can click create config file  and pick use a windows common setting

pastedImage_0.png

0 Kudos
grahamp1981
Contributor
Contributor
Jump to solution

Hi. I have created the config file and can see from the log file that it looks to import from the archives folder. However, when I log off of the desktop, nothing is exporting to this archive folder and so there is nothing to import. The log file doesn't mention anything when I log off the desktop.

I am not using the DirectFlex approach just the config file processing with the process during logon and logoff enabled.

Is there something I am missing?

0 Kudos
DEMdev
VMware Employee
VMware Employee
Jump to solution

Hi grahamp1981,

Can you double-check the configuration of your logoff script as per the Configure FlexEngine to Run From a Logoff Script topic in the docs?

0 Kudos
jlpolanco
Contributor
Contributor
Jump to solution

Sounds like your logoff/login script is not working correctly.  Double check that.

0 Kudos
grahamp1981
Contributor
Contributor
Jump to solution

Thanks Guys. I was running the logoff script from the UEM Console itself instead of as a separate GPO. As soon as I changed it to run as a GPO, the settings were being exported to the users UEM share and the changes made to taskbar and pinned documents were all there on log in.