Windows Certification Program：Windows认证程序.docx

Windows Certification Program - 42Windows Certification ProgramHardware Certification Policies and ProcessesJanuary 7, 2014AbstractThis paper provides information about the Windows Hardware Certification Program. It contains high-level guidelines on certification testing and product submission policies, and useful business process requirements. This document has been updated to reflect new processes and policies for the launch of Windows 8.1Document HistoryDateChangeJanuary 7, 2014Submission fees removed. Updated Touch Device Resubmission instructions. Addition of Graphic Adapter Test Optimization Procedure.November 22, 2013Added links to certification newsletter and certification blog.July 3, 2013Updated for Windows 8.1, Server 2012 R2, and the revised HCK for Windows 8.1. Added contingency policy and simplified Windows 8 testing. New fees for submissions are documented. November 13, 2012Added Windows RT connected devices, specialized PC, updated details for multifunction device testing and docking stations.October 26, 2012Updated testing fees for Windows8 and Windows Server2012.Added information on the policy for using previously certified motherboards in client systems.May 10, 2012Added information on Signature-only policies, UEFI requirements, and server testing requirements.Additional edits for style and clarity.February 28, 2012First publicationDisclaimer: This document is provided as-is. Information and views expressed in this document, including URL and other Internet website references, may change without notice. Some information relates to pre-released product, which may be substantially modified being commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here. You bear the risk of using it.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. 2014 Microsoft. All rights reserved.DirectX, Microsoft, MSDN, Windows, Windows Server, and Windows Vista are trademarks of the Microsoft group of companies. All other trademarks are property of their respective owners.ContentsIntroduction5Overview of Windows Hardware Certification5General certification concepts, policies, and processes6How requirements are defined and tested6Turning a positive test result into certification7Product Types7Testing optional features and functionality8How do I know what requirements my product needs to meet?8What if my product type is not automatically discovered?8“Other” products and conditional certification8General certification testing policies9General testing guidance9Testing all features and functionality10Seeking Windows HCK support10Correcting false test failures with errata10Contingencies11Merging test results into a single submission or project12Submission requirements13Legal agreements13Essential agreements13Optional agreements13Symbol files14Listing products14Product naming15Naming restrictions15Product name details15Post-certification requirements16Certification and support obligation lifetime16Audits17Audit selection and product procurement17Response to observed audit failures17Submissions types that dont require complete testing18Reseller submissions18Driver update acceptable18Conditions where a DUA is acceptable19Conditions for a DUA19Submissions for device driver maintenance19Acceptable device changes without resubmitting19Simplified submissions for Windows 820Testing policies for devices21Device family testing21Definition of family21Determining when to consider a group of devices as a separate family21Portable device families24Network media device families25Multifunction devices26Special cases for multifunction devices27Testing devices with multiple connectivity28Switched-mode devices28WindowsRT connected device certification and testing28Testing exception for network media devices and routers29Para-virtualization drivers29Touch device testing31Touch Device Resubmission and Multi-source Subcomponents31Graphic Adapters Test Optimization Procedure32Testing policies for client systems33Certified components33Digital signature policy for systems33Systems and the use of Signature-only components34System form-factor definitions34Using previously certified motherboards in client systems35Specialized PCs36Testing a docking station designed for the system37System family testing and updates that require a new submission37Testing GPUs across different GPU families38Using Distributed Testing for System Family Testing38Touch device39Sensors39UEFI requirements for systems and devices39UEFI configuration for system certification39UEFI client system required for device testing40UEFI and Server systems40Testing policies for server system41Up-level and down-level certification policies for Windows Server 2012 and Windows Server 2012 R241Run Server tests on physical hardware41Rules that control server system testing and retesting41Closing comments42IntroductionWelcome to the Windows Certification Program for Windows8.1. This document updates earlier versions to reflect the changes in the program brought about by Windows 8.1, Windows Server 2012 R2 and the Windows Hardware Certification Kit for Windows 8.1.This document contains the business policies to prepare products for Windows8.1 and Windows Server 2012 R2 for use with x86/x64-based systems and successfully certify those products. The policies for certifying devices for Windows RT are included. The policies and processes for testing and submitting Windows RT systems are covered in a separate document. For clarification, contact with any questions. Overview of Windows Hardware Certification The Windows Certification Program is the primary channel that we use to communicate to the partner community the core expectations that Windows places on devices, kernel-affecting software, and systems so that those products can successfully and seamlessly integrate into Windows. This communication starts with the core tenets and user scenarios that drove Windows design. Those design principles translate into a set of features that cover fundamentals, connectivity, and device-specific features. These design features are codified as discrete requirements which define what Windows expects from the various components and connected devices. A device designed to meet the requirements will be reliable, stable, efficient in power and performance, and provide a great Windows experience.The program is unique in the industry in terms of the detail and engineering tools that can freely provide to build, test, secure, and maintain products for success in the Windows environment. No other program provides access to in the field telemetry to facilitate end-user support and quality assurance, nor as powerful a method to deliver software, driver and certain firmware updates to end-users to correct identified problems or allow new features to be embraced. Partners can self-assess how their products comply with certification requirements by using the tests in the Windows Hardware Certification Kit (HCK). The current version of the Windows HCK is named the WindowsHCK for Windows 8.1. The Windows HCK for Windows 8.1 supports testing all actively certified versions of Windows and contains significant enhancements to encourage efficient testing practices, such as early and focused testing, distributed testing and merged multifunction device fundamental testing. Not all requirements are testable in an automated fashion, and automated testing cant fully assure absolute compliance with the requirements, so we continue to analyze the end-user experience and improve the tools over time. Certification is a public statement of confidence from us that the tested device, filter driver, or system works well with Windows. Certification benefits include: Signing the device drivers. Publishing the product as certified in various catalogs and the compatibility center. Collecting and pre-analyzing telemetry on your product in the field to improve your quality assurance efforts. Providing a free and extremely effective distribution channel for driver updates. Providing eligibility for various marketing incentives and a logo license.The following processes and policies describe how the program moves from a collection of requirements and tests to certification of a product. These policies can have an impact on a products eligibility for certification and the efficiency of your efforts. Use them in planning for testing cycles and resources.The Windows Certification Program continuously re-evaluates the requirements and the test environment, with major revisions timed to Windows releases. This policy and process guide reflects the latest requirements and testing philosophy. We reserve the right to revise these policies as needed to improve the program. Revisions in the policies described here will be announced in the certification newsletter or in the certification blog, and changes will be listed in the Document History section of this document.The Policy FAQ on MSDN may address questions regarding these policies. For any additional questions that are not covered in the FAQ, contact . Questions on policy are also taken in the forum located at /Forums/en-US/whck.General certification concepts, policies, and processesHow requirements are defined and testedSome key terms describe how we test the Windows scenarios that certification is validating.A feature is a Windows capability that is exposed or enhanced by a device or a kernel-mode driver. Features fit into these classifications: Fundamental features that are common to any device or driver in the environment. Connectivity features that are necessary for a particular bus and protocol to work successfully. Critical features that are necessary for a particular product to interoperate with Windows. Optional features that enhance the experience that the device provides.Features use a descriptive CamelCase name, like Device.Graphics.WDDM13, System.Client.BluetoothController.Base, or Filter.Driver.Network.LWF. A requirement is the written document that specifies what a device must do to qualify for Windows hardware certification. See Windows8 Hardware Certification Requirements in the Windows Dev Center. Within the namespace, requirements are descendants of features. For example, Device.Imaging.Scanner.Base.RawFileFormat is a requirement for the feature Device.Imaging.Scanner.Base.The Windows Certification Program uses the Windows HCK to assess compliance with the requirements. The Windows HCK uses a unique method to determine which tests are necessary to run. The Windows HCK identifies the features of the product that is being tested and generates a set of tests for the test harness to schedule. For specific guidance on how to use the Windows HCK, see Windows Hardware Certification Step-by-Step Guide. This document includes policies for testing practices. The current version of the Windows HCK is HCK for Windows 8.1.A product type is a collection of features that are associated with a particular device, filter, or system in common use with Windows. Product types are important for identifying a category of product for catalogs, compatibility lists, and the dev nodes and inner workings of Windows. Most partners who are engaged in the certification program are actively seeking to certify a particular product that matches a product type.Turning a positive test result into certificationAnyone can download and use the requirements and the Windows HCK. We encourage you to design your product to meet the certification requirements and then test compliance with the requirements throughout the product cycle. However, to fully participate in the certification program and have the product certified, you must register with the Windows Certification Program through the membership process that is described at the Hardware and Desktop dashboard in the Windows Dev Center.After you register with the program and the product has completed testing, create a submission package and submit it for certification at Hardware and Desktop dashboard. Product TypesThe process for hardware certification has changed. In the earlier kit, Windows Logo Kit1.6, you selected a category to test and assumed that that category contained the right set of tests that exercised all of the device features that interoperate with Windows. The Windows HCK implements feature-based testing. The test harness detects all of the features of the device that interoperate with Windows and schedules testing for all implemented features. The certification process evaluates all of the exposed features of the device, rather than only a subset of features.This new approach has a definite advantage when the device being tested does not fit neatly into a defined category or exposes multiple functions. For example, a device may connect in many different ways. Each method represents a testable feature. These connectivity features dont contribute to the definition of product types, but are expected to be tested as an exposed feature.Tests are grouped into product types rather than categories, which provide certified product with a label that is appropriate for cataloging.When a device is tested, the kit identifies any product types that the device is eligible to claim in the catalog. If more than one product type matches the features that a device exposes, you may choose what product type best describes the device.Testing optional features and functionalityDefinitions of product types contain only the minimum feature set that is necessary to describe those product types. Windows is designed to support beyond the basics in many scenarios, and many defined features are optional. The Windows HCK tests any known features that your product exposes to Windows. For a product to be certified, it must pass all the Windows HCK tests. The tests validate the required and optional features of the product.How do I know what requirements my product needs to meet?All Products will expose a suite of features that can be categorized into 5 basic groupings. These features map to requirements and tests. The five groups are:1. Basic features expected of any device, filter or system (the fundamental features) 2. The connectivity features exposed for the type of connectivity the device uses.3. The features that define the basics of a Product Type4. The optional features that are associated with a feature area. If your device or system exposes an optional feature the device must successfully comply with all of the associated requirements.5. Additional features that are related to secondary functions added to the product. For example, removable storage is commonly found on mobile broadband USB-connected units.For your convenience, a product type matrix is located at /download/2/3/6/23662F33-71E8-43C1-8547-5DE49B0374AB/windows-hck-product-type-matrix.zip. This file can help identify all of the features, requirements and tests your submission will need to comply with for certification.What if my product type is not automatically discovered?Occasionally the gatherer will not detect all of the features your device supports and therefore the product type options exposed in the kit for certification does not include the certification product type you are after. In this case, from the selection tab in the HCK, right click to see the list of all features and manually add the missing features. This process will improve over time as the detection becomes more sophisticated. “Other” products and conditional certificationSome devices introduce features for which Windows has no specific design scenario. In previous programs, a product that does not map to a product type was called Unclassified and was tested with a limited set of tests which assured the driver installed correctly but little else. As a platform, we embrace innovation, but we retain the reliability and performance of Windows by testing whatever features these innovative devices expose to the operating system. These unclassified devices that do not match a Product Type are now designated “Device-Other” or in some cases a more specific classification like “Storage Device-Other” to reflect certain additional features in key areas were exposed. The Other classification allows for signing of the drivers and distribution on Windows Update, but the device does not receive the complete benefits of a certified product.If your device does not match any product type definition no product types will appear in the Windows HCK. On submission, however, the option “Device Other” will be visible. The limitations of “Other” products are: They arent certified for Windows because they dont match recognized product types that are designed for Windows scenarios. They arent mentioned in certified product listings or catalogs. They cant use the Windows logo artwork. To avoid confusion with certified products, “Other” products cant use the same product names as certified products. A certified system cant replace expected functionality normally provided by a component of a defined product type with an “Other” product.Despite these limitations, “Other” devices do receive important benefits: The products driver receives a Microsoft digital signature and is distributable on Windows Update. The product can take advantage of metadata services. Microsoft teleme