I believe there's a bug in the Windows service implementation, if this issue is by design, it's problematic.
I have non-admin users were when I initially set them up with wireguard, I configured it to use the service, using the command: wireguard /installtunnelservice "C:\Program Files\WireGuard\Data\Configurations\vpn.domain.org.conf.dpapi" The tunnel worked fine the first time. Then the user reboots the laptop, or closes it or leaves whatever coffee shop they were at and get disconnected from the wireless network they were using. When this happens, for some reason, the wireguard service then gets torn down never to come back again until I issue the command from my admin account again. There was an issue with some users initial configuration in that they could not query hostname via DNS, so that entering the command to installservice would not even create the service. Here's a few notes that might help with understanding. - Users must have the VPN established before they log into the active directory servers on the remote network so that they can get all of their GPO directives. - Wireguard Service should stay up so that any time a users connects to any network, the VPN is established immediately after that. - The Wireguard service should also stay because non-admin users cannot create a new service If this issue is how things will stay, and this is not considered a bug, how would you configure windows non-admin users to tunnel to an enterprise network before login via WireGuard and to continuously try to establish the tunnel while the user is not connected to a network? -- Tony Pros - Owner t...@tpro.tech 615 656 3543 T-Pro Tech LLC Audio & IT Consulting
