similar to: DC validity test needed?

Thank you for hint to this VBS script. In fact I alraedy saw it but I'm not too confident in my VB knowledge, so I didn't use that script, prefering rely on Samba command and shell scripts to work around issues. You spoke about SOA record which wasn't changed, same here. There is another DNS record I had to change: _ldap._tcp.pdc._msdcs.samba.domain.tld. I spoke about removing

On 10/29/2015 9:56 AM, Ole Traupe wrote: > > > Am 29.10.2015 um 14:37 schrieb James: >> On 10/29/2015 9:15 AM, Ole Traupe wrote: >>> >>> >>> Am 29.10.2015 um 13:54 schrieb mathias dufresne: >>>> Thank you for hint to this VBS script. In fact I alraedy saw it but >>>> I'm not >>>> too confident in my VB knowledge, so

On 10/29/2015 9:15 AM, Ole Traupe wrote: > > > Am 29.10.2015 um 13:54 schrieb mathias dufresne: >> Thank you for hint to this VBS script. In fact I alraedy saw it but >> I'm not >> too confident in my VB knowledge, so I didn't use that script, prefering >> rely on Samba command and shell scripts to work around issues. >> >> You spoke about SOA

On 10/30/2015 9:19 AM, Ole Traupe wrote: > > > Am 30.10.2015 um 13:33 schrieb James: >> On 10/29/2015 9:56 AM, Ole Traupe wrote: >>> >>> >>> Am 29.10.2015 um 14:37 schrieb James: >>>> On 10/29/2015 9:15 AM, Ole Traupe wrote: >>>>> >>>>> >>>>> Am 29.10.2015 um 13:54 schrieb mathias dufresne:

Hi, I played with demote recently on a test AD domain composed with Samba version 4.3.0 and 4.3.1. I demoted all version 4.3.0. I was facing same issue as you. I written long mails here to explain how I managed that. My DNS looks clear now. Today I played with AD sites and I found in default sites all demoted DC. They weren't removed from DNS DB nor here. For now I have no idea how to get

Hi all, I posted on both mailing as this seems to be (to me) an internal issue. As the 4.3.1 went out I decided to switch my DC from 4.3.0 to this new version. The process was to install Samba 4.3.1 on new systems, joining these Samba as DC, seizing FSMO roles, demote all 4.3.0. The few I tested until now is working except for DNS entries: samba_dnsupdate is not working as it tries to update

On 10/30/2015 10:11 AM, Ole Traupe wrote: > > > Am 30.10.2015 um 14:56 schrieb James: >> On 10/30/2015 9:19 AM, Ole Traupe wrote: >>> >>> >>> Am 30.10.2015 um 13:33 schrieb James: >>>> On 10/29/2015 9:56 AM, Ole Traupe wrote: >>>>> >>>>> >>>>> Am 29.10.2015 um 14:37 schrieb James:

dear roland and mathias i already upgrade samba server version to 4.4.4 i have domote 3 of 4 offline dc successfully one dc that i cant demote shown this error message /**//*[root at pdc ~]# samba-tool domain demote --remove-other-dead-server=dc25*//* *//*ERROR: Demote failed: DemoteException: dc25 is not an AD DC in domain.co.id*//* *//*A transaction is still active in ldb context

2016-02-10 14:37 GMT+01:00 Rowland penny <rpenny at samba.org>: > On 10/02/16 11:12, mathias dufresne wrote: > >> Hi all, >> >> Using 4.3.4 + Bind DLZ @ Centos 7. >> >> Regarding AD sites, I have several questions: >> >> 1° Is it possible with Samba4 to rename Default-First-Site-Name? >> > > Depends on what you mean, if you mean

hi mathias let me confirm your statement so.. you think if we demote those 2 DC server that already offline, the DNS will be running well well if this is one of option we have, i will consider to upgrade our FSMO DC from samba 4.1.X to 4.4.x , by the way, are there any consideration if we update samba directly from 4.1 to 4.4 ? let me answer some of your question *1 - what command are you

Hey, Thank you Louis for this script, I didn't yet took time to dig in but I'll do. I didn't took time neither to perform another test. That should be done today. Anyway I waited for DC synchronisation before posting. I joined my DC and removed the old ones almost at same time then I gave more than 12 hours to my DC to synchronize. Then I tried to understand what happened, I wrote

My answer below. 2016-02-10 15:38 GMT+01:00 Rowland penny <rpenny at samba.org>: > On 10/02/16 14:07, mathias dufresne wrote: > >> >> >> 2016-02-10 14:37 GMT+01:00 Rowland penny <rpenny at samba.org <mailto: >> rpenny at samba.org>>: >> >> >> On 10/02/16 11:12, mathias dufresne wrote: >> >> Hi all, >>

2016-02-10 16:54 GMT+01:00 Rowland penny <rpenny at samba.org>: > On 10/02/16 15:36, mathias dufresne wrote: > >> My answer below. >> >> 2016-02-10 15:38 GMT+01:00 Rowland penny <rpenny at samba.org <mailto: >> rpenny at samba.org>>: >> >> On 10/02/16 14:07, mathias dufresne wrote: >> >> >> >>

Hi all, After installing a bunch of new AD DC using the 4.3.1 version I decided to remove the old ones. On one DC I've set up log level as follow: log level = 1 auth:9 registry:7 winbind:7 passdb:7 sam:3 rpc_srv:2 rpc_cli:2 First I'm not sure this is the right way to declare specific log levels but man smb.conf gives me: Example: log level = 3 passdb:5 auth:10 winbind:2 So it sems, to

Thx mathias for your reply First, yes im using internal DNS, i just try to add new dns from other dc but it doesnt work, i think the (maybe) corrupted dns data already sync to other dc And i still run my samba4 installation, because sofar the only problem is, i cant add new dns record In other case i found up one of my team just re install 2 samba4 server in site office with different AD

On 01/04/16 22:38, spindles7 wrote: > Hi Rowland, > Have tried your patch, and now the Demote succeeds: > > root at dc3:~# samba-tool domain demote -Uadministrator > Using dc1.microlynx.com as partner server for the demotion > Password for [MICROLYNX\administrator]: > Deactivating inbound replication > Asking partner server dc1.microlynx.com to synchronize from us >

On 23/07/15 16:23, mathias dufresne wrote: > Hi all, > > I tried "samba-tool ldapcmp" several times to solve this issue, without > success. > > On DC acting as full FSMO: > dc20:~# samba-tool ldapcmp ldap://dc00.ad.dgfip.lan > ldap://dc20.ad.dgfip.lan domain > ERROR(ldb): uncaught exception - ldb_wait: Time limit exceeded (3) > File

Hello, I had tried to demote a samba DC and re-join it as a member over the weekend, but something went horribly wrong. Starting point was a samba DC which also acted as a file server. It was the single DC in that domain. I first set up a Windows 2008 R2 machine and promoted it to DC within the same domain. I then changed DNS entries on all machines to point to the new DC, transferred the FSMO

Hi, I demoted a running domain controller by running the samba-tool demote command on the running system to be demoted and there's still some DNS entries for the old one kicking around. It's still listed under _msdcs and also _kerberos._udp and _ldap._tcp. Should I manually remove them? If so, is there a list of spots to look in for DNS entries of old DCs? Also, does the fact that

Mandi! Denis Cardon via samba In chel di` si favelave... > what version of Samba are you running? Recent versions do a much better job > at DNS cleaning during demote. Eh, domain controllers are still on samba 4.5... > I also advise you to run the demote on another DC than the one you are > demoting (samba-tool doamin demote --remove-other-dead-server=xxxxx). > Running a