I was initally testing a sysprep image with unsigned audio drivers, which was
problematic as the first user to login post-clone has no hardware install rights
(installation of unsigned drivers is postponed until the next admin login).

I have since obtained signed drivers for the audio device - they came in an
InstallShield package called audio.exe. If I run audio.exe on the target machine
the drivers install with no prompts and device manager reports the installed
drivers as being signed. Now, if I instead extract the contents of audio.exe then
point the hardware wizard at the subdirectory containing the INF files I am once
again prompted and the install even looks for files that were not installed when
I had run audio.exe.

Any thoughts on how to trace this? I've searched the contents of audio.exe (INI
and INF files) for reference to the offending files and nothing has been found.
I also looked at the InstallShield setup.exe and it's only being called with /SMS
and /S switches - nothing that affect the files being copied/installed.


0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Looks like i've made a bit of progress. Even with the signed drivers in place (shipping
drivers taken straight from the original install disc that accompanied the machine) XP
was still hitting an INF located in C:\WINDOWS\inf which was pointing to the offending
file that could not be found/was not even required. So, I temporarily moved any INF's
from C:\WINDOWS\inf that referenced this file and the shipping drivers installed fine
when manually pointing to the correct INF's - no prompts. Unfortunately, one of the
driver files is not signed, but i'm getting there.
Answered 05/04/2005 by: kick
Senior Yellow Belt

Please log in to comment
What about

DriverSigningPolicy = "Ignore"

in the Sysprep.inf ?
Answered 05/17/2005 by: Dr. Soup
Senior Yellow Belt

Please log in to comment
Add this to your unattended answer. The full tips and tricks article I wrote can be found here: http://itninja.com/blog/view/autoexnt2

AdminPassword=xxxxxxx (should be your local admin password)

{Path to batch file}

To get the batch file onto the local machine you must create add the file into the folders where you keep the drivers usually \$OEM$\$1\. Anything in this folder will be copied to the root of the c:\ so you will want to burry it at least one more folder deep. Then in the GuiRunOnce section you can call it as c:\{folder}\secedit.bat. At this point the file will exist locally so there should be no problem calling it. You will want to make sure that in your batch file you specify shutdown.exe -r to reboot the machine. If not then you will have a machine sitting logged in as administrator. Shutdown is in the res kit for win2k. I created a similar setup to manually change a registry setting upon reboot. Here is what my batch file looked like:

regedit.exe /s c:\drv\reg\ddhcpms.reg

c:\drv\reg\shutdown.exe /r

del /Q c:\drv\reg\*.*
Answered 05/17/2005 by: cdupuis
Third Degree Green Belt

Please log in to comment