similar to: Samba upgrade

Hello List, In preparation to update my samba ad-dc's running debian wheezy with backported samba 4.6.8 to 4.7.3. I'd like to fix two errors showing up in dbcheck whom hab been reported by dbckech --cross-ncs for an long time but without causing any issues so far. I'm getting this error on my main dc root at server:~# samba-tool dbcheck --cross-ncs Checking 4188 objects ERROR: no

root at dom2:~# samba-tool dbcheck --fix --yes Checking 705 objects Checked 705 objects (0 errors) root at dom2:~# samba-tool dbcheck --cross-ncs Checking 4506 objects Not resetting nTSecurityDescriptor on CN=Deleted Objects,CN=Configuration,DC=tlk,DC=loc Not resetting nTSecurityDescriptor on CN=Deleted Objects,DC=DomainDnsZones,DC=tlk,DC=loc Not resetting nTSecurityDescriptor on CN=Deleted

Am 25.11.2017 um 16:55 schrieb Achim Gottinger via samba: > > > Am 25.11.2017 um 04:39 schrieb Andrew Bartlett: >> On Fri, 2017-11-24 at 11:55 +1300, Andrew Bartlett via samba wrote: >>> On Tue, 2017-11-21 at 11:21 +0100, Achim Gottinger via samba wrote: >>>> Hello List, >>>> >>>> In preparation to update my samba ad-dc's running

Hi, Have changed the subject line to make my question clearer :) What is the expected behaviour of 'samba-tool dbcheck --fix'? Should running this command two times still produce the same output? I think I was bitten by bug 13228, but am not sure if I'm running the right command to resolve. Cheers Jonathan On 7 February 2018 at 23:44, Jonathan Hunter <jmhunter1 at

On Fri, 2024-04-12 at 08:03 +0200, Daniel M?ller via samba wrote: > Hello to all, > > After updating to samba 4.20 (from samba 4.19) on Debian 11, samba-tool > dbcheck --cross-ncs > results in: > samba-tool dbcheck --cross-ncs > Checking 4499 objects > Not resetting nTSecurityDescriptor on CN=Deleted > Objects,CN=Configuration,DC=tlk,DC=loc > Not resetting

I did it: root at dom2:~# samba-tool dbcheck --fix Checking 705 objects Reset nTSecurityDescriptor on CN=Deleted Objects,DC=tlk,DC=loc back to provision default? Owner mismatch: SY (in ref) DA(in current) Group mismatch: SY (in ref) DA(in current) Part dacl is different between reference and current here is the detail:

On Mon, 15 Apr 2024 07:53:16 +0200 Daniel M?ller via samba <samba at lists.samba.org> wrote: > I did it: > root at dom2:~# samba-tool dbcheck --fix > Checking 705 objects > Reset nTSecurityDescriptor on CN=Deleted Objects,DC=tlk,DC=loc back > to provision default? Owner > mismatch: SY (in ref) DA(in current) Group mismatch: SY (in ref)

Hi everybody! I have two samba AD server ( 4.2.7-SerNet-Debian-8.wheezy ). I try to make gpo working but I'm facing some problems... My Samba4 comes from an old windows AD so I have launch these command : samba-tool dbcheck --cross-ncs --reset-well-known-acls --fix samba-tool ntacl sysvolreset ( that take about 10 minutes to complete ) samba-tool dbcheck --cross-ncs --fix But the

I have setup an samba 4 AD DC. The Domain Administrator SAMDOM\Administrator can't create GPO (access denied). SAMDOM\Administrator is member of Domain Admins group. I have try samba-tool ntacl sysvolreset samba-tool dbcheck --cross-ncs --reset-well-known-acls --fix samba-tool dbcheck --cross-ncs --fix without success.

On Fri, 2017-11-24 at 11:55 +1300, Andrew Bartlett via samba wrote: > On Tue, 2017-11-21 at 11:21 +0100, Achim Gottinger via samba wrote: > > Hello List, > > > > In preparation to update my samba ad-dc's running debian wheezy with > > backported samba 4.6.8 to 4.7.3. > > I'd like to fix two errors showing up in dbcheck whom hab been reported > > by

