Note: We are doing step #4 because the shared directory should belong to "RHSQE-DC+domain users" and with glusterfs vfs plug-in samba does not automatically mount the volume on RHS nodes.ĭuring our testing the join domain works fine for the RHS gfs-vol1]# net join -S rhsqe-dc1 -U administrator e.g: mkdir /mnt/samba/gfs-vol1/rhsdata01Į.g.: chgrp "RHSQE-DC+domain users" /mnt/samba/gfs-vol1/rhsdata01 Mount the samba volume as fuse mount with "-o acl" optionĮ.g: mount -t glusterfs -o acl 10.70.35.174:/gfs-vol1 /mnt/samba/gfs-vol1/ĥ. Join the rhs node to the Active directory domainĤ. RHS2.0 and this worked fine.īelow is the document we are referring for Active directory integration and it has exact steps for it.ģ. Note: We tried the same steps on Anshi i.e. So the below command should workĬhgrp "RHSQE-DC+domain users" /mnt/samba/gfs-vol1/rhsdata01Ĭhgrp: invalid group: `RHSQE-DC+domain users' In our case, the domain name is "RHSQE-DC". So for samba share to work correctly with AD, the share/directory should belong to "+domain users". Any user created in the AD domain automatically gets added to "domain users" group. The "domain users" is a user group in active directory. So that domain users in the active directory can access it.
Samba share engineering group windows#
To integrate RHS2.1 +samba share with Windows Active Directory we need to change the group of samba share/directory to "+domain users".
0 kommentar(er)
