search for: nis_domain

...gt; >> /Davor >> > > How about this: > > ssh into the DC, either as root or as a user that can use sudo (you > can use kerberos, but I am not going into that here) > > Create the group: > samba-tool group add unixadmins --gid-number=GID_NUMBER > --nis-domain=NIS_DOMAIN > > Add the group to Administrators: > samba-tool group addmembers Administrators unixadmins > > Add the required users to unixadmins, they should get the same rights > as if they were directly members of Administrators. > samba-tool group addmembers unixadmins anADuser > &...

...ld be grateful if you could share your thoughts. > > /Davor > How about this: ssh into the DC, either as root or as a user that can use sudo (you can use kerberos, but I am not going into that here) Create the group: samba-tool group add unixadmins --gid-number=GID_NUMBER --nis-domain=NIS_DOMAIN Add the group to Administrators: samba-tool group addmembers Administrators unixadmins Add the required users to unixadmins, they should get the same rights as if they were directly members of Administrators. samba-tool group addmembers unixadmins anADuser Now with setfacl, give the group unixa...

...>>> >>> ssh into the DC, either as root or as a user that can use sudo (you can >>> use kerberos, but I am not going into that here) >>> >>> Create the group: >>> samba-tool group add unixadmins --gid-number=GID_NUMBER >>> --nis-domain=NIS_DOMAIN >>> >>> Add the group to Administrators: >>> samba-tool group addmembers Administrators unixadmins >>> >>> Add the required users to unixadmins, they should get the same rights as >>> if they were directly members of Administrators. >>>...

On 2015-10-29 09:52, Rowland Penny wrote: > On 29/10/15 08:34, Davor Vusir wrote: >> Hi all! >> >> We have got many delegations in our AD. To add a certain >> administrator group to the local Administrators group you can use GPO >> for Windowsservers. As Samba does not understand GPO I have initially >> used the "username map" feature to add a

...User's phone number --physical-delivery-office=PHYSICAL_DELIVERY_OFFICE User's office location --rfc2307-from-nss Copy Unix user attributes from NSS (will be overridden by explicit UID/GID/GECOS/shell) --nis-domain=NIS_DOMAIN User's Unix/RFC2307 NIS domain --unix-home=UNIX_HOME User's Unix/RFC2307 home directory --uid=UID User's Unix/RFC2307 username --uid-number=UID_NUMBER User's Unix/RFC2307 numeric UID --gid-nu...

...gt; >> How about this: >> >> ssh into the DC, either as root or as a user that can use sudo (you can >> use kerberos, but I am not going into that here) >> >> Create the group: >> samba-tool group add unixadmins --gid-number=GID_NUMBER >> --nis-domain=NIS_DOMAIN >> >> Add the group to Administrators: >> samba-tool group addmembers Administrators unixadmins >> >> Add the required users to unixadmins, they should get the same rights as >> if they were directly members of Administrators. >> samba-tool group addmembers...

...as a user that can use sudo >>>>> (you can >>>>> use kerberos, but I am not going into that here) >>>>> >>>>> Create the group: >>>>> samba-tool group add unixadmins --gid-number=GID_NUMBER >>>>> --nis-domain=NIS_DOMAIN >>>>> >>>>> Add the group to Administrators: >>>>> samba-tool group addmembers Administrators unixadmins >>>>> >>>>> Add the required users to unixadmins, they should get the same >>>>> rights as >>>...

...newal in 1438 seconds. Jan 15 05:35:32 localhost dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.host_name -- Jan 15 05:35:32 localhost dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain Jan 15 05:35:32 localhost dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers Jan 15 05:35:32 localhost NetworkManager: <information> Retrieved the following IP4 configuration from the DHCP daemon: Jan 15 05:35:32 localhost Net...

...e DC, either as root or as a user that can use sudo (you >>>> can >>>> use kerberos, but I am not going into that here) >>>> >>>> Create the group: >>>> samba-tool group add unixadmins --gid-number=GID_NUMBER >>>> --nis-domain=NIS_DOMAIN >>>> >>>> Add the group to Administrators: >>>> samba-tool group addmembers Administrators unixadmins >>>> >>>> Add the required users to unixadmins, they should get the same >>>> rights as >>>> if they were direct...

...udo >>>>>> (you can >>>>>> use kerberos, but I am not going into that here) >>>>>> >>>>>> Create the group: >>>>>> samba-tool group add unixadmins --gid-number=GID_NUMBER >>>>>> --nis-domain=NIS_DOMAIN >>>>>> >>>>>> Add the group to Administrators: >>>>>> samba-tool group addmembers Administrators unixadmins >>>>>> >>>>>> Add the required users to unixadmins, they should get the same >>>>>&gt...

I'm coming from a Debian system so my system accounts are below 1000, regular accounts start at 1000. For some historical reason somebody gave our main group id 500 so therefor I want my usable range to start at 500. Do I need both idmap config *:range and idmap config SAMDOM:range? I also tried with only 'idmap config *:range' but that didn't seem to help. I'll try again