wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: Bruno UT1 <bandry@ut1.org>
To: wireguard@lists.zx2c4.com
Subject: Windows Client - issue with LimitedOperatorUI rights
Date: Tue, 13 Jul 2021 16:59:30 +0200	[thread overview]
Message-ID: <fb69332b-a210-179a-4692-995f8dc19b5b@ut1.org> (raw)

Hi !

I install Wireguard Client on Windows 10 systems.

My users are not administrators, so the registry key LimitedOperatorUI 
is set to 1.

My issue is that the client has to run at least once as administrator to 
work for "Network Configuration Operators".

My script adds users to the administrative group, create the registry 
key then installs Wireguard Client:

  - If i don't use the parameter |DO_NOT_LAUNCH, |I have a popup telling 
me I need administrator rights. I don't want that popup, be everything 
works after a reboot.

  - If I use the parameter |DO_NOT_LAUNCH,| ||I don't have the popup but 
Wireguard don't start, even after a reboot. If I run Wireguard as 
administrator, it's unlocked for other users.

  - A third possibility is to install the client after a reboot, so the 
rights are good, |DO_NOT_LAUNCH |is not needed and no popup appears. But 
I don't want to force that reboot (I use SCCM and it don't like reboots 
before install is complete).

So I think there is a first start issue that needs administrator rights 
even with LimitedOperatorUI  active.



ps: I send another message (06/28) for another issue. I received "Your 
message to WireGuard awaits moderator approval" but message isn't posted 
and i got no notification from the moderator. Am I doing something wrong ?

                 reply	other threads:[~2021-08-08 22:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fb69332b-a210-179a-4692-995f8dc19b5b@ut1.org \
    --to=bandry@ut1.org \
    --cc=wireguard@lists.zx2c4.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).