samba - Jul 2018 - Post classicupgrade Windows registry changes?

All,

I am getting ready to tackle a classicupgrade. Test runs have gone well. I
am just wondering about the Windows client machines after the upgrade.

Do I need to remove the previously applied registry changes:
DomainCompatibilityMode
DNSNameResolutionRequired

Do I need to dis-join, and re-join the clients?

Current setup is:
Single Server: Samba NT4/PDC
LDAPsam

New setup is:
Single Server: Samba AD/DC
internal dns

Thanks,
coop

On Tue, 31 Jul 2018 06:16:47 -0400
cooper via samba <samba at lists.samba.org> wrote:
> All,
> 
> I am getting ready to tackle a classicupgrade. Test runs have gone
> well. I am just wondering about the Windows client machines after the
> upgrade.
> 
> Do I need to remove the previously applied registry changes:
> DomainCompatibilityMode
> DNSNameResolutionRequired
Yes
> 
> Do I need to dis-join, and re-join the clients?
No, but you will need to reboot the clients

Rowland

Great. Thanks, Rowland!

On Tue, Jul 31, 2018 at 6:48 AM, Rowland Penny via samba <
samba at lists.samba.org> wrote:
> On Tue, 31 Jul 2018 06:16:47 -0400
> cooper via samba <samba at lists.samba.org> wrote:
>
> > All,
> >
> > I am getting ready to tackle a classicupgrade. Test runs have gone
> > well. I am just wondering about the Windows client machines after the
> > upgrade.
> >
> > Do I need to remove the previously applied registry changes:
> > DomainCompatibilityMode
> > DNSNameResolutionRequired
>
> Yes
>
> >
> > Do I need to dis-join, and re-join the clients?
>
> No, but you will need to reboot the clients
>
> Rowland
>
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
>

Hi Rowland,

On Tue, 31 Jul 2018 11:48:06 +0100
Rowland Penny via samba <samba at lists.samba.org> wrote:
> > I am getting ready to tackle a classicupgrade. Test runs have gone
> > well. I am just wondering about the Windows client machines after the
> > upgrade.
> > 
> > Do I need to remove the previously applied registry changes:
> > DomainCompatibilityMode
> > DNSNameResolutionRequired  
> 
> Yes
Well, I didn't removed this registry settings, and it worked so far.
After the Migration we had to re-join half a dozen Windows 10 clients,
but that's about it.

Are we just lucky and may be there any side effects we may suffer later?

Kind Regards,
Henry