Changes between Version 32 and Version 33 of HLKTesting


Ignore:
Timestamp:
05/23/19 15:09:01 (5 years ago)
Author:
Samuli Seppänen
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • HLKTesting

    v32 v33  
    5050* HLK clients need to be physical computers, not virtualized (unverified)
    5151
     52Also remember to rename the network devices ("MessageDevice", "SupportDevice0") as described [https://docs.microsoft.com/en-us/windows-hardware/test/hlk/testref/lan-testing-prerequisites LAN testing prerequisites].
     53
    5254= Installing HLK software =
    5355
    5456For 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].
    5557
    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].
     58The 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]. To check Windows version from Powershell do:
     59
     60{{{
     61PS> [System.Environment]::OSVersion.Version
     62}}}
    5763
    5864= Preparing HLK clients for test-signed drivers =
     
    256262= Configuring and running the mandatory HLK tests =
    257263
     264== Adding machines to pool ==
     265
     266It seems required/useful to add HLK clients to the pool first, then the support machine. Otherwise when you select the driver in "Device manager" tab HLK will assume that the HLK support machine has the driver under test. This ''may'' create problems down the line.
     267
    258268== Multi-machine tests ==
    259269
     
    368378Installing HLK software automatically opens ports in the Windows firewall for HLK traffic. In case HLK controller and HLK clients are not in the same switch some firewall (e.g. EC2 security group rules) might block HLK traffic. Here is a reference for the ports which need to be open for HLK tests to work:
    369379
    370 * HLK clients -> OpenVPN server udp/1194
     380* OpenVPN peer (udp/1194) <-> OpenVPN peer (udp/1194)
    371381* HLK clients -> HLK controller tcp/1771 (HLK Server Receiver Port)
    372382* HLK clients -> HLK controller tcp/1782 (HLKSvc Receiver Port)