upgrading from server 2000 to server 2003

[johnmac60]

I recently added a new windows server 2003 to a 2000 domain.

I ran all the required adprep & domain prep on the 2000 server and then dcpromo'd the new 2003 server.

The 2000 server has remained as the Primary DC Contoller and I would like to make the new server the Primary Dc Controller. See other questions at bottom.

If I shut down, not demote, the 2000 server, I can still log in to the network, but it is extremely slow.

I have run DCDIAG and NETDIAG with the following results -
Just the error messages only.

Starting test: systemlog
* The System Event log test
An Error Event occured. EventID: 0x00000457
Time Generated: 07/23/2007 10:24:27
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 07/23/2007 10:24:27
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 07/23/2007 10:24:29
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 07/23/2007 10:24:29
(Event String could not be retrieved)
......................... MONTYDC2003 failed test systemlog

NETDIAG produced numerous error messages

Testing the WINS server
Local Area Connection
Sending name query to primary WINS server 192.168.1.4 - Failed
There is no secondary WINS server defined for this adapter.

Testing trust relationships... Failed

WINS service test. . . . . : Failed
Sending name query to primary WINS server 192.168.1.4 - Failed
There is no secondary WINS server defined for this adapter.
The test failed. We were unable to query the WINS servers.
IPX test : IPX is not installed on this machine.

Query for DC DNS entry failed....

Cannot find PDC emulator in domain...

Failed to enumerate DC's by using browser...

The question is - Do I need to run WINS in the new server, I only have XP machines and how do I make the 2003 server, the primary server.

I have searched the forum and microsoft for answers and found none.

Thanks,

John

 

[itsp1965]

Well you can't just shutdown a domain controller (especially if it holds all FSMO roles and is also THE global catalog server for your domain). If you are planning on removing this server;
1. Transfer all FSMO roles to the new server. Note you will also need to move your DNS (and WINS if you have installed it) services also
2. Make this new server also a Global Catalog server
3. Demote the existing Windows 2000 Domain controller

 

[Cstorms]

You will also need to have dns installed on the new server as well. Allow time for replication between the servers and make sure to rid yourself of any old entries referencing the old DC, then dcpromo the old one out.

 

[johnmac60]

Ok,

I have done the following -

DNS is running on the new server
I'm using the instructions in Microsoft KB 324801 to transfer the FSMO roles.

Step 1 - I have used the mmc snap in to change the Active Directory Schema and that gose as the directions say. But if I go out of MMC snap in and look, the old server is listed again.

Step 2 - Active Directory Domains and Trusts already says the new server is the domain controller, which appears to be right according to the instructions.

Step 3 - Active Directory users and Computers - Operations Master now says the RID, PDC and infrastucture are all offline and cannot transfer them to the new server.

What should I try next?

John