Export (0) Print
Expand All

AllSignersEqual Group Policy

Starting with Windows Vista, if the AllSignersEqual Group Policy is disabled, Windows ranks drivers signed by a Windows signing authority (Microsoft signature) better than drivers that have one of the following:

If the AllSignersEqual Group Policy is disabled, Windows selects a driver signed by a Windows signing authority over an Authenticode-signed driver, even if the Authenticode-signed driver is otherwise a better match to a device.

Signatures from a Windows signing authority are ranked equally and include the following signature types:

  • Premium WHQL signatures and standard WHQL signatures

  • Signatures for inbox drivers

  • Windows Sustained Engineering (SE) signatures

  • A WHQL signature for a Windows version that is the same or later than the LowerLogoVersion value of the driver's device setup class.

A network administrator can change this behavior by enabling the AllSignersEqual Group Policy. This configures Windows to treat all Microsoft signature types and Authenticode signatures as equal with respect to rank when selecting the driver that is the best match to a device.

Note  Starting with Windows 7, the AllSignersEqual Group Policy is enabled by default.

For example, consider the situation where a network administrator has to configure client computers on a network to install drivers as follows:

  • A client computer should install a new driver only if the driver has an Authenticode signature that is issued by an Enterprise Certificate Authority (CA) that is created for the network. An enterprise might want to do this in order to ensure that all drivers that are installed on client computers are signed and that the only trusted signing authority other than Microsoft is the CA managed by the enterprise.

  • For signed drivers, the signature score should not be used to determine the driver that has the best rank. Only the sum of the feature score and identifier score is used to compare driver ranks. For example, if the sum of the feature score and identifier score of a new driver is lower than the corresponding sum of an inbox driver, Windows installs the new driver.

To accomplish this, a network administrator:

  • Adds an Enterprise CA certificate to the Trusted Publisher Store of the client computers.

  • Enables the AllSignersEqual Group Policy on the client computers.

After the network administrator configures the client computers in this manner, the administrator can sign the driver that has the Enterprise CA certificate and distribute the driver to the client computers. In this configuration, Windows on client computers will install the new driver for a device instead of a Microsoft-signed driver if the sum of the feature score and the identifier score is lower than the corresponding sum for the Microsoft-signed driver.

Follow these steps to configure the AllSignersEqual Group Policy on Windows Vista and later versions of Windows:

  1. On the Start menu, click Run.

  2. Enter GPEdit.msc to execute the Group Policy editor, and click OK.

  3. In the left pane of the Group Policy editor, click Computer Configuration.

  4. On the Administrative Templates page, double-click System.

  5. On the System page, double-click Device Installation.

  6. Select Treat all digitally signed drivers equally in the driver ranking and selection process and then click Properties.

  7. On the Settings tab, select Enabled (to enable the AllSignersEqual Group Policy) or Disabled (to disable the AllSignersEqual Group Policy).

To ensure that the settings are updated on the target system, do the following:

  1. Create a desktop shortcut to Cmd.exe, right-click the Cmd.exe shortcut, and select Run as administrator.

  2. From the Command Prompt window, run the Group Policy update utility, GPUpdate.exe.

This configuration change is made one time and applies to all subsequent driver installations on the computer until AllSignersEqual is reconfigured.

For more information about driver ranking, see How Windows Ranks Drivers.

 

 

Send comments about this topic to Microsoft

Show:
© 2014 Microsoft