Re: Upgrading Hardware
From: Les Connor [SBS MVP] (les.connor_at_DEL.cfive.ca)
Date: 08/19/04
- Next message: Aart Jansen: "SBS and mail thats not for a specified mailbox."
- Previous message: T H KONG: "Exchange Server Message Tracking Log"
- In reply to: Steve Bruce, mct: "Re: Upgrading Hardware"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 18 Aug 2004 19:47:45 -0500
This is consistent with my experience moving SBS2k3 to new hardware.
The only difference may using the loopback adapter(s) as placeholders for
the nic configurations (see http://www.smallbizserver.net)
I've done it like this:
1. Install the loopbacks and configure them with network settings, disabling
or deleting you nic(s).
2. ghost a disk > image, with the image on whatever media you have that can
be read on both boxes. This can be a tape, IDE drive, USB drive, SCSI
drive - whatever.
3. Shut down your source sbs, and move any hardware you need into the new
box.
4. Ghost disn > image onto the new box.
5. Start up new box in DSRM and attend to whatever needs attention. If DSRM
has trouble:
6. Boot from CD1, doing a repair as outlined previously in the thread.
7. Once settled - disable loopbacks, transfer nic settings, and delete
loopbacks.
I used this method this past Saturday to move a SBS2k3 install to
drastically different hardware. The biggest challenge was in the initial
ghost operation, as I didn't have many media options that were available to
both source and target boxes. I ended up ghosting to a spare scsi drive on
the target, transferring the image to USB via laptop. The new server could
read the ghost image from the USB drive no problem.
-- Les Connor [SBS MVP] ------------------------------------- SBS Rocks ! "Steve Bruce, mct" <swb_mct@msn.com> wrote in message news:uGfa8RHhEHA.592@TK2MSFTNGP11.phx.gbl... > > If you are a little adventurous, with the probable payoff of saving a lot > of time you could try Microsoft's " inplace reinstall". > > ( I would like to here from other newsgroup contributors if they have seen > issues with this procedure - I simply tried it, and it has worked each of > several times) > > I recently successfully performed the same task with an SBS 2003 > production server. Microsoft does not actually recommend this with domain > controllers but I have done it several times with domain controllers in a > lab environment plus in two SBS Servers in production environments without > issues. > > If you are working with IDE or SCSI drives you can work with disk or > partition images to move the installation to the new server. If you are > moving between ide and scsi, you would want to perform a full system > restore from tape or file to the new hardware. > > Both of these approaches leaves your existing server in operation while > you are cloning the installation to the new server. > > In either case, when you restore the image or full system backup to the > new hardware it will generally not start because the > hardware-abstraction-layer is not the same between the two servers. > > After restoring the backup or image of your old server to the new > hardware, boot into CD1 of SBS. You will be presented with the option of > "Setup" or "Repair". Select "Setup". After setup checks your drives, you > will be presented with additional options after a few seconds including > "Repair". This time select "Repair". It will run on its own to > conclusion. > > The Server 2003 setup portion of SBS is the only item that needs to run, > because only only your hal and other drivers need to be updated. When I > did this most recently, I was surprised that even the TCP/IP configuration > transferred to the NIC (of the same type). > > It add a convenience if you have prepared you new server to have internet > access without your intervention on the first startup because "activation" > will not let you log in. You will have the option of an internet > activation or phone call, but no chance to configure the server for > internet access. To do this I setup a temporary consumer cable router to > isolate the new Server from the existing network. You could also > temporarily disconnect you existing server from the network. > > All of you Server 2003 patches will need to run again and your mailboxes > and other data synchronized from a backup. You can't run both boxes on > the network together, so removable media must be used to migrate updated > content. > > > > > > "Steve LLG" <drunkonsunday@hotmail.com> wrote in message > news:ezwg1dGhEHA.712@TK2MSFTNGP09.phx.gbl... >> Our network is growing and it is time for a new box. Are there any >> resources/whitepapers etc. around that run through best prcatices for >> hardware migrations of SBS 2003 to a new box??? >> >> Thanks in Advance >> >> > >
- Next message: Aart Jansen: "SBS and mail thats not for a specified mailbox."
- Previous message: T H KONG: "Exchange Server Message Tracking Log"
- In reply to: Steve Bruce, mct: "Re: Upgrading Hardware"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
