(21:04:58) mattock: assuming Microsoft's systems are happy with the test submission package, that is (21:05:12) mattock: they _should_ be, but we have not tested submitting anything yes
1. Do the SDV and DVL to get tap901.DVL.xml. 2. Compile the driver and EV sign it. Save PDBs too. 3. Deploy the driver on test computers (including tap901.DVL.xml, remember?). 4. Do the WHLK. 5. When creating submission package, add the driver binaries and PDBs (on HLK Studio submission page). 6. Submit the driver to Microsoft WHQL. 7. Miscrosoft should return you a WHQL signed driver in about 10 minutes. (21:07:09) mattock: worst case scenario is that I have to reinstall the HLK client as Windows Server 2019 core _if_ Microsoft is not happy with the "Operate in Server Core" having been run on a virtual machine, or on some old i5 laptop which does not have the required 4 physical processor cores Microsoft is fine with that test being run on a virtual Windows Server 2019 Core in Wintun case. And this test is pretty straight forward - just checks that driver loads and adapter responds, it doesn't need to be connected and have traffic. Use devcon to make a single TAP adapter on the Server Core. No need to have a running OpenVPN connection for this test to pass. (21:14:42) mattock: I also finally ate our own dogfood and installer OpenVPN on the virtual host running the HLK controller so that I can access the HLK controller and clients remotely, which speeds the testing up quite a bit Not a good idea, as WHLK tests can and will interfere with all TAP-Windows6 adapters on test computers. Not just the one that is being tested. Expect OpenVPN connections to flicker or die. Just use it to access controller server only. I never experienced any issues requiring intervention on test computers. Best regards, Simon
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
