samba - May 2022 - Migration 3.5 to 4.x, realm identical to domain

On Tue, 2022-05-31 at 10:00 +0200, Philippe Maladjian via samba
wrote:
> Hi there,
> 
> I am performing tests to migrate an old domain controller from Samba
> 3.5 + ldap + bind to Samba branch 4 to simulate an AD and I find
> myself
> facing a problem with the domain name.
> 
> The current domain name is DOM.MONDOMAIN and according to the docs
> that
> I read and test carried out, I cannot have an identical NDD and
> realm.
I take it that 'DOM.MONODOMAIN' is a very bad Netbios domain name (aka
workgroup), if so then you are going to have to change it. I would do
this before the upgrade. I suggest you read this:

https://wiki.samba.org/index.php/Migrating_a_Samba_NT4_Domain_to_Samba_AD_(Classic_Upgrade)

Rowland

In order to comply with the recommendations, I thought of renaming the
domain with my external domain (mondomaine.fr) and adding a prefix for
the AD domain.

Currently the Samba 3 domain is: dom.mondomain
TLD after migration: mondomaine.fr
Realm: nomrue205.mondomaine.fr
AD domain: nomrue205

Can I do this through a classic update?



Le mardi 31 mai 2022 ? 14:26 +0100, Rowland Penny via samba a
?crit?:
> On Tue, 2022-05-31 at 10:00 +0200, Philippe Maladjian via samba
> wrote:
> > Hi there,
> > 
> > I am performing tests to migrate an old domain controller from
> > Samba
> > 3.5 + ldap + bind to Samba branch 4 to simulate an AD and I find
> > myself
> > facing a problem with the domain name.
> > 
> > The current domain name is DOM.MONDOMAIN and according to the docs
> > that
> > I read and test carried out, I cannot have an identical NDD and
> > realm.
> 
> I take it that 'DOM.MONODOMAIN' is a very bad Netbios domain name
> (aka
> workgroup), if so then you are going to have to change it. I would do
> this before the upgrade. I suggest you read this:
> 
>
https://wiki.samba.org/index.php/Migrating_a_Samba_NT4_Domain_to_Samba_AD_(Classic_Upgrade)
> 
> Rowland
> 
> 
>