This is generally performed on DCs in an Active Directory domain. Then all workstations use AD to get time from the DCs. This could also be used on a non-DC windows machine to be your NTP server for your network that you point to for all of your switches/routers and various other devices.

First, open PowerShell and stop the Windows Time Service:

> net stop w32time

then set the used NTP servers using

> w32tm /config /syncfromflags:manual /manualpeerlist:"0.us.pool.ntp.org,1.us.pool.ntp.org,2.us.pool.ntp.org,3.us.pool.ntp.org"

(get the best servers for your region from https://www.ntppool.org)

mark the servers as reliable with

> w32tm /config /reliable:yes

and last, start the service again.

> net start w32time

You can check the configuration by using following commands:

> w32tm /query /configuration
> w32tm /query /status

The installation and/or removal of GPO pushed software can sometimes fail with error %%1274. This behavior can occur if the network has not started up or is starting up too slow for the machine boot process. Apply/enable following GPO to the failing computer:

Computer Configuration -> Policies -> Administrative Templates -> System -> Logon -> Always wait for the network at computer startup and logon

Computer Configuration -> Policies -> Administrative Templates -> System -> Group Policy -> Startup policy processing wait time

This should solve the problem. You need to try out which processing wait time works. some people reported that 30 seconds is enough, others 120 seconds.

If not, have a look at https://serverfault.com/questions/44257/group-policy-installation-failed-error-1274