VMware Horizon Community
PavelV9
Enthusiast
Enthusiast
Jump to solution

Explorer settings is applied but not effective

Hi,

I have found out that some Explorer settings are not applied when a user log-in to a desktop.

We are using Linked Clones desktops with “Refresh after logoff” settings.

So, users have always clean desktop when log-in.

When a user unset (clear) “Always show icons, never thumbnails” in File Explorer it is correctly exported by UEM when the user logoff.

But when the user logon to a new desktop File Explorer do not show thumbnails.

I have found out that it is because Explorer.exe is already running when user UEM settings are applied.

So, when I kill Explorer.exe and run it again it is applied.

We don’t want to kill Explorer.exe on all desktops after a user log-in.

Does anyone experience with it?

Is it possible to support similar Explorer settings by UEM?

Thanks,

Pavel

1 Solution

Accepted Solutions
DEMdev
VMware Employee
VMware Employee
Jump to solution

Hi PavelV9,

As a quick test: does it help if you create a personalization config file with the Active Setup Windows Common Template? That might prevent some (re-)initialization by File Explorer in subsequent logons.

View solution in original post

11 Replies
DEMdev
VMware Employee
VMware Employee
Jump to solution

Hi Pavel,

How did you configure to run UEM/DEM at logon? Can you provide a log file of a complete session from logon till logoff, at log level DEBUG?

Reply
0 Kudos
sujayg15
VMware Employee
VMware Employee
Jump to solution

See if you are capturing the following registry value, else you can inject the desired value at logon.

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Advanced

IconsOnly DWORD

0 = Off - show icons

1 = On - show thumbnails

Reply
0 Kudos
PavelV9
Enthusiast
Enthusiast
Jump to solution

Yes, we save this key.

It is inverse.

0 = show thumbnails

1 = show icons

Reply
0 Kudos
PavelV9
Enthusiast
Enthusiast
Jump to solution

Hi DEMdev​,

UEM is running as GPO Extension.

We are using bulit-in "Windows Common Setting / Windows Explorer and view settings" config file.

After user logoff I can see correct registry entry in user's archive folder.

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Advanced

IconsOnly: 0

So it is saved correctly.

2019-10-29 13:54:18.873 [INFO ] Exporting profile using config file 'Windows Explorer.INI' (\\server.domain\UEMCONFIG\Shared\general\Windows Settings\Windows Explorer.INI)

2019-10-29 13:54:18.873 [INFO ] Binary Settings: Applied Common Setting 'Windows Explorer and view settings'

2019-10-29 13:54:18.891 [INFO ] Exporting Registry information

2019-10-29 13:54:18.892 [DEBUG] ExportRegistry: Exporting tree 'HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\Shell\BagMRU'

2019-10-29 13:54:18.902 [DEBUG] ExportRegistry: Exporting tree 'HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\Shell\Bags'

2019-10-29 13:54:18.920 [DEBUG] ExportRegistry: Exporting tree 'HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced'

2019-10-29 13:54:18.920 [DEBUG] ExportRegistry: Exporting tree 'HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\BitBucket'

2019-10-29 13:54:18.921 [DEBUG] ExportRegistry: Exporting tree 'HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Desktop\CleanupWiz'

2019-10-29 13:54:18.921 [DEBUG] ExportRegistry::ExportKey: Key 'HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Desktop\CleanupWiz' does not exist

2019-10-29 13:54:18.921 [DEBUG] ExportRegistry: Exporting tree 'HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\HideDesktopIcons\ClassicStartMenu'

2019-10-29 13:54:18.921 [DEBUG] ExportRegistry::ExportKey: Key 'HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\HideDesktopIcons\ClassicStartMenu' does not exist

2019-10-29 13:54:18.921 [DEBUG] ExportRegistry: Exporting tree 'HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\HideDesktopIcons\NewStartPanel'

2019-10-29 13:54:18.921 [DEBUG] ExportRegistry: Exporting tree 'HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\HideMyComputerIcons'

2019-10-29 13:54:18.933 [DEBUG] ExportRegistry::ExportKey: Key 'HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\HideMyComputerIcons' does not exist

2019-10-29 13:54:18.933 [DEBUG] ExportRegistry: Exporting tree 'HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\MenuOrder\Favorites\Links\Order'

2019-10-29 13:54:18.933 [DEBUG] ExportRegistry::ExportKey: Key 'HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MenuOrder\Favorites\Links\Order' does not exist

2019-10-29 13:54:18.933 [DEBUG] ExportRegistry: Exporting tree 'HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Modules\GlobalSettings\Sizer'

2019-10-29 13:54:18.933 [DEBUG] ExportRegistry::ExportKey: Key 'HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Modules\GlobalSettings\Sizer' does not exist

2019-10-29 13:54:18.933 [DEBUG] ExportRegistry: Exporting tree 'HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\RecentDocs'

2019-10-29 13:54:18.933 [DEBUG] ExportRegistry::ExportKey: Key 'HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\RecentDocs' does not exist

2019-10-29 13:54:18.933 [DEBUG] ExportRegistry: Exporting tree 'HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Streams'

2019-10-29 13:54:18.933 [DEBUG] ExportRegistry: Exporting tree 'HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\UserAssist'

