I'm hoping someone can help me out with an error I'm getting in trying to promote an already Domain-Joined Server 2012 to a Domain Controller with the intention of making it the PDC. This Windows 2012 Server is brand new.
Current PDC is Windows Server 2003 R2 SP3 Standard 32-bit
Secondary DC is Windows Server 2008 Standard SP2 32-bit (off-site).
Forest Functional Level: Windows Server 2003
Domain Functional Level: Windows Server 2003
Server to Add: Windows Server 2012 Standard 64-bit
Able to add Server 2012 to Domain as Member.
Able to add AD DS Role to Server 2012
Server 2012 'Promotion to Domain Controller' Wizard gives following Error after all Pre-requisites have passed:
ADPrep execution failed --> System.ComponentModel.Win32Exception (0x80004005): A device attached to the system is not functioning
Looking in the ADPrep.log, the following error:
Adprep was unable to complete because the call back function failed.
Error message: An error occurred while attempting to bind to object default-Display using the path LDAP://server.domain.com/CN=default-Display,CN=406,CN=DisplaySpecifiers,CN=Configuration,DC=domain,DC=com. An operations error occurred.
winerror = 0x1f
NT BUILD: 9200
NT BUILD: 16384
Adprep was unable to update forest information.
Adprep requires access to existing forest-wide information from the schema master in order to complete this operation.
I've looked around and verified/tried the following:
Server 2012 is joined to domain.com as server1.domain.com
Server 2003R2 is PDC as server.domain.com
Only 1 NIC Card per server. IPs statically set on both.
DNS on 2003R2 is set to its own IP (not loopback).
DNS on 2012 is set only to 2003R2 IP.
Can ping server.domain.com from server1.domain.com and vice versa.
Verified Administrator login (used in Promote 2012 to Domain Controller Wizard) is part of Enterprise Admins, Schema Admins, Domain Admins groups.
Tried logging on to the local Administrator account on 2012 and manually entering Domain Administrator account when running promotion wizard.
Checking to ensure Remote Registry service on 2003R2 is running. It is.
Am I missing something?