s0nic
asked on
Adprep error: 2003 server to windows 2008
Im having a problem with adprep. Heres what i have:
2 Windows Server 2003 no sp3
(Domain Controller) File, printer, server as well
(Exchange and BDC)
1 New 2008 Server
(The new PDC win server 2008 that I just built)
Im trying to replicate the DC to the 2008 box. Then making it my DC.
What Ive tried
-Restarted
-Check for any weird services. Such as Adware, Mcfee, antivirus, etc.
- run adprep.exe /forestprep on the 2003 DC (master sche. role, and logged in as admin) to have it prepared.
Then error!
-I've tried it even when after hours.
Another thing I just did to my 2003 DC Rasied the Function level from windows 2000 native to windows 2003. Another thing I checked it's not windows server 2003,sp2.
What I want to do is kill all of the services, and startup, in msconfig. then run it.
I'm new to this domain and trying to fix all the problems left behind.
Much thanks
2 Windows Server 2003 no sp3
(Domain Controller) File, printer, server as well
(Exchange and BDC)
1 New 2008 Server
(The new PDC win server 2008 that I just built)
Im trying to replicate the DC to the 2008 box. Then making it my DC.
What Ive tried
-Restarted
-Check for any weird services. Such as Adware, Mcfee, antivirus, etc.
- run adprep.exe /forestprep on the 2003 DC (master sche. role, and logged in as admin) to have it prepared.
Then error!
-I've tried it even when after hours.
Another thing I just did to my 2003 DC Rasied the Function level from windows 2000 native to windows 2003. Another thing I checked it's not windows server 2003,sp2.
What I want to do is kill all of the services, and startup, in msconfig. then run it.
I'm new to this domain and trying to fix all the problems left behind.
Much thanks
ADPREP WARNING:
Before running adprep, all Windows 2000 Active Directory Domain Controllers in t
he forest should be upgraded to Windows 2000 Service Pack 4 (SP4) or later.
[User Action]
If ALL your existing Windows 2000 Active Directory Domain Controllers meet this
requirement, type C and then press ENTER to continue. Otherwise, type any other
key and press ENTER to quit.
c
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
........................................................................
Adprep was unable to complete because the call back function failed.
[Status/Consequence]
Error message: Error(8224) while running ""C:\WINDOWS\system32\LDIFde.exe" -o Ob
jectGuid -d "CN=serversContainer-Display,CN=416,CN=DisplaySpecifiers,CN=Configur
ation,DC=KG,DC=local" -u -f "C:\DOCUME~1\ADMINI~1.KIR\LOCALS~1\Temp\2
\TMP3CD.tmp" -j "C:\WINDOWS\debug\adprep\logs\20090227131349" -s DC". See error file: "C:\WINDOWS\debug\adprep\logs\20090227131349\Displ
aySpecifierUpgradeLdifError.001.txt." (0x80004005).
[User Action]
Check the log file ADPrep.log, in the C:\WINDOWS\debug\adprep\logs\2009022713134
9 directory for more information.
Adprep was unable to update forest information.
[Status/Consequence]
Adprep requires access to existing forest-wide information from the schema maste
r in order to complete this operation.
[User Action]
Check the log file, ADPrep.log, in the C:\WINDOWS\debug\adprep\logs\200902271313
49 directory for more information.
The IDif.log states:
Connecting to "Doman Name"
The connection cannot be established
The error code is 8224
(But I can ping it from the new server and everything else)
ASKER
It checks good
Schema owner tdc.
Domain role owner tdc.
PDC role tdc.
RID pool manager tdc.
Infrastructure owner tdc
The command completed successfully.
C:\Program Files\Support Tools>
Schema owner tdc.
Domain role owner tdc.
PDC role tdc.
RID pool manager tdc.
Infrastructure owner tdc
The command completed successfully.
C:\Program Files\Support Tools>
Also validate that your schema can be written, see this article:
http://support.microsoft.com/kb/285172
Seb
http://support.microsoft.com/kb/285172
Seb
ASKER
This is pretty dangerous. I do have a backup but I'm nervous about doing this. What are my chances that this could cause an error and is there another way before attempting this? thanks
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
Ok I have a BDC so I'll give it a try tonight.
ASKER
Sorry it took so long to respond but I got injuired. However it worked!!! Thanks a bunch!!
Therefore the first thing I would do is install the support tools from a Windows Server CD and then run
netdom query fsmo
and ensure that all the servers listed are valid and live.
-M