2. Driver Servicing Updates
WinHEC 2015
4/17/2018 3:09 AM
Driver Servicing Updates
Thank you for attending this session.
1.The goal of this session is to provide you overall Driver Servicing Updates.
2.For those of you who have attended yesterday’s sessions, I hope this session will be the refresher as well as the way connect dots for yesterday’s session.
3.Also, this session will provide you good background on why we are moving to DCHU model before you are going to the Universal Driver lab session.
Naomi Rosell
Principle Program Manager
Strategy & Ecosystem
© 2015 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

3. Session Content Looking Back Upcoming Changes
Tech Ready 15
4/17/2018
Session Content
Looking Back
Summary of changes last 12 months
Upcoming Changes
What you can expect to see next 6 months
HLK & Compatibility Program
What are the new changes?
Windows Update for Business
Enterprise servicing story
HW Dev Center Best Practices & Tips
Best practices and tips to help your servicing activities
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

4. Looking Back

5. 90 Looking Back Hardware Dev Center Launch
Tech Ready 15
4/17/2018
Looking Back
Hardware Dev Center Launch
Over 1,500 hardware partners submitted drivers from the new site!
Driver Submission moved to HW Dev Center
Sysdev migration is in progress
Release + 90 days
Compatibility Program requirement for System Certification
Driver forward distribution policy
Windows 10 S
Code Integrity verification & policy compliance confirmation required
Hardware Dev Center launched Nov 2016.
Fast ramp up in first a couple of months and growth of overall partner volume.
We have migrated most of HLK and HCK drivers. Others including remaining features are in progress as Palani shared at his yesterday’s session.
Release + 90 days concept was introduced last year, and you should be aware 2 main things with this concept.
The impact to the system certification when following for the compatibility program, what HLK version is supported for the certification.
Driver forward distribution policy: when publishing a driver to WU, WU will offer the driver 90
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

6. Windows 10 S Driver Servicing
4/17/2018 3:09 AM
Windows 10 S Driver Servicing
WU = Driver Servicing Tool 
Microsoft unsinged binaries
Executable
Non Microsoft UX
(CPL, 3rd party shell extension)
Code Integrity Policy applied
Microsoft Legacy UX (CPL, 3rd Party Shell extension) NOT allowed
Signing & Publishing
When code integrity is enabled, code execution is restricted to integrity verified code.
Code integrity is a feature that validates the integrity of a driver or system file each time it is loaded into memory. Code integrity detects whether an unsigned driver or system file is being loaded into the kernel, or whether a system file has been modified by malicious software that is being run by a user account with administrator privileges.
Code Integrity Policy
Any binaries not Microsoft signed
.exe installer package (INF base install only)
Microsoft Legacy UX (CPL, 3rd Party Shell extension) NOT allowed
Microsoft signed driver
HLK or Attestation
Confirmation of compatibility and validation
© 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

7. Upcoming Changes (2017) HW Dev Center Improvements
Tech Ready 15
4/17/2018
Upcoming Changes (2017)
HW Dev Center Improvements
Scalable servicing improvements
Windows Update Server
We’re upgrading!
DCHU Transition
Transitioning the driver model to serviceable in scale with minimum cost
Driver Installation (Update)
Driver installation behavior change
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

8. HW Dev Center Migration of remaining Sysdev features
Tech Ready 15
4/17/2018
HW Dev Center
Migration of remaining Sysdev features
WLK, Test Signing, UEFI, etc.
Servicing in scale Improvements
Search, filter capability improvements
Submission process optimization
Public API support for driver servicing tasks
Driver Flighting process optimization
Documentation and Release Notes
Additional contents will be added in MSDN pages
Release notes for monthly updates
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

9. Windows Update Upgrade to modern distribution architecture
WinHEC 2015
4/17/2018 3:09 AM
Windows Update
Upgrade to modern distribution architecture
Performance improvements
Extension INF support (Componentized drivers)
Driver servicing for Creators Update and later
Change with this transition
Specific CHID targeting scenario
We are upgrading Windows Update server that is used for driver update.
Our OS distribution is already using the same infrastructure. The server for the driver is upgrading it to the same model this late summer- to fall.
With this upgrade, you can expect
Publishing performance improvements, large driver package with many targeting destination sometimes took us days to complete the publishing tasks. We are expecting such process in much shorter time. More details will be shared as we deploy and confirm the improvement data.
Extension INF which is a part of DCHU, driver componentization feature. The servicing story is supported with this new server.
Finally, with this new server upgrade, driver signed for Creators Update or later are supported through this new server
What is the impact with this transition?
© 2015 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

