Windows 10 Driver Publishing Workflow

Scenarios

1. Publishing Drivers with Distribution Targeting

If the Distribution Targeting list is used with Installation Targeting INF changes, Windows Update will distribute the driver to an intersection of the set of CHIDs from the Distribution Targeting list and the set of CHIDs from the Installation Targeting information in the INF.

The scenario outlined in Error: Reference source not found assumes only Distribution Targeting is used (no Installation Targeting information is included in the driver INF).

List : Workflow Steps for Publishing with Distribution Targeting

1. 
   Fabrikam creates a driver fix for a device within the Contoso Model B matching on HWID2. This same device, matching on HWID2, is present in other Contoso systems and other OEM systems.
   
2. 
   Fabrikam submits their driver to the Windows Hardware Dashboard.
   
3. 
   This driver fix would ideally apply to other systems, but Fabrikam does not want to release it to other systems until OEM testing is completed. Thus, Fabrikam uses the Distribution Targeting list on the Windows Hardware Dashboard to constrain distribution to only Contoso Model B’s Computer HardwareID-5 (refer to Error: Reference source not found).
   
   • 
     Computer HardwareID-5 = Manufacturer + Family + ProductName = Contoso + Contoso Line + Model B
     
   • 
     Fabrikam provides the Distribution Targeting information during publishing by entering it into the publishing web page. Alternatively they can modify (add/remove) this information for their driver even after it has been published to Windows Update.
     
4. 
   The Windows Hardware Dashboard uses the Distribution Targeting list to ensure Windows Update only distributes the driver to Contoso Model B systems based on Contoso Model B’s Computer HardwareID-5.
   
5. 
   Fabrikam can return to the Windows Hardware Dashboard to manage their driver’s Distribution Targeting List at any time. This includes adding new CHIDs and removing existing CHIDs. The Windows Hardware Dashboard will ensure Windows Update uses the new distribution targeting.
   
6. 
   PnP on end user systems installs the driver as long as the driver is the best ranked driver for the device present on the system.
   
   • 
     PnP will not prevent this driver from being side-installed, because the Distribution Targeting list info is only used for distribution settings in Windows Update.
     

2. Publishing Drivers with Installation Targeting

If a driver’s INF contains Installation Targeting information then Windows Update will distribute the driver to only those systems which have a CHID identified in the Installation Targeting information in the INF.

The scenario outlined in Error: Reference source not found assumes only Installation Targeting information from the driver’s INF is used (no Distribution Targeting).

List : Workflow Steps for Publishing Drivers with Installation Targeting

1. 
   Fabrikam creates a driver for a device within the Contoso Model A matching on HWID1.
   
2. 
   Fabrikam does not want this driver to install on any system that is not Contoso Model A, even if there is a HWID match. Thus, Fabrikam adds Installation Targeting to the driver’s INF with only Contoso Model A’s Computer HardwareID-5 (refer to Error: Reference source not found).
   

Computer HardwareID-5 = Manufacturer + Family + ProductName = Contoso + Contoso Line + Model A

3. 
   Fabrikam submits their driver to the Windows Hardware Dashboard, and selects to publish it to Windows Update.
   
4. 
   The Windows Hardware Dashboard consumes the Installation Targeting info from the INF and ensures Windows Update only distributes the driver to Contoso Model A systems based on Contoso Model A’s Computer HardwareID-5
   
5. 
   PnP on end user systems ensures that there is a Computer Hardware ID match before installing Fabrikam’s driver. If there is no match, PnP will not install the driver.
   

Therefore, in a side-install scenario, PnP would not install this driver.

3. Reselling a submission and using Distribution Targeting

The Distribution Targeting list can be used with a resold driver submission. In this case, a partner can resell a driver submission to another partner. The partner can then use Distribution Targeting to constrain distribution for the resold driver.

The scenario in Error: Reference source not found uses only Distribution Targeting thus no Installation Targeting information is included in the driver INF.

List : Workflow Steps for Publishing Resold Drivers with Distribution Targeting

1. 
   Fabrikam creates a driver fix for a device within the Contoso Model B matching on HWID2. This same device, matching on HWID2, is present in other Contoso systems and other OEM systems.
   
2. 
   Fabrikam submits their driver to the Windows Hardware Dashboard.
   
3. 
   Fabrikam resells the driver to Contoso so that Contoso can retrieve signed drivers binaries and catalogs, and can distribute the driver through Windows Update.
   

Fabrikam can still distribute the initial submission to Windows Update if they choose.

4. 
   Contoso accepts the resold submission.
   
5. 
   This driver fix would ideally apply to other systems, but Contoso does not want to release it to other systems until OEM testing is completed. Thus, Contoso uses the Distribution Targeting list on the Windows Hardware Dashboard to constrain distribution to only Contoso Model B’s Computer HardwareID-5 (refer to Error: Reference source not found).
   
   1. 
      Computer HardwareID-5 = Manufacturer + Family + ProductName = Contoso + Contoso Line + Model B
      
   2. 
      Contoso can add this information during driver publishing, or after their driver has been published to Windows Update.
      
6. 
   The Windows Hardware Dashboard consumes the Distribution Targeting list and ensures Windows Update only distributes the driver to Contoso Model B systems based on Contoso Model B’s Computer HardwareID-5.
   
7. 
   Contoso can return to the Windows Hardware Dashboard and add or remove CHIDs from the Distribution Targeting list at any time. The Windows Hardware Dashboard will ensure Windows Update uses the new distribution targeting.
   
8. 
   PnP on end user systems installs the driver as long as the driver is the best ranked driver for the device present on the system.
   

PnP will not prevent this driver from being side-installed, because the Distribution Targeting list info is only used for distribution settings in Windows Update.

4. Reselling a submission and using Installation Targeting with driver submissions

The Distribution Targeting list can be used with a resold driver submission. In this case, a partner can resell a driver submission to another partner. The partner can then use Distribution Targeting to constrain distribution for the resold driver.

The scenario outlined Error: Reference source not found assumes only Installation Targeting information from the driver’s INF is used (no Distribution Targeting).

List : Workflow Steps for Publishing Resold Drivers with Installation Targeting

1. 
   Fabrikam creates a driver for a device within the Contoso Model A matching on HWID1.
   
2. 
   Fabrikam submits their driver to the Windows Hardware Dashboard.
   
3. 
   Fabrikam resells the driver to Contoso so that Contoso can retrieve signed drivers binaries and catalogs, and can distribute the driver through Windows Update.
   
   1. 
      Fabrikam can still distribute the initial submission to Windows Update if they choose.
      
4. 
   Contoso accepts the resold submission.
   
5. 
   Contoso does not want this driver to install on any system that is not Contoso Model A, even if there is a HWID match. Thus, Contoso adds Installation Targeting to the driver’s INF with only Contoso Model A’s Computer HardwareID-5 (refer to Error: Reference source not found) via the Driver Update Acceptable (DUA) process.
   
   1. 
      Computer HardwareID-5 = Manufacturer + Family + ProductName = Contoso + Contoso Line + Model A
      
6. 
   The Windows Hardware Dashboard consumes the Installation Targeting info from the INF and ensures Windows Update only distributes the driver to Contoso Model A systems based on Contoso Model A’s Computer HardwareID-5.
   
7. 
   PnP on end user systems ensures that there is a Computer Hardware ID match before installing Contoso’s driver. If there is no match, PnP will not install the driver.
   
   1. 
      Therefore, in a side-install scenario, PnP would not install this driver.
      

Note: It is not possible to resell a driver submission after going through the Driver Update Acceptable process. It is also not possible to resell a resold driver.

6.