Reset Trust Relationship Without Rebooting

On a domain joined Windows Client, you may get an image like this:

(From Windows 8)

This means that the client computer’s account with the domain had a password change but for some reason your client does not know the password. This can happen if you restore your client operating system from a backup. To fix this, we would normally rejoin the client to the domain. This would cost us a reboot. Here is an alternative.

· Log into the client as a local administrator.

· Open PowerShell

· Type Test-ComputerSecureChannel

Notice the response back is False That means the secure channel cannot be negotiated between the client and the domain controller. The secure channel allows for your client to verify that it is talking with the correct domain controller. If the secure channel does not work, then you cannot log in. Here is how to fix this.

· Type Test-COmputerSecureChannel –Credential <Domain/DomainUser> -Repair and press Enter.

· Provide the domain users password and press Enter.

Notice the response is now True.

· Log off as a local user and log in as a domain user.

You should now be able to log in without a reboot.

This will also work on Windows 7.

Comments

Anonymous said…

Been trying to get this to work in Windows 7 but keep getting the error that the -credential parameter cannot be found.

Any suggestions to be able to run the command with a domain account?

March 11, 2016 at 12:54 PM

Jason Yoder said…

My tests were with PowerShell 3. What version are you using?

March 11, 2016 at 1:15 PM

Adding a Comment to a GPO with PowerShell

As I'm writing this article, I'm also writing a customization for a PowerShell course I'm teaching next week in Phoenix. This customization deals with Group Policy and PowerShell. For those of you who attend my classes may already know this, but I sit their and try to ask the questions to myself that others may ask as I present the material. I finished up my customization a few hours ago and then I realized that I did not add in how to put a comment on a GPO. This is a feature that many Group Policy Administrators may not be aware of. This past summer I attended a presentation at TechEd on Group Policy. One organization in the crowd had over 5,000 Group Policies. In an environment like that, the comment section can be priceless. I always like to write in the comment section why I created the policy so I know its purpose next week after I've completed 50 other tasks and can't remember what I did 5 minutes ago. In the Group Policy module for PowerShell V3, th

Return duplicate values from a collection with PowerShell

If you have a collection of objects and you want to remove any duplicate items, it is fairly simple. # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2 # Remove the duplicate values. $Set1 | Select-Object -Unique 1 2 3 4 5 6 7 What if you want only the duplicate values and nothing else? # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2 #Create a second collection with duplicate values removed. $Set2 = $Set1 | Select-Object -Unique # Return only the duplicate values. ( Compare-Object -ReferenceObject $Set2 -DifferenceObject $Set1 ) . InputObject | Select-Object – Unique 1 2 This works with objects as well as numbers. The first command creates a collection with 2 duplicates of both 1 and 2. The second command creates another collection with the duplicates filtered out. The Compare-Object cmdlet will first find items that are diffe

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory. To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

Jason Yoder, MCT

Search This Blog