Windows server 2012R2 as additional domain controller along with Server 2008R2 fails

Question

On running ADPrep passes all prerequisite, but fails in the last stage with the below error:

ADPrep execution failed --> System.ComponentModel.Win32Exception (0x80004005): A device attached to the system is not functioning.

ADPrep log says:

Adprep requires access to existing forest-wide information from the schema master in order to complete this operation.

I'm using the credentials of Enterprise Admin (schema admin too) couldn't find why it still throws access denied error.

Solution 1

I'd comment on the original question so I can gather more info before posting my answer, but I don't have enough reputation yet as I'm new; go figure right :)

Anyway, I've ran into this twice for two different clients, one that was running SBS 2003 and another running 2008 R2 like you are. Both times had a few different tweaks but ultimately the solution turned out to be this:

1. Remove the Active Directory Domain Services role from the 2012R2 server if you have already installed it.

2. Reboot.

3. I know you already said you had Enterprise and Schema rights, but make sure you're using an account with Enterprise, Schema, and Domain admin creds.

4. Reboot the 2008 R2 DCs; yes all of them.

5. Go to the 2012 R2 server and add the Active Directory Domain Services role and reboot after it successfully adds.

6. Once logged back into the 2012 R2 server open Server Manager and on your post installation tasks you should see something similar to this screenshot:

picture source: http://blogs.interfacett.com/wp-content/uploads/2013/02/015-promote-domain-controller-server-2012-add-a-child-domain-ad-ds.png

click on the link "Promote this server to a domain controller" (ADPrep (both forest and domain) will run automatically without manually needing to have you run it from a command prompt)

7. Reboot the server once the dcpromo finishes.

If you are still having trouble please look for the value in ADSI Edit for your server entitled "ClaimIsValueSpaceRestricted"; it will either be true or false. Let me know if it's true or false and if it's greyed out or not. We can troubleshoot further should we need to, but steps 1-7 should resolve your issue.

Solution 2

Here is what I did to get it to work

• Setup a Windows server 2008
• Promoted it to a domain controller.
• I still got the ADPrep execution failed --> System.ComponentModel.Win32Exception (0x80004005): A device attached to the system is not functioning.
• Some discussion I saw suggested access to the schema master was the issue and recommended moving the schema master to the 2008 server.
• This wouldn’t work from the Schema Master MMC so I used ntdsutil.
• Went back to my 2012 server and attempted to promote it again. When given a choice out what DC to replicate from, I pointed to the 2008 server. I got a lot further that time, but still failed. Ran it again and pointed it to the old SBS 2003 server and it worked.

Comments

[Nandan]

Brad, i have already done all your 6 steps. I get the exception in ADPrep and never completes.

[Brad Bouchard]

I don't know if you can, but can you add a 2012 (non-R2) server and add it as a DC without any issue?

[Brad Bouchard]

Also, what about the ADSI Edit value I referenced, did you look at it?

[Nandan]

I didn't yet chenked a non R2 server yet as it was not my intention to build 2012(non R2), though its not a bad idea. It did failed in step 6 with the same old error "DPrep execution failed --> System.ComponentModel.Win32Exception (0x80004005)"

[Nandan]

I coudnt find this attribute in ADSI edit! Sorry can u pls help where to look at?

[Brad Bouchard]

Nandan, give me a little bit today to finish up a project and I'll get back to you. Don't worry, we will get you a solution.

[Brad Bouchard]

In ADSI edit you will want to look for the server object (the 2012 R2 one) and then you will find an attribute entitled ClaimIsValueSpaceRestricted

[Nandan]

Its now solved. Actual there was problem with DC running 2k8R2 was not allowing DCOM connection from 2012R2 server. No fix did solved the issue, atlast installed another 2k8R2 AD server then installed 2012R2 which worked atlast!

[BeowulfNode42]

Due to licensing SBS 2003 servers must hold all 5 FSMO roles, which means it must be the "Schema Master". There is however a grace period to allow for migration. After that the SBS server shuts down every couple of hours or some other thing to make it useless in the environment.