Why break time?

Good afternoon. I have to work this problem, loses time on the client machines. There is a server there to spin AD, there is a GPO which is synchronized with an external NTP server. There is a second GPO policy which must synchronize with the client machines. All settings made on this article https://winitpro.ru/index.php/2017/01/06/nastrojka...
When prescribed cmd gpupdate /force time sync, then using some of that time again to go astray. You do not know already in what side to dig , can anyone faced with such a problem. Please help.
April 4th 20 at 13:16
2 answers
April 4th 20 at 13:18
In the domain GPO is not needed for time synchronization, as it is written on your link. Remove the GPO and configure the server.
On the server time correct on the client machines troubles. On 7 minutes late. - Corrine.Hudson commented on April 4th 20 at 13:21
@Corrine.Hudson, Clients in the domain can handle yourself, without GPO. - Isabella_Koch commented on April 4th 20 at 13:24
@Isabella_Koch, All the problem was solved. - Corrine.Hudson commented on April 4th 20 at 13:27
April 4th 20 at 13:20
In AD everything is invented and there are no additional policies.
PDC root domain\forest should synchronize with the source, and everything else is automatic on the chain reaches the workstations.
Except if the CD came off of the ADDS service, then it ceases to give time. - rollin.Luettg commented on April 4th 20 at 13:23
@rollin.Luettg, Too, thought so, derived from the domain and again drove but all exactly the same( - Corrine.Hudson commented on April 4th 20 at 13:26
@Corrine.Hudson, this is not enough, you should check whether all the services are running. It happens because of the Hilo iron they timed out at the start off. - rollin.Luettg commented on April 4th 20 at 13:29

Find more questions by tags Group policyWindows Server