I just upgraded from version 6.4 to 7.2 of KACE and now an autolog script that has been used for years does not work.  Every time a non administrative user would try to login it would logoff right away. I found that this issue was in the registry HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon 
userinit  The value name was C:\\Windows\SysNative\KusrInit.exe  I know that KusrInit is from KACE, obviously this has changed since the upgrade.  I manually changed the string to \Windows\System32\userinit.exe which fixed the issue, but now obviously this will break KACE seeing it or talking to it.

So now that I run 7.2 I am assuming that string will have to be different.  What changes will I have to make to the script to fix this?  I never had to add this before here is the script:
  1. Set “HKLM64\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon!DefaultDomainName” to “*****”.
  2. Set “HKLM64\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon!DefaultUserName” to “******”.
  3. Set “HKLM64\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon!AutoAdminLogon” to “1”.
  4. Set “HKLM64\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon!DontDisplayLastUserName” to “1”.
  5. Set “HKLM64\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon!DefaultPassword” to “******”.
  6. Launch “%WINDIR%\System32\cmd.exe” with params “/C shutdown -r -f -c ”Restart by KBOX“ -t 120 -d U:00:00”   
What I am I missing?
0 Comments   [ - ] Hide Comments


Please log in to comment

Answer this question or Comment on this question for clarity


This is not a 7.2 issue, Userinit changes from time to time depending on the agent version.

For example, see this PRE 6.4 post from 2012

Kind of the issue you are having... I'm afraid that script will need to be adjusted.

My advice is update your kbox and agents to 8.0, and then do the adjustments.

If you choose to stay in 7.2, then a year from now you update your agents to 8.0, then you will need to re-adjust the script again.

Another option, grab a dummy PC experiencing the  issue , and try a NOHOOKS agent install:

This will help you to narrow it down.
Answered 02/19/2018 by: Channeler
Seventh Degree Black Belt

Please log in to comment