similar to: Upgrade DC from 4.2 sernet packages to 4.3 self compiled

Hello Rowland, thanks for your tipp. the last time i tried this (was fairly samba 4.0), transferring fsmo roles ended up in corruption. is this now a safe feature? i found out, that the build options are nearly the same, just modules dir differs. so replace the binaries would make it? remove sernet packages and install my own Am 20.04.2016 um 22:15 schrieb Rowland penny: > On 20/04/16

Hello, i want to replace the sernet packages with an own one. Because it's the DC, which is the last one which remains, i'm sure, having the same configure/built options would help with replace the binaries and keeping the database. The other DC's (2 raspberries) have been configured and built with (but complete demote/rejoin process): ./configure --prefix=/usr

In that case, just move all the Samba files once the first server is offline. All the join/demote games suggested here are more likely to cause you trouble than help, due to a bug in our RID Set management:  https://bugzilla.samba.org/show_bug.cgi?id=12394 None of Samba's databases are arch-specific, so if the hostname and IP are the same, just restore the databases and config files and it

Hi, i want to move my DC from an amd64 debian jessie to a armhf debian jessie. My first guess is to demote the dc and rejoin the new server. Der DC has all FSMO roles and is part of a three DC setup. Would this be the right way or should i choose another way? Regards, Dirk

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 >

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

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

Thanks Rowland. Have submitted a bug report (No 11818). spindles7 On Thu, 31 Mar 2016 09:38:02 +0100, Rowland penny <rpenny at samba.org> wrote: >On 30/03/16 23:26, spindles7 wrote: >> Hi all, >> I am consistently getting the error: >> >> root at dc2:~# samba-tool domain demote -Uadministrator >> Using dc1.microlynx.com as partner server for the demotion

moving to a temporary server could help? what i mean is: trasnfer fsmo roles to samba02 join temp01 demote old samba01 bring up new samba01 join samba01 remote temp01 correct? this should work? Am 27.10.2016 um 13:09 schrieb Rowland Penny via samba: > On Thu, 27 Oct 2016 11:10:58 +0200 > Dirk Laurenz via samba <samba at lists.samba.org> wrote: > >> Hi, >>

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

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

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:

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 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:

Hello $LIST, i setup a new clean domain to examine the feature of updating/creating PTR records. When i call ipconfig /registerdns on the client i get this entry in the windows eventlog (sorry german) Fehler beim Registrieren der Hostressourceneinträge (A oder AAAA) für den Netzwerkadapter mit den folgenden Einstellungen: Adaptername: {2A467E48-624B-4CCF-9B7D-9BA5629D8117}

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

Hello, I am in the process of upgrading one single DC (internal DNS) to 4.8.12. I have followed the procedure of adding a new DC, transfert FSMO roles and demote the old DC. Everything gone right (except at the tranfert FSMO step where I faced the problem described here https://lists.samba.org/archive/samba/2017-August/210140.html , this bug subsists in 4.8.12 , maybe it has been fixed in later

Thanks for your answer Rowland. That's bad news since the new DC is now in production and I can't take the risk to break anything. Reply inline : > -----Message d'origine----- > De?: samba <samba-bounces at lists.samba.org> De la part de Rowland penny > via samba > Envoy??: lundi 5 ao?t 2019 11:18 > ??: samba at lists.samba.org > Objet?: Re: [Samba] DNS state

Hi, While upgrading Samba-AD fromm 4.15.9 to version 4.18, I ran into a peculiar problem. AD Component is up, but DNS is just not coming up. kinit is reporting KDC not found problem. All these years I have been compiling samba from source and for nearly 7 years, it was working like a charm. But this upgrade activity, we ran into rough weather. We do not upgrade the existing servers where as,