X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:in-reply-to
	:references:mime-version:content-type:content-transfer-encoding;
	 q=dns; s=default; b=aqFXsCzER2o8vK9DDpgs58H9RUGUUa3I+Gt4wgrtEVs
	umUFUJkw1NR3++TXV17a8Mw12QmTPMcIqrcV0Og0JNI4ordjiHsze+G80P57wU2W
	VxP87lIIqSTIfChchCRoKU8syqkUPrLJg8CZ+qPKrY4xkbNvcxQtkGdMvBdKK9hs
	=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:in-reply-to
	:references:mime-version:content-type:content-transfer-encoding;
	 s=default; bh=KLwtiQBqrESITkrGEgcmOeX/ABg=; b=w4dmikpqO8Y3SWKV+
	EXC6xANynb7l7tM52KQuLlgiD0tpxP3DdremyqXVMa/44vGawf8mWelpvidFpBpz
	WBKGiPkEkwDk1VwRtuxsuP0j3bCEESIOcJY+JV7yCmUElCErlLwGOh6HDfpulbBP
	ublPSIRxQiKNkwFAZ/GMTpmsjw=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 spammy=menu, rights, H*F:D*ne.jp
X-HELO: conssluserg-01.nifty.com
DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-01.nifty.com w5DLMBWN023723
X-Nifty-SrcIP: [125.3.30.127]
Date: Thu, 14 Jun 2018 06:22:18 +0900
From: Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>
To: cygwin AT cygwin DOT com
Subject: Re: [bug: csih] Setting privileged rights to cyg_server fails on Windows 7.
Message-Id: <20180614062218.eee6704d2ebc62383a2927c7@nifty.ne.jp>
In-Reply-To: <20180613181407.GT7851@calimero.vinschen.de>
References: <20180613224901 DOT d2cf679cef8eab89a834c494 AT nifty DOT ne DOT jp>	<20180613181407 DOT GT7851 AT calimero DOT vinschen DOT de>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

Hi Corinna,

On Wed, 13 Jun 2018 20:14:07 +0200
Corinna Vinschen wrote:
> There's something fishy in your environment.  The variable LOGONSERVER
> is always set in Windows NT, at least since NT4.  For standalone
> machines LOGONSERVER is set to "\\<machinename>".  You should really
> try to find out why LOGONSERVER isn't set for you.

With your advice, I have found the cause. I usually logon as a user
who does not have administrator rights for security reason. This user
belong to only "Users" group. When I need administrator rights,
I use "Run as administrator" menu to switch to another user who
has administrator rights. In this case, LOGONSERVER is not set.

If I logoff from the first user account and logon as the second user,
LOGONSERVER is set.

Moreover, the behaviour above seems to be true not only on Windows 7,
but also on Windows 10.

I have confirmed that iu-config successfully finishes without the
patch I proposed, if I logon as an administrative user instead of
using "Run as administrator".

Thank you very much.

-- 
Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple