similar to: Roaming Profile issue in Windows 10

Hi folks, Hardware/OS =========== - Samba AD DC ver. 4.9.1 (compiled using standard CentOS tools and libraries) functions only as AD server (authentication, AD services), migrated from old Samba NT PDC through classicupgrade, OS CentOS 7.5, kernel 4.9.40 (elrepo-lt), VM under Xen 4.9.0 - Samba AD member server ver. 4.7.1 (from distribution) with different shares for different user groups, 

On 08.10.2018 21:02, Rowland Penny via samba wrote: > On Mon, 8 Oct 2018 18:53:45 +0200 > Peter Milesson via samba <samba at lists.samba.org> wrote: > >> Hi folks, >> Problem >> ======= >> Setting up and managing the shares on the Samba member server differs >> significantly from the Samba Wiki documentation. It seems that the >> domain

I've set up a profiles share according to the wiki article: https://wiki.samba.org/index.php/Implementing_roaming_profiles Users are able to create new roaming profiles and they cannot browse each others' profiles, so all that is working. The only issue is that the group "domain admins" does not have privileges to read or delete user profiles. The acls on the profiles directory

On Thu, 18 Apr 2019 14:29:30 -0400 Bob Smith <bobs04475 at gmail.com> wrote: > Hello Rowland, > > Thank you for the suggested link! > > I followed "Using POSIX ACLs on a Unix domain member" also. Don't ;-) Use Windows acls > "Granting the SeDiskOperatorPrivilege Privilege" > # net rpc rights grant "SAMDOM\Domain Admins"

Inviato da Posta per Windows 10 >Da: Rowland Penny via samba >Inviato: lunedì 8 gennaio 2018 18:48 >A: samba at lists.samba.org >Oggetto: Re: [Samba] R: cannot list/access samba share from Windows client > >You are now solely using sssd for the authentication, you need to ask >on the sssd-users mailing list, either that or purge sssd and set up >winbind correctly. >I

I've a working old fashion PDC samba server. When I've to create a new user I add it to the system with adduser and to the samba using pdbedit. In the smb.conf I've the [homes] shared folder for the homes and [profile.V6] for the windows 10 profiles. When the user enter in a Windows 10 machine, he's able to enter in his home directory mapped as Z: and when exits his profile is

On Fri, 26 Jan 2018 14:18:53 +0000 Rowland Penny via samba <samba at lists.samba.org> wrote: > On Fri, 26 Jan 2018 14:10:40 +0100 > Micha Ballmann <ballmann at uni-landau.de> wrote: > > > To set share windows permissions and windows acl i login on a > > windows 7 computer with the administrator user.|Open ||Computer > > Management and connect to the

On 10/9/18 10:41 PM, Rowland Penny via samba wrote: > On Tue, 9 Oct 2018 22:16:41 +0200 > Peter Milesson <miles at atmos.eu> wrote: > >> >> On 09.10.2018 21:25, Rowland Penny via samba wrote: >>> On Tue, 9 Oct 2018 19:44:55 +0200 >>> Peter Milesson via samba <samba at lists.samba.org> wrote: >>> >>>> Hi Rowland,

I am running a file server off OEL7.1, domain member in a Windows AD. The machine was joined using realm join. Samba version is 4.1.12 from the yum repo. I am using SSSD, so no winbind here. net rpc rights grant 'SAMDOM\Domain Admins' SeDiskOperatorPrivilege -U'SAMDOM\administrator' does not work with the errors described in

Hi All, Some time ago I reluctantly moved DC functionality off my file server and onto a separate machine, due to the well-known challenges using the same machine as both a file server and a DC. This went mostly fine, with one exception - I have one piece of functionality that worked before, but I still don't have working now. I use wpkg for software distribution, having all relevant

On 09.10.2018 10:23, Rowland Penny via samba wrote: > On Mon, 8 Oct 2018 22:52:05 +0200 > Peter Milesson via samba<samba at lists.samba.org> wrote: > >> On 08.10.2018 21:02, Rowland Penny via samba wrote: >>> On Mon, 8 Oct 2018 18:53:45 +0200 >>> Peter Milesson via samba<samba at lists.samba.org> wrote: >>> >>>> Hi folks,

Hello, I've been setting up new file server using samba 4.8.3 (centos 7 RPM), as samba 4 AD member server using my earlier smb.conf when I realised that I was  previously somewhat circumventing the SeDiskOperatorPrivilege by using "admin users map" to SAMDOM\Domain admins" parameter in smb.conf. I decided to change my smb.conf and setup shares following samba wiki. All

> > OK, you should use the standard 'rwx' permissions *or* ACLs, not both. If > you create a directory on Unix that you want to share, set the owner:group > to root:'Domain Admins' and permissions to 0770. You will then be able to > set the permissions from windows or with setfacl on the Unix machine, you > do not need the 'force group' lines in smb.conf,

Hai, In reponse to the why i recommend that. Since this is a "windows" only share, i recomment to set it up for that usage, with results in better matching for windows rights. Resulting in better working policies. The current POSIX rights did not match to my needs and resulted in inconsistant policies. This is why i use these for profiles and sysvol. And this is my setup order:

Giving a domain user group privilege SeDiskOperatorPrivilege fails with NT_STATUS_NO_SUCH_PRIVILEGE. The domain is controlled by a MS 2012 R2 DC. Has this privilege been renamed or replaced with some other privilege? How to give the domain user group necessary rights for defining file share permission settings from MS environment? The RHEL 7 file server is running Samba 4.1.1-38 and the id

sorry , the original message was in error. Follow: Hi. Sorry. Today I have a big problem with the samba I can not solve! My permissions do not work properly. in the RSAT created groups, OU and users. I configured in Windows the shared directory *TECNOLOGIA* security settings assigning full permissions to *grupo_tecnologia* (technology group). However users who are with *grupo_tecnologia*

On Thu, 2 Aug 2018 13:16:26 -0400 pisymbol via samba <samba at lists.samba.org> wrote: > On Thu, Aug 2, 2018 at 1:11 PM, Eric Altman via samba > <samba at lists.samba.org > > wrote: > > > > > It’s just that the mount has read-only access despite the file > > ownership and modes being set to give full read-write? > > > > > That is almost

Dear all, I have set a small test domain in virtualbox. 1. Samba AD DC on Debian bullseye testing 4.11.6 2. Samba domain member Debian Stretch 4.10.14 3. Windows 10 Enterprise evaluation version 1909 Roaming profiles with folder redirection setup. PAM working. The above was setup basically using guides in wiki.samba.org, with nearly the only thing changed was SAMDOM to SAMBA. "Unix

Hi Rowland, Those low numbers you refer to are in fact the standard numbers assigned to those groups, so I fail to see the problem. As for mapping Administrator to root, I believe that's entirely optional, rather than required. Under normal circumstances we don't use the domain Administrator account at all. We have a root account we use instead. In regard to winbind, we have never

On Thu, 13 Apr 2017 17:10:16 -0400 Rommel Rodriguez Toirac via samba <samba at lists.samba.org> wrote: > > [root at gtmpve nagios]# net rpc rights list accounts > ATGTM00\Domain Admins > SeDiskOperatorPrivilege > > It look like the Domain admins yes have the > 'SeDiskOperatorPrivilege' privilege. I change the group of the share > with chgrp and try from