|
From: Charles D. <cd...@sp...> - 2006-12-14 16:15:19
|
Kris Jordan wrote: > Darren Spruell wrote, On 12/12/2006 6:57 PM: >> On 12/12/06, Kris Jordan <ope...@jj...> wrote: >>> Windows 2k/XP: >>> >>> Is there an automated method to rename the newly created OpenVPN tap >>> network connection? Like "Local Area Connection 28" --> "Company VPN". >>> The only hope I see, is doing something to the tap driver installation >>> to give it a specific name to begin with, but I don't see anything >>> special in the .inf file for this. >> The string used for the description field on the interface is stored >> in the registry in several locations. In theory you could find the >> key(s) that store that and update them, perhaps as part of your >> installationi script or something. > > Yeah, found the keys before I send the email. But I don't see a way to > distinguish which one is the current/new one. Windows also doesn't > bother to remove the non-existent interface registry keys either. I don't know how Windows UUIDs are formatted -- but type 1 GUIDs have their creation time encoded; that section could possibly be used for comparison. For just narrowing down which devices are tap-win32 adapters, you might look at what openvpn --show-adapters does and the relevant code behind it. |