Sysprep Clarification

[jvpublic]

Hi,

I would like to be able to image my computers at work using symantec
ghost. I have been doing this reasonably successfully for a few years.
The problem that I have come to now is that I am using computers with
different mass storage boot controllers.

Can I create a sysprep image that will boot from different mass storage
boot devices?

If so does anybody have a working example of the sysprep.inf and
directory structure?

Thanks,
Jason

 

[Steve Maser]

Hi,

I would like to be able to image my computers at work using symantec
ghost. I have been doing this reasonably successfully for a few years.
The problem that I have come to now is that I am using computers with
different mass storage boot controllers.

Can I create a sysprep image that will boot from different mass storage
boot devices?

If so does anybody have a working example of the sysprep.inf and
directory structure?

Thanks,
Jason

It's been years since we set this up, but I think all you have to do
is run:

sysprep -bmsd

when your image is in a couple of computers and that should work to
popuplate your .inf file.

That's how we did it, IIRC...

There's something here about it:

http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/T
echRef/27e9936c-3275-4826-b665-4a6739d00bf8.mspx

- Steve

 

[jvpublic]

I have done that, but I think the problem is that the other boot
devices are not in the base windows disk and are not installed on that
machine. Can I install drives for hardware that is not there?

Jason

 

[Johan Arwidmark]

Just add them manually to the drive and to sysprep.inf before sealing
the image.

Here is an example with a qlogic HBA (used in IBM 8843 PGM blades).
This example is from win2003 server install but xp uses the same....

[SysprepMassStorage]
......
All builtin drivers, around 660 lines
.....
PCI\VEN_1077&DEV_2312&SUBSYS_01001077=C:\Drivers\QL23HS20\OEMSETUP.INF
PCI\VEN_1077&DEV_2312&SUBSYS_01011077=C:\Drivers\QL23HS20\OEMSETUP.INF
PCI\VEN_1077&DEV_2312&SUBSYS_01021077=C:\Drivers\QL23HS20\OEMSETUP.INF
PCI\VEN_1077&DEV_2312&SUBSYS_010A1077=C:\Drivers\QL23HS20\OEMSETUP.INF
PCI\VEN_1077&DEV_2312&SUBSYS_01000E11=C:\Drivers\QL23HS20\OEMSETUP.INF
PCI\VEN_1077&DEV_2312&SUBSYS_027D1014=C:\Drivers\QL23HS20\OEMSETUP.INF
PCI\VEN_1077&DEV_2312&SUBSYS_01010E11=C:\Drivers\QL23HS20\OEMSETUP.INF
PCI\VEN_1077&DEV_2312&SUBSYS_01020E11=C:\Drivers\QL23HS20\OEMSETUP.INF
PCI\VEN_1077&DEV_2312&SUBSYS_34BA8086=C:\Drivers\QL23HS20\OEMSETUP.INF
PCI\VEN_1077&DEV_2312&SUBSYS_01021749=C:\Drivers\QL23HS20\OEMSETUP.INF
PCI\VEN_1077&DEV_2312&SUBSYS_10511734=C:\Drivers\QL23HS20\OEMSETUP.INF
PCI\VEN_1077&DEV_2322&SUBSYS_01701028=C:\Drivers\QL23HS20\OEMSETUP.INF
PCI\VEN_1077&DEV_2312&SUBSYS_01030E11=C:\Drivers\QL23HS20\OEMSETUP.INF
PCI\VEN_1077&DEV_2312&SUBSYS_01040E11=C:\Drivers\QL23HS20\OEMSETUP.INF
PCI\VEN_1077&DEV_2312&SUBSYS_01050E11=C:\Drivers\QL23HS20\OEMSETUP.INF
PCI\VEN_1077&DEV_2312&SUBSYS_018A1028=C:\Drivers\QL23HS20\OEMSETUP.INF
PCI\VEN_1077&DEV_2312&SUBSYS_12BA103C=C:\Drivers\QL23HS20\OEMSETUP.INF
PCI\VEN_1077&DEV_2312&SUBSYS_12C2103C=C:\Drivers\QL23HS20\OEMSETUP.INF
PCI\VEN_1077&DEV_2312&SUBSYS_12C7103C=C:\Drivers\QL23HS20\OEMSETUP.INF
PCI\VEN_1077&DEV_2312&SUBSYS_12C9103C=C:\Drivers\QL23HS20\OEMSETUP.INF
PCI\VEN_1077&DEV_2312&SUBSYS_02FB1014=C:\Drivers\QL23HS20\OEMSETUP.INF

regards

Johan Arwidmark
Microsoft MVP - Setup/Deployment

 

[jvpublic]

Is that one line per device? Do they repeat for a reason or is that
just from the cut and paste?

Thanks,
Jason

 

[Johan Arwidmark]

It's at least one line per device, most drivers supports many
different revisions and PNPIDs

Sometimes you can shorten the PNPID to a more generic like the example
below, but I prefer to copy and paste the PNPID belonging to the
particular driver I'm adding from the INF file, then I know
(hopefully) that the vendor actually tested all those devices..

PCI\VEN_1077&DEV_2312=C:\Drivers\QL23HS20\OEMSETUP.INF


regards

Johan Arwidmark
Microsoft MVP - Setup/Deployment