similar to: Samba vs Windows server 2019

For the moment, Samba4 cannot participate as DC with Windows 2019 servers (unless you downgrade to schema 47, the one that comes with Windows 2008R2): https://wiki.samba.org/index.php/AD_Schema_Version_Support The developers are working on Windows 2012R2 support.   So for now, anything above 2008R2 is experimental. On 2019-03-19 11:31 a.m., Rowland Penny via samba wrote: > On Tue, 19 Mar

Yes, I mean running samba as a Unix Domain Member. The domain should be manage by a Windows server 2019 AD. EdG Le 19/03/2019 à 12:31, Rowland Penny via samba a écrit : > On Tue, 19 Mar 2019 12:14:41 -0300 > Edouard Guigné via samba <samba at lists.samba.org> wrote: > >> Hello Samba Users, >> >> In my infrastructure, samba is set with a Windows Server 2012R2.

Hello Dale, Set inherit acls = yes locally to my share groups, and remove map acl inherit = yes from global parameters of smb.conf does not solve my issue. I still have acl "Domain Users" added to new folders/files. As i write in my previous email, the only way i found to disable acl "Domain Users" to be added was with : inherit owner = yes With some disavantages for users

Edouard, These are the 4 available parameters containing the word "inherit". inherit acls (S) inherit owner (S) inherit permissions (S) map acl inherit (S) Would "inherit acls" work for you? Dale On 12/10/18 10:56 AM, Edouard Guigné via samba wrote: > Hello, > > I add to my previous mail, the only way i found to disable acl

Hello, I set a share on a samba 4.7.1 as domain member with an Active Directory controler, this share is used by all domain users. All users from the AD domain have a primary group "Domain Users", and secondary groups to filter access on the folders of the share. I noticed that when a user create a sub-folder/file inside a "Top folder", the default permissions from the

Thanks for answers. Why do you have this option if it is not working yet? Just out of curiosity... Regards; On 22-05-2018 12:52, Rowland Penny via samba wrote: > On Tue, 22 May 2018 12:39:53 -0300 > Carlos via samba <samba at lists.samba.org> wrote: > >> HI!! >> >> I have one question, in samba 4.8.2 , --forest-level and >> --domain-level is worked

On Fri, 28 Apr 2017 11:01:14 -0400 Luc Lalonde <Luc.Lalonde at polymtl.ca> wrote: > Hello Rowland, > > Is this what you mean? > > [root at roquefort ~]# echo $LANG > fr_CA.utf8 > What I was trying to get at is, does your username have any of those funny marks above some of the letters (you can tell I am English, I don't know the correct name for them because we

On Fri, 28 Apr 2017 09:41:31 -0400 Luc Lalonde <Luc.Lalonde at polymtl.ca> wrote: > Hello Rowland, > > Have you tried deleting a user, re-creating the same user and then > try to add him to a group? > > I'm convinced that this will point us in the right direction to > correct the bug. > Yes and to confirm it, I just did it again: samba-tool user create User2

The user exists in AD: - I can see the user using 'wbinfo', 'samba-tool user list' - I can add the user to a group with 'Active Directory Users and Computers' in Windows 2008R2 - It's seems impossible to use 'samba-tool group addmembers foogroup foouser' I looked at the user's attributes but can't find anything different from any other user that

Hello, I've just upgraded to 4.9.6  and can't seem to be able to use the 'offline' backup?   It seems that the only options are:  online, rename, and backup. Can someone confirm this?   I plan to get to migrating to 4.10.2, but I'm doing it incrementally:   v4.7.6  -> v4.8.11 -> v4.9.6 -> v4.10.2 Before going to the v4.10.2, I want to backup my AD database using

Thanks Luc, First, can I just use the small /etc/krb5.conf suggested in Samba AD docs or do I need something more substantial on the server & client for Kerberos NFS to work? [libdefaults]         default_realm = SUBDOMAIN.DOMAIN.COM         dns_lookup_realm = false         dns_lookup_kdc = true I understand a /etc/krb5.keytab file has to be created on both server & client. Most

This is the case for this user too... Could it be that Samba is trying to work with the old SID??? Le 2017-04-26 à 10:47, Dale Renton via samba a écrit : > On Tue, Apr 25, 2017 at 3:31 PM, Luc Lalonde via samba < > samba at lists.samba.org> wrote: > >> The user exists in AD: >> >> - I can see the user using 'wbinfo', 'samba-tool user list'

On 2016-09-19 14:08, Marcio Vogel Merlone dos Santos via samba wrote: > Em 09/09/2016 12:48, Luc Lalonde via samba escreveu: > >> We have some machines that have updated to the Windows 10 anniversary update (1607) that are having roaming profile sync problems. >> >> Before I search the event logs or provide details, has anyone experience profile sync wierdness? >>

Hello Folks, I'm getting this strange error when I try to add a particular member to a group: [root at roquefort admin]# /usr/local/samba/bin/samba-tool group addmembers foogroup foouser ERROR(exception): Failed to add members "foouser" to group "foogroup" - Unable to find "foouser". Operation cancelled. File

Still doesn't work for that user... for works for another user: [root at roquefort samba]# cp -av ./lib64/python2.6/site-packages/samba/samdb.py ./lib64/python2.6/site-packages/samba/samdb.py.bak « ./lib64/python2.6/site-packages/samba/samdb.py » -> « ./lib64/python2.6/site-packages/samba/samdb.py.bak » [root at roquefort samba]# vi ./lib64/python2.6/site-packages/samba/samdb.py [root

Hello Folks, We just moved our Samba file server from version 3.6.3 to 4.2.10 (the lastest updates for CentOS 7.2). Our Windows clients are working well, but we are unable to use it for our Mac clients (Yosemite). The clients are configured to use their home directories from this file server. Here's the config: [global] workgroup = BLAH.COM netbios name = FILESERVER

Hello Folks, There seems to be contradicting sentences in the release notes for 4.11.0RC1: Default schema updated to 2012_R2 --------------------------------- Default AD schema changed from 2008_R2 to 2012_R2. 2012_R2 functional level is not yet available. Older schemas can be used by provisioning with the '--base-schema' argument. Existing installations can be updated with the

Ahh ok, thanks for the clarification!?? I'll go to bed less ignorant tonight ;-) On 2019-07-29 12:07 p.m., Rowland penny via samba wrote: > On 29/07/2019 16:41, Luc Lalonde wrote: >> The first sentence says that default schema has changed from 2008R2 >> (schema 47) to 2012R2 (schema 69). >> >> This does not mean that we're now at Windows 2012R2 functional level

Log level to 10 was for debug reasons, I can now surely set to 1 now. Concerning idmap config IPGAD, I don't see why is the reason to start at 1... I will set to 10000 as according to the documentation, thank you. What do you mean by " You are also using the winbind 'ad' backend, so have you added anything to AD ? " ? Le 10/04/2019 à 12:38, Rowland Penny via samba a

Hello Tim, Wow, great documentation! ? That really clears a lot of the terminology? for me. We have to remove our Win2008R2 Servers before Jan2020.?? Hopefully Samba 4.11.x will permit us to join a Win2012R2 Server at a 2008R2 functional level...? Your documentation gives steps on how to do this.? But I need some clarifications... Here's my understanding of the workflow: 1. Upgrade