similar to: Upgrading samba and OS - can I rejoin ?

On 25/08/2019 20:49, gizmo via samba wrote: > Hi, > I want to upgrade samba 4.8.2 to samba 4.10.7. According to here: > > https://wiki.samba.org/index.php/Upgrading_a_Samba_AD_DC#Rejoining_the_upgraded_DC > > best way is to rejoin the server after the upgrade. > But also I need to upgrade the OS, in my case it means a new installation from the OS, > because an upgrade is

On 26/08/2019 13:44, Joachim Lindenberg wrote: > It is interesting to see two members of the Samba Team disagree. Just because we are on the same team, this doesn't mean we will agree 100% of the time ;-) > Though I really appreciate the support provided by Rowland a lot, I definitely favor Andrew?s "If something isn't being cleaned up then that's a bug". I never

And (re)joining is not recommended ? There are so many services and computers connected to the samba server, which are not in my hand. Means after I upgraded all our 5 ADs I would have to inform many people about the new name and IP. Thanks

On 26/08/2019 06:06, Andrew Bartlett via samba wrote: > On Mon, 2019-08-26 at 06:54 +0200, gizmo via samba wrote: >> And (re)joining is not recommended ? > We do recommend it: > https://wiki.samba.org/index.php/Upgrading_a_Samba_AD_DC > >> There are so many services and computers connected to the samba server, which are not in my hand. >> Means after I upgraded all

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

On Mon, 2019-08-26 at 23:10 +0200, gizmo via samba wrote: > Ok, I understood, I should join with a new name. > But what's the difference between my plans and the docu "Rejoining the upgraded DC" ? > There is nothing mentioned, that a new name is necessary. > Is it because I install a new OS and so I start from scratch ? A new name is not necessary, which is why this

It is interesting to see two members of the Samba Team disagree. Though I really appreciate the support provided by Rowland a lot, I definitely favor Andrew?s "If something isn't being cleaned up then that's a bug". Best Regards, Joachim -----Urspr?ngliche Nachricht----- Von: samba <samba-bounces at lists.samba.org> Im Auftrag von Rowland penny via samba Gesendet: Monday,

Hai Andrew, I just tested this on 4.10.7 Which resulted in : ERROR(<class 'samba.join.DCJoinException'>): uncaught exception - Can't join, error: Not removing account DC1$ which looks like a Samba DC account matching the password we already have. To override, remove secrets.ldb and secrets.tdb The wiki does not say we have to remove the old the secrets. Report it as

On Mon, 2019-08-26 at 06:54 +0200, gizmo via samba wrote: > And (re)joining is not recommended ? We do recommend it: ? https://wiki.samba.org/index.php/Upgrading_a_Samba_AD_DC > There are so many services and computers connected to the samba server, which are not in my hand. > Means after I upgraded all our 5 ADs I would have to inform many people about the new name and IP. The

Hi Rowland, Recently I have upgraded a single server 4.4.5 to 4.10.7 with in-place method and all seems to works fine. Can you give detail what are this advantages to upgrade with rejoins about database, performance (index recreated?), stability, dbcheck... what are the realadvantages and disadvantages to evaluate in our case what is the best method To rejoin I think with this steps: - fsmo

On 10/22/20 9:38 AM, Robert Marcano wrote: > On 10/22/20 9:30 AM, Marco Shmerykowsky via samba wrote: >> I've been looking at the Sambawiki for notes on upgrading >> (https://wiki.samba.org/index.php/Upgrading_a_Samba_AD_DC) >> >> The way I read it it is suggested to uninstall samba >> completely and then essentially re-installing.? That seems >> like a

On 10/22/20 10:10 AM, Marco Shmerykowsky via samba wrote: > > On 10/22/2020 9:40 AM, Robert Marcano via samba wrote: >> On 10/22/20 9:38 AM, Robert Marcano wrote: >>> On 10/22/20 9:30 AM, Marco Shmerykowsky via samba wrote: >>>> I've been looking at the Sambawiki for notes on upgrading >>>> (https://wiki.samba.org/index.php/Upgrading_a_Samba_AD_DC)

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?

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

I've been looking at the Sambawiki for notes on upgrading (https://wiki.samba.org/index.php/Upgrading_a_Samba_AD_DC) The way I read it it is suggested to uninstall samba completely and then essentially re-installing. That seems like a Murphy's Law disaster (with my luck) waiting to happen. Is "upgrading "in-place" a realistic option?

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

Hi, Recently we have added 4.10.7 as additional dc, to our existing 4.4.5 samba AD DC, comparing output testparm I have detected that 4.4.5 has map readonly = no store dos attributes = Yes but 4.10.7 doesn't have Also compared smb.conf and both has the same configuration. Is this correct? Are required this configurations on 4.10.7? In a few day I want to upgrade this 4.4.5

I used the DC rejoin method as described in the WiKi to upgrade one of my DCs to version 4.11.0. Following the steps, when I came to rejoin the domain, it initially failed, complaining that the DC already existed, but to force the rejoin, remove the files: secrets.ldb and secrets.tdb. I assume you don't demote the DC before the upgrade, as there's no mention of this? Anyway, I

On 18/09/2019 13:10, Rowland penny via samba wrote: > On 18/09/2019 12:34, Roy Eastwood via samba wrote: > > I used the DC rejoin method as described in the WiKi to upgrade one of my DCs to version 4.11.0. Following the steps, when I came > > to rejoin the domain, it initially failed, complaining that the DC already existed, but to force the rejoin, remove the files: > >

I ran across this several times during my experimentation and assumed it is safe to remove secrets.*db. Actually I would prefer if the tool would just prompt whether this is a rejoin attempt and then does whatever is needed to clean up. Regards, Joachim -----Urspr?ngliche Nachricht----- Von: samba <samba-bounces at lists.samba.org> Im Auftrag von L.P.H. van Belle via samba Gesendet: Monday,