Ok, so here's the lead-up to present day:
Windows 2000 domain with roughly 20 computers. 2 Windows 2000 DCs, 4 non-DC servers and the rest are client computers.
I was requested to install an Exchange 2003 server (not my choice, so please don't tell me how horrible it is! ). I had read many well documented sites stating that I had to prepare the domain because of the changes that are made to the domain/forest when a 2003 server is added to the domain. This domain had originally had an Exchange 2000 server running on it however the server had crashed (hardware failure). This was right about the time that I took over for the company taking care of their network.
Well, so I printed out and followed the MS document for adding a Windows SBS 2003 server to the Windows 2000 domain. I went through the OS installation, stopped the SBS installation and promoted the DC manually and then installed Exchange. The 2003 server SEES the others. The other servers SEE the 2003 server.
Ok, so as per the steps of the integration of the new SBS server I went through the process of transferring FSMO roles. All of them would transfer but the schema master. For some reason, the schema master role will NOT transfer from the 2000 DC to the 2003 DC.
After running dcdiag on all of the servers (they were all having DNS/AD replication errors), it was stating that the RPC server was unavailable... Everything pointed to DNS, yet they all resolve the DNS correctly. When I try to force replication, I get the following error:
The following error occured during the attempt to synchronize naming context schema from domain controller [2000 server] to domain controller [2003 server]:
The replication operation could not be completed due to a schema incompatibility.
This operation will not continue.
I'm hoping the solution won't be the inevitable... The only information on the web about this exact error are on the sites that list Windows error codes.
Thanks in advance.
Windows 2000 domain with roughly 20 computers. 2 Windows 2000 DCs, 4 non-DC servers and the rest are client computers.
I was requested to install an Exchange 2003 server (not my choice, so please don't tell me how horrible it is! ). I had read many well documented sites stating that I had to prepare the domain because of the changes that are made to the domain/forest when a 2003 server is added to the domain. This domain had originally had an Exchange 2000 server running on it however the server had crashed (hardware failure). This was right about the time that I took over for the company taking care of their network.
Well, so I printed out and followed the MS document for adding a Windows SBS 2003 server to the Windows 2000 domain. I went through the OS installation, stopped the SBS installation and promoted the DC manually and then installed Exchange. The 2003 server SEES the others. The other servers SEE the 2003 server.
Ok, so as per the steps of the integration of the new SBS server I went through the process of transferring FSMO roles. All of them would transfer but the schema master. For some reason, the schema master role will NOT transfer from the 2000 DC to the 2003 DC.
After running dcdiag on all of the servers (they were all having DNS/AD replication errors), it was stating that the RPC server was unavailable... Everything pointed to DNS, yet they all resolve the DNS correctly. When I try to force replication, I get the following error:
The following error occured during the attempt to synchronize naming context schema from domain controller [2000 server] to domain controller [2003 server]:
The replication operation could not be completed due to a schema incompatibility.
This operation will not continue.
I'm hoping the solution won't be the inevitable... The only information on the web about this exact error are on the sites that list Windows error codes.
Thanks in advance.