Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 219
  • Last Modified:

Migrating from Windows 2000 to Windows 2003

Just looking for thoughts and possible issues we may incur with the following

We have a fairly decent sized client with the following

2 - 2000 domain controllers
1 - 2000 server running exchange 2000

various other 2000 & 2003 servers acting as file, print and citrix servers

100 + users always connected and active

We will be adding 2  Windows 2003 servers to replace the current end of life 2000 DC's and migrating AD over to them

the exchange server will stay as is with windows 2000 and exchange 2000

the 2 new 2003 servers will have new names

this client runs 24x7 and has experienced literally no noticeable downtime in 6 years so we would like to try not putting them through any major downtime now

thanks for any input
0
myrtlenet
Asked:
myrtlenet
1 Solution
 
MidnightOneCommented:
myrtlenet:

Add the new servers to the domain.
Run ADPREP /FORESTPREP
Run ADPREP /DOMAINPREP

promote W2K3 server to DC, then the other.
Reboot both.

Move over FSMO roles to new DCs.
Change DHCP to point to the new AD-integrated DNS servers (your new DCs) for DNS and WINS resolution as necessary
Demote the two current DCs

Go off to the pub for a few pints on the company tab.

HTH

MidnightOne
0
 
Jay_Jay70Commented:
Hi myrtlenet,

standard steps for me...

can be done quite easily with a clean install of the new server

**Note - If introducing a 2003 R2 Server into the network as a DC you will need to run the ADPREP tools from the second cd

\CMPNENTS\R2\ADPREP

you can also download here
http://www.microsoft.com/downloads/details.aspx?familyid=5B73CF03-84DD-480F-98F9-526EC09E9BA8&displaylang=en

this boosts the schema up to cope with R2 functionality
http://www.microsoft.com/windowsserver2003/r2/whatsnewinr2.mspx

1) Promote your new machine as an additional domain controller in an already existing domain - this will allow AD to replicate to the new server
2) Make sure DNS is AD integrated on your old DC to allow all DNS replications also
3) Transfer the FSMO roles to the new server
http://www.petri.co.il/transferring_fsmo_roles.htm
http://support.microsoft.com/default.aspx?scid=kb;en-us;255690
4) Make the new DC a Global Catalog under Sites and Services
http://support.microsoft.com/?kbid=313994
5) Deactivate DHCP on the old DC (if used) and recreate the scope on the new DC, note if you have a fairly complex or Large DHCP scheme you may want to export and import the database
http://support.microsoft.com/kb/325473/
6) Run DCDIAG to make sure all is well and replication is fine
7) Demote the old DC if you dont intend to keep it as a backup
8) Recreate Shares etc on the new server
9) Reinstall printers and share them etc....


this will allow you to have the complete AD directory on the new DC and clients will barely be aware of any changes
0

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

Tackle projects and never again get stuck behind a technical roadblock.
Join Now