Go Premium for a chance to win a PS4. Enter to Win

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

Upgrade from Win 2000 SP 4 to Win 2003

What are the best practices to follow when upgrading a Win 2000 server to a Win 2003 server? My LAN setup is as follows: Win 2000 server - SP4, DC, AD, Norton (This unit is up for upgrade), Win 2003 (Application server), Win 2003 (IIS server), Win 2003(ISA server) + LAN. Should I install Win 2000 SP4 on a test unit to facilitate replication and then upgrade the Win 2000 DC to win 2003?
0
wilkersons
Asked:
wilkersons
  • 3
  • 3
1 Solution
 
swinterbornCommented:
Depends on how cautious you want to be. Ideally, take a spare server, build to Win2k sp4, and run dcpromo to make it a DC in the existing domain. Leave it for a few days to make sure there are no replication errors, then when you are ready to upgrade, remove the spare server from the network. That way if anything does go wrong with the upgrade, your AD database is safe. Give the upgrade a couple of days to settle down, making sure there are no errors, then reconnect the spare to the network, check replication is functioning, and run dcpromo to demote the spare back to a member server, before killing it. Of course, the upgrade is meant to be totally secure and painless, so all this will be totally unnecessary ,.... ;,)

Cheers
0
 
wilkersonsAuthor Commented:
>>Give the upgrade a couple of days to settle down, making sure there are no errors, then reconnect the spare to the >>network, check replication is functioning, and run dcpromo to demote the spare back to a member server, before killing it.

You mean reconnect the upgrade to the domain right??

So I need to promote a spare to a DC and let replication start after which
remove it from the domain
upgrade the Win2k SP4 to Win2003
let the upgrade settle down for a few days
join the spare to check for replication
demote the spare to member server
0
 
swinterbornCommented:
Thats it - the spare will just be disconnected from the network (unplug the patch cable) , not removed from the domain, if you remove it from the domain, it will no longer be a DC, your aim is to preserve a pristine copy of the AD database during the upgrade:

Promote spare
disconnect spare from network
upgrade to win2003
let upgrade settle down
reconnect spare to check replication
demote spare

Cheers
0
Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

 
wilkersonsAuthor Commented:
Ok looks good I have tried promoting a Win2003 server to additional DC and the replication failed. The primary DC is a Win2000 sys. What might be the reason. Is there compatibility issues between a 2003 and 2000 os?
0
 
swinterbornCommented:
No compatibility issues at all. Could be a number of reasons why it failed, lack of disk space, DNS misconfiguration, network connectivity, etc, etc. It's always worth making sure a server is healthy and connecting perfectly with the domain before starting dcpromo.
0
 
wilkersonsAuthor Commented:
Ok just finished promoting the spare to DC will let it stay that way for the next day or so ...
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

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