I'm more concerned with how tokens are created and whether they will by default query the old resource domains that haven't been migrated into the AD environment.
Theoretical situtation: I am a member of 50 groups in my user domain, I'm accessing something in my user domain. We have 150 trusted resource domains where I have 6 group memberships in each through SID history. Is the GC/DC going to query all trusted domains for my memberships through SID history? (resource domains are all NT4 domains)
I'm assuming that it's not going to, because of how the authentication path works (resource server - user domain DC - user domain GC - resource server DC, resource server), but everything I've seen never really talks about SID History much.
On 9/24/06, joe <[EMAIL PROTECTED]> wrote:
I would recommend poking through the MSDN security docs. It sounds like there is a break in understanding of how the SIDs are used in combination with the DACLS.Start here:but poke around that whole area.joe
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Matt Hargraves
Sent: Thursday, September 21, 2006 4:59 PM
To: ActiveDir@mail.activedir.org
Subject: [ActiveDir] SID History.Conceptual situation:
User domain
Resource domain (s)
I bring all users into a single AD environment, bringing over SID History information.
Now I start moving over file servers from the resource domain to the AD environment. One of the file servers has groups ACL'd from the resource domain. When the server goes to check for access rights, will it pull over *all* group memberships from the appropriate resource domain or simply pull over the single group membership and append that to the user's token?
Mostly just looking at SID history impact between semi-active resource domains that are being decomissioned and current domains. Microsoft's site mostly seems to point to groups that are pointing to SID history objects that are within the AD environment, not cross-domain SID history impact.
