similar to: Logon script via GPO

Hello, I'm wondering if there's a plan for including the possibility of modifying user attributes (must-change-at_next-login, profile-path, home-drive, home-directory, etc)? For the moment, it seems the only way to do this is when the user is created (samba-tool newuser) or by doing so via 'administrative tools' via a Windows machine. Thank You! -- Luc Lalonde, analyste

Hello Folks, I've successfully created a GPO for user logon scripts with Samba4... However, the 'SYSVOL\domain\Policies' folder and contents is not replicated to the other DC's. Is this normal? It is working, but it seems that this is a 'single point of failure' for 'logon' scripts. Thank You! -- Luc Lalonde, analyste

Hello Folks, This directive works with Samba3 but does not seem to work with Samba-4.0.5: winbind use default domain = Yes I want to get a username that does not contain the domain (GIGL). Instead here's what I get: [root at roquefort ~]# getent passwd | grep GIGL GIGL\Administrator:*:0:100::/usagers/%U:/bin/bash GIGL\Guest:*:3000002:3000003::/usagers/%U:/bin/bash

Hello Luc, thanks for your answer. If I understand you correctly than you are using samba4 as windows domaincontroller and you do not have another Windows DC? So after all you have exactly one Kerberos Server that is part of the samba4 server? Thanks Rainer Am 24.03.2015 um 12:41 schrieb Luc Lalonde: > Guten tag Rainer, > > We use our Samba4/Win2k8 AD domain to authenticate all our

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

Hello Johan, I'm having the same problems with DFS and WinXP clients since I upgraded to 2.2.8. I tried to clear the cache on the client side with dfsutil.exe that comes with the Win2000 SP2 but to no avail. Can anyone else confirm this problem? It's also strange that on the WinXP clients the version of the samba server is still registered as a previous version (2.2.6 or 2.2.7).

Hello, I'm getting replication errors of this type on the Samba (version 4.1.4) server (name=Roquefort): ##### ############################# ERROR(<class 'samba.drs_utils.drsException'>): DsReplicaSync failed - drsException: DsReplicaSync failed (8418, 'WERR_DS_DRA_SCHEMA_MISMATCH') File

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

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 by default??? I must be missing something... On 2019-07-29 11:29 a.m., Rowland penny via samba wrote: > On 29/07/2019 15:59, Luc Lalonde via samba wrote: >> Hello Folks, >> >> There seems to be

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

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

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

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

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

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'

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

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

Hello, We seem to not be able to use Eclipse with a network drive since we upgraded our Samba server to version 4.4.3. Here's the error we get: mac-mini:MacOS user$ ./eclipse java.lang.RuntimeException: Error initializing storage. at org.eclipse.osgi.internal.framework.EquinoxContainer.<init>(EquinoxContainer.java:68) at

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

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