Use the following steps to clean boot one of the affected client devices running any supported Microsoft Windows operating system:
A) Blocking Group Policy Inheritance
1. Using i.e. the Active Directory Users and Computers management console (dsa.msc) create a new Organizational Unit (OU)
2. Move the affect Computer account in Active Directory into the newly created OU
3. Using the Group Policy Management Console (gpmc.msc) find and right-click the newly created OU and choose "Block inheritance"
NOTE: Group Policies can be configured for Computers and Users but statistics show that Computer related Group Policies are most often the culprit.
3. Either reboot the affected client device now or proceed to the next step which includes a reboot
B) Disabling all 3rd Party Windows Services using msconfig.exe
1. Using the Start Menu or the command line, run msconfig.exe
2. Inside the msconfig.exe utility, click the "Services" tab
3. On the bottom left, check the "Hide all Microsoft services" checkbox
4. On the bottom right, click the "Disable All" button
5. Since KACE is a 3rd Party from Microsoft perspective, re-enable all KACE related services
NOTE: If step 5 is not performed, the client device will end up booting without KACE related services.
It is good to double-check if any other service is required: i.e. for remotely connecting to a machine (VNC, DameWare, etc.).
Microsoft RDP should be used ideally for remote connections. Another thing to note is the Anti Virtus related services usually cannot be disabled this way and sometimes the last step to troubleshoot the issue might be to uninstall the Anti Virus solution for a test only.
6. Click the "Apply" and "Ok" button and eventually the "Restart" button to perform the clean boot
Example screenshot without 3rd Party services but KACE: