Re: [Samba] idmap problems
- Date: Tue, 8 Jan 2019 11:56:10 +0100
- From: "L.P.H. van Belle via samba" <samba@xxxxxxxxxxxxxxx>
- Subject: Re: [Samba] idmap problems
> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces@xxxxxxxxxxxxxxx] Namens
> Rowland Penny via samba
> Verzonden: dinsdag 8 januari 2019 11:13
> Aan: samba@xxxxxxxxxxxxxxx
> Onderwerp: Re: [Samba] idmap problems
> On Tue, 8 Jan 2019 10:36:49 +0100
> "L.P.H. van Belle via samba" <samba@xxxxxxxxxxxxxxx> wrote:
> > Hai,
> > I still dont understand the fuss about "domain admins" and no GID
> > because im running this for 3 years now. So... Again what was the
> > problem here, i dont remember it.. (sorry)
> The problem is that you use Administrators instead of Domain Admins, which, if you think about it, is the same as using another group instead of Domain Admins.
No, thats not the problem.. Im using it as Windows designed it by default.
Builtin\Adminsitrators != "DOMAIN\Domain Admins" and DOM\Domain admins is member of Builtin\Adminsitrators
Now your idee..
Builtin\Adminsitrators != "DOMAIN\Domain Admins" and DOM\ANY group but is not default a member of Builtin\Adminsitrators
Table B-1: User Rights and Privileges
Table B-1: Built-in and Default Accounts and Groups in Active Directory
The importent parts are the "Direct user rights" and "Inherited user rights."
That might help you understanding what im trying to say.
My setup is a set as close as possible to a windows domain setup.
Im thinking in ..
BUILTIN <-> NTDOM <-> Workstations/users
NTDOM <-> Workstations/users ( the reflex more to a member server )
And not ADDC-server
BUILTIN <-> Workstations/users ( this reflex more to a standalone server )
To unsubscribe from this list go to the following URL and read the