On Fri, Jul 18, 2008 at 03:00:11PM -0500, Mark Martin wrote: > On Fri, Jul 18, 2008 at 2:02 PM, Nicolas Williams <Nicolas.Williams at > sun.com> > wrote: > > > > > > > I've updated ad(5) as follows: > > > > +++ ad.5.txt Fri Jul 18 11:10:26 2008 > > > <snip> > > > > > + protocol to access naming information from the AD servers. No > > + schema modification is needed on the AD servers because the Solaris > > + client works with native AD schema. The Solaris AD client uses > > > I wasn't able to find enough materials on the public site for this case or > for CIFS client incl. idmap to validate this -- will this work for SBS as > well? What if SFU is installed (or the server is R2)?
There's plenty of documentation, starting with the CIFS server admin guide, which contains the ID mapping admin guide, as well as various ARC cases, man pages, ... The case materials for this case indicate that SFU will not be used by nss_ad for any purpose, although a future case may add support for using SFU in idmapd for mapping Windows users in _one_ domain to non-ephemeral UIDs and GIDs. Such a future case would cause nss_ad to indirectly support SFU for the same purpose because nss_ad will use ID mapping APIs for mapping Windows SIDs to UIDs/GIDs, and consequently nss_ad will use idmapd. Nico --
