# How to Discover and Resolve Server Time Mismatch using NTP Client?

Last updated: July 24, 2026

Server time mismatches can cause enrollment, profile distribution, or app deployment failures, so admins with server access, an NTP client, and outbound access to Google and Apple time servers can detect and fix drift. Running date shows the current server time, ntpdate -q against time.google.com or time.apple.com reveals the offset, and running ntpdate against either host synchronizes the server clock, resolving time-related certificate and communication errors.

Accurate server time is crucial for authentication, certificate validation, and communication between managed devices and servers. A mismatch in server time can cause failures in operations such as enrollment, profile distribution, or app deployment. To detect and correct such mismatches, the NTP (Network Time Protocol) client can be used to synchronise the system time with trusted external hosts. This document explains how admins can identify server time mismatches and synchronise with reliable time sources.

## Pre-requisites

1. Admin access to the server.
2. NTP client installed on the server.
3. Outbound access enabled to .google.com and .apple.com for time synchronisation.

## Steps to Discover and Sync Server Time

1. **Check Current Server Time**
   - Run the following command to display the current server time:

     ```bash
     date
     ```

   - Compare the displayed time with a reliable external time source (for example, time from a trusted NTP server or another reference device).

2. **Use NTP Client to Detect Time Mismatch**
   - Run the NTP query command to check for drift:

     ```bash
     ntpdate -q time.google.com
     ```

     or

     ```bash
     ntpdate -q time.apple.com
     ```

   - The output will display the offset (difference) between the server time and the external time source.

3. **Synchronize Server Time**: If a mismatch is detected:
   - Run the following command to synchronise with Google:

     ```bash
     ntpdate time.google.com
     ```

   - Alternatively, sync with Apple:

     ```bash
     ntpdate time.apple.com
     ```

## Hosts Used for Time Sync

The following external hosts are used for server time synchronisation:

1. **time.google.com**
2. **time.apple.com**

## Outcome

- Server time will be synchronised with reliable NTP sources.
- Issues caused by time drift (e.g., certificate validation failures or communication errors) will be minimised.

If the issue still persists, please contact our [MDM support team](https://www.manageengine.com/mobile-device-management/support.html).

## Frequently Asked Questions

### Why does server time matter for MDM operations?

Accurate server time is crucial for authentication, certificate validation, and communication between managed devices and servers - a mismatch can cause failures in operations such as enrollment, profile distribution, or app deployment.

### How do I check whether my server's time is out of sync?

Run the `date` command to see the current server time, then run `ntpdate -q time.google.com` or `ntpdate -q time.apple.com` to display the offset between the server time and the external time source.

### How do I fix a detected time mismatch?

Run `ntpdate time.google.com`, or `ntpdate time.apple.com` as an alternative, to synchronize the server clock with the trusted external time source.

### What should I do if time-related errors continue after synchronizing?

Contact the MDM support team if certificate validation failures or communication errors persist after synchronizing the server time.