similar to: Error Upgrading Schema

In general we do not allow the removal of schema. In particular, because records in samba are stored under the attribute name, removing schema or renaming schema items describing those attributes and objectclasses can mean records cannot be processed correctly. However, if you confirm you really have exactly the entry already in the schema, you could edit the new schema not to add that

I'm wondering if anyone can make any suggestions? Rowland? Andrew? Even if it's just to suggest a framework for troubleshooting on my own? I really appreciate any time you can spare. Matthew On 2020.11.02, 5:59 PM, "samba on behalf of Matthew Delfino Samba List via samba" <samba-bounces at lists.samba.org on behalf of samba at lists.samba.org> wrote: Hello! I

Hello, Since responses were not forthcoming, I started looking for plausible explanations that might be unique to my company's setup. A few years ago, we imported ldif schema files to support directory integrations with Kerio Connect server. The attribute "msDS-MembersOfResourcePropertyList" was included in one of those ldif files. Since we no longer require directory integration

Andrew, I feel that it is your prerogative to determine how many odd possibilities you want your tools to account for, so that they might know what to do rather than exit with an error. You have a better sense for how likely it is that someone in the wild is altering their schema and might have changed an already existing attribute, as it seems I did. If you'd allow me to impose upon your

Thank you for taking time to do this, Andrew. But, of course, it will be too late for me. I’ve just returned from exile, where I went on a spirit quest of sorts. Except that, on this quest, I was obliged to keep my distance until I had found a way to export and import all users, groups and group membership from my old samba domain to my new one. I updated schema to support Kerio Connect using

Hello from Sunny and frigidly cold Minneapolis, MN, USA! I have a SAMBA domain with three DCs running v4.4.16 on Ubuntu Server 14.04.5 LTS (BIND9 DLZ Backend). I need to move all my records to a new domain (from DOMAIN.LOC to SAMDOM.DOMAIN.NET). I know that it's not possible to change domains on a samba install, so I've created three new DCs running v4.7.4 on Ubuntu Server 16.04.3 LTS

On 20/11/2020 02:13, Matthew Delfino Samba List wrote: > Thank you, Andrew! > > This evening I attempted the upgrade. I first carefully commented out each of the attributes from the Schema-Updates.md file. I then saved the file and ran the following command, which gave me the subsequent output: > > (as root) > > # samba-tool domain schemaupgrade > Temporarily

On 20/11/2020 15:46, Matthew Delfino Samba List wrote: > Rowland, > > I had the same thought. When I do that and try again, I get this message: > > # samba-tool domain schemaupgrade > Temporarily overriding 'dsdb:schema update allowed' setting > Patched Sch49.ldf using /usr/share/samba/setup/adprep/WindowsServerDocs/Sch49.ldf.diff > Exception in patch:

On 10/11/2020 22:47, Matthew Delfino Samba List via samba wrote: > Andrew, > > I feel that it is your prerogative to determine how many odd possibilities you want your tools to account for, so that they might know what to do rather than exit with an error. You have a better sense for how likely it is that someone in the wild is altering their schema and might have changed an already

Hello! I just upgraded from Samba v4.10.9 to v4.11.15. The upgrade seems to have gone smoothly. As part of major release maintenance, I ran the following command on my schema master DC: > samba-tool domain schemaupgrade I get the following output: > Temporarily overriding 'dsdb:schema update allowed' setting > Patched Sch49.ldf using

On Wed, 2020-11-18 at 23:12 +0000, Matthew Delfino Samba List via samba wrote: > > There is only one thing that concerns me: One of the attributes > specified in the Samba script has a parameter whose value directly > contradicts the value specified in my old ldif file: > Well done with the analysis! > > In Samba script: > > dn:

Hello Samba People, We have a Kerio Connect (email) server using Samba 4.8.5 as it’s directory service (3 AD DCs). We’ve been using this setup for about 3 years now. Over the last several months, we’ve been trying to find out why Samba starts rejecting attempts that the Kerio Connect mail server makes to authenticate our users. The errors in Kerio look like this: Authentication failed for user

> Is this an existing domain or a new domain ? It is an existing domain (productive for about 15 years) > Did you check if the schema needs upgrading ? As I told before, it's currently at 69 root at TUX:~# ldbsearch -H /var/lib/samba/private/sam.ldb -b 'cn=Schema,cn=Configuration,dc=briesebaer,dc=intern' -s base objectVersion # record 1 dn:

Hi I wonder if anyone can help. I am trying to upgrade the schema version. Current environment: Two domain controllers both running samba 4.7.6 - Ubuntu package Version: objectVersion: 44 (server 2008) According to samba docs, 'samba-tool domain schemaupgrade' only works from 2008 R2 version 47. For earlier it says: 'the ldf files must be manually sourced from the

On 4/21/2017 1:28 PM, Matthew Delfino via samba wrote: > Hey Samba Friends, > > Maybe the below question is too general. How about this: I’ve set my "log level = auth:10" in the global parameters of my smb.conf file. > > I then purposely failed to log into an account on my Windows 10 machine until the account was locked. > > I’ve run the following command where x

Hi! I'm running samba 4.3.11 on Ubuntu server Xenial. It's the only AD-DC in a windows domain that used to be hosted by a single Win2k3 server. The AD schema version is 30, the functionality level is already raised to 2008_R2 (domain) and 2008 (forest). ~# ldbsearch -H /var/lib/samba/private/sam.ldb -b 'cn=Schema,cn=Configuration,dc=domain,dc=com' -s base objectVersion #

root at pdc1-samba:/opt/adprep# ldbsearch -H /usr/local/samba/private/sam.ldb -b "CN=Schema,CN=Configuration,$(echo "DC=$(hostname -d)" | sed 's/\./,DC=/g')" -s base objectVersion | grep 'objectVersion' | awk '{print $NF}' 30 The scheme that this domain: 30 because it was a migration from a 2003 server some time ago. I want to upgrade. Now Try this

Hello Samba Friends, For those of you who have had to sift through Samba logs for clues on how to determine what caused an account to lock after repeated failed logon attempts, what "log level" settings have you found to be most helpful? Thanks, Matthew ©2017 KNOCK, inc. All rights reserved. KNOCK is a registered trademark of KNOCK, inc. This message and any attachments contain

Hey Rowland, thanks for your quick reply. Answers below… > On 2017.01.18, at 12:41 PM, Rowland Penny via samba <samba at lists.samba.org> wrote: > > On Wed, 18 Jan 2017 11:34:41 -0600 > Matthew Delfino via samba <samba at lists.samba.org> wrote: > >> Hello, >> >> I have an Ubuntu 14.04 server with Samba 4.4.6 and a BIND DLZ backend >> that

Hey Rowland, Thanks for getting back to me. I just finished my recompile. I even ran a "samba-tool dbcheck --fix". I still I get this error: samba-tool domain passwordsettings set --max-pwd-age=270 ERROR(<class 'TypeError'>): uncaught exception - unorderable types: NoneType() >= int()   File "/usr/lib/python3/dist-packages/samba/netcmd/__init__.py", line