On Tue, 26 Nov 2024 14:31:15 +0100
Arnaud FLORENT via samba <samba at lists.samba.org> wrote:
>
> Le 26/11/2024 ? 14:07, Arnaud FLORENT a ?crit?:
> >
> > Le 26/11/2024 ? 13:31, Rowland Penny via samba a ?crit?:
> >> On Tue, 26 Nov 2024 12:46:54 +0100
> >> Arnaud FLORENT via samba<samba at lists.samba.org> wrote:
> >>
> >>> windows reports it can not find domain....
> >>>
> >>> i try to reproduce this and provide technical details...
> >>>
> >> I suppose the questions have to be:
> >>
> >> If you created a new test Samba AD domain and pointed your Windows
> >> 11 24H2 client at it, would it find that domain.
> >>
> >> Is any else using Windows 24H2 with a Samba domain that wasn't
> >> classic upgraded ?
> >
> > no problem joining directly a samba AD domain...
> >
> >
> > after classic upgrade dns seems broken on windows 24H2
> >
> > primary dns suffix points to netbios domain not AD realm...
> >
> >
> > no dNSHostName nor servicePrincipalName nor operatingSystem in
> > computer LDAP entry
> >
>
> problems are only on windows 11 computers that were joined to OLD NT
> domain and upgraded to windows 24H2 and unfortunately even after
> domain classic upgrade.
>
> rejoining to dns domain name fixes everything
>
> > --
> > Arnaud FLORENT
> > IRIS Technologies
>
I have had a quick look at the classic upgrade code and as far as I can
see there should be no real difference between an upgrade NT4-style
domain and a new AD domain. The first part of the script gets the
information to use and then uses that to provision the AD domain using
the same code that provisions a new domain. It looks like this is a
Windows bug, so unless the difference (if there is one) can be
identified between an upgraded domain and a new one, then Samba cannot
fix this.
Rowland