I currently have two DC's and both are WinServer 2003 (latest SP) and I just recently built a new WinServer 2008 R2 that I want to take over the DC roles of the PDC due to resources/age/etc. I installed the AD Services binaries on the Win2008 server and then ran dcpromo but I got a message telling me to run adprep first. I read all that I could on the adprep subject, downloaded the correct 32 bit version of it and ran adprep /forestprep successfully. Then I ran adprep /domainprep successfully. Then I ran adprep /domainprep /gpprep successfully. I then ran netdom query fsmo and confirmed there were no issues with the DC's. I forced a AD replication and confirmed everything else.When I run the adprep command it says it has already been run before successfully and that it didnt need to run it again.

I go back to my new server and run dcpromo and the same thing pops up. Yup it registered in another DNS. 10.0.0.61 was that in the ipconfig list anymore on the apps1 server? If not I'd check the old dns. Easy quick fix on the laptop hosts file edit. Adobe photoshop elements 10 ebay.

Contoh proposal kegiatan 17 augustus peringatan hut ri 72. This totally demonstrates what was so great about the fertile U.K.

Jan 19, 2009 - In Windows Server 2008, ADPREP follows the same logic. Server 2008 32-bit installation media to run ADPREP, so just download the file. Mar 26, 2010 - I want to bring a Windows 2008 R2 Server into an existing Windows 2003 domain. Surely the adprep.exe exists and can be downloaded from.

But that only works for the laptop. Same steps on laptop and OLD DNS server. A: Clear Server Cache B: Ipconfig /flushdns on OLD server C: Ipconfig /flushdns on laptop D: ping cccapps1 if still resovling.61 then one of the dns servers is holding that record.

Find the record. DELETE IT and then clear all caches again. Delete on both old and new dns if there is a forward lookup record for it there.

New sever might do a ipconfig /registerdns again to see if puts the crap IP back into dns. Then you'll have an idea where its coming from. Its basically registering the Second NIC's IP address and using that as the server IP address in dns due to it being registered first at some point. Nick3C wrote: beta - Schema Version - objectVersion 31 Your schema is still at Windows 2003 R2.

You will have to update this by running adprep /forestprep on the DC that acts as the Schema Master. How did you run this before? You said you downloaded it? You can put the DVD in your 2003 Schema Master and run adprep32 /forestprep that way, or you can copy the adprep folder on the R2 DVD to the Schema Master and run it from there.

You will also have to run adprep32 /domainprep on the Infrastructure Master. Yes I have run it on the Schema Master. Microsoft has a link from technet to a download of adprep.exe which comes with the both 32-bit/64-bit/IA versions and you extract it to the root of C: and then through cmd prompt run adprep /forestprep I type adprep /forestprep and it comes up with a message saying to make sure your Windows 2000 DC's are all at least SP2, blah blah blah. Then it says If all your Windows 2000 DC's are up to SP2 type C and press ENTER to continue.

I type in C and press ENTER and It comes back with this. C Forest-wide information has already been updated. [Status/Consequence] Adprep did not attempt to rerun this operation. It onl y says this because I have already run that earlier today and it appeared successful. The same message comes up if i do adprep /domainprep or adprep /domainprep /gpprep I.