Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 380
  • Last Modified:

Windows 10 client lost trust relationship with 2012r2 domain

One of the PCs we upgraded to windows 10 will not login to the domain because the machine has lost the trust relationship.
If you enter a bogus password it knows it is incorrect.
A correct password will produce the issue.

No longer have the local machine user credentials.  When trying to log into the local machine with user "administrator" and a bogus password it responds with a this account has been disabled message.

Thought I would ask if there is a resolution before rebuilding the machine from scratch.
Thanks
Karl
0
kbettencourt
Asked:
kbettencourt
2 Solutions
 
Scott CSenior Systems EnginerCommented:
Did-join the machine from the domain by joining it to a workgroup.  Make sure the machine account has been deleted from AD, then join it back in again.

You may need to power down the machine and unplug it from the wall to make sure no junk information is left in the NIC.

Ooopps...never mind...just read you don't have the local PC creds.

At this point your only option is to rebuild the machine from scratch as you said.
0
 
Adam BrownSr Solutions ArchitectCommented:
Make sure you the computer isn't attempting to log you in using the local administrator. That may be the account that is disabled. When you type in "Administrator" as your username, since Windows Vista came out and changed the login system, the login screen will default to the local administrator account if you just enter "Administrator" as your user name. You need to type in the domain if you want to log in as the domain admin. Use domain\administrator or administrator@domain.local.
0
 
Rich WeisslerProfessional Troublemaker^h^h^h^h^hshooterCommented:
You can try resetting the machine account for that Windows 10 computer.  From a server logged in as an administrator:  "dsmod computer <ComputerDN> -reset"

Option 2:
I don't know if Windows 10 has the equivalent to safe mode.  Booting in safe mode in older OS would re-enable the disabled local administrator account.  (Possibly old knowledge though, I don't know for certain that it applies in Windows 10.)
1
What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

 
Rich WeisslerProfessional Troublemaker^h^h^h^h^hshooterCommented:
Here's more on the 'Reset Computer account' option.  (Why, and a GUI option to accomplish.  Hint: you can do it in ADUC, right on the computer object.)  ;-))
1
 
McKnifeCommented:
The computer account pw is something the client and the DCs both know and synchronize. So if you reset it at the server, the client side is unchanged. I don't see how this should help.

Donwload the pogostick bootdisk (google it) and reset  the password of the local administrator (blank it) and make the account usable (=enable it). Then logon with it and trigger a sync with the DC like this:
from an elevated powershell prompt, launch:
Reset-ComputerMachinePassword -Credential yourdom\yourdomadmin

Open in new window

(you'll be asked for the domain admin password).
Afterwards, you can login with a domain account again.
0
 
Rich WeisslerProfessional Troublemaker^h^h^h^h^hshooterCommented:
If you know a domain account that was an administrator on the local box, that administrator has logged into the system, and you haven't disabled credential caching -- disconnect the NIC, and login using the domain administrator.
0
 
kbettencourtAuthor Commented:
Thanks all for the replies.  Will give it a try in the morning.
0
 
kbettencourtAuthor Commented:
Thanks.  I was able to contact the person that installed the OS and have the local machine password now.  
Also was able to get in with my domain admin account after disconnecting the NIC and booting.  That one was a simple intuitive and logical method.  
Also liked the pogostick bootdisk.  It works.
0

Featured Post

Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now