A
alistg
I'm familiar with use of "-bmsd" , "BuildMassStorageSection=Yes" and the
[SysprepMassStorage] section.
Now I want to include JUST the PnP IDs for devices that I actually NEED
below [SysprepMassStorage] in order to minimise start-up times.
Deploy.chm says:
"To identify the potential mass-storage controllers on destination computers
- Generate a list of each of the hardware IDs for each of the mass-storage
controllers that may be on the destination computers
- Compare the list in step 1 with the hardware IDs listed in the .INF files
to determine which references are needed".
I want to automate this and run a script against a representative example of
each machine type I have within the environment, find the IDs for the boot
devices - I can then scan machine.inf, scsi.inf, pnpscsi,inf and mshdc.inf
(or maybe - more ideally - find the .inf used from the machine I scanned -
this would then cover non-natively supported devices !) and add the relevant
section to [SysprepMassStorage].
Questions:
- How do I identify JUST the boot device ? so as to avoid superfluous
drivers ? (- maybe use of ClassID ?, or looking in CriticalDeviceDatabase ?)
- Any suggestions on how to scan for this info ? (e.g. VBscript to check
registry - if so precisely where etc)
I've tried stuff like WMI and Select * from Win32_SystemDriver - within this
I can then look at StartMode, however there are still quite a lot of devices
that start at boot (all I want is the mass storage driver !).
(Rather than simply providing the -bmsd stuff and reccomending manual
"pruning", it would have been cool if MS provided a script that could run on
machines in an environment in order to build up a list of entries that could
be added to [SysprepMassStorage]).
[SysprepMassStorage] section.
Now I want to include JUST the PnP IDs for devices that I actually NEED
below [SysprepMassStorage] in order to minimise start-up times.
Deploy.chm says:
"To identify the potential mass-storage controllers on destination computers
- Generate a list of each of the hardware IDs for each of the mass-storage
controllers that may be on the destination computers
- Compare the list in step 1 with the hardware IDs listed in the .INF files
to determine which references are needed".
I want to automate this and run a script against a representative example of
each machine type I have within the environment, find the IDs for the boot
devices - I can then scan machine.inf, scsi.inf, pnpscsi,inf and mshdc.inf
(or maybe - more ideally - find the .inf used from the machine I scanned -
this would then cover non-natively supported devices !) and add the relevant
section to [SysprepMassStorage].
Questions:
- How do I identify JUST the boot device ? so as to avoid superfluous
drivers ? (- maybe use of ClassID ?, or looking in CriticalDeviceDatabase ?)
- Any suggestions on how to scan for this info ? (e.g. VBscript to check
registry - if so precisely where etc)
I've tried stuff like WMI and Select * from Win32_SystemDriver - within this
I can then look at StartMode, however there are still quite a lot of devices
that start at boot (all I want is the mass storage driver !).
(Rather than simply providing the -bmsd stuff and reccomending manual
"pruning", it would have been cool if MS provided a script that could run on
machines in an environment in order to build up a list of entries that could
be added to [SysprepMassStorage]).