Hello to all, After updating to samba 4.20 (from samba 4.19) on Debian 11, samba-tool dbcheck --cross-ncs results in: samba-tool dbcheck --cross-ncs Checking 4499 objects Not resetting nTSecurityDescriptor on CN=Deleted Objects,CN=Configuration,DC=tlk,DC=loc Not resetting nTSecurityDescriptor on CN=Deleted Objects,DC=DomainDnsZones,DC=tlk,DC=loc Not resetting nTSecurityDescriptor on CN=Deleted

The morning I ran "samba-tool dbcheck --cross-ncs" and found 10 errors on the DC with the FSMO roles. (Checked the other DC and found the same 10 errors.) When I run "samba-tool dbcheck --cross-ncs --fix" I am being asked to "y|N|all|none" questions and not sure what my reply needs to be. Two Samba 4.5.0 as ADDC's on Ubuntu 16.04LTS. (If that matters.) The

Hello all; I use CentOS 7.5.1804 I update from samba-4.8.2 to samba-4.9.1 and finish with not errors, but when I run samba-tool dbcheck --cross-ncs I have the error: [root at gtmad ~]# samba-tool dbcheck --cross-ncs Checking 4087 objects ERROR(<type 'exceptions.UnicodeEncodeError'>): uncaught exception - 'ascii' codec can't encode character u'\xe9' in

Hi All, On my two-DC setup (dc00 and dc01 - Used to be a 4-Dc setup but 02 and 03 are gone), I've noticed the following errors which I am unable to fix.. Any hints? * Basic dbcheck is clean. [root at dc00 ~]# samba-tool dbcheck Checking 327 objects Checked 327 objects (0 errors) * Cross-NCS shows two errors related to a de-comissionned DC (dc02) and cannot auto-fix this.. How do I fix

On Thu, August 20, 2020 16:14, Rowland penny wrote: > On 20/08/2020 20:40, James B. Byrne via samba wrote: >> FreeBSd-12.1p8 >> Samba-4.10.15 >> >> >> I have this problem: >> >> samba-tool dbcheck --cross-ncs >> Searching for dsServiceName in rootDSE failed: operations error at >> ../../source4/dsdb/samdb/ldb_modules/rootdse.c:518 >>

Hello, I have 2 samba DCs. DC1 with FSMO role and DC2. These days, when I use dbcheck in DC1 ,I got the following error: # samba-tool dbcheck --cross-ncs Checking 4419 objects ERROR: incorrect DN SID component for member in object CN=Domain Users,CN=Users,DC=adagene,DC=cn - <GUID=c5c33d48-226b-4105-9c69-0506a22d3a15>;<RMD_ADDTIME=131526914300000000>

Recently upgraded my 3 dc's to samba 4.12.1 as part of the install ran dbcheck --cross-ncs on each dc after make install first dc dbcheck reported 5474 objectssecond dc reported 5476 objects last dc (the one with all the fsmo roles, etc.)? reported 1406 objects! now all of them report 1406 objects. (drs replication obviously) ADUC, DNS, GPO manager all seem to have the requisite data. I

> -----Message d'origine----- > De : samba [mailto:samba-bounces at lists.samba.org] De la part de Rowland > Penny via samba > Envoyé : samedi 26 août 2017 12:00 > À : samba at lists.samba.org > Objet : Re: [Samba] DC Upgrade from 4.1.7 to 4.6.7 > ... > On Sat, 26 Aug 2017 11:28:00 +0400 > > Hi, > > > > I have begun to add a new 4.6.7 DC (following

I have a Samba4 Domain Controller, which we have run in production since ~2009 (early alpha). It's had a few issues over the years which we've managed to recover from. I'm trying to join a second Samba4 DC to the domain, but having trouble when I issue the join. I have run dbcheck on the existing DC, which found and fixed some errors. There are still about 60+ errors like this: #

Hi All, I upgraded one of our 2 DC's from 4.6.8 to 4.7.2. I am scouting the log for post upgrade errors and seeing this entry. Should I be concerned? I should note, I ran a samba-tool dbcheck --cross-ncs and samba-tool dbcheck --cross-ncs --fix after the upgrade. (6 errors found and fixed) I am not seeing any adverse effects yet. Kind regards