similar to: duplicate sids against classicupgrade

Hello Marc, thank you for your answer. I already added gidNumber 513 for the group. Now I added the two additional attribute for the group. I installed RSAT, and enabled the necessary modules according to the Samba wiki. I opened AD users and computers, and Domain Users' properties. When I click on the UNIX Attributes tab, I get an error: Execution denied. On the panel I see: NIS Domain: xxx;

Hi, I have Samba3 domain, and I test the upgrade process to Samba4 AD (Samba 3.6.6->4.1.17). After classicupgrade I found a problem. I created a test file, and wanted to change its group with chown "xy:Domain Users" testfile. I got an error message: invalid group: "xy:Domain Users" (I think, because the message was localised). chown xy testfile works. I had old files with

Hi, I have Samba 4.2.10 server with NT4 configuration, with ldap backend on Debian Jessie, and I want to upgrade it to AD. I test it now in virtul environment. The classicupgrade was succesful. getent passwd username and chown "username:Domain Users" test.txt didn't work with this nsswitch.conf: passwd: files ldap group: files ldap shadow: files ldap , so I changed ldap to winbind.

Hi all, rsync-2.4.6 has been running for quite a while with no problems, until about a week ago when for some reason it blocked on the same host ever time. I use it to backup about thirty hosts to my backup server, but for some reason it's illiciting that blocking bug that some people experience with 2.4.6. So, I upgraded the client side with 2.4.7, but it complained of protocol differences.

On 09/08/2019 10:33, Pisch Tam?s via samba wrote: >> You have to give any users you require visible on Unix a uidNumber attribute > Ok, I can do it with samba-tool user edit... >> You have to give 'Domain Users' a gidNumber attribute. >> You have to give any group you require to be visible a gidNumber > I know that I can set gidNumber when I create a group, but how

> >> Current plan : add a third DC, make dc2 a dm file server. Best solution > > imo. > > Yes, I know that it would be better to use a separate dc, but I didn't > > want it on that site. > Hi Pisch, that wasn't aimed at you, but it does show why you should > never hijack an existing thread, my fault for not forking it off into a > new thread, sorry ;-)

Hi, there is a recommendation in the Samba AD DC howto: "We do not recommend using the Domain Controller as a file Server." We have two sites. We have two Samba3 servers now with ldap on site1, and one Samba3 BDC on site2. We have ~200 users, and around 50 clients connect to the servers at the same time on site1, and around 20 clients connect to the BDC on site2. On the BDCs there are

Pisch Tam?s <pischta at gmail.com> ezt ?rta (id?pont: 2019. j?l. 4., Cs, 13:15): > > >OK, I set up Buster RC3 in a VM > Thanks a lot! > > >I could add 'Domain Admins' to the 'Properties' on the share without any > >problem. > :o > > > Back to Buster machine: > > root at dbrc3:~# ls -lad /home/users > > drwxrwx---+ 2 root

Hi, I installed a SaMBa PDC and a BDC. When I log in to an XP client with a new user, sometimes I get the initial profile settings from the netlogon share, but often from local. When I get the local default settings, it is not syncronized to the server at logout. Even if I get the new profile from the server, on the same client, next time, with a new user, I get the new profile from local. I

> >>>> Run this : getfacl /home/users > >>> getfacl: Removing leading '/' from absolute path names > >>> # file: home/users > >>> # owner: root > >>> # group: A\\domain\040admins > >>> user::rwx > >>> user:root:rwx > >>> user:10512:rwx > >>> group::rwx > >>>

Hi, I set up Samba DCs for two sites. The first site is for example domain.ourdomain.com, the second is site2.ourdomain.com. On the first site, there will be 2 DCs, and one fileserver, on the second site there will be one DC, and it will act as fileserver too. Is it true that Samba's internal dns server won't good for that, and I need Bind, because of Bind's zone transfer feature?

Hi, I would like to connect our AD to the Azure AD. As I see, it needs 2012_R2 functional level. I don't have any Windows AD DC. Is it safe to raise the functional level to 2012_R2 in production environment? I read that 4.19 has initial support for 2019 schema, and for the 2016 functional level, but the 2012 support is still not complete. Thanks, Tamas Pisch

Fran - thanks for your reply. I'm cc'ing you directly on this as well as posting to the list as I'm not sure how often you check the list and I'm down to hanging by my last fingernail on this project. I have some preliminary questions interspersed below. Thanks, --Mark -----Original Message----- > Subject: Re: My dovecot works fine against Active Directory 2003, but not >

Hi, I posted a bug report more than a month ago to bugzilla about a samba-tool classic upgrade error, but without any answer: https://bugzilla.samba.org/show_bug.cgi?id=10648 Can somebody give me a hint, how can I avoid that error? Sorry, if it is not correct to write here after I sent that bug report. I work for a school, and I wanted to upgrade Samba in the summer holiday. Thanks, Tamas

Hello, I have a PDC with master ldap backend and a BDC with slave ldap backend (both are SaMBa 3.2 on Debian Lenny). I want to install an additional SaMBa server on an another site (on Debian Squeeze). The two sites is connected with VPN (on not so reliable ADSL lines). I read an interesting network scenario in the Samba Guide chapter 6: theoretically it is possible to install one PDC on both

Hi, I upgraded our servers from Wheezy to Jessie. I use samba in classic mode, with openldap backend. After the upgrade, on the PDC (srv3) everything seems to be ok, it authetnicates, the netlogon share is accessible on it, but on the BDC (srv7), what is the file server, the authentication doesn't work, shares are inaccessible. I compared and syncronized the configuration files to as similar

Hi all. I'm doing an upgrade from samba 3.4.8 domain to samba 4.1 I followed this guide: http://wiki.samba.org/index.php/Samba4/samba-tool/domain/classicupgrade/HOWTO I'm upgrading on a new virtual server (for testing purposes). Executing the command /usr/local/samba/bin/samba-tool domain classicupgrade --dbdir=/root/samba3/ --use-xattrs=yes /root/smb.conf (where /root/samba3/ contains

Hi, When trying to upgrade from Samba 3.6.25 on FreeBSD 10.3-RELEASE-p17 to Samba 4.7.6 on FreeBSD 11.1-RELEASE-p6, I receive an error: # samba-tool domain classicupgrade --dbdir=/usr/local/etc/samba3/ --realm=samdom.example.com --dns-backend=BIND9_DLZ /usr/local/etc/samba3/smb.conf [...] Committing 'add users' transaction to disk Adding users to groups Committing 'add users to

On Wed, 04 Apr 2018 15:13:09 +0700 Olivier via samba <samba at lists.samba.org> wrote: > Hi, > > When trying to upgrade from Samba 3.6.25 on FreeBSD 10.3-RELEASE-p17 > to Samba 4.7.6 on FreeBSD 11.1-RELEASE-p6, I receive an error: > > # samba-tool domain classicupgrade --dbdir=/usr/local/etc/samba3/ > --realm=samdom.example.com --dns-backend=BIND9_DLZ >

Oh Boy. User 'Administrator' in your existing directory has SID S-1-5-21-2070472328-935435760-1634736958-1000, expected it to be S-1-5-21-2070472328-935435760-1634736958-500 ERROR(<class 'samba.provision.ProvisioningError'>): uncaught exception - ProvisioningError: User 'Administrator' in your existing directory does not have SID ending in -500 It's not all