My Top 3 Favorite/Informative UEM Community Forum Discussions – August/September
In this blog post I want to share my top 3 favorite/informative UEM Community Forum discussions of August/September 2017.
#3 – Methods to Capture Registry and Profile Changes – Tools that can be used to monitor registry/file/folder changes.
#2 – Windows App Dissapear after logoff (Windows 10) – Known issue with Windows 10 and “remove local profile at logoff”.
#1 – Acceptable Horizon Desktop Logon Time – Reduce the amount of time for showing the Welcome Screen.
3 – Methods to Capture Registry and Profile Changes
Key takeaway: Tools that can be used to monitor registry/file/folder changes and help you choosing the correct content for your INI files.
Forum user mrstorey303 asked:
Can anyone explain the easiest way to identify registry settings / profile changes for settings that can’t be captured using the application profiler?
For example – I know I can use the app profiler to monitor an application executable and capture the config changes I make within the app, but how can I easily identify things like Windows OS changes – changes like ‘enable file name extensions’ and ‘hidden files’ in Windows Explorer? (BTW I have tried monitoring explorer.exe with app profiler, but the profiling session immediately terminates – so I suspect it’s not designed for processes like that).
Perhaps I can google around for these settings, but I just wondered if there were some good tools or processes you are using to capture changes like these, so I can configure them within UEM.
There are several tools you can use. I always use a combination of the following.
VMware UEM Application Profiler
2 – Windows App Dissapear after logoff (Windows 10)
Key takeaway: Do not use “remove local profile at logoff” (for now ;-)) when using Windows 10
Forum user ErikVb84 reported:
We are currently creating a windows 10 (1703) image and are testing the workings of all the features and applications. The environment uses local profiles and VMWare UEM version (18.104.22.1681) and we use the Advance UEM GPO setting to remove the profile after logoff.
Part of Windows 10 are the apps from the Store which are visible in the start menu. We are now seeing that after the user has logged on twice on the same machine all the apps disappear from the start menu and will not return. The problem persists for the user on that machine unless two things happen:
- the user profile is deleted via advanced system settings in Windows;
- Machine is reinstalled.
To test we setup VMware UEM without any configuration (no shortcuts no Config file, no conditionsets, nothing.) and have only applied our GPO settings(see GPO settings below). When UEM is turned off (no config set) the problem does not occur. When we turned on the test config the problem would occur after two logons.
The first suspect was the local profile deletion so we turned this feature off and tried again and as expected the problem did not occur anymore.
Our guess of the cause?
We are unable to find a solution for this issue at it seems it might be a timing issue or maybe 1703 changes the way it stores user app information and the way UEM does the deletetion creates some sort of lock on this new method.
Does anyone have a similar issue or is there a solution out there for this problem.
Pim_van_de_Vis his answer:
This is a know issue with Windows 10 and the ‘remove local profile at logoff’ option. Windows leaves user SID information behind at this location:
When you manually remove the user SID key there, the issue is gone. We are trying to fix this in the future.
1 – Acceptable Horizon Desktop Logon Time
Key takeaway: Reduce the amount of time for showing the Welcome Screen and improve user logon time
Although this is an older thread, a nice addition was done by JohnTwilley:
That pesky “Welcome Screen” !!
One of my favorite tweaks is DelayedDesktopSwitchTimeout
This is a nice setting to play around with, to show the User Desktop is little sooner than normal.
Some people set it to 0. I liked setting it to 2. See what works best for you…