Afw time on non-800xA node
is it possible to install/configure AFW Time service on the node which is not a part of 800xA System?
In 800xA sv. 6.0.3 there is an option in Node Preparation Tool to install "Generic node". Basicaly, it is used for Domain Controllers to install RNRP. It would be nice to install AFW Time as well, since I found Windows time protocol (SNTP) unreliable.
Voted best answer
Have you tried forcing quality to "Always Authorative" in the time server using the AnnounceFlags registry key?
I find the W32Time service quite "chatty" - perhaps you can see reason for problem in Windows Event (System) Log when filtering for Time-Service events?
ID24: Time Provider NtpClient: No valid response has been received from domain controller ... after 8 attempts to contact it.
ID35: The time service is now synchronizing the system time with the time source
ID36: The time service has not synchronized the system time for 86400 seconds because none of the time service providers provided a usable time stamp
ID37: The time provider NtpClient is currently receiving valid time data from ...
ID38: NtpClient succeeds in resolving domain peer ... after a previous failure.
ID50: The time service detected a time difference of greater than 5000 milliseconds for 900 seconds. The time difference might be caused by synchronization with low-accuracy time sources or by suboptimal network conditions. The time service is no longer synchronized and cannot provide the time to other clients or update the system clock. When a valid time stamp is received from a time service provider, the time service will correct itself.
ID129: NtpClient was unable to set a domain peer to use as a time source because of discovery error
ID131: NtpClient was unable to set a domain peer to use as a time source because of DNS resolution error
Enclosed is a procedure I have created in quite complicated arcitecture ( production 800xA system, workgroup with 800xA History and test 800xA system) divided by the firewall. Three system are now running and synchronizing without any problem for a year. But it gave me a headache during the setup.
Now I have smaller system (9 800xA servers, 4 non-800xA nodes) and the same prcedure does not work. When I check the settings using:
W32tm /query /status
I got only error messages. I think that is it because at this stage I do not have the controller and GPS clock connected, so windows time servise does not recognise Connectivity server as a reliable source, since its time is taken from BIOS time, not the GPS. Problem is that during the FAT it is quite common, that I do not have GPS connected and I cannot "trust" windows that it will start working on site.
My idea was to get rid of all this work a just simply install AFW time to non-800xA nodes the same way RNRP is installed.