Sysprep Difficulties

[Guest]

I've been trying to do some drive Ghosting with Symantec Ghost. The program
will run sysprep for you, or you can run it manually on your model machine.
I've tried both. The model is an IBM P III NetVista, with XP Pro, SP2. The
client machines are a variety of IBM's, Dells and clones. Even downloaded the
latest deployment cab file with the newest version of sysprep designed for
SP2.

Anyway... I can pull the model image fine, and send them out to the clients,
but every client machine gives me a quick BSOD, then the Windows safe mode
menu, where it will not start into any mode, Safe, Last Know Good, Normal,
nothing.

Now this is my first time using sysprep, as most of the ghosting I did in
the past was Win 98, but is this not what sysprep is designed to handle?
Isn't it supposed to force a rebuild of the PnP database, in other words,
redetect all the different hardware? Or is there a command line switch I
should be using to force this?

Mike A

 

[Torgeir Bakken \(MVP\)]

Hi

You might want to post your question in the newsgroup
microsoft.public.windowsxp.setup_deployment

 

[Guest]

Hi

You might want to post your question in the newsgroup
microsoft.public.windowsxp.setup_deployment


--

Hmm... I just had a look there, thanks. Seems I'm not the only one having
problems with sysprep. The comment I keep seeing is that almost ANY
difference in hardware will mess things up. Isn't that what sysprep was
designed to accomodate? (aside from changing the SID). Looks like
Microsoft screwed up again! Why is it that good old Windows 98 was so much
better at this sort of thing?

And of course, we IT professionals are the last ones to get what we need
made right. If it doesn't have some catch phase like "Wi-Fi" attached to
it......

Mike

 

[granny]

-----Original Message-----




Hmm... I just had a look there, thanks. Seems I'm not the only one having
problems with sysprep. The comment I keep seeing is that almost ANY
difference in hardware will mess things up. Isn't that what sysprep was
designed to accomodate? (aside from changing the SID). Looks like
Microsoft screwed up again! Why is it that good old Windows 98 was so much
better at this sort of thing?

And of course, we IT professionals are the last ones to get what we need
made right. If it doesn't have some catch phase like "Wi-Fi" attached to
it......

Mike


.

Where did you get the idea that Sysprep was designed to
accomodate hardware differences? I have been using it for
several years for SID gen in Windows2000 and WindowsXP. It
has always been required that the hardware be nearly
identical.