10. DCHU Transition Driver for Modern HW Servicing
WinHEC 2015
4/17/2018 3:09 AM
DCHU Transition
Driver for Modern HW Servicing
Declarative
Componentized
Hardware Supported Application
Universal
Servicing Story This Fall
Extension INF (Componentized)
Independent servicing from HW Dev Center
Flighting is supported
HSA (Hardware Supported Application)
Pre-install and targeted servicing
Extension INF (Componentized)
Componentizing Base & Customization by using Extension INF
Allowing independent development and servicing for custom configurations
© 2015 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

11. Driver Installation Minimize disruption by driver installation
Drivers are installed immediately after the installation
Reboot after installation happens when certain conditions are met
( Non-active hours, etc.)
- System not function
Application crash
Driver Installation behavior Change
Delay the installation while user is actively using Windows
Frequent check to ensure the automatic driver is installed in timely manner
!!!!!!!!

12. HLK & Compatibility Program Update

13. Windows Hardware Compatibility Program (WHCP) Updates
Hardware Requirements
Finalized and available at RTM
New requirements added to support DCHU transitions
-Windows 10 S Fall Creators Update: DCH compliant
-Feb 2018: DCH compliant
-Summer 2018: DCHU compliant
Hardware Lab Kit (HLK)
Infrastructure and function remain the same
New jobs to support new requirements
Fall Creators Update Compatibility Program opens at RTM

14. Submit Symbol with Driver Package
Improve Driver Diagnosis
Warning message will be displayed from Fall Creators Update
Public symbols must be submitted with driver package from Spring 2018
How to build Public Symbols
Give us feedback

15. Windows Update for Business

16. Windows Update for Business
WinHEC 2015
4/17/2018 3:09 AM
Windows Update for Business
Address Enterprise customer needs with simple, extensible solutions
Flexibility through MDM and Group Policy settings
Support multiple scenarios within the same organization
Address Enterprise customer needs with simple, extensible solutions
Client centric, policy based method to leverage Windows Update service
Lowers TCO by reducing servicing costs
Flexibility through MDM and Group Policy settings
Settings can be configured separately for Feature and Quality updates
Use other Windows Update policies to manage user experience
Support multiple scenarios within the same organization
Support on premise or remote devices
© 2015 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

17. Type of Update Feature Update Driver Update (Separate) Quality Update
Security and quality revisions, feature additions & change
Semi-annual release
Quality Update
Security and critical update
Non-Windows updates
Can be configured for regular Windows Update
The second Tuesday of each month
Non-deferrable Update Antimalware and antispyware
Cannot be deferred
Driver Update (Separate)
Optional
Dynamic Update (DU)
Critical
Case by case release

18. What’s New Extending support and maximum deferral
Support simplified: Feature updates as supported for 18 months from release
Feature Update maximum deferral doubled (180 days in Anniversary Update to 365 days in Creators Update)
More customization through policy
Both MDM and Group Policy support
Pause policy changes to clarify and make behavior more predictable
Management tool integration
Releasing as part of the SCCM and InTune Creators Update
Win10 support policy
Perhaps one of the bigger policy changes is around support for the operating system. In 1607 and earlier, Microsoft supported each Windows 10 version until the second release after the release, plus an addition 60 days for CBB devices.
Instead, we are simplifying this and providing a clean, 18 month support policy based on the public availability date of the Feature update (e.g., CB).
In addition, we have extended the maximum deferral for Feature updates from 180 days in 1607 to 365 days in 1703, providing a years’ deferral.
More customization through policy
Based on customer feedback, we have again provided more options for utilizing WUfB through MDM and GP policies.
The most important one in 1703 is probably how you set Pause.
Previously, Pause as a switch – you paused a machine, or you switched pause off.
In 1703 you set pause by using a start date, 35 days after which the pause will expire (or earlier if removed) and the device will again check WU for updates.
This provides two benefits:
There is no confusion about when Pause begins or expires (35 days after the defined start date).
IT Pros can set the start date for this policy in the past, essentially shortening the 35 day expiration window.
Management Tool Integration
Both System Center Configuration Manager and InTune are proviing additional support for managing WUfB settings in their 1707 release. More information is available from the SCCM and InTune teams.

