Hi,
$customer is asking for advice how to setup OpenVPN on Windows in a
"pre-logon" fashion ("so the machine can talk to AD right away").So I found https://gist.github.com/selvanair/1a1f12b9b2a040f5b92b9fb5f3d83f91?permalink_comment_id=4518375 which all makes sense, except for the "pwfile" and "port" thing (--management...) - well, of course it makes sense, but I wonder how to automate this in a good way. Our config files come from a config maker tool ("you authorize to an internal host, click on what profile type you want, and get a .ovpn for download") - which has no way to add a password file, and no way to ensure that $port is actually *free* on "that windows". So, anyone here using PLAP? How do you set up your user PCs, in a way that does not require hours of admin time to maintain? gert -- "If was one thing all people took for granted, was conviction that if you feed honest figures into a computer, honest figures come out. Never doubted it myself till I met a computer with a sense of humor." Robert A. Heinlein, The Moon is a Harsh Mistress Gert Doering - Munich, Germany [email protected]
signature.asc
Description: PGP signature
_______________________________________________ Openvpn-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openvpn-devel
