similar to: upgrading AD DC and rejoin recommendation

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,

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,

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 not possible, the old and the new version are to different. Can I do this the

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

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

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

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

Hi there, in a specal case I want to send IP packets from one IP address to another IP address on the same multihomed linux box. The problem is, that the packets should leave the box by passing one ethernet interface, go through a hub/switch and get back into the box via the second interface. Well, this sounds crazy. Anyway, does anyone know a solution? Bernd

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

I could really use some support with this. I understand it's always possible to just restore from a backup but the more interesting question is if something can be done with the data at hand. Basically, I'm trying to understand how it's possible that a dbcheck shows no errors, an ldbsearch is successful, and yet it's not possible to start the AD properly. What else is there that

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

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: > secrets.ldb and secrets.tdb. I assume you don't demote the DC before

I've samba 3.0.2 joined to a NT 4.0 domain as a domain member server. # net rpc join -U -UAdministrator%password Windows clients access it using winbind. If I upgrade all NT 4.0 servers to W2K3 AD, # net ads join -U Administrator%password do I need to rejoin the samba servers to AD? Will winbind continue to work? I think W2K3 by default uses kerberos. Will all uid.gid mapping be lost?

Somehow my workstations lost their connection to the domain recently. I can rejoin them, but when I leave the domain and rejoin the previous user profiles are lost. Well, the data is still on the system, but all pre-rejoin domain profiles are listed as "account unknown" in the profile manager. I know I can probably use the Files and Settings Transfer Wizard on the XP machines as long

Hi Everybody, Here in my company we have migrated from nt4 to Debian Sarge with Samba 3.0.14a + OpenLdap 2.2.23 + db4. Well, it's working fine except for one problem. When I have to get back to a backup copy on my ldap slaves on my BDCs some, or sometimes all, Windows XP machines need to be rejoined to the domain. I manage a workaround stopping Samba every time I need to reset the ldap

You might need to do a meta data cleanup before rejoining the DC: https://support.microsoft.com/en-us/kb/216498 Regards Davor Vusir -- Skickat fr?n mobilusken! -- ----- Ursprungligt meddelande ----- Fr?n: "Karl Heinz Wichmann" <wichmann-karl at web.de> Skickat: ?2015-?07-?02 20:16 Till: "samba at lists.samba.org" <samba at lists.samba.org> ?mne: [Samba] Rejoin

We recently replaced a failing PDC, and it seems to be working just fine: # net rpc testjoin Join to 'OURDOMAIN' is OK # net lookup dc OURDOMAIN 172.16.1.40 But the BDC now seems to be having problems. We cannot get new workstations (in the subnet with the BDC) to join the domain, and while logged into the BDC, we get: # net rpc testjoin Unable to find a suitable server Join to