I don't recommend roaming the complete local AppData folder for multiple reasons.
1. You don't know what exactly is saved in the local AppData folder and as such may create profile bloat.
2. You are only able to completely reset the local AppData settings.
3. User logon/logoff takes longer.
I recommend to create separate UEM config files per application for the following reasons.
1. You only save the settings that are really required.
2. You are able to reset settings on application level.
3. User logon/logoff takes shorter.
4. You can also consider DirectFlex for faster user logon/logoff.
Does this answer your question?
How would you accomplish roaming the entire folder? How is that done in UEM console?
By simply specifying the <LocalAppData> in your config file.
Which config file? I know there are config files for each app. just wondering which config file you're specifying the <LocalAppData> in order to capture all apps?
In any config file you want. For instance, you can create a new config file (INI) LocalAppData.INI and specify [IncludeFolderTrees] and <LocalAppData>. See screenshot below as example. But notice, this is something I do NOT recommend!
specifying the <LocalAppData> in order to capture all apps
I am not saying that you capture all apps by including the folder tree <LocalAppData>. It depends on the application if it saves to this location or not. And again, I do not recommend saving the complete <LocalAppData> folder tree!
Does this make it more clear?
Completely agree with Ivan. Do NOT roam the entire APPDATA folder. That's not a good practice at all.
Create separate config files for each application. The Application Profiler is a very helpful tool to figure out where all application settings are stored in the user profile:
Thanks for the clarification. Got it now.