Re: OSD Image Help

Tech-Archive recommends: Fix windows errors by optimizing your registry

I'm going to try to explain myself a little better. It might help with
getting the answer I want.

I have a reference machine prepared and imaged, using the following
Sysprep.inf

[Sysprep]
BuildMassStorageSection = Yes

[SysprepMassStorage]

During the "Post-Install" phase I would like to copy the drivers for all our
different hardware to C:\Sysprep\Drivers from our server and insert the the
correct lines into the Sysprep.inf file, along the lines of:

[Unattended]
OemPnPDriversPath =
SysPrep\Drivers\Chipset\;SysPrep\Drivers\Network\;SysPrep\Drivers\Video\;Sysprep\Drivers\Audio\;Sysprep\Drivers\Other
UpdateInstalledDrivers = yes
DriverSigningPolicy = ignore

As a start I created a batch file to copy over the driver files from
\\server\share\drivers to C:\Sysprep\drivers. Moving one step at a time as
not to create to many variables should an error occur. Sure enough one did.
Once the "Post-Install" phase starts it starts running the actions, the
action to copy the files over exits with "Error Code 4". So I've failed at
the first hurdle really.

I would like some help with resolving this issue and any suggestions on how
to insert the lines I need into the local sysprep.inf file without damaging
the entries that the OSD has already created to install the machine.

Also am I taking the right approach? The other avenue I persued was to
populate all the drivers and the correct sysprep.inf file whilst creating
the reference machine. This meant that I would have to create a new
reference machine each time some new hardware arrived or if a driver update
was required. I would like to be able to create as few OS Images as possible
and try to only update them on a 6 month cycle or when a major service pack
is released.

I hope that someone can help.


.