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: 885
  • Last Modified:

SID duplicated mystery on a host but not created from an image file ?!?

As you maybe know, when more than one server are using the same SID it can keep from sending emails from OWA (Exchange 2010)
http://www.petrikb.com/email-stuck-in-drafts-folder.htm

This is exactly what we've been living with recently.  Both DCs (VM) we using the same SID.  But each Exchange server had a unique SID.  

So I demoted a DC.  Then a new VM has been created.  This time Windows 2008 R2 has been installed from the CD, no image, no sysprep, nothing.  I ran DCPROMO.  

But the new server has the same SID !    How come ?  It has a different name, it comes from a fresh Windows installation.  I don<t get it but maybe someone knows ?

However, Exchange is no longer preventing the emails to to be sent out.  

Thank you
0
quadrumane
Asked:
quadrumane
  • 7
  • 6
  • 2
4 Solutions
 
elpwCommented:
Dupilicate SID's occur when cloning workstations and servers.  You should use a SID Changer whenever initializing a new workstation/server from a clone.  NewSID.exe (can search and dowload free from internet) is an application can be used to change the SID on such clones.  In the future you should consider using Sysprep which automatically generates a new SID.
0
 
quadrumaneAuthor Commented:
Thanks

But as I said, the new server has not been created from an image or from a cloned vm.  So it shouldn't have the same SID.
0
 
geowrianCommented:
Actually, that information is outdated and no longer correct. NewSID has been retired as it is not necessary. Duplicate machine SIDs should not cause problems. The NewSID program, as well as many other SID changers, have many various issues on Windows Vista, Windows 7, and Server 2008. Read the article here:
http://blogs.technet.com/b/markrussinovich/archive/2009/11/03/3291024.aspx

The issue is caused by cloning a PC already on the domain. This creates duplicate domain SIDs, which will have many various problems. It is highly recommended to remove the PC from the domain and then use sysprep prior to imaging a system.

As for the duplicate SIDs you are seeing on the DCs, are you referring to the domain SID or the machine SID? The local SID on the DCs should be the same, while the domain SID should be the same as the local SID except for the very end of it which should be unique on the domain (similar to having how RIDs). See here:
http://www.excaliburtech.net/archives/117
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
quadrumaneAuthor Commented:
All servers with the same SID but one have been completely removed.  But I had to keep one (a DC)  Maybe this server is assigning the same SID to all new DCs although the new DC  has not been created from an image.  
0
 
geowrianCommented:
To restate my above comment:
As part of promoting a PC to a DC, it will change the local SID to match all the other DC's local SID. It should also create a domain SID that is the same as the local SID except with another part appended to it, which should be unique. Having duplicate machine SIDs for all the DCs is normal. Just make sure the domain SIDs are unique.
0
 
quadrumaneAuthor Commented:
Here is what I got:

The new server (Windows 2008 R2 has been installed, not from an image)
SID for \\S1-DC-002:
S-1-5-21-1977992388-383641019-900119157

the old server (this one has been created from a clone)
SID for \\S2008DC01:
S-1-5-21-1977992388-383641019-900119157

It looks like it is the local SID
0
 
geowrianCommented:
Using psgetsid.exe I'm assuming. I just did the same on my DCs and got the same type of results. All DCs were created from scratch. This is normal.

You can check the domain SID in the attributes of the computer via LDAP tools or Active Direttory Users and Groups.
0
 
quadrumaneAuthor Commented:
but in the attribute in object editor the same is almost the same except for the last 4 digits

S-1-5-21-1977992388-383641019-900119157-1000

S-1-5-21-1977992388-383641019-900119157-1256
0
 
geowrianCommented:
That's good & completely normal. That is what you should be what you are seeing.
0
 
geowrianCommented:
Wow - I need to slow down my typing! I meant to say:

That's good & completely normal. That is what you should be seeing.
0
 
quadrumaneAuthor Commented:
Ok I now understand.  I didn't check the local SID before promoting the new server.  So now it has the same local SID but it's normal.

Correct me if I'm wrong
0
 
geowrianCommented:
That is correct.
0
 
quadrumaneAuthor Commented:
And me I should refresh my browser ;-)  Ok so all is said, all is normal, all is good

Thank you very much !
0
 
elpwCommented:
geowrian:  Thanks for the info... shows how long it's been since I've ran into this problem.  It has long been common practice not to clone Windows installed drives; as mentioned, a number of years since I've seen the problem.
0
 
geowrianCommented:
No problem. I have been following Mark's website and blog for years, so I am aware of why he made the tool. I was also surprised by his findings as changing the SID was common practice. I also assumed it was necessary like nearly everybody else.

Another department at my employment also encountered a number of the SID change issues on Windows 7 computers that were being imaged, so some good reading and good communication saved everybody a lot of headaches.
0

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

  • 7
  • 6
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now