X-Spam-Check-By:	sourceware.org
From:	"Dave Korn" <dave DOT korn AT artimi DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: Wich privileges required by ssh-host-config running user?
Date:	Wed, 18 Jan 2006 15:45:27 -0000
MIME-Version:	1.0
In-Reply-To:	<43CE619E.6070708@equate.dyndns.org>
Message-ID:	<SERRANOGNZ4mF1IT18o000001b6@SERRANO.CAM.ARTIMI.COM>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

Chris Taylor wrote:
> Dave Korn wrote:

>>   Simplest workaround would be to always join the machine to the domain
>> first and install cygwin second. 
>> 
> 
> And to install as the domain administrator, not the local admin,
> otherwise you run into this problem, as the OP has done.

  Probably a domain user would suffice.  It might be best if the domain user
account was made a "Power User" in the machine's local user accounts.


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


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

- Raw text -