bradenterpstra01

Prominent
Mar 22, 2020
22
2
515
0
My company deploys images with Microsoft Deployment Toolkit through Windows Deployment Server. Upon installation, the Local Administrator account works without issue. You can install software, perform administrative tasks, and reboot the machine without issue. The moment Windows Update is run (uses WSUS to manage updates) and the computer reboots, the local Administrative profile is set as a BACKUP profile. This means that when you re-login after the update, it creates a temporary profile that can do little Administrative tasks on the machine. Basic tools like System Services or even start menu search do not work. The only way I have found to fix this is to login with a Domain Admin account, delete the local administrator profile and any TEMP user profile in the C drive Users folder, and reboot the machine. This will make the Administrative profile reset and it will work as expected. Has anyone else had this issue? This often occurs with many of our machines when Windows pushes an update. Any way to prevent this or a quick fix solution?
 

bradenterpstra01

Prominent
Mar 22, 2020
22
2
515
0
Are you using different names for these different admin accounts?
It WSUS breaking all local admin accounts (including ones manually created) or only the one deployed?
We have domain admins "user-admin@domain.com" that have full administrative priveleges, and we use the built-in Windows Administrative Account. We enable it upon installation as we need it for various software installations in the field. Basically, after imaging, the only two active accounts on the machine are the Local Administrative account and the DefaultUser. Once the computer talks to WSUS (wuauclt.exe /resetauthorization /detectnow) and detects updates, it will set the Local Admin account as BACKUP upon reboot. The updates can be run by any account and it does the same thing. So it seems like WSUS is breaking it, even when it does not have any visible updates to be installed.
 

ASK THE COMMUNITY