• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

How to use SysPrep in win2k

C

Cooky

Golden Member
I'm trying to make a master image off a computer. After running sysprep.exe with [-reboot] option, the machine reboots and now I don't know what to do next.
According to this MCSE book I got I'm supposed to do a disk duplication using 3rd party software such as Drive Image or Norton Ghost but what's the point of using SysPrep if I have to use 3rd party software anyway??

Any input would be appreciated.
 
SYSPREP is used to prepare a computer so that it is suitable to make an image that can be rolled out across a network of many computers.
It removes any unique features of the computer so that you can have the same sytem installed on all your machines, as long as they are all identical in hardware attributes.
SYSPREP'S function is to prepare the machine, not create an image, this is why you need a third party application, such as Ghost to finish the job.
It is not really siutable for the home user, enthusiast.
Just use Ghost, or something similar.
 
to use sysprep:

1. Get your sysprep files/image the way you want them.(mainly make sure you have your hard disk
controlers listed correctly or the image will blue screen with an inaccessable boot device)
2. place a bootable floppy/cd rom in the drive(this should contain your imaging software ie ghost)
3. run the sysprep with the -r attribute
4. When your machine reboots, create an image of the drive(partation)

You should be able to apply this image to other PCs in your environment.

5. When you apply this image to another PC, it will go through "mini setup" to find devices and add the machine to the network. that's why you have a disk in the floppy, to keep it from re-booting before you make an image.


jd
 
Sysprep does all of the things mentioned above, but it is also good for deploying across multiple computer types. As long as they use the same interface controllers (normally, Standard IDE), power spec (ACPI), and HAL, everything is great. Windows does a good job of hardware re-enumeration on the first bootup. It really impressed me the first couple of times I used it.
 

The big difference:
You can now use your images smoothly on different hardware.

Some minor differences:
You can set some options to prompt after the reimage. Time zone, IP settings etc. If you use an OEM PC + OS License you can punch in the license straight from the case sticker. That way you won't go illegal by using the same number on all boxes.

You don't have to use a SID changing utility.
 
>
As long as they use the same interface controllers (normally, Standard IDE), power spec (ACPI), and HAL, everything is great. Windows does a good job of hardware re-enumeration on the first bootup.
>

shrinertech,

The hal is the most important listed. The image MUST have the same hal(the two main hals are ACPI and NON-ACPI). Or it bluescreens right away. You can even upgrade teh hal to a multi-processor HAL if you pick the fight one.

As for harddisk controllers, you can put a list of hard disk controlers in the "sysprep.inf" file so you can have the image load the specific HDC for several different PCs. You have to know the "plug n play id" for for each specific HDC you want to use. You can also use the "generic" controler.

Sysprep is a REALLY good tool if you wish to deploy the same image over a large number of PCs. The more standard teh hardware the better.

jd
 
Yeah I kinda fouled up when I wrote that out...
I already knew that though. I don't know what I would do without sysprep.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top