5 Replies Latest reply on Jan 28, 2020 6:18 AM by DEMdev

    HKCU registry items not set (UEM 9.6)

    UniSander Lurker

      Hi all,

       

      I use UEM 9.6 and want to set some items in the HKCU, these items are not set during logon. I know UEM works because I tested it with some icons on the desktop and they are working.

      I even tested a HKCU setting with a test key:

      *********************************************************************************************************************

      Windows Registry Editor Version 5.00

       

      [HKEY_CURRENT_USER\Software\Immidio\Flex Profiles\ImportMarkers]

      "Pre"=dword:b0dafda1

       

      [HKEY_CURRENT_USER\Environment]

      "TestKey"=dword:000000000

       

      [HKEY_CURRENT_USER\Software\Immidio\Flex Profiles\ImportMarkers]

      "Post"=dword:7004260c

      *********************************************************************************************************************

       

      Debug logs tells me that the key is set:

      2020-01-24 08:28:14.405 [INFO ] Importing UEM settings 'TestKey.zip' (\\fs01.uwsd.loc\UEMconfig$\Production\General\FlexRepository\Settings\Reg\TestKey.zip)

      2020-01-24 08:28:14.418 [DEBUG] ImportRegistry::Import: Calling '"C:\Windows\REGEDIT.EXE" /S "C:\Users\SANDER~1.TES\AppData\Local\Temp\FLXCDD7.tmp"' (RPAL: l=0 (D/E), r=0)

      2020-01-24 08:28:14.470 [DEBUG] Read 1 entry from profile archive (size: 576; compressed: 234; took 57 ms)

      2020-01-24 08:28:14.470 [INFO ] Successfully imported settings ('TestKey.xml')

        • 1. Re: HKCU registry items not set (UEM 9.6)
          DEMdev Master
          VMware Employees

          Hi UniSander,

           

          Good question; it had me stumped for a minute

           

          Regedit is pretty particular about the .REG format, and it seems that it did not like your test DWORD with nine zeroes... After changing that to eight zeroes, it works for me.

           

          However, I'd suggest to use the built-in functionality to create environment variables rather than tweaking the registry directly.

          • 2. Re: HKCU registry items not set (UEM 9.6)
            UniSander Lurker

            Demdev,

             

            You got me there ...

            Ok, now I know that registry settings working, that brings me back to my original problem. A specific regkey I created is not changed

             

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

            "IconsOnly"=dword:00000000

             

            The default is 1 and I want this to 0. The log tells me it is set correctly. But when I'm on my VDI it is still 1.

             

            And I know now my test reg item works

            • 3. Re: HKCU registry items not set (UEM 9.6)
              DEMdev Master
              VMware Employees

              Hi UniSander,

               

              In that case, it's probably overwritten by something else after DEM has initially set that value.

               

              Maybe it's Explorer's own (re-)initialization. As a quick experiment, you could try creating a config file with the Active Setup Windows Common Setting; that might prevent some settings from being reinitialized.

               

              Alternatively: Can you run ProcMon to see what processes touch that IconsOnly value?

              1 person found this helpful
              • 4. Re: HKCU registry items not set (UEM 9.6)
                UniSander Lurker

                DEMdev,

                 

                Still having issues. Tried lots of things to find the process that is overruling the setting.

                 

                I know procmon, but how would I start it before uem starts processing?

                • 5. Re: HKCU registry items not set (UEM 9.6)
                  DEMdev Master
                  VMware Employees

                  Hi UniSander,

                   

                  Yeah, that's always "fun"... You can use SysInternals' PSExec to run ProcMon non-interactively in the system account while a normal logon takes place, using steps similar to the following:

                  • Log on to the console with an admin account
                  • Copy PSExec.exe and ProcMon.exe to folder C:\X
                  • Run C:\X\PSExec.exe -accepteula -sd C:\X\ProcMon.exe -accepteula -quiet -backingfile C:\X\Log.PML
                  • Log off
                  • Log on "the normal way", with your test user
                  • From an elevated prompt, run C:\X\PSExec.exe -accepteula -s C:\X\ProcMon.exe -accepteula -quiet -terminate
                  • Open C:\X\Log.PML in ProcMon and analyse
                  1 person found this helpful