similar to: classicupgrade error: User 'Administrator' does not have SID ending in 500

The two domain controllers (Debian) and the member server (CentOS) are all running Samba 4.1.4 from the sernet packages. The member server I am testing from was fully patched as of this morning. Things that work: - wbinfo -u - wbifno -g - getent group {ad_group} Things that don't work: - getent passwd {any_ad_user} - getent group - getent passwd I jacked up the winbindd

OK, further to my previous message I've configured BIND, but when I try to run samba_dnsupdate I get the following: Nov 18 16:19:23 sles-shire named[6112]: samba b9_putrr: unhandled record type 0 Nov 18 16:19:24 sles-shire named[6112]: samba_dlz: starting transaction on zone _msdcs.main.adlab.netdirect.ca Nov 18 16:19:24 sles-shire named[6112]: samba_dlz: disallowing update of

I was hoping this would be simpler. I'd like to prepopulate an RODC with all users accounts that are permitted. But I can only pre-populate one at a time: samba-tool rodc preload (<SID>|<DN>|<accountname>) sles-shire:~ # samba-tool group listmembers 'Allowed RODC Password Replication Group - Shire' Allowed RODC Password Replication Group - Global WIN7-SHIRE$ bilbo

Is this a problem? Does this mean no replication links exist? michael at sles-bree:~> samba-tool drs showrepl -k yes Bree\SLES-BREE DSA Options: 0x00000025 DSA object GUID: 7ea641b0-d418-4c74-a4fa-c15b852467b8 DSA invocationId: 1017ff29-756c-4777-b395-b481f4b5387c ==== INBOUND NEIGHBORS ==== ==== OUTBOUND NEIGHBORS ==== ==== KCC CONNECTION OBJECTS ==== Connection -- Connection name:

We've joined an RODC to the domain (Windows 2008R2 running a W2003 FFL/DFL AD) but are getting these errors on first startup. It was joined with: samba-tool domain join main.adlab.netdirect.ca RODC --realm=main.adlab.netdirect.ca --username=administrator at main.adlab.netdirect.ca --dns-backend=BIND9_DLZ but we get these errors right after startup: Nov 28 12:35:27 sles-bree samba[3939]:

Hi all, We're still experimenting with the samba3 -> samba4 upgrade. Lot's of nice progression. :-) ANyway: my question is how to deal with the userPrincipalName AD field. The classicupgrade does not fill this field. Reading up on it, tells me that it appears to be required, and should be something like username at samba4.domain Is this correct? How do you generally deal with

When you try to upgrade on a test stand, an error occurs. I do not understand that you need to add ldap, or improve migration script? Before that I tried to version 4.1.7, but the error was the sam root at dc1:~/smb_old# samba --version Version 4.2.2-SerNet-Ubuntu-7.trusty I also modified the file --- ./upgrade.py 2014-10-01 00:00:00.000000000 +0600 +++

Hi, I'm trying to migrate a NT4 domain under Samba3 to an AD DC under Samba4 on a separate server. During the classicupgrade, there were a number warnings while importing groups: WARNING 2019-05-13 15:09:56,728 pid:25284 /usr/local/samba/lib64/python2.7/site-packages/samba/upgrade.py #299: Could not add group name=Domain Admins ((68, 'Entry CN=Domain

Hello, I'm trying to get samba4 up and running as a DC in a lab environment. I have a freshly installed AD environment (W2012R2 servers, W2008R2 functional level) and I'm trying to join samba4 to it as a domain controller. When I try, I get this: # samba-tool domain join ad.netdirect.ca DC -Uadministrator --realm=AD.NETDIRECT.CA -W AD Finding a writeable DC for domain

We have a couple Samba4 AD domains we've implemented and I've noticed a difference between how users look when created via ADUC versus samba-tool. Created via ADUC, the following extra attributes are added: msSFU30Name: bilbo msSFU30NisDomain: netdirect unixHomeDirectory: /home/bilbo unixUserPassword: ABCD!efgh12345$67890 Created via samba-tool, the following extra attributes are added:

On Fri, Mar 18, 2016 at 4:04 PM, Andrew Bartlett <abartlet at samba.org> wrote: > The upgrade code assumes you run on the same host. I realise now that > folks doing an upgrade use that an an opportunity to upgrade hardware, > and keep old systems as fallbacks, so the assumptions cause trouble. > > Make the new host identical in terms of the data needed to upgrade >

Hi, i upgrade on a new server samba3 to samba4 with a LDAP Backend. I have followed this HowTO ?http://wiki.samba.org/index.php/Samba4/samba-tool/domain/classicupgrade/HOWTO until de classicupgrade step Here is the errors I get ?/usr/local/samba/bin/samba-tool domain classicupgrade --dbdir=/root/samba3/tdbfiles --use-xattrs=yes? --realm=bceao.int /root/samba3/tdbfiles/smb.conf Reading

Hello, this is a Samba AD Domain upgraded from Samba 3.x with classicupgrade. Debian 9.4 Samba: 4.7.6 (packages from tranquil.it) # cat /etc/samba/smb.conf [global] netbios name = DC1 realm = IWW.LAN server role = active directory domain controller workgroup = IWW idmap_ldb:use rfc2307 = yes dns forwarder = 172.16.1.12 dsdb:schema update

I have a new server running CentOS 6.4 x64, which will serve as our new Samba4 server. It is set up in a test environment, and I've copied over the tdb files and the smb.conf file from our samba3 server (Same OS and version). I'm trying to do an in-place upgrade on the copied files, but keep hitting an assert / uncaught exception during the upgrade: # /usr/local/samba/bin/samba-tool

Hi all, We'er running a classicupgraded samba4 AD 4.1.6 sernet for a month or two now, and all is very well. :-) It has been classicupgraded using the same 4.1.6. Today I wanted to try GPO's and they are not applied. GPUpdate /force tells me: "Windows attempted to read the file blahblah\gpt.ini from a domain controller and was not successful". Taken from the mailinglist, I

I used to upgrade samba3 to samba4 with almost successful with one problem, administrator can't access. As administrator, by default it is the only user account that is given full control over the system. My query is how to change the administrator password? we have one account which can join to the samba 4 AD based on the migrated data but the problem can't change the administrator or

Hello everyone. I'm trying to fix sysvol rights, because i see errors in output of /usr/bin/samba-tool ntacl sysvolcheck ERROR(<class 'samba.provision.ProvisioningError'>): uncaught exception - ProvisioningError: DB ACL on GPO directory /var/lib/samba/sysvol/samdom.svmetal.cz/Policies/{6AC1786C-016F-11D2-945F-00C04FB984F9}

Hello, I'm running a Samba 4.3.3 install on FreeBSD 8.4 (ZFS) in domain mode with passdb tdb backend. The databases and config files are the current versions of an install that I think started in the 1.9.x version range back in the late 90s (I can't remember exactly--it's been a long time!) and smbpasswd days. I'm now trying to convert to an AD install using the classicupgrade

Hi at all, i´am using samba 4.3.4 as "ad", "migrated by classicupgrade" some time ago from an nt4-domain. By trying samba_upgradedns --dns-backend=BIND9_DLZ i get the following error: Traceback (most recent call last): File "/usr/sbin/samba_upgradedns", line 262, in <module> paths, lp.configfile, lp) File

Hi, I am trying to create a build on CircleCi with smaba4 AD. It seems the filesytem doesn't support ACL's, which s3fs requires. I get the folowing error: ?ERROR(<class 'samba.provision.ProvisioningError'>): Provision failed - ProvisioningError: Your filesystem or build does not support posix ACLs, which s3fs requires.? Try the mounting the filesystem with the