search for: dc_authenticated_users

Hi, We just upgraded the Samba-AD from version 4.6.5 to 4.7.5. The upgrade threw many challenges and I will write a separate mail explaining the workaround that we adapted to get over them. One of the main challenges is GPO. While the user policy applies properly, the computer policies are not getting applied, rather they are erratic, On some PCs within the same LAN, it works, while on some,

...t uid/gids are where used. The script looks them up for you, but it must be error free so we are sure what is set is correct. If you look in the script, you see the four SID. DC_SERVER_OPERATORS="S-1-5-32-549" DC_ADMINISTRATORS="S-1-5-32-544" DC_SYSTEM="S-1-5-18" DC_AUTHENTICATED_USERS="S-1-5-11" These must work in resolving with wbinfo to get the correct uid/gid for sysvol. These wbinfo --... Tests For "BUILTIN\Administrators" and BUILTIN\Server Operators --sid-to-uid --uid-to-sid --gid-to-sid --sid-to-name --name-to-sid For System and Authenticated users...

Thank you both, Rowland and Louis. I'll try to answer you both and give you more info about our domain. Generally: In the past, we have Samba 3.5 NT4 domain on SLES server (designed ages before, never upgraded). In 2015 I finally decided to migrate to Samba 4 AD. In those day it was 4.2. samba-tool ntacl sysvolcheck was ok, no errors. AD worked (and working) as expected. This summer, I