19. Greater Control of Driver Servicing
Windows Update for Business WSUS Management tool
Commercial customers ask for the ability manage drivers at a more granular level, allowing them make necessary drivers available, and ignoring driver updates that are not required. Here are three examples :
An IHV supports all of their devices with a single driver. However, specific most updates are for supporting devices that are not on company machines, and IT chooses to not deploy these updates.
A driver has had a history of causing issues within an environment and IT wishes to test these drivers before making them available to their users.
A piece of hardware requires additional configuration before it can be correctly used in an environment. This might a smart card device that requires corporate certificates and configuration options to be installed. IT wants to control the distribution of any updates to this driver to avoid downtime for users.
We’ll focus on Microsoft solutions at a high level, but third party tools can be supported as well.

20. Driver Policy Enterprise customer can select the policy
Exclude driver update from Windows Update
Less flexibility (This is for certain business scenario)
Additional configuration options and tasks may be required
For WSUS:
Within WSUS, download and approve drivers for distribution
For third party management tools
Reference your third party software’s documentation

21. Reporting
Update Compliance | Defender | Upgrade Analytics through OMS

22. HW Dev Center Best Practice

23. Best Practice: Signing
Singing/Certification
Use supported HLK version
Latest HLK version is 1703 for Creators Update
HLK version older than 1607 is not supported
Run INF verifier before submission
HW Dev Center uses INF verifier version
Latest INF verifier available in WDK
Sign according to “Forward distribution policy”
Driver will be offered to N and N+1…
Driver will not be offered to N-1…
Signing for Fall Creators Update will opens at RTM

24. Best Practice: Publishing
WinHEC 2015
Best Practice: Publishing
4/17/2018 3:09 AM
Targeting
HWID vs. CHID
Down level OS vs. Windows 10
HWID Policy
Publishing/Management
Use Shared Product ID
Shared Shipping Label Visibility
Understand Win 10S Compliance
Unique ID (GUID) for Firmware
CHID management
Join Driver Flighting Program!
© 2015 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

25. Tips: HW Dev Center ID System
5 Different IDs
Publisher ID
Private Product ID
Submission ID
Shared Product ID
Shipping Label ID
Resell DUA Scenario
Company A
Company B
Publisher ID: 1
Publisher ID: 2
Private Product ID = Initial driver submission
Submission ID = DUA/Customization ID
Shared Product ID = Only shared ID between companies
Shipping Label ID = Resell or Publishing ID
Initial Driver
Resold Driver
Private Product ID: A100
Private Product ID: A101
Submission ID: B200
Submission ID: B201
Shared Product ID: C300
Shared Product ID: C300
Shipping Label ID: D401
Shipping Label ID: D402

26. Tracking your submission
Use Shared Product ID
Private Product ID
Product ID>
Where is Shipping Label ID?
Product ID>/submission/<Submission ID>/ShippingLabel/<Shipping Label ID>
Know your global administrator and Publisher ID
There is one global admin who can manage user role/permission and new registration
Publisher ID is assigned to each account/company
Shared Product ID

27. Debugging HW Dev Center issue
#?debug for capturing diagnostic information

28. Device Certification Report
WinHEC 2015
4/17/2018 3:09 AM
Device Certification Report
Downloading the Certification Report
Build URL with 3 IDs
ID>/<Private Product ID>/<Submission ID>
*Compatible product list view for HW Dev Center will be supported in the future
© 2015 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

29. Did you know? Shipping Label
While promotion request is in process, we publish the driver to WU as Optional
(Deprecated) means you tried to make a change not supported, you need to create a new Shipping Label
No Windows 10 S category: Windows 10 driver can be distributed to Windows 10 S as long as confirming the compliance & policy requirement
If you make any changes and republish the promotion Shipping Label, the Flight review restarts

30. Call to Actions Prepare your HW Servicing for this Fall
DCHU readiness & related new servicing scenarios
New HLK requirements and enforcement timing
Understand Enterprise HW Servicing offerings
Windows Update for Business policy and update
Follow HW Dev Center Best Practices

31. Resource Universal Driver How to Public Symbols Hardware Dev Center
How to Public Symbols
Hardware Dev Center
Windows Update for Business

32. 4/17/2018 3:09 AM
© 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.