Skip to main content

Does Windows Server 2008 R2 allow you to rejoin a disjoin client to the domain with the same SID?

By
To test this theory, I created a Snapshot in Hyper-V of a Windows 7 Client. Once I completed this I had Active Directory reset the password to the client. Next I applied the snapshot that I just took to create a disjointed account.

When an attempt to log in is made, this is the error:
image

The question from class is if I put this client in a workgroup, and then back in a domain, will it have the same SID?

First off, I went into Active Directory and recorded the SID for the clients computer object.
image

Next I logged in as the local administrator on the client and first put the client in a workgroup, and then back in the domain.  One thing that I did notice during this process.  Even though the computer could not create a secure channel to the domain controller, when I took it off the network, the computers object was disabled.

image

Once the client was joined to the network, its account re-enabled.
Also, the SID was reused.

image

On a side note.  This client was used previously to test the ability for a standard user to add a client to the domain without Domain Administrator credentials.  In that process, the users SID was recorded in the computer objects ms-DS-CreatorSID.  Even thought I rejoined the client to the network using a Domain Admin account, the original user who added this client to the domain still has their SID listed in the ms-DS-CreatorSID attribute of the clients account.
Labels:

Comments

Anonymous said…
Hi, Did you try deleting the machine account after you removed the computer from the Domain and before rejoining it back to the Domain?
April 20, 2011 at 7:12 AM
Jason Yoder, MCT said…
If you delete the computer object from Active Directory and then rejoin the client, you will get a new SID. However, if you first restore the object from the Active Directory Recycle Bin first, and then join the client back into the domain, the original properties of that object, including the SID, will be retained.
May 2, 2011 at 1:04 PM
Post a Comment

Popular posts from this blog

Sticky Key problem between Windows Server 2012 and LogMeIn

By
This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this.  First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .
6 comments
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

Where did a User’s Account Get Locked Out?

By
Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...
18 comments
Read more