Generating Windows MSI with autologin VERSUS installing "openvpn-install....exe" with autologin .OVPN config file.

Business solution to host your own OpenVPN server with web management interface and bundled clients.
Post Reply
gjones
OpenVpn Newbie
Posts: 1
Joined: Mon Oct 10, 2016 11:41 pm

Generating Windows MSI with autologin VERSUS installing "openvpn-install....exe" with autologin .OVPN config file.

Post by gjones » Wed Dec 07, 2016 3:20 pm

Hello,

In relation to the above outlined installation for a user (i.e. use Access Server to generate an MSI or use the Community Download for the OpenVPN-install-2.3....._64.exe) are there any specific technical security differences (i.e. advantages / disadvantages) to either approach from an end user perspective if they still use the same autologin profile?

From an automation perspective, I would prefer the MSI approach but can easily change to the Community Download GUI approach should this be better.

Curious to know as I can't quite find this information on the forums.

Note: Currently running Openvpn-as-2.0.24-CentOS6.x86_64

Thanks

GJ

Post Reply