Changes between Version 31 and Version 32 of HLKTesting
- Timestamp:
- 05/15/19 07:36:16 (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
HLKTesting
v31 v32 24 24 = HLK test environment overview = 25 25 26 HLK testing always requires a HLK !Controller/Studio node, plus one or more HLK clients. 26 HLK 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/ 27 as described in MS documentation. 28 27 29 28 30 According 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: … … 51 53 52 54 For 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 56 The 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]. 53 57 54 58 = Preparing HLK clients for test-signed drivers =