Changes between Version 74 and Version 75 of HLKTesting

Timestamp:

07/08/19 17:31:37 (5 years ago)

Author:

Samuli Seppänen

Comment:

--

HLKTesting

@@ -24 +24 @@
 = HLK test environment overview =
 
-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/ as described in MS documentation].
+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/ as described in MS documentation]. For example, if your goal is to get a signature for Windows Server 2019 you need to use HLK 1809. This requirement is clearly outlined in the [https://techcommunity.microsoft.com/t5/Windows-Hardware-Certification/Accepting-Windows-10-version-1809-and-Windows-Server-2019/ba-p/364926 HLK 1809 release blog post]. Additionally since [https://techcommunity.microsoft.com/t5/Windows-Hardware-Certification/Accepting-Windows-10-version-1803-submissions/ba-p/364921 HLK 1709 release] HLK will support testing a single Windows 10 version only.
 
 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: