samba - Jun 2024 - Classicupgrade FL 2012_R2 NTLM/Kerberos logon

Mandi! Havany via samba
  In chel di` si favelave...
>> It sounds like you are still using the old, deprecated (by Windows)
>> roaming profiles, instead of Folder redirection.
?! Some more clue, Rowland? I use roaming profiles *AND* folder redirection,
usually... ;-)

> So, I think I will use the "classicupgrade" method. I will wait a
few
> days to make sure everything works well before making the final decision 
> and moving on to the next steps.
I think i'm late.

Con consider that if you have  the same user/login and password on both
domain (NT and AD), you can safely migrate machine (and users) from NT to AD
and keep user access the old server. You need only some attention, eg keep
enabled SMB1 in Ad to access the old server and have a WINS server active on
the network.

Windows (windows, not samba) infact (try to) use domainless user and current
password against other servr/domain, so if login and password match, access
is granted.


This can leave to you time sufficient to plan a smooth upgrade...

--

On Wed, 19 Jun 2024 19:16:51 +0200
Marco Gaiarin via samba <samba at lists.samba.org> wrote:
> Mandi! Havany via samba
>   In chel di` si favelave...
> 
> >> It sounds like you are still using the old, deprecated (by
Windows)
> >> roaming profiles, instead of Folder redirection.
> 
> ?! Some more clue, Rowland? I use roaming profiles *AND* folder
> redirection, usually... ;-)
It was just a comment, but from my understanding, you should use one or
the other, not both.
> 
> 
> > So, I think I will use the "classicupgrade" method. I will
wait a
> > few days to make sure everything works well before making the final
> > decision and moving on to the next steps.
> 
> I think i'm late.
> 
> Con consider that if you have  the same user/login and password on
> both domain (NT and AD), you can safely migrate machine (and users)
> from NT to AD and keep user access the old server. You need only some
> attention, eg keep enabled SMB1 in Ad to access the old server and
> have a WINS server active on the network.
From experience, once a client has seen and connected to AD, it will
never connect to an NT4-style domain again.

Rowland