similar to: How to move DC to other Server

Displaying 20 results from an estimated 10000 matches similar to: "How to move DC to other Server"

2016 Oct 30
2
How to move DC to other Server
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
2016 Oct 27
1
How to move DC to other Server
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, >>
2016 Apr 20
3
Sernet Packages - configure Options
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
2017 May 15
2
Problems with samba-tool ntacl sysvol reset
On Mon, 15 May 2017 22:02:30 +0200 "Dirk Laurenz" <samba at laurenz.ws> wrote: > Any idea? > > > > root at samba01:~# uname -a > Linux samba01 4.9.14-v7+ #977 SMP Mon Mar 13 18:25:19 GMT 2017 armv7l > GNU/Linux > > root at samba01:~# cat /etc/debian_version > 8.7 > > root at samba01:~# samba -V > Version 4.6.3 I take that you have built
2016 Apr 21
2
Sernet Packages - configure Options
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
2017 Nov 03
3
dns module not found
Nope, but that was not the problem... root at samba01:~# dpkg -l | grep python-dns root at samba01:~# apt-get install python-dns Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: python-dns 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 28.7 kB of archives. After this operation, 135
2017 Nov 03
2
dns module not found
Hello @all, i have three samba dc's each running with Version 4.7 on raspbian strech On one oft hem i have now this problem and i don't know why? I'm not sure what caused the problem. because it worked before. root at samba01:~# /usr/sbin/samba_dnsupdate --help Traceback (most recent call last): File "/usr/sbin/samba_dnsupdate", line 52, in <module>
2015 Dec 22
5
Dead Domain Controller server
Good afternoon, I have an environment with 4 servers samba 4 and yesterday one of them died, I tried removing it and not found, then recreated the server with the same name and joined him as a DC, however, he created a new uuid and sync entres servers I stopped, I had to force a forced sync: # samba-tool drs replicate samba02 samba01 DC=example,DC=com,DC=br # samba-tool drs replicate samba03
2019 Sep 05
4
Questions about 2n dc and samba update
Hi, I have to upgrade 2 different samba AD DC (2 domains) from 4.4.5 to 4.10.7 First is a single server and updaded with in-place upgrade from 4.4.5 to 4.10.7 and all perfect Second environment I need to add a second dc and also upgrade existing server, and I have some question about how to do this: - join second domain server with 4.10.7 - then make in place upgrade on existing server dc1?
2019 Sep 19
4
Error demote
Hi, during a demote of an online and working DC I receive this error dsreplicasync failed (8440 'werr_ds_dra_bad_nc') Any suggestion where could be the issue, server is not really demoted Server is samba 4.4.5 and other server that has fsmo roles is 4.10.7 Thanks
2017 Jan 23
2
DNS Update not working after update to 4.5.3
Hi, i reduced to one reverse dns zone (192.168.x.x.) same error when converting internal to bind_dlz Jan 23 14:55:39 samba01 named[3279]: Loading 'AD DNS Zone' using driver dlopen Jan 23 14:55:40 samba01 named[3279]: samba_dlz: started for DN DC=local,DC=laurenz,DC=ws Jan 23 14:55:40 samba01 named[3279]: samba_dlz: starting configure Jan 23 14:55:40 samba01 named[3279]: samba_dlz:
2019 Sep 12
5
Questions about samba upgrade
Hi, I'm making tests to migrate our actual 4.4.5 to a latest versions and add a second dc. I have added a second dc with 4.10.7 and seems to work fine, now I have 4.4.5 with fsmo roles and a second dn with 4.10.7, but reading wiki https://wiki.samba.org/index.php/Upgrading_a_Samba_AD_DC seems that since latest days some changes about steps to upgrade, now seems that is recommended to us
2017 Jan 23
5
DNS Update not working after update to 4.5.3
Hai,   Seeing : > Jan 23 14:55:40 samba01 named[3279]: samba_dlz: configured writeable > zone '168.192.in-addr.arpa' > Jan 23 14:55:40 samba01 named[3279]: zone local.laurenz.ws/NONE: has no > NS records > Jan 23 14:55:40 samba01 named[3279]: samba_dlz: Failed to configure zone > 'local.laurenz.ws'   Normaly you should see first the local.laurenz.ws
2017 Jan 20
5
DNS Update not working after update to 4.5.3
I suspect a zone overlap. Did you add an extra zone manualy in bind? Or something like this... You added : Zone1.Domain.TLD and then Domain.TLD But then with the reverse zones. Because this : > Jan 20 13:58:09 samba02 named[10811]: zone 2.168.192.in-addr.arpa/NONE: > has no NS records Does not look likes the samba_DLZ log lines but a pure bind log line. Review you bind config and
2016 Oct 31
0
How to move DC to other Server
meanwhile i move the dc from amd to rasp - i have now an orphanded drs entry.. how can i remove this? DC=ForestDnsZones,DC=local,DC=laurenz,DC=ws NTDS DN: CN=NTDS Settings\0ADEL:96ed4fb0-045f-4c4c-91ec-aebdd6a903c1,CN=SAMBA01\0ADEL:1c13e668-fe18-4093-b969-aef51a24a97f,CN=Servers,CN=Zuhause,CN=Sites,CN=Configuration,DC=local,DC=domain,DC=toplevel Regards, Dirk Am 30.10.2016 um
2015 Oct 29
1
Upgrade DC from 4.2 sernet packages to 4.3 self compiled
Hello list, i've upgraded my second dc to 4.3 self compiled from 4.2 sernet packages via demote and join. Now i want to upgrade the first dc. is it better to demote it too or just to replace the binaries? Regards, Dirk
2017 May 13
2
Problems with samba-tool ntacl sysvol reset
Raspian root at samba01:~# uname -a Linux samba01 4.9.14-v7+ #977 SMP Mon Mar 13 18:25:19 GMT 2017 armv7l GNU/Linux root at samba01:~# cat /etc/debian_version 8.7 root at samba01:~# samba -V Version 4.6.3 root at samba01:~# cat /etc/samba/smb.conf # Global parameters [global] netbios name = SAMBA01 realm = LOCAL.xx.xx workgroup = LAURENZ server role = active
2017 Jan 25
1
DNS Update not working after update to 4.5.3
i will do so.... thanks Am 25.01.2017 um 08:46 schrieb L.P.H. van Belle via samba: > Still > > Check this line from you named config. > > include "/etc/bind/named.conf.default-zones"; > > This can cause an overlap in the zones, so be carefull with that one. > > > Greetz, > > Louis > > >> -----Oorspronkelijk bericht----- >> Van: samba
2019 Sep 05
1
Questions about 2n dc and samba update
Thanks Rowland!!! Missatge de Trenta sis <trenta.sis at gmail.com> del dia dj., 5 de set. 2019 a les 11:52: > > Hi, > > Thanks for your information about DNS config. > About second server and update, I understand that First I have to > transfer role to new added, demote old, and then rejoin and transfer > fsmo roles to source server, right? > My question is related
2018 Apr 08
2
Unable to rejoin domain, LDAP error 50
On Sun, 08 Apr 2018 13:34:52 +0200 Kris via samba <samba at lists.samba.org> wrote: > W dniu 2018-04-08 12:49, Rowland Penny via samba napisał(a): > > On Sun, 08 Apr 2018 12:31:26 +0200 > > Kris via samba <samba at lists.samba.org> wrote: > > > >> I should try this command sooner. Now I have made full backup and > >> something is missing: >