DCPROMO for a Windows 2003 R2 64 bit member server to 2003 domain

[vianceadmin]

Okay, first let me say I have seen quite a bit of information about this topic but can't seem to figure out what is going on in my case...

I have a Win2003 domain with 2 DC's and wanted to introduce a win2k3 64 bit DC into the mix. Got the message about having to run the adprep on the schema master when trying to run dcpromo on the win2k3 64 bit server and when I tried to run the CD2 adprep from the 64 bit cd, it wouldn't open on the 2003 schema master because it said something about the file being the wrong type. So I ran the R2 32 bit adprep on the schema master and it appeared to upgrade fine. After updating the schema, I dcpromo'd the win2k3 64 bit server and it promoted to a DC with no issues and the server rebooted.

Now I have all kinds of replication issues. The other 2003 DC (not the schema master) won't replicate with the schema master that has all the FSMO roles and neither does the new 64 bit DC that I just promoted.

In the error logs of the non-schema master, I get:

While replicating the following schema object, a conflict was detected with the following existing attribute.

Schema object:
msDS-SourceObjectDN
Attribute:
CN=ms-DS-Source-Object-DN,CN=Schema,CN=Configuration,DC=*****,DC=net

As a result, inbound replication from the domain controller with conflicting schema will fail on the local domain controller.

User Action
If the attribute definition on the local domain controller is corrupted, restore the domain controller from backup media that was created earlier than the attribute schema object was modified.

Time of last modification:
2007-05-01 08:18:53

Additional Data
Error value:
8379 Schema update failed: duplicate OID.

Along with:

Internal error: The operation on the object failed.

Additional Data
Error value:
5 0000215F: SvcErr: DSID-03260277, problem 5003 (WILL_NOT_PERFORM), data 8543


If I try and force a replication between the two 2003 servers, I get the message:

The replication operation failed because of a schema mismatch between the servers involved.

The FSMO holder (main server that I ran the 32-bit adprep on) says in the event logs:


This server is the owner of the following FSMO role, but does not consider it valid. For the partition which contains the FSMO, this server has not replicated successfully with any of its partners since this server has been restarted. Replication errors are preventing validation of this role.

Operations which require contacting a FSMO operation master will fail until this condition is corrected.

FSMO Role: CN=Infrastructure,DC=viance,DC=net



Not sure what happened...Read alot of articles about just having to run R2 adprep on the schema master and all is well. Read another article about having to (after the R2 server is a DC) move the FSMO role over to the new R2 DC and then run the 64 bit adprep...

Any ideas? Sorry for the long email but I wanted to give as much info as I could...

 

[FloDiggs]

Are you sure that the ADPrep tool you used upgraded AD to version 31 and not version 30? The tool off of CD 2 should be the one you need, but like you said, the 64bit version won't work. Where did you get the 32-bit version? You can check the version of AD in the registry at HKLM\system\CurrentControlSet\Services\NTDS\Parameters. Look at the Schema Version entry. It should be 31.

 

[vianceadmin]

Yes, it was off the cd and checked the version and is 31.

Noticed the schema master was sp1...Would that matter?

Are there any differences between R2 32-bit adprep and R2 64-bit adprep?

Since I couldn't run the 64-bit adprep and ran the 32-bit but have a 64-bit DC, would that matter?

Thanks for your help!

 

[FloDiggs]

From what I understand, the version of ADPrep just needs to match the server it is running on. The two version make the same changes to the Scheme, etc., they are just made for the specific verision of Windows. Have you run DCDiag or Replmon to see if you get any additional information from those tools?

 

[vianceadmin]

For AD replication monitor under the CN=Schema,CN=Configuration for the schema master, it shows the other 2003 server with a replication failure: The reason is: The replication operation could not be completed due to a schema incompatbility.

 

[FloDiggs]

Check the Schema Version on the new server. Maybe it is 30. I know that sounds crazy, but R2 uses two CDs. CD 1 is essentailly Server 2003 with SP1 slipstreamed in. It doesn't become R2 until you install what is on Disk 2. If that part of the installation didn't work correctly, your new server may be a version behind in terms of AD.

 

[vianceadmin]

Schema version on the new server is 31 as well...(did use disk 2).

Taking the new 64 bit server out of the picture, as soon as I ran the adprep, the two 2003 servers that I had that were DC's couldn't replicate..

 

[FloDiggs]

Did youa allow time for everything to replicate between the two steps of adprep?

 

[vianceadmin]

just ran the adprep.exe /forestpre (domain prep) didn't need to run it said...Waited a few minutes and then dcpromo'd the 64bit server to a DC...That was yesterday and still getting replication errors...Would sp2 have anything to do with it?

Once you have a 64 bit DC, do you transfer the schema master role over to this new server?

 

[FloDiggs]

Just to clarify, you ran adprep /forestprep and then ran adprep /domainprep, or did you just do forestprep?

 

[vianceadmin]

I just did the adprep /forestprep (Read that I didn't have to do the /domainprep if I already had a 2003 DC). I did try and run it afterwards but said it didn't need to run.

 

[FloDiggs]

Back to your question about roles. You shouldn't have to transfer the schema master to the new server. That is what the adprep is for: to make sure that the schema is ready for 2003 R2. Which servers are holding which roles? You can use "netdom query fsmo" to find out.

 

[vianceadmin]

Yeah, this is weird...Researched yesterday and today and nobody else seems to be having this issue...

Server 1 has all the FSMO roles (the server that I ran the /forestprep on). I have one other 2003 DC and then the 64-bit DC.

 

[FloDiggs]

Well, it would be a bad idea to start transferring roles before we fix the replication issue. KB309628 describes all the changes adprep makes to a 2000 domain's schema and such, but I can't find one that explains what it does to 2003 in preperation for 2003 R2 so that you could verify that all of the changes were made correctly. That may be a good place to start.

 

[FloDiggs]

Any progress?

 

[vianceadmin]

Ended up forcing a dcpromo on the 64 bit machine and one of the other original DC's that I had since they weren't replicating because of the schema.

After both were demoted, I cleaned up DNS and AD with the ntdsutil and then promoted both back to DC's...Everything looks good.

 

[PronetservFL]

This thread about the adprep process was very helpful. Maybe the participants can lend a hand on one more related problem. My customer has a Windows 2003 domain. He just purchased a Windows 2003 R2 X64 server, and I am suppose to make this a domain controller. He only has the 64 bit installation disks and I need a Windows 2003 R2 32 bit version of adprep.

Anyone know where or how I can get a Windows 2003 R2 32 bit copy of adprep to run on the 32 bit Windows 2003 domain controller aside from buying the media kit for 32 bit?

Thanks!

Tony