Time service on server

Question

i am having an error from a Azure AD server that is hosted on a VM ware Host and the server is connected also on a NTP server on the same network and physical host, what might could be the problem?

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.

Answer 1

Hello

The error message indicates that the Azure AD server is experiencing time synchronization issues, which could be due to network conditions or synchronization with a low-precision time source. You can try some of the following steps to troubleshoot:

NTP Configuration: Ensure that your NTP server is correctly configured and that the Azure AD server is pointing to the correct NTP server. Misconfigurations can lead to time discrepancies.

Network Latency: Suboptimal network conditions can cause delays in time synchronization. Check your network for any latency issues that might be affecting the time sync process.

VMware Host Settings: Sometimes, the settings on the VMware host can interfere with time synchronization. Ensure that the VMware tools are installed and configured correctly on your VM. VMware has specific recommendations for time synchronization in virtual environments.

Time Service Settings: Verify the settings of the Windows Time service on your Azure AD server. You can use the w32tm command to check the status and configuration of the time service. For example:

w32tm /query /status

w32tm /query /configuration

Event Logs: Check the event logs on your Azure AD server for any additional errors or warnings related to time synchronization. This can provide more insight into what might be causing the issue.

Synchronization with Low-Accuracy Sources: Ensure that your server is not synchronizing with low-accuracy time sources. You can configure the time service to use more reliable sources.

If these steps don’t resolve the issue, you might need to delve deeper into the specific configurations of your network and virtual environment.

Answer 2

Hello,

Do you have any other questions?

If the above reply is helpful to you, please mark it as answer, thank you very much!

Thanks.