DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; q=dns; s=default; b=YojmMrNzm7VSKeJkvWT1VJDQx135Z
	GOhEEVOUoep6BQAFpVGm91qxkrtLt1+hgiClEP26TPa5o23if0aNW2+peSOnzmkx
	J8DyEZGUTG1J5nplfKC3pmujQBhN8haCIvPToZUzz+gpmlNv85rXxAbPA7YITlr1
	nhPNuaAhRyq+5M=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: "Habermann, David (D)" <DAHabermann@dow.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: occasional failure to look up
Date: Tue, 25 Nov 2014 17:09:12 +0000
Message-ID: <C9D37D92E903B347A31B9CF82643BA2807385B5E@046-CH1MPN1-041.046d.mgd.msft.net>
References: <C9D37D92E903B347A31B9CF82643BA2807362157@046-CH1MPN1-043.046d.mgd.msft.net> <20141118152211.GZ3151@calimero.vinschen.de> <C9D37D92E903B347A31B9CF82643BA2807362297@046-CH1MPN1-043.046d.mgd.msft.net> <20141118155809.GD3151@calimero.vinschen.de> <C9D37D92E903B347A31B9CF82643BA2807384C70@046-CH1MPN1-041.046d.mgd.msft.net> <20141125151928.GQ3810@calimero.vinschen.de> <C9D37D92E903B347A31B9CF82643BA2807385AF1@046-CH1MPN1-041.046d.mgd.msft.net> <20141125163833.GA8118@calimero.vinschen.de>
In-Reply-To: <20141125163833.GA8118@calimero.vinschen.de>
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Received-SPF: None (protection.outlook.com: dow.com does not designate permitted sender hosts)
Content-Transfer-Encoding: 8bit

> Two things to keep in mind:

> - It's not actually clear yet if it's a sidHistory entry or some SID
>  created by another mechanism.

> Even if it's sidHistory, it may be *very* old.  Did you work at the
>  company already back in NT4 times?  That might explain the sidHistory
>  entry and the total lack of files still having this SID in its ACL.
>  As far as I know, Microsoft suggests to remove the sidHistory entries
>  as soon as they are not needed anymore.

Yes, I guess I'll have to date myself now.  I've worked here with the same user ID since 1975 (full time since 1980), so I span basically the entire non-mainframe computer era.  So what you are suggesting is quite likely, and it would not be surprising for clean-up work to have been neglected.  A quick look in our AD shows numerous things such as "Legacy local groups" and "Legacy Mailboxes".  One concern I have here is that when I dig down into AD to "DC=dow,DC=com,OU=Dow Users,OU=Employees" and find what I believe is my current active record I find a record with "U074036" (capital 'U') whereas the record we saw as my "UID" earlier in this thread was with a lowercase 'u'. I found this by searching for sAMAccountName=u074036, and it is the only record found by this search.