Windows Forum

Ask something
Discussion Locked

Replacing NT server

0 helpful
11 replies

by bporter

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am going to be replacing one of our NT 4.0 servers. We are not upgrading the OS, just the equipment. We will be basically building the new server from scratch and transferring apps/data to the new unit.

The problem that I think I am facing isthat the client/server app which resides on this box requires the client to have the ip address and server name in the configuration to connect correctly. IP isn't a problem, but I can't build the server with the same name as the existing server - unless I build it off the network.

If I build the server off our network, won't I have a trust relationship issue when I add it to the network? I don't think the SAM would include this new server. Is there a workaround? I really don't want to visit each workstation just to change the host name if I can avoid it.

TIA,

Byron

11 replies

by jennisonn

Make sure you have a full off line backup, I know this works with NT backup. Build a load of NT on the new hardware, restore just winnt\system32\config file minus *.evt and system.* and make sure you choose to restore the local registry. Reboot. When the computer starts up you should have a computer that has the same SAM info. So make sure that you know the local admin password of the old machine and login using it. Next restore all of the other files on the machine minus the files on the root of C: and the \winnt\system32\config. After you restart you should have the same machine on new hardware. But remember test test test first.

by nettek

You can rename NT servers. Why don't you build the new server on your network, give it a different name, take the old server off the network, and then rename the new server to have the same name as the old server?

support.microsoft.com has articles on how to rename NT servers.

by green lantern

If this is indeed a server and not a DC you don't have a problem. Just create your new server on your network, Don't join it to the domain. After it is created, note the IP and name on the server being replaced. Remove this server from the domain. Now change the name of the new server to the old server name. Change the IP address also. After rebooting, join the domain. You should now have the new server with the same IP and Name as the old server. Just be aware there are some programs out there which refer back to the SID of machines and one of those can bite you after you have forgotten about replacing servers.
If your server has to be a member server in a domain for your software to be installed, don't install that software until after the new server has joined the domain.

by bohicam1

You are going to run into SID issues if you install a new server offline. My suggestion is that you get your new box and simply place the existing server hard drive into the new one. Once you have all your new hardware configured (new drivers and such)place the new harddrive in and from the winnt resource kit use the utility called robocopy.exe to transfer all the files and data over without losing permissions.
Good luck!

Mike

by stephen

Is it PDC? If so, just make the new one a BDC and then upgrade to a PDC after downing the old server. I have done this before and lost nothing.
Stephen

This discussion is closed to new replies.