Windows 10 Driver Publishing Workflow



Yüklə 159,22 Kb.
səhifə1/8
tarix08.10.2017
ölçüsü159,22 Kb.
#3899
  1   2   3   4   5   6   7   8


Windows 10 Driver Publishing Workflow

June 2015

Some information relates to pre-released product, which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.

Copyright

This document is provided "as-is." Information and views expressed in this document, including URL and other Internet Web site references, may change without notice.

Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection is intended or should be inferred.

This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes.

© 2015 Microsoft. All rights reserved.

Please refer to Microsoft Trademarks for a list of trademarked products.

Bluetooth® is a trademark owned by Bluetooth SIG, Inc., USA and licensed to Microsoft Corporation.

All other trademarks are property of their respective owners.

Contents


1Driver Publishing Workflow for Windows 10 4

2Windows Update Distribution 4

2.1Pre-Windows 10 Driver Update Scenarios 4

2.2Reselling (Redistributing) Drivers and the Driver Update Acceptable Process 5

2.3Pre-Windows 10 Driver Publishing Workflow 5

2.3.1Driver Submission Options 5

2.3.2Removing a Driver from Windows Update 7

2.4Windows 10 Initial Driver Publishing Workflow (29 April 2015) 7

2.4.1Driver Submission Options 7

2.5Windows 10 Release Driver Publishing Workflow 8

2.5.1New Features 8

2.5.2Driver Publishing Workflow 9

3Driver Targeting 10

3.1Background 10

3.2Computer Hardware IDs 10

3.2.1Tips for consistent CHIDs 12

3.3Types of Targeting 12

3.3.1Installation Targeting 13

3.4CHIDs: Installation Targeting vs. Distribution Targeting 14

3.5Scenarios 15

3.5.1Publishing Drivers with Distribution Targeting 15

3.5.2Publishing Drivers with Installation Targeting 15

3.5.3Reselling a submission and using Distribution Targeting 16

3.5.4Reselling a submission and using Installation Targeting with driver submissions 17

3.6Examples 18

4Publication restrictions 23

5Firmware Update support for systems 25

5.1UEFI Firmware UpdateCapsule Support 25

5.1.1Publishing an UpdateCapsule: 25

5.1.2Validating Firmware Update Capsules 26

6.Driver publishing FAQ 26

7.Document Revision History 28

5.2November 2014 – Initial Release 28

5.3January 2015 Update 28

5.4April 2015 Update 28

5.5May - June 2015 Upadate 29





  1. Driver Publishing Workflow for Windows 10


To align with the new Windows as a Service philosophy, users will routinely receive OS updates. These updates will fix bugs and issues but also light up new features and enable new scenarios. Because of this, Windows 10 will be an ever-evolving OS.

For Windows 10, the end-to-end Windows driver publishing and distribution workflow has been modified to accommodate these changes. This document outlines the goals, scenarios, and requirements that enable the end-to-end driver publishing workflows which will enable Upgrade/Update Customer Satisfaction.


  1. Windows Update Distribution


Microsoft offers hardware partners a distribution channel for their updated drivers called Windows Update. Windows has built-in support to retrieve drivers from Windows Update from a variety of scenarios, such as when new hardware is connected to Windows to updating existing drivers with newer versions.
    1. Pre-Windows 10 Driver Update Scenarios


Distributing a driver through Windows Update falls into three different scenarios. List shows the three different driver scenarios that Windows Update facilitates.

List : Windows Update Driver Scenarios

  • Missing Driver
    This scenario occurs when Windows discovers new hardware. This could be due to a user plugging in a new peripheral, pairing with a networked or wireless device (such as Bluetooth or Wi-Fi Direct), docking with a new docking station, and so on.

When Windows recognizes the new hardware, it checks Windows Update for a driver for the newly discovered hardware. Even if a driver was already installed, the new hardware will trigger a search on Windows Update to check for a newer version of the driver. If one exists then it is downloaded and installed.


A good example of this scenario is if a user formats their hard drive and installs Windows fresh, from a DVD or USB drive. Once Windows is up and running it discovers all of the hardware components (display, USB hub, internal components, and so on) and fetches drivers from Windows Update.




This scenario occurs when a user requests that Windows Update download and update an existing driver that is already installed on a device running Windows.

This typically occurs because the user is advanced and wants to use a newer driver, or because an IT administrator or customer support technician has instructed the user to do so.



  • Auto Update Driver
    Similar to the Update Driver scenario, the Auto Update Driver scenario involves updating an existing driver on a device running Windows. The difference between the two scenarios is that Auto Update Driver happens automatically, without any user interaction.

This requires that the device running Windows is configured to automatically update itself from Windows Update.

These scenarios have been supported for several releases. Windows 10 will support the Missing Driver and Auto Update Driver scenarios.


    1. Yüklə 159,22 Kb.

      Dostları ilə paylaş:
  1   2   3   4   5   6   7   8




Verilənlər bazası müəlliflik hüququ ilə müdafiə olunur ©www.genderi.org 2024
rəhbərliyinə müraciət

    Ana səhifə