Changes between Version 32 and Version 33 of HLKTesting
- Timestamp:
- 05/23/19 15:09:01 (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
HLKTesting
v32 v33 50 50 * HLK clients need to be physical computers, not virtualized (unverified) 51 51 52 Also 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 52 54 = Installing HLK software = 53 55 54 56 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 57 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]. 58 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]. To check Windows version from Powershell do: 59 60 {{{ 61 PS> [System.Environment]::OSVersion.Version 62 }}} 57 63 58 64 = Preparing HLK clients for test-signed drivers = … … 256 262 = Configuring and running the mandatory HLK tests = 257 263 264 == Adding machines to pool == 265 266 It 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 258 268 == Multi-machine tests == 259 269 … … 368 378 Installing 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: 369 379 370 * HLK clients -> OpenVPN server udp/1194380 * OpenVPN peer (udp/1194) <-> OpenVPN peer (udp/1194) 371 381 * HLK clients -> HLK controller tcp/1771 (HLK Server Receiver Port) 372 382 * HLK clients -> HLK controller tcp/1782 (HLKSvc Receiver Port)