Windows 10: Domain Admin account disabled, but one computer can still logon to it.

In our network we have a domain admin account, but disabled it as it's for tech-support purposes only and should only be enabled when needed (in our case). However, even though it's disabled, a computer and probably more are still able to log into the account and bypass UAC. How is this happening? Is the account locally cached and still able to be used for admin rights?


Thanks.

:)

 

Domain admin account as built-in admin account


I just upgraded two brand new pc's from Win 7 to Win 10. Computers were already added to the domain in Win 7 and I was logged into the domain administrator account when I did the upgrade to Win 10. Now when I am logged in with the domain administrator account, I can't open Edge. It says "This app can't open. Microsoft Edge can't be opened using the Built-in Administrator account. Sign in with a different account and try again."

How do I get the local "Administrator" account to be the Built-in administrator account?

The list of user accounts are:
admin (local admin account I made in Win 7)
Administrator (I assume local administrator account that is automatically created)
administrator.AESSEINVLTD (domain admin account I am logged in with)
Default.migrated
Public.

 

Admin Account Disabled


I am glad that the problem is fixed.

It occurs to me that [whilst I know nothing about domains] since you now have your working Admin account & a spare Admin account you might want to make a system image then connect to that domain again.

• I suspect that the domain might only mess up Admin accounts that you are currently logged into at the time & leave your other Admin accounts alone.
• If this is true then you could routinely make a temporary [sacrificial] Admin account to connect with so that your normal accounts were kept safe.

All the best,
Denis

 

Can't login as local user after adding a computer to a domain

Your logon username for local is incorrect.

If the username created was "Admin", then the local machine logon is:

Workstation001\Admin (Omit "Local") It already knows you are logging onto the machine from the machine header.