search for: profwiz

...years. On th DC I've tried both chrony and ntp-4.2.8. In the ntp case I used the same 4.8.2 version on the old DC; in both cases built with --enable-ntp-signd. One possible issue was that these Windows domain members were unjoined from the 4.8.2 domain, rejoined to the new 4.18.9, and had Profwiz.exe run on each member to migrate the domain user's profile. None of that was done when they were first joined to the old 4.8.2 domain. One participant in this thread suggested I try joining a "virgin" Windows computer. I did that today with a scratch install of Windows 10. After...

...C I've tried both chrony and ntp-4.2.8. In the ntp case I used the same > 4.8.2 version on the old DC; in both cases built with --enable-ntp-signd. > > One possible issue was that these Windows domain members were unjoined from the > 4.8.2 domain, rejoined to the new 4.18.9, and had Profwiz.exe run on each member > to migrate the domain user's profile. None of that was done when they were > first joined to the old 4.8.2 domain. One participant in this thread suggested > I try joining a "virgin" Windows computer. I did that today with a scratch > install of Wi...

...h chrony and ntp-4.2.8. In the ntp case I used the same > > 4.8.2 version on the old DC; in both cases built with --enable-ntp-signd. > > > > One possible issue was that these Windows domain members were unjoined from the > > 4.8.2 domain, rejoined to the new 4.18.9, and had Profwiz.exe run on each member > > to migrate the domain user's profile. None of that was done when they were > > first joined to the old 4.8.2 domain. One participant in this thread suggested > > I try joining a "virgin" Windows computer. I did that today with a scratch &gt...

...ntp-4.2.8. In the ntp case I used the same >>> 4.8.2 version on the old DC; in both cases built with --enable-ntp-signd. >>> >>> One possible issue was that these Windows domain members were unjoined from the >>> 4.8.2 domain, rejoined to the new 4.18.9, and had Profwiz.exe run on each member >>> to migrate the domain user's profile. None of that was done when they were >>> first joined to the old 4.8.2 domain. One participant in this thread suggested >>> I try joining a "virgin" Windows computer. I did that today with a sc...

I've added a Windows 10 domain member to my Domain. I'm now following the procedure in https://wiki.samba.org/index.php/Time_Synchronisation#Configuring_Time_Synchronisation_on_a_Windows_Domain_Member. I've created the Group Policy for the "Time Sources". This doesn't seem to be working. This did work fine with my old 4.8.2 DC, so I know it works in principle. I have