Windows: Does OpenVNP make perm.changes (ie tapinstall*.exe)

How to customize and extend your OpenVPN installation.

Moderators: TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech

Post Reply
johnbessa
OpenVpn Newbie
Posts: 2
Joined: Sat Feb 09, 2013 2:34 pm

Windows: Does OpenVNP make perm.changes (ie tapinstall*.exe)

Post by johnbessa » Sat Feb 09, 2013 2:46 pm

Hello,

Does OpenVPN make "intrusive" changes to the system, by which I think I need to say (for the domain) "permanent changes that will not be 'erased' by a reboot?" I need this for customer acceptance.

VPCS (virt pc for cisco admin) does not make any changes at all --that I can tell. I am not really a "windows person" so the underlying system is basically alien to me.

I just got introduced to OpenVPN through Qemu and require an free/open solution.

Thanks, John

mokk
OpenVPN User
Posts: 21
Joined: Thu Dec 30, 2010 2:03 am

Re: Windows: Does OpenVNP make perm.changes (ie tapinstall*.

Post by mokk » Thu Feb 21, 2013 12:21 pm

tapinstall.exe is just a renamed DevCon.exe (http://support.microsoft.com/kb/311272/en-us). If tapinstall.exe installs a TAP device driver, this change is obviously permanent. So tapinstall.exe adds a new network adapter and a new network connection (a network interface) to the system. Is it a big deal? :) Oh, and openvpnserv.exe installs a new service (OpenVPNService).

johnbessa
OpenVpn Newbie
Posts: 2
Joined: Sat Feb 09, 2013 2:34 pm

Re: Windows: Does OpenVNP make perm.changes (ie tapinstall*.

Post by johnbessa » Thu Feb 21, 2013 9:36 pm

Thanks, making changes would not be a problem from the user perspective, then, if microsoft does it. On the other hand, running without the ability to use admin privileges would be a problem on, say, a library machine

Thanks again, appreciate it, John

Post Reply