Hello,
we have updated out OVPN Client to 2.4.4 and also the RDM Add-On for OVPN (2.5.3.0). We configured that RDM should ask after the session to close the VPN - if we confirm this, OVPN will not be closed - respectively disconnected.
If the user is not member of the local administrator group, rather member of "OpenVPN Administrators" (membership will be asked by first access without a admin account) the OpenVPNGUI disappears from the taskbar, but is still running in background (checked via task manager and network- and sharingcenter) and the VPN connection are still active.
We tried it also with a user account that is a member of local admin group -> same behaviour
It would be perfect if the application could be closed (kill the application) with a non local admin account.
Appears on RDM Version: 13.0.6.0
Thanks!
Regards,
Min
Hello Min,
This is a really good question and we have some questions about if it's possible to do it in RDM.
First, does Windows let a non local admin account the possibility to kill a process?
If yes, what is the exact process name that you would like to close?
Best regards,
David Grandolfo
Hello David!
here some more infos:
I made some more tests and we figured follwing out:
It looks like a issue with the new OVPN version.
The openvpn-gui.exe is still active in the background (and in the info bar). If we now want ro start aanother or the same session again, it looks like that RDM believe the VPN is already open and did not tryto open the VPN, instead the session starts and failes, beacause of no VPN ;) If I kill (as non admin user) the task openvpn-gui.exe before I attempt to open a connection in RDM everything works flawless.
I think it would be helpful to add an option to the OVPN entry like "kill openvpn-gui.exe process after disconnect" and identify why the button "Close VPN" is without function in this case.
Or reconfigure the Option "Kill existing OpenVPN sessions before connection" to kill the task before the new VPN are connected (in our case the option is already checked)
Tested this behviour with a user without administrative permission on windows 10 and server 2016.
Just one important thing: OVPN must be at least version 2.4.4 - with lower version the issue with the add route is still present.
So i was able to succesfully configure the OVPN without admin rights, only the way for disconnection need some adaption :)
Thanks!
Regards,
Min
Hello,
I had a chat with Hubert and he mentioned me that when we close the VPN, there's already a taskkill of OpenVPN.
However, it seems that you would need to run RDM as an administrator to accomplish this.
That being said, are you running RDM as an administrator?
Best regards,
Jeff Dagenais
Hello Jeff,
no, RDM is running in user context. But the openvpn-gui.exe can be killed via taskmanger (as user) - therefore I think this would be possible via RDM?
Thanks!
Regards,
Min
Hello,
Could you test with elevated privileges to see if it's working or not please. If it's working, there's probably something that we can do to fix this.
Best regards,
Jeff Dagenais
Hello,
with elevated privileges the openvpn-gui.exe will be succesfully killed. And, if you reconnect to a session where the VPN is linked, the OpenVPN GUI will be opened correctly.
If you need, I can provide my OpenVPN configuration settings.
Regards,
Min
Hello,
Thanks for testing. Let me verify this with Hubert and get back to you.
Best regards,
Jeff Dagenais
Hello,
I had a chat with Hubert and they don't have found a solution regarding this for the moment. They will continue to look at it.
Best regards,
Jeff Dagenais
Hello,
thanks for the effort guys! :) If you need additional informations or I can help / test anything please let me know! ;)
Regards,
Min