How to setup new computer to replace Win2000 Server

[Vince]

I just got a new and much needed server to replace the one I am running now.
I want to make the transition as smooth as possible for the users. Is there
any documentation as to the best practice for doing this.
Some concerns: I can't name the new system the same as the old until I am
ready to take the old off the network but I have many shares on the old that
need to come over smoothly. I have hardware that needs to be moved over to
the new system (i.e. external scsi starage box and an AIT-1 Library). These
are a few of the many things going through my head.
Any info would be greatly appreciated.
Thanks
Vin

 

[J.C. Hornbeck [MSFT]]

In case you missed my previous reply:
--------------------------------------

Here's something that should help:

249694 - How to Move a Windows 2000 Installation to Different Hardware
(http://support.microsoft.com/?id=249694).

--
J.C. Hornbeck, MCSE
Microsoft Product Support

NOTE: Please reply to the newsgroup and not directly to me. This allows
others to add to and benefit from these threads and also helps to ensure a
more timely response. Thank you!

This posting is provided "AS IS" without warranty either expressed or
implied, including, but not limited to, the implied warranties of
merchantability or fitness for a particular purpose.

 

[Mike Brown - Process Manager]

I just got a new and much needed server to replace the one I am running now.
I want to make the transition as smooth as possible for the users. Is there
any documentation as to the best practice for doing this.
Some concerns: I can't name the new system the same as the old until I am
ready to take the old off the network but I have many shares on the old that
need to come over smoothly. I have hardware that needs to be moved over to
the new system (i.e. external scsi starage box and an AIT-1 Library). These
are a few of the many things going through my head.
Any info would be greatly appreciated.
Thanks
Vin

The best advice I can give you: you're gonna be home late. Phone the wife.

As long as I'm working in a small operation, I prefer to do things like
this:

1) Wait for all users to go home.
2) Close all programs and log all users off or shut down.
3) Rename the old server. Change IP if necessary. (You can wait until the
new server needs an IP and name, if you want to)
4) Start software load on the new server. Set the IP and name you want to
keep at this point.
5) Finish updates, load programs, etc. COPY (DO NOT MOVE) data after
recreating shares, etc.
6) Boot up each client and check connections. Make sure the shares remained
mapped correctly, and printers are connected.

Naming the server the same, and/or setting the same IP will make your
migration easier. Things like Outlook PST files, Word DOCs, and other files
that are accessed off a server will work the same this way. Printers shared
from a server will continue to function (you may have to check that "extra
drivers" loaded before are reloaded.)

Give it a month (or more, if you're concerned about it) before you erase
your old server. You never know what someone will ask for that you thought
wasn't important.