similar to: DC Upgrade from 4.1.7 to 4.6.7

> -----Message d'origine----- > De : samba [mailto:samba-bounces at lists.samba.org] De la part de Rowland > Penny via samba > Envoyé : lundi 21 août 2017 16:34 > À : samba at lists.samba.org > Objet : Re: [Samba] DC Upgrade from 4.1.7 to 4.6.7 > > On Mon, 21 Aug 2017 15:52:01 +0400 > HB via samba <samba at lists.samba.org> wrote: > > > Hello all,

> -----Message d'origine----- > De : samba [mailto:samba-bounces at lists.samba.org] De la part de Rowland > Penny via samba > Envoyé : lundi 21 août 2017 16:34 > À : samba at lists.samba.org > Objet : Re: [Samba] DC Upgrade from 4.1.7 to 4.6.7 > > On Mon, 21 Aug 2017 15:52:01 +0400 > HB via samba <samba at lists.samba.org> wrote: > > > Hello all,

On Sat, 26 Aug 2017 11:28:00 +0400 HB via samba <samba at lists.samba.org> wrote: > > -----Message d'origine----- > > De : samba [mailto:samba-bounces at lists.samba.org] De la part de > > Rowland Penny via samba > > Envoyé : lundi 21 août 2017 16:34 > > À : samba at lists.samba.org > > Objet : Re: [Samba] DC Upgrade from 4.1.7 to 4.6.7 > >

I did a similar DC upgrade from 4.1.13 to 4.6.6(like your option 1, upgrade on existing AD servers, I have two, first upgrade on none-FSMO). and I don't have any issues with the DC upgrade itself. But be careful with your member servers. After the upgrade, I have to change some default values on file servers: 1. samba 3.5.10 member server(rpm from CentOS 6.2) lost connection to samba

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

> -----Message d'origine----- > De : Andrew Bartlett [mailto:abartlet at samba.org] > Envoyé : samedi 26 août 2017 12:40 > À : HB; samba at lists.samba.org > Objet : Re: [Samba] DC Upgrade from 4.1.7 to 4.6.7 > > On Sat, 2017-08-26 at 12:32 +0400, HB via samba wrote: > > > > > Here is the output of samba-tool dbcheck : > > # samba-tool dbcheck >

Hello all, I've planned to upgrade a Samba DC from 4.6.7 to 4.9.4 . For that I will use the following method : - build a new DC from 4.9.4 sources (on CentOS 7) - join this new DC to the domain - transfer the FSMO roles from the old DC (4.6.7) to the new DC (4.9.4) - replicate the sysvoldir from old DC to new DC - demote the old DC - switch off the old DC Since I prefer to

On Wed, 12 Dec 2018 15:43:09 +0100 peter grotz via samba <samba at lists.samba.org> wrote: > I forgot: this is samba 4.9.3 on centos 7 Where did you get Samba 4.9.3 from ? > > Thanks > > > Hello, > > I got a problem with adding an new dc to a domain. when I try to join > I get the following: What are the other DC(s) ? Rowland

On Wed, 12 Dec 2018 16:01:52 +0100 "peter.grotz--- via samba" <samba at lists.samba.org> wrote: > Thanks Rowland for your answer. > > these are sernet-packages from their subscription. > > There are 4 DCs (all with last sernet-rpms) 2 are demoted with probs > (dc-01 and dc-02 both centos6) and 2 are running (dc-10 and dc-11 on > centos 7) > >

Thank you Rowland for your answer . I reply inline. > > On Wed, 6 Feb 2019 15:20:56 +0400 > henri transfert via samba <samba at lists.samba.org> wrote: > > > Hello all, > > > > I've planned to upgrade a Samba DC from 4.6.7 to 4.9.4 . > > STOP! > > Do not do this directly, reports on here have shown that this will not work. > > You

On Mon, 21 Aug 2017 15:52:01 +0400 HB via samba <samba at lists.samba.org> wrote: > Hello all, > > Our Samba AD DC is running perfectly for years with the following > basic setup (see smb.conf below) : > - one DC running Samba 4.1.7 / CentOS 6.5 (compiled from > sources) > - internal DNS > - this DC is also a Print Server > - about

Hi, I've tried to update my samba AD/DC environment. Then, I've removed a existing offline DC with "samba-tool domain demote --remove-other-dead-server=genos". I've re-created "genos" (yes, I try to keep the same name and IP address) and install a 4.10.2 samba version (I know the new version is 4.11.0). When I've tried to join it on my domain, I've received

When I attempt to join samba 4.8.0 (stable) to my samba 4.6.7 DC (Ubuntu), I receive the following error: Partition[DC=us,DC=dignitastech,DC=com] objects[500/1605] linked_values[0/118] Failed to commit objects: WERR_GEN_FAILURE Join failed - cleaning up Deleted CN=DC3-CLONE,OU=Domain Controllers,DC=us,DC=dignitastech,DC=com Deleted CN=NTDS

> Get rid of samba3 by demoting it again as you did last time, search > through sam.ldb for any mention of samba3 and samba4 (you will > probably have to use '--cross-ncs' with ldbsearch or lbdedit), then > remove them. > Now start again with a new DC, but this time, call it anything but > samba3 or samba4. Getting worse and worse .... I demoted samba3 and then also

Hi, Just to reiterate an important point, the 'domain backup' command is there to backup your domain information, not your DC. If you still have a working domain, then you can recover any DC by simply rejoining it to the domain. Do not use backup/restore to recover an individual DC. If you want to recover your entire domain (i.e. power off all your DCs and start again from scratch),

Hello, after successfully demoted a samba4 dc node (redhat linux 6.4 with samba v4.1, hostname:samba4dc3) i tried to join another dc to domain (redhat linux 6.4 with samba v4.1, hostname:samba4dc4) and this is what i get: root at samba4dc4 /root #samba-tool domain join samdom.example.com DC -Uadministrator --realm=samdom.example.com --dns-backend=NONE Finding a writeable DC for domain

I happily and trustfully use Louis' backup-script from https://github.com/thctlo/samba4 to dump AD content via cronjob. Is it necessary/recommended to do that on *each* samba DC? Is there something server-specific in the dump(s) or is it enough to do that once per domain? thanks ...

This showed up at -d3: DRS replication add DN of aca72580-587e-4dab-adee-07a5f8027dfa is CN=foo,OU=bar,DC=baz Failed to apply records: Failed to locally apply remote add of CN=foo,OU=bar,DC=baz: ../lib/ldb/ldb_tdb/ldb_index.c:2012: Failed to re-index servicePrincipalName in CN=blah,OU=blah,DC=blah - (null): Operations error Failed to commit objects: WERR_GEN_FAILURE I've deleted the object

Hi, I have a Samba4 domain consisting of two 4.0.6 Samba servers, in two different AD sites. I am trying to join a new 4.0.7 Samba server as a DC. Previously, I had had some issues caused by hardware failure of one of the DCs; I have learnt my lesson about checking backups properly, as it took me a surprisingly (for me) long time to recover from this (there was no FSMO after the failure and I

Hello to all, I currently have a samba server with the following specs : - Samba 4.1.7 , compiled install from source code (samba wiki guided) - CentOS 6.5 x86_64 (VM) - AD DC + print server / CUPS - Internal DNS server I'm considering an upgrade to the last stable release 4.4.2. Since this server is in production with 400 users , 500 computers (XP, 7 Pro, OSX) , NAS members