Windows 10: Disabled a computer account and then enabled it but still cannot log in to the domain

Hi AllDisabled a computer account and then enabled it but still cannot log in to the domain. Still get trust relationship error. The workstation has no local admin account to log in to and re add to domain.The domain user is not an admin to the PC.Is there any other way to re establish domain membership? Apart from using Hirens to boot and enabling admin account etc and then re joiningThe computer account is re enabled on AD

:)

 

Auto logging into disabled account Windows 10

I was able to fix this by doing the following:

• Boot up the computer, then kill the power after startup is complete.
• Do step #1 again. (Two crashes within two minutes after startup will cause Windows to boot into Safe Mode automatically.)
• You will be forcibly logged in to Safe Mode with the Administrator account.
• Enable the Administrator account, and setup your normal account as needed.
• Restart again, you will auto login as the Administrator account (which has now been enabled).
• Log out of the Admin account, and log in with the normal account.
• Disable the default Administrator account once again.

 

UnattendedJoin error: failed to find the domain data (0x6e)

Thanks for the suggestion! I don't want to add a domain account, as this is a generic unattended install that will be used for all company machines. Do you think it's possible that the computer would join the domain if, instead of using UnattendedJoin in specialize, I used your steps but left out the specific account? The other thing I was thinking was to use a generic account to allow the domain join during the specialize step. I added a machine password in the UnattendedJoin component, and instead of getting the error listed above, I got an authentication error, which makes me think I could probably do a secure join instead of the unsecure join. Thoughts?

 

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.