From: "Glenn Meadows" 

Ghost or some other HD cloning software your existing hard drive, and have
that as a full backup/spare, so if something falls over on the disk you
upgrade on, you can at least build the old system with the original HD
cloned back, and original Hardware and be back to square one.

I've had problems doing just that, putting a new MB into a Windows 2K
server system, getting the system to work again properly.  I solved the
problem by just building a whole new server, and migrating the applications
to the new server, and scrapping the old one.  It turned out to be easier
in the long run for me.

--
Glenn M.


"Mike N."  wrote in message
news:tt6pt0lve2l5nqq93tqm38ik8he92f4b3n{at}4ax.com...
> On Wed, 05 Jan 2005 13:38:03 -0800, Randall Parker
>  wrote:
>
> >Am I better off swapping
> >the motherboard while still running NT or is there a greater chance of
success if I
> >swap motherboard after I upgrade to Win2k?
>
>   From simulating recovery scenarios and actual practice, NT is much
easier
> than Win2k  when swapping Mobos as long as the new configuration is
> 'compatible' (similar or same video card and same disk controller, and
same
> single/dual processor configuration).  We have upgraded a particular NT
> server about 4 times in place just by dropping in  a new Mobo.   No
> hardware autodetect sequence, just reprogram the network card, load all
the
> IP aliases, and go.  Perhaps some fine tuning of the swap file for extra
> RAM.
>
>   Win2k is much more specific, requiring a complete hardware autodetect
> even when swapping to an identical Mobo.
>
>    Geo's idea of dropping in the new Mobo and upgrading sounds like the
> best approach.  Just make sure your data is backed up; I haven't done that
> before!
>

--- BBBS/NT v4.01 Flag-5