Domain admin cannot unlock screen saver on Windows Server 2003 domain controller – Managing your servers can streamline the performance of your team by allowing them to complete complex tasks faster. Plus, it can enable them to detect problems early on before they get out of hand and compromise your business. As a result, the risk of experiencing operational setbacks is drastically lower.
But the only way to make the most of your server management is to perform it correctly. And to help you do so, this article will share nine tips on improving your server management and fix some problem about windows-server-2003, domain-controller, windows, , .
I have a problem accessing a Windows Server 2003 R2 machine which is a domain controller. A domain admin account is logged in and the screen saver has activated, but bringing up the “Unlock Computer” dialog and entering the username and password results in the “Computer Locked” dialog with the message “This computer is locked. Only domain username (username) or an administrator can unlock this computer.” The username entered is the same as the one that has it locked, but the error dialog suggests the machine thinks it’s not the same user (an incorrect password would give a different error, no?)
Interestingly, the “Log on to:” dropdown in the “Unlock Computer” dialog contains lots of blank lines i.e. the domain the user belongs to is not there.
I have tried entering domain username for the username, but this gives the same result.
I would use pstools or something like it to kill the screensaver process remotely, or issue a clean shutdown/restart remotely after hours.
You may consider asking yourself why people are logging onto the console of a DC, but that’s off-topic.