swapping different motherboard in a win2000 advance server

  • Thread starter Thread starter cst112
  • Start date Start date
C

cst112

I don't think I would ever do this to upgrade a server but I am curious if
this is really feasible.

I have a fileserver with exchange running on it. I know with windows 2000
and xp, if you replace the motherboard, it probably won't boot up because
the motherboard may be running a different hal/acpi. For workstations, I
run a sysprep so it will boot up and reinstall all the devices etc. How
would you replace a motherboard on a server???

The way I would upgrade the server is bring another server online and
migrate the data etc and remove active directory from the old server.

Any thoughts on this??

Kevin
 
Step 1: Device Manager, set Computer to Standard PC (by going to Update
Drivers, Choose driver to install )

Step 2: Device Manager, set IDE Controller to Standard Dual IDE Controller
(as above)

Step 3: Uninstall driver for video

Shutdown the server, change motherboards, reboot and watch it redetect the
new devices.

Wayne McGlinn
Brisbane, Oz
 
cst112 said:
I don't think I would ever do this to upgrade a server but I am curious if
this is really feasible.

I have a fileserver with exchange running on it. I know with windows 2000
and xp, if you replace the motherboard, it probably won't boot up because
the motherboard may be running a different hal/acpi. For workstations, I
run a sysprep so it will boot up and reinstall all the devices etc. How
would you replace a motherboard on a server???

The way I would upgrade the server is bring another server online and
migrate the data etc and remove active directory from the old server.

Any thoughts on this??

Kevin
Click to expand...

That's no server, it's a domain controller. You'ld need to install new OS on
new system, join domain, install apps, run dcpromo and transfer the FSMO
roles from old DC before demoting the old DC.

As far as workstation image + sysprep is concerned, unless you at least have
a motherboard with the same chipset and no new storage devices, the
workstation installation should fail since PnP happens after the hal loads.
 
This older computer has scsi drives, will that have any effect on what you
told me?
I think just for experiment, I will uninstall the items you mentioned and
put in a new motherboard to see what happens. (yes it is an active
directory domain controller).

Kevin
 
my images work on all different computers. Laptops, Desktops.
They don't have to be the same chipset. That is why I use sysprep.
 
That's incorrect, sysprep does not modify a hal even with the "/pnp" switch.
In fact, sysprep does nothing to detect hardware. It's purely supported by
the OS's PnP service. Sysprep only regenerates the GUIDs associated with the
OS, absolutely nothing else. Besides, the hal loads before the PnP service
ever kicks in.

That shouldn't present any serious malfunctions if the chipsets are all
similar intel chipsets, for example. PnP will redetect but note the disabled
devices in device manager while in safe mode, there is a reason why these
are present and disabled.

I've seen syspreped images fail because the original system had the NIC in a
different slot but exactly the same hardware. As clearly specified by OS
manufacturer, imaging + sysprep is reserved for "similar" hardware. We are
an OEM manufacturer so images + sysprep are a religion here.
 
Sysprep doesn't replace the HAL. That is one of the limitations of having
images of computers.
You do need a different image with each system with a different HAL. The
problem with images not cloning properly (unable to boot) is usually the
mass storage driver that is being used on a machine is different so you use
sysprep with the different switches to have the machine redetect all the new
hardware (including the mass storage driver).

For example, I put the same windows 2000 image on machines ranging in speed
from 200MHz to 1.0Ghz, Compaq Computers, HP Computers, Dell Computer, Dell
Laptops, Compaq Laptops. All of these with my one Windows 2000 image with
all my software preinstalled. The only problem is you may want to put the
drivers on the image so the computer can find them when it first starts up
(these are options in sysprep).

The statement" Sysprep only regenerates the GUIDs associated with the OS,
absolutely nothing else" is absolutely wrong. Hopefully this helps people
out there "sysprep" is a wonderful tool!!!

Kevin
 
I pointed out in my original post the steps to take so that 1 image will go
onto any combination of motherboard and ide controller, it is easy to do and
I haven't had it fail yet.

Wayne McGlinn
Brisbane, Oz
 
Hey Wayne,

Thanks for your info. I will use this tip to when I replace a mb. I will
still be using sysprep to implement our ghost images on our network. They
both are good for something.

Thanks again.

Kevin
 
Back
Top