?
Solved

Need advice about moving a Windows 2000 Server to new hardware that will be running Server 2003

Posted on 2008-06-21
6
Medium Priority
?
258 Views
Last Modified: 2013-12-05
I have an HP server (true server hardware, raid, etc.) that has windows 2000 server running on it.  I have a new DELL server (again true server running raid, etc) that has windows 2003 server installed on it.  I want move from the 2000 server to the 2003 server and the following are my stipulations/details:

1.  Server name and IP address must remain the same
2.  Must migrate over all user accounts
3.  Must migrate all data
4.  Terminal services is currently being used and must be switched as well
5.  Downtime must be minimal (like a weekend)

My plan of attack is to upgrade the existing 2000 server to 2003 server using transitional licensing.  Then clone that upgraded installation to the new DELL server and perform a repair installation of windows.  Then install all new drivers that are needed and bring back online.

The only thing I am not familiar with is cloning raid hard drives.  I imagine I should image the old server through the network and place that image on the new server.

Based on what I have and my plan of attack, are there any suggestions or advice anyone can give me to make this procedure go smoothly?

Thanks in advance
0
Comment
Question by:shinomen
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
6 Comments
 
LVL 96

Accepted Solution

by:
Lee W, MVP earned 1000 total points
ID: 21837974
I wouldn't do that...

Why does the server name and IP need to remain the same?  This may be the only thing that's complicating your plan. Is tis a domain or a wrokgroup.

If it does have to remain the same, then you need a six step approach (I call them stages below)

Stage 1:
Setup a temporary server and migrate Active Directory to that.  This temporary server can be a virtual server.

Stage 2:
Migrate all data to the new server which would have a DIFFERENT Name and IP (for now).

Stage 3:
Demote and remove the old server

Stage 4:
Givve the new server the old server's IP and name (change it).

Stage 5:
Promote the the new server to be a DC, transfer DNS, DHCP, etc.

Stage 6:
Demote the temporary server and remove it.
0
 

Author Comment

by:shinomen
ID: 21837993
It is a domain controller.  They have a billing and accounting software that has been ported from a unix based system to run on windows and every terminal connects either to the name of the server or the ip address of the server. (it's a mixed environment).  I have done repair installations on windows xp serveral times successfully and one time successfully on a windows server 2003 domain controller.  So I know if can be done, but again just looking for advice to make it easier.

Thanks.
0
 
LVL 96

Expert Comment

by:Lee W, MVP
ID: 21838018
Well, you can't do it here... (almost certainly).  The copy of 2003 that came with the server is almost certainly an OEM copy which will NOT do an upgrade.  So while you may be able to repair 2000, you couldn't get it to 2003 without using my procedure or possibly spending money on third party software I'm not familiar with.
0
 

Author Comment

by:shinomen
ID: 21839203
I read some time back in the past that microsoft has what are called transitional licenses that allow a server OS to be upgraded temporarily because it is getting moved.  So basically they give you an upgrade license that works for something like 30 days (I don't remember the time length) so that you can upgrade the 2000 server then you can transfer using whatever method you use.   So I figure that if the OS's are the same then the repair will work.

Thanks for your replies so far.  Anyone else have any thoughts on this?
0

Featured Post

Veeam Disaster Recovery in Microsoft Azure

Veeam PN for Microsoft Azure is a FREE solution designed to simplify and automate the setup of a DR site in Microsoft Azure using lightweight software-defined networking. It reduces the complexity of VPN deployments and is designed for businesses of ALL sizes.

Question has a verified solution.

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

Welcome to my series of short tips on migrations. Whilst based on Microsoft migrations the same principles can be applied to any type of migration. My first tip Migration Tip #1 – Source Server Health can be found here: http://www.experts-exchang…
Issue: One Windows 2008 R2 64bit server on the network unable to connect to a buffalo Device (Linkstation) with firmware version 1.56. There are a total of four servers on the network this being one of them. Troubleshooting Steps: Connect via h…
If you’ve ever visited a web page and noticed a cool font that you really liked the look of, but couldn’t figure out which font it was so that you could use it for your own work, then this video is for you! In this Micro Tutorial, you'll learn yo…
In this video, Percona Solutions Engineer Barrett Chambers discusses some of the basic syntax differences between MySQL and MongoDB. To learn more check out our webinar on MongoDB administration for MySQL DBA: https://www.percona.com/resources/we…
Suggested Courses

770 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