Changes between Version 31 and Version 32 of HLKTesting


Ignore:
Timestamp:
05/15/19 07:36:16 (5 years ago)
Author:
Samuli Seppänen
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • HLKTesting

    v31 v32  
    2424= HLK test environment overview =
    2525
    26 HLK testing always requires a HLK !Controller/Studio node, plus one or more HLK clients.
     26HLK testing always requires a HLK !Controller/Studio node, plus one or more HLK clients. The HLK client Windows version and HLK versions need to be in sync [https://docs.microsoft.com/en-us/windows-hardware/test/hlk/
     27as described in MS documentation.
     28
    2729
    2830According to practical testing done by [https://www.wintun.net/ wintun] developers it is possible to get a code signature that is valid for all Windows 10 platforms using the following HLK clients:
     
    5153
    5254For HLK software installation please refer to the official MS documentation, check out [https://github.com/Puppet-Finland/puppet-hlk/ puppet-hlk] or try out the [https://docs.microsoft.com/en-us/windows-hardware/test/hlk/getstarted/getstarted-vhlk Windows Virtual Hardware Lab Kit].
     55
     56The version of HLK you need to install depends on the version of Windows you're attempting certify as described in [https://docs.microsoft.com/en-us/windows-hardware/test/hlk/ Microsoft documentation].
    5357
    5458= Preparing HLK clients for test-signed drivers =