samba - Jun 2022 - GPO on a DC

Hello Rowland,

In my initial post of June 19th, 2022
> nsswitch.conf:
> passwd:         files systemd winbind
> group:          files systemd winbind
The SID if course the computer SID and of course it maps (dump idmap) or resolve
manually, besides samba-gpupdate --force does the mapping correctly (I have
attached the logs a few days ago).

In yesterday's email, I ago detail all the 3 problems (one not related, but
however a problem)

Eric




------- Original Message -------
On Sunday, June 26th, 2022 at 6:30 PM, Rowland Penny via samba <samba at
lists.samba.org> wrote:


> Who or what is SID S-1-5-21-3771616199-2733218289-4272702380-1000 ?
>
> Does it map to the xidNumber 3000141 ?
>
> Is nsswitch.conf set up to get users and groups from winbind ?
>

On Sun, 2022-06-26 at 16:21 +0000, samba-ml-en via samba
wrote:
> Hello Rowland,
> 
> In my initial post of June 19th, 2022
> 
> > nsswitch.conf:
> > passwd:         files systemd winbind
> > group:          files systemd winbind
> 
> The SID if course the computer SID and of course it maps (dump idmap)
> or resolve manually, besides samba-gpupdate --force does the mapping
> correctly (I have attached the logs a few days ago).
That explains that then, whilst a computer in AD is a basically a user
with an extra objectclass (computer), it isn't a user and isn't mapped
by Samba to a user.
> 
> In yesterday's email, I ago detail all the 3 problems (one not
> related, but however a problem)
Now I know that I can ignore the above error, I will have another look
and see if anything jumps out :-)

Rowland