samba - Jan 2024 - Joining Windows 10 Domain Member to Samba AD/DC

On Fri, Jan 5, 2024 at 2:32?PM Mark Foley via samba
<samba at lists.samba.org> wrote:
> <snip> I would think the wikis would mention the GPO not being
> needed.
Did you see the section titles "Default Time Source" in the page you
link to that I quoted previously? The wiki clearly spells it out that
using a GPO is usually unnecessary.
> How do you know you're syncing with the DC?
'w32tm /query /status' will show you.
> What does your 'w32tm /query /source' give you?
My Windows domain members point to the DC.

Chris

You think ntp works with samba but it doesn?t.

You *must* use chrony. It will take you exactly 5 minutes to get it up and
running.
On 5 Jan 2024 at 20:21 +0000, Mark Foley <mfoley at novatec-inc.com>,
wrote:
>
>
>
> How do you know you're syncing with the DC? What does your 'w32tm
/query /source'
> give you?
It?s all here :

http://samba.bigbird.es/doku.php?id=samba:install-chrony

On Fri Jan  5 15:20:54 2024 Sonic <sonicsmith at gmail.com>
wrote:
>
> On Fri, Jan 5, 2024 at 2:32?PM Mark Foley via samba
> <samba at lists.samba.org> wrote:
> > <snip> I would think the wikis would mention the GPO not being
> > needed.
> Did you see the section titles "Default Time Source" in the page
you
> link to that I quoted previously? The wiki clearly spells it out that
> using a GPO is usually unnecessary.
>
> > How do you know you're syncing with the DC?
> 'w32tm /query /status' will show you.
>
> > What does your 'w32tm /query /source' give you?
> My Windows domain members point to the DC.
>
> Chris
>
That section says, "you *usually* do not need to reconfigure the
clients."
However, my 'w32tm /query /source' returned time.windows.com, not
dc1.hprs.locl,
so I figured that I must be one of those that did need the "alternative
configuration".

Also, as I mentioned, I did do this with this same Windows member on my Samba
4.8.2 DC, and that works fine.

Possibly since this Windows domain member already had the 'w32tm /config
/manualpeerlist" set from its original join to the old DC, that may have
messed
something up and might explain why I got back time.windows.com right away after
re-joining to the new domain, before doing any GPO.

So, any idea how I can get this straighted out? Should I delete the GPO? Is
there a w32tm command to reset back to "default"?

Thanks --Mark