Skip to main content

Reset Trust Relationship Without Rebooting

By

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

clip_image001

(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

clip_image002

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.

clip_image003

· Provide the domain users password and press Enter.

clip_image004

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.

Labels:

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
Post a Comment

Popular posts from this blog

How to list all the AD LDS instances on a server

By
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.
Post a Comment
Read more

How to run GPResult on a remote client with PowerShell

By
In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.
Post a Comment
Read more

Error icon when creating a GPO Preference drive map

By
You may not have an error at all.  Take a look at the drive mapping below. The red triangle is what threw us off.  It is not an error.  It is simply a color representation of the Replace option of the Action field in the properties of the drive mappings. Create action This give you a green triangle. The Create action creates a new mapped drive for users. Replace Action The Replace action gives you a red triangle.  This action will delete and recreate mapped drives for users. The net result of the Replace action is to overwrite all existing settings associated with the mapped drive. If the drive mapping does not exist, then the Replace action creates a new drive mapping. Update Action The Update action will have a yellow triangle. Update will modify settings of an existing mapped drive for users. This action differs from Replace in that it only updates settings defined within the preference item. All other settings remain as configured on the ma...
1 comment
Read more