-
Deploy Win2k
I have to replace the OS on - 12 machines,
- 3 are Dell machines
- 7- IBM,
- 1- Gateway,
- and 1 patch together,
- some run
- win95b,
- win98,
- win98se,
- winMe,
- and 1-dos 6.22.
All are Pmmx 166 or better
The owner wants to install Windows 2000 pro
What is the easiest way to deploy win2k pro to these machines? I’m thinking of Ghost, but I’m not sure of how to set the image up for so many different machines. Any help
Thanks
Sly :rolleyes: :D :rolleyes:
-
166mhz + win2k pro = living hell for the poor user!
You need at least above 2-or-300mhz plus butt-loads of RAM... 256 is good/ minimum i would reccomend.
-
I should have said 166 and higher, the dos box is the only 166, the rest are all over 233mhz. :D
-
you can do ghost but you may have to repair them after being ghosted. Id just do it all by hand, I upgraded 150 systems from win nt 4.0 to win2k pro in 3 months.
Corse I backed each one up and had some problems here and there. BUt I did it :)
-
The SIDS will get in the way if you use ghost / ghost walker....Sysprep only works for identical machines...i would upgrade at each machine manually....then make ghosted copys of them, so if the user &&&&'s up the machine 1/2 hour you're done...
-
I would make a ghost for each type of machine...ie Dell, IBM, etc...
Then ghost the others with the correct ghost and run a utility such as NewSID to assign a new SID to the machine. It should save you a lot of time.
-
Are the machines going to join any domains? If not, you can get away with Ghost 7.0 enterprise (contains support for NTFS partitions) and the duplicate SID's should not be a problem. However, if you are joining any domains or sharing files within a workgroup, duplicate SID's will cause big headaches. In that case, manually rebuilds with a Ghost copy of each model may be you best option.
Your hardware sounds woefully inadequate for Win 2k, though. P233MMX will not get it no matter how much RAM you are running. I recommend 300Mhz+CPU/128MB RAM (minimum) 256MB RAM (recommended).
-
Actually Sysprep resets the hardware configuration, so if you set up one machine, run sysprep and then Ghost it, it will redetect the hardware on first boot and you should be fine...
That is what I would do...
-
Thanks, I think I have a few thoughts on this and a way to go... :eek: :eek: :eek: