X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=1.6 required=5.0 tests=AWL,BAYES_20
X-Spam-Check-By:	sourceware.org
Date:	Thu, 02 Apr 2009 07:45:41 -0400 (EDT)
From:	"Michael T. Davis" <DAVISM AT ecr6 DOT ohio-state DOT edu>
Subject:	Promoting cygwin system to member server
To:	cygwin AT cygwin DOT com
Message-id:	<01N7AZJAP67S8XW3IJ@ecr6.ohio-state.edu>
X-VMS-To:	IN%"cygwin AT cygwin DOT com"
MIME-version:	1.0
X-IsSubscribed:	yes
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

	We have a standalone server running Windows Server 2003 SP2.  We would
like to promote it to a member server in an existing Windows domain.  Will this
affect how cygwin accounts are managed and maintained?  We want to preserve
the functionality of the existing local accounts, and be able to continue to
manage them (add, remove, etc.) so that the users can continue to use cygwin
(esp. the SSH server) independent of the Windows domain.  (In fact, we don't
want domain users to access the system via cygwin's SSH server, only local
users.)

Thanks,
Mike

--
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 -