Solved

Adding 2003 to a 2000 network

Posted on 2004-04-08
6
200 Views
Last Modified: 2010-04-19
Hi all, I have a Dell 2650 server with windows server 2003.  Our network infrastructure is 2000.  My plan is to put the 2003 server on the network and make it a DC.  Would that be a problem to the 2000 network when it is a Domain Controller?  The initial intent is to take away the DC role from a server that is also our Exchange server running 2000.  So to recap, can I add the 2003 server to the network of 2000 servers and make it a DC.  What would be, if any, the problems that I will encounter?

Thanks
0
Comment
Question by:ynb2628
  • 2
6 Comments
 
LVL 20

Expert Comment

by:What90
ID: 10783956
Hi ynb2628,

You will need to prepare your forest before simply installing a DC. Forest preparation involves extending and modifying the SCHEMA to support the additional features offered by 2003.

The full process is held in the readme files on the W2k3 cd and in the \DOCS folder.

However the very minimum required is to pre your forest with these commands:

On the schema master, at the command prompt, type "adprep /forestprep"
On the infrastructure master, at the command prompt, type "adprep /domainprep"

After you complete this procedure, you can leave your DCs running W2k or you can begin the upgrade immediately. There is no issue of co-existence and everything will work as before.

Taken from:
http://www.experts-exchange.com/Operating_Systems/Windows_Server_2003/Q_20938284.html
0
 

Author Comment

by:ynb2628
ID: 10784373
Thanks for the info, However my last question to you would be an Exchange 2000 one.  Seeing as though we are running Exchange 2000 in a full 2000 domain.  Would it be best to deal with this first rather than the DC?  Do I nee t upgrade the OS on the mail server to 2003 first?  The mail server is a DC, I can demote it from the DC role.  What would be the best way to deal with the Exchange server?

Regards  
0
 
LVL 20

Accepted Solution

by:
What90 earned 250 total points
ID: 10784582
Leave the Exchanger server to last. make the changes above, Add the 2003 server, make it a DC, wait until replication is working firn and there aren't any errors.

Then demote the 2000 DC. Exhange will need to be repointed to the 2003 DC server for Global Catalog needs and name resolution.

Once that's okay then upgrade the server exchange is on to windows 2003 after reading this:
http://support.microsoft.com/default.aspx?scid=kb;en-us;321648
http://forums.msexchange.org/ultimatebb.cgi?ubb=get_topic;f=4;t=001407

Hope that helps.
0

Featured Post

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Recently, I had the need to build a standalone system to run a point-of-sale system. I’m running this on a low-voltage Atom processor, so I wanted a light-weight operating system, but still needed Windows. I chose to use Microsoft Windows Server 200…
On July 14th 2015, Windows Server 2003 will become End of Support, leaving hundreds of thousands of servers around the world that still run this 12 year old operating system vulnerable and potentially out of compliance in many organisations around t…
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …

840 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question