new 2012 domain can't join a machine-unique sid identical

hello

I am building a new 2012 domain. I deployed a new 2012 ovf and configured a new DC.
When I try to join a machine to the domain , I get the error:
"the domain join cannot be completed because the SID of the domain you attempted to join was identical to the SID of the machine.".....

Please help.

thank you
pulke13Asked:
Who is Participating?
 
Patrick BogersConnect With a Mentor Datacenter platform engineer LindowsCommented:
Ok, did you run it from the %WINDIR%\system32\sysprep directory  ??

Maybe you should open a command prompt, go to this path %WINDIR%\system32\sysprep directory and run:      sysprep /oobe /generalize    (this should release the SID)

After reboot Windows should run the 'welcome to windows routine'
1
 
Patrick BogersDatacenter platform engineer LindowsCommented:
Hi

You need to renew the SID for the member server by running sysprep.exe
And try to join again.

I suspect you use the same image for multiple machines?!
0
 
pulke13Author Commented:
yes, same image- wrong.
I tried sysprep without any good.

Should I do sysprep to the dc ?
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

 
Patrick BogersDatacenter platform engineer LindowsCommented:
No, i would not run sysprep on a active domain controller.

What did sysprep say and do? What happened after rebooting?
0
 
pulke13Author Commented:
It asked for a new password and language but nothing changed after reboot.
0
 
Will SzymkowskiSenior Solution ArchitectCommented:
If you are using a the same image to create the DC as you are for clients joining, it is a good practice to "always" do a sysprep before make a computer part of a domain or using as a domain controller. If you have not gotten far with this DC, i would consider doing a sysprep on it as well.

If you do this you will need to re-create the domain.

Server 2012 is very picky on SID's and using sysprep to get machines connecting correctly. Past OS versions 2003/2008/etc did not have this issue. Simply having an image that was off the domain and adding it to the domain generates a new SID automatically (and worked in previous versions) but 2012 is more sensitive.

Will.
0
 
pulke13Author Commented:
now when I try to connect to the domain I can't - there is a dns error.
0
 
pulke13Author Commented:
I reconfigured dns and now it works.

thank you!
0
 
Patrick BogersDatacenter platform engineer LindowsCommented:
Cool ! youre welcome.
0
All Courses

From novice to tech pro — start learning today.