Re-install Win2K for new mobo/CPU or just use Sysprep?

[LocutusX]

If you are familiar with Win2K Enterprise Deployment, you probably have used the Sysprep utility.

The thought occurred to me that instead of wiping out \WINNT and re-installing Win2K when I migrate over to my new AthXP, to just run the Sysprep utility, and shut down the P3 -- and the next time I turn on the comp (when it's on the Athlon mobo) Sysprep should handle the "hardware re-configuration" correctly recognize the new CPU, mobo chipset, etc.

Anyone tried this? Will it work?

 

[btvillarin]

Well, I guess it doesn't hurt to try it. (You have all your stuff backed up?) If it doesn't work, then I guess you'd have to reinstall.

 

[LocutusX]

We are going to start using Sysprep at work for small deployments of Win2K among certain test groups (currently a proprietary solution is used) and one thing I noticed when reading the docs for Sysprep 1.1, is how you can use one "image" for both SCSI and IDE systems, and even systems with different HALs -- such as Uniprocessor and Multiprocessor! That's what got me thinking.

Surely, if it can handle such big changes, it should be able to handle me migrating my CPU to AthlonXP (from P3 Coppermine), my chipset to KT266A (from Apollo Pro 133) and my RAM to DDR (from SDR). Absolutely nothing else is being changed.

One potential cause of problems may be the various drivers that also exist in Add/Remove Programs -- like the VIA 4-in-1's.

I guess I'll just do a backup and try it. If it works, I'll save a LOT of time. 😉 If not, just blow it all away and make do like I normally do.