2019-10-29 13:54:18.935 [DEBUG] ExportRegistry: Exporting tree 'HKCU\Software\Microsoft\Windows\Shell\BagMRU'

2019-10-29 13:54:18.936 [DEBUG] ExportRegistry: Exporting tree 'HKCU\Software\Microsoft\Windows\Shell\Bags\1\Desktop'

2019-10-29 13:54:18.936 [DEBUG] ExportRegistry: Exporting tree 'HKCU\Software\Microsoft\Windows\ShellNoRoam\BagMRU'

2019-10-29 13:54:18.936 [DEBUG] ExportRegistry::ExportKey: Key 'HKEY_CURRENT_USER\Software\Microsoft\Windows\ShellNoRoam\BagMRU' does not exist

2019-10-29 13:54:18.936 [DEBUG] ExportRegistry: Exporting tree 'HKCU\Software\Microsoft\Windows\ShellNoRoam\Bags'

2019-10-29 13:54:18.948 [DEBUG] ExportRegistry::ExportKey: Key 'HKEY_CURRENT_USER\Software\Microsoft\Windows\ShellNoRoam\Bags' does not exist

2019-10-29 13:54:18.948 [INFO ] Exported Registry information successfully

2019-10-29 13:54:18.975 [DEBUG] Stored 1 entry in profile archive (size: 250308; compressed: 20233)

But when the user log-in again there are IconsOnly: 1 in registry. 😞

There are following data in the log regarding the config file:

2019-10-29 14:03:28.115 [INFO ] Importing profile archive 'Windows Explorer.zip' (\\server.domain\UEMUSERS\folder\user1\ARCHIVES\Windows Settings\Windows Explorer.zip)

2019-10-29 14:03:28.130 [DEBUG] ImportRegistry::Import: Calling '"C:\Windows\REGEDIT.EXE" /S "C:\Users\user1\AppData\Local\Temp\FLXF780.tmp"' (RPAL: l=0 (D/E), r=0)

2019-10-29 14:03:28.551 [DEBUG] Read 1 entry from profile archive (size: 246772; compressed: 19962; took 432 ms)

Reply
0 Kudos
PavelV9
Enthusiast
Enthusiast
Jump to solution

It is interesting because when I log-in to a desktop by Console the settings is applied correctly. 😮

Any idea what is different between Console and Horizon Client log-in?

There are no Conditions set for the config file.

Reply
0 Kudos
DEMdev
VMware Employee
VMware Employee
Jump to solution

Hi Pavel,

(Sorry for the delay; I was on holiday.)

If it works when you log on to the console, maybe something Horizon-related affects this? Can you run ProcMon to see which processes touch this registry value? You should see the RegEdit.exe that is launched by DEM/UEM to import your Explorer settings, but maybe something else overwrites it later?

Reply
0 Kudos
PavelV9
Enthusiast
Enthusiast
Jump to solution

Hi,

I have tested the scenario again and I have to correct the previous info.

Previously I have written that the setting is applied correctly when I login to console.

It is not true.

The setting is applied correctly when user profile already exists on the desktop.

So when a user is login first time on a desktop the setting is not applied.

When the user is login to same desktop again the setting is applied correctly.

I have captured changes by ProcMon during login process.

When a user is login first time to a desktop there are following processes which are written to the key (HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Advanced - IconsOnly😞

18.11.2019 13:41:10,7615539

"C:\Windows\REGEDIT.EXE" /S "C:\Users\USER~1.000\AppData\Local\Temp\FLX986C.tmp"

Data:     0

18.11.2019 13:41:46,6184628

C:\Windows\Explorer.EXE

Data:     0

18.11.2019 13:43:03,7659038

C:\Windows\Explorer.EXE

Data:     1

18.11.2019 13:46:47,3022498

C:\Windows\Explorer.EXE

Data:     1

When the user is login to same desktop again there are the only UEM which is written to the key:

18.11.2019 13:53:11,9436747

"C:\Windows\REGEDIT.EXE" /S "C:\Users\USER~1.TES\AppData\Local\Temp\FLX4A2E.tmp"

Data:     0

There are something what is running when new user profile is created but I have no idea what it is. 😞

I am going to test the scenario in different environment with different OS image but it takes a while...

Pavel

Reply
0 Kudos
DEMdev
VMware Employee
VMware Employee
Jump to solution

Hi PavelV9,

As a quick test: does it help if you create a personalization config file with the Active Setup Windows Common Template? That might prevent some (re-)initialization by File Explorer in subsequent logons.

PavelV9
Enthusiast
Enthusiast
Jump to solution

It works!

Thank you very much for your help.

P.

AdamSeifert
Contributor
Contributor
Jump to solution

I have the same issue as the original poster. I tested with a new template using the Active Setup suggestion and it does appear to work. My question is if there is another way to accomplish the same result without having to save Active Setup for every user?

Reply
0 Kudos
DEMdev
VMware Employee
VMware Employee
Jump to solution

Hi Adam,

With some ProcMon analysis you might be able to figure out which specific Active Setup component is reinitializing this setting, which you could then use to maybe create a slightly more targeted config file than our Active Setup template.

But, out of curiosity: any reason why you don't want to capture Active Setup for every user?

Reply
0 Kudos