David Edfeldt Windows Logo Program

 Unintentional failures in the logo tests that are masked by filtering the results:  Applied to every submission matching the proper conditions.  Limited life expectancy until test can be fixed.  Expanded to be helpful hints even when the failure is not to be removed.

Log with failures Goes through errata filter Problem resolved automatically

 Problem identified (CSS, WHQL, test).  Incident Bug Created (Common Bug DB).  Test Dev Does analysis:  If a test problem test bug created  If possible filter created  Filter entered into Winqual system:  Regex with constraints  Downloadable  Same filter used in WLK and on Winqual site

 Born from incidents.  Recognized as correct outcome but unnecessary support hit:  Unclear setup  Poor documentation  Common coding problem  Focused FAQ triggered by a failure message in a log

 Some of this is actually driving some manual reviews into automated (mark tomorrow).  Are looking at the errata volume to drive fix and prioritize QFE.  Using the data to reality check proper application of errata.

 Logopoint POLICY-007.  Failure allowed to a logo requirement based on a business judgment.

 A Contingency Agreement may be requested when a test failure has been determined to be caused by a problem with the device or driver being submitted for logo, but the submitting partner believes it is in the best interest of the partner and Microsoft to waive the requirement until it can be remedied.

 Get-out-of-jail-free card  Some statistics:  Contingencies requested since Windows Vista launch – 68  Contingencies approved – 35  Pending – 9  Total submissions where contingencies were applied – 130

 PCI failures (we did not expose test, no customer impact because not PCI requirements that Windows leverages).  HPET – not clearly defined, too short a window.  Digital Audio Jack – Analog solution did not defeat DRM. Aggressive plan to correct. No customer impact since the DTM had not hit market.

 Contingencies may be granted for a limited period based on an assessment of the technical issue and the related business needs after fully considering the customer impact and the firm commitment from the affected partner to resolve the issues. Not all contingencies are approved.  The typical contingency review process takes 4 to 6 weeks, please plan in advance prior to making any requests.  Once a contingency is approved by Microsoft, a legal agreement is signed and a contingency filter is created which in most cases will reverse a failure on submission (some may require manual review, depending on the nature of the failure).  Approved Contingencies are not covered under Non-Disclosure Agreement (NDA). Microsoft reserves the right to publish the information regarding the affected hardware products.

 “Windows Logo Program Procedures and Information” document.  "How to request a contingency" section.  Reviewed and introduced by logo team member specializing in that area.  Weekly meetings of review board.  Approval of logo team and device area.  TAMs can be very helpful.

 © 2007 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.