> > We add them to the Windows built-in "Network Configuration > Operators" > > Do you know this to work with Windows 8 Enterprise (or Win 10 > for that matter)? I've seen this work in some versions of > Windows, but when we tried it in Win 8 Enterprise, it didn't > seem to work. We didn't probe further, suspecting that it > was due to security changes in Windows >=8.
I dealt with this issue recently, so I'll chime in for my $0.02. This works for WinXP, but for Vista and newer, you really need the OpenVPN GUI add-on. IIRC, the particular security group no longer provides the desired permissions in Vista and newer. With the GUI add-on, basically you ensure that the openvpn service is running (autostart) and add a few lines to your .ovpn config, something the likes of: management 127.0.0.1 1194 management-hold management-query-passwords auth-retry interact and then the OpenVPN GUI will connect to the openvpn service to manage it "remotely". So basically the permission issue is avoided by letting the openvpn service perform all the tasks instead. After putting some registry settings and adding command line args to the GUI shortcut, it all works nice enough. On a sidenote, setting the openvpn service to autostart may result in some odd post-login delays. Setting it to delayed start avoids this, but that means that the user needs to be competent / patient enough to wait until the service is up and running, which can take a while, and close / re-open the GUI client afterwards. -Marijn _______________________________________________ List mailing list List@lists.pfsense.org https://lists.pfsense.org/mailman/listinfo/list
