Retiring a server

We need to retire a server, let's call it serv1, but the
servers name is hard coded into many jobs. This server is
also the PDC.

We have another server that is being build to replace
serv1, which currently called serv2, but it's hardware
platform is very much different although it's drives are
the same size than the old serv1. Serv1 is a old 500 Mhz
PII where the new server is a 2.6Ghz Celeron running on a
SuperMicro P4SCi motherboard.

I'm done serv2 must be called serv1 and also contain all
of the file with the correct rights from serv1. Users must
be able to connect using the old server name without any
changes to shares or server names hard coded into programs.

I have the BackupEXEC 9.1 that is currently used to backup
serv1, and other systems on the network, so one option
would be to do a full server restore of serv1 onto serv2.
The problem there the difference in the hardware
platforms.

I've thought of serveral ways to do this but I would like
suggestions on how to get from A to B on this one in the
safest and fastest way.

Thanks

Option #1
You can't rename a DC and you probably won't get away with tape-restoring it
to the new hardware if the differences are very great between the two. Leave
it in place until all the "jobs" have been reajusted to the new name, then
demote it to a BDC then remove it.

Option #2
1. Build a temporary DC (serv3??) make it the PDC (which should
automatically demote Serv1 to a BDC).
2. Remove or just unplug the serv1 and keep it away from the system.
3. Rebuild Serv2 from scratch and name it Serv1 and make it a BDC.
4. Promote Serv1 to a PDC (should automatically demote Serv3)
5. Do what you will with the Serv3 or old Serv1, you could keep Serv3 as a
BDC or rebuild the old Serv1 as a BDC with a new name.

If you do it on the week end then all should be well on Monday and know one
would know the difference.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"John" <(E-Mail Removed)> wrote in message
news:109801c42631$fd98d080$(E-Mail Removed)...
> We need to retire a server, let's call it serv1, but the
> servers name is hard coded into many jobs. This server is
> also the PDC.
>
> We have another server that is being build to replace
> serv1, which currently called serv2, but it's hardware
> platform is very much different although it's drives are
> the same size than the old serv1. Serv1 is a old 500 Mhz
> PII where the new server is a 2.6Ghz Celeron running on a
> SuperMicro P4SCi motherboard.
>
> I'm done serv2 must be called serv1 and also contain all
> of the file with the correct rights from serv1. Users must
> be able to connect using the old server name without any
> changes to shares or server names hard coded into programs.
>
> I have the BackupEXEC 9.1 that is currently used to backup
> serv1, and other systems on the network, so one option
> would be to do a full server restore of serv1 onto serv2.
> The problem there the difference in the hardware
> platforms.
>
> I've thought of serveral ways to do this but I would like
> suggestions on how to get from A to B on this one in the
> safest and fastest way.
>
> Thanks
>