Changes between Version 63 and Version 64 of HLKTesting


Ignore:
Timestamp:
07/02/19 12:11:41 (5 years ago)
Author:
Samuli Seppänen
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • HLKTesting

    v63 v64  
    423423This was done to be consistent with what was in constants.h, but it also seemed to get some tests passing.
    424424
     425== Test-signing issues ==
     426
     427You may encounter the follwoing error when building with EWDK from the command-line with buildtap.py with --hlk switch, which has test-signing enabled:
     428
     429{{{
     430SIGNTASK : SignTool error : No certificates were found that met all the given criteria.
     431}}}
     432
     433This happens even though a properly named (e.g. "WDKTest samuli") certificate is present under ''cert:\!CurrentUser\My''. This problem was probably caused doing a "Hlk" build from inside Visual Studio 2019 Community, which created the WDKTest certificate automatically, but in a way that EWDK was unable to use it.
     434
     435This problem can be resolved by simply removing the old certificate. For example:
     436
     437{{{
     438PS> Remove-Item Cert:\CurrentUser\My\91047502F73D5410C106E05CEC8A990219810FBE
     439}}}
     440
     441Then just run buildtap.py with --hlk to create a new test-signing certificate.
     442
     443You will also need to export the new certificate from the certificate store. For example:
     444
     445{{{
     446PS> Get-Childitem Cert:\Currentuser\My\F1E725722C5BB56757B6D261D958425869213089|Export-Certificate -Filepath C:\users\samuli\opt\wdktest-samuli.cer
     447}}}
     448
     449Then import that certificate to the certificate store on HLK clients. The puppet-hlk_tap6_openvpn module handles that part automatically with Powershell DSC.
     450
    425451= HLK logging =
    426452