Rex Dieter wrote:
Jim Kusznir wrote:
Rex Dieter wrote:
Jim Kusznir wrote:
From what I undrestand, there is no feesable way of implementing
winbind
in NSS and maintaining existing UID/GID mappings.
AFAIK, If SFU is installed on your Windows AD domain controller, it
will extend the schem
Jim Kusznir wrote:
Rex Dieter wrote:
Jim Kusznir wrote:
From what I undrestand, there is no feesable way of implementing winbind
in NSS and maintaining existing UID/GID mappings.
AFAIK, If SFU is installed on your Windows AD domain controller, it
will extend the schema to allow you to define
On Monday 31 October 2005 16:50, Jim Kusznir wrote:
> Rex Dieter wrote:
> > Jim Kusznir wrote:
> >> From what I undrestand, there is no feesable way of implementing winbind
> >> in NSS and maintaining existing UID/GID mappings.
> >
> > AFAIK, If SFU is installed on your Windows AD domain controller
Rex Dieter wrote:
Jim Kusznir wrote:
From what I undrestand, there is no feesable way of implementing winbind
in NSS and maintaining existing UID/GID mappings.
AFAIK, If SFU is installed on your Windows AD domain controller, it
will extend the schema to allow you to define UID/GID/homedir
Jim Kusznir wrote:
From what I undrestand, there is no feesable way of implementing winbind
in NSS and maintaining existing UID/GID mappings.
AFAIK, If SFU is installed on your Windows AD domain controller, it will
extend the schema to allow you to define UID/GID/homedir for winbind's
use.
