Skip navigation
1 2 Previous Next 11201 Views 17 Replies Latest reply: Jun 20, 2011 9:09 AM by EMiranda RSS
Apprentice 250 posts since
Sep 4, 2008

Has received 1 of 9 achievements.
Currently Being Moderated

Apr 7, 2010 11:45 AM

Unattend.xml / DriverSigningPolicy

I've been searching around for a bit of time now however I haven't been able to find a clear cut answer.

 

In my old sysprep.inf file there was a field for DriversSigningPolicy and it was set to ignore. Does anyone know the equivalent to that in the new Unattend.xml format?

 

I saw the PersistAllDeviceInstalls just not sure if this is the setting that would work.

  • Mach6 Employee 637 posts since
    May 23, 2008

    Has received 6 of 9 achievements.
    Currently Being Moderated
    1. Apr 8, 2010 8:54 AM (in response to Stoj)
    Re: Unattend.xml / DriverSigningPolicy

    Paul,

     

    I don't know how (or if it's possible in Win7) to do the same thing through a single option in the unattend, but PersistAllDeviceInstalls just tells sysprep to assume that it's going to similar hardware so to not make it hardware agnostic.  Basically it's saying, "I don't want to be hardware independent!"

     

    It's definitely not what you're looking for.

  • zman Master 3,277 posts since
    Dec 14, 2007

    Has received 9 of 9 achievements.
    Currently Being Moderated
    3. Apr 9, 2010 7:31 AM (in response to Stoj)
    Re: Unattend.xml / DriverSigningPolicy

    I have not tried this but saw it on another post:

     

    bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
    bcdedit.exe -set TESTSIGNING ON
    

     

    Then reboot.  Microsoft has deprecated the driversigningpolicy

  • Mach6 Employee 637 posts since
    May 23, 2008

    Has received 6 of 9 achievements.
    Currently Being Moderated
    5. Apr 12, 2010 7:51 AM (in response to Stoj)
    Re: Unattend.xml / DriverSigningPolicy

    I believe you would need to set those up as runonce commands.  BCDEDIT.exe modifies the file BCD, which replaces the boot.ini file from older versions of Windows (and adds additional functionality/flexibility as well).

     

    I'll try this also, when I get a chance, but it might be a couple of days before I'm able to get to it, so if anyone else can try it and report back that would help everyone.

  • peoples Apprentice 45 posts since
    Oct 4, 2010

    Has received 1 of 9 achievements.
    Currently Being Moderated
    9. Dec 6, 2010 6:54 AM (in response to Stoj)
    Re: Unattend.xml / DriverSigningPolicy

    Hello ,

     

    is there something news ? I currently have exactly this problem but no solution.

     

    I've tried your RunOnce command in unattend.xml

    I tried to run "bcdedit.exe" -set loadoptions DDISABLE_INTEGRITY_CHECKS" before capturing the image

    and setting [HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows NT\Driver Signing key BehaviorOnFailedVerify to "0" ignore

     

    nothing helps.

     

    some idea ?

     

    thanks.

  • Froggmann Apprentice 55 posts since
    May 20, 2009

    Has received 1 of 9 achievements.
    Currently Being Moderated
    10. Feb 3, 2011 4:22 PM (in response to peoples)
    Re: Unattend.xml / DriverSigningPolicy

    Just wanted to bump this. I'm trying to work through the same issue here but so far no dice.

     

    Setting these options in the image yield nothing:

     

    bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
    bcdedit.exe -set TESTSIGNING ON


    Same goes for entering them in run once in the OSD script. 
  • jameshopkins Rookie 22 posts since
    Apr 30, 2009

    Has received 1 of 9 achievements.
    Currently Being Moderated
    11. Jun 20, 2011 7:58 AM (in response to Froggmann)
    Re: Unattend.xml / DriverSigningPolicy

    Hi, did you manage to get this working in the end? I am having the same problem, where it is asking to install unsigned drivers from Dell.

  • Rookie 29 posts since
    Feb 4, 2008

    Has received 1 of 9 achievements.
    Currently Being Moderated
    12. Jun 20, 2011 8:14 AM (in response to jameshopkins)
    Re: Unattend.xml / DriverSigningPolicy

    interested too in a fix/workaround. Provisioning Windows 7 and I get prompted two times. I tell it to download and Provisioning will continue but this does not allow our techs to walk away once a device is being provisioned like they can now for an xp device.

  • jameshopkins Rookie 22 posts since
    Apr 30, 2009

    Has received 1 of 9 achievements.
    Currently Being Moderated
    13. Jun 20, 2011 8:22 AM (in response to skihaus)
    Re: Unattend.xml / DriverSigningPolicy

    I found this post here about setting the driver signing in gpedit, possibility of doing this on the base image, not got around to testing it yet though.

  • Mach6 Employee 637 posts since
    May 23, 2008

    Has received 6 of 9 achievements.
    Currently Being Moderated
    14. Jun 20, 2011 8:33 AM (in response to jameshopkins)
    Re: Unattend.xml / DriverSigningPolicy

    Are these drivers for 32-bit or 64-bit systems?  In the case of 64-bit the requirement is that the drivers be signed.  It is possible to enable "test signed" drivers, although this is supposed to be for development work only and drivers shouldn't be released in that state.  Information can be found here:

     

    http://technet.microsoft.com/en-us/library/dd744517(WS.10).aspx#SignatureReqs

1 2 Previous Next

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • Correct Answers - 20 points
  • Helpful Answers - 10 points
LANDESK Community powered by Jive SBS® 4.5.7.1  |  Legal Notices  |  Privacy Policy  |  Icon 

TweeterOn Twitter  |  Icon FacebookOn Facebook © 2007 LANDESK Software