[cifs-protocol] RID Allocation behaviour
Sebastian.Canevari at microsoft.com
Wed Jan 6 14:47:57 MST 2010
I will be helping you with this case.
I'll let you know if I have news or questions.
Senior Support Escalation Engineer, US-CSS DSC PROTOCOL TEAM
7100 N Hwy 161, Irving, TX - 75039
"Las Colinas - LC2"
Tel: +1 469 775 7849
e-mail: sebastc at microsoft.com
From: Andrew Bartlett [mailto:abartlet at samba.org]
Sent: Tuesday, January 05, 2010 6:05 PM
To: Interoperability Documentation Help
Cc: pfif at tridgell.net; cifs-protocol at samba.org; Andrew Tridgell
Subject: RID Allocation behaviour
Tridge and I are working on Samba4's implementation of the distributed RID allocation.
We are unclear on a number of aspects of the expected behaviour, particularly when the RID manager is not the DC adding users.
I'll describe this in terms of the 'RID manager DC' and the 'remote DC'
It appears that the Remote DC is responsible for updating the ridNextRID attribute, but rather than storing the next RID, it appears to store the last allocated RID. The actual remote DC allocation process for RIDs appears undocumented.
It appears the RID Manager DC is responsible for updating the rIDAllocationPool for each DC, and the rIDAvailablePool. We think the remote DC is responsible for ridPreviousAllocationPool and allocates RIDs from that pool, but this is only described in the schema doc.
Any light you can shed on this process would be most appreciated.
Authentication Developer, Samba Team http://samba.org
Samba Developer, Cisco Inc.
More information about the cifs-protocol