Timedrift on Windows Server 2019 often stems from a failing CMOS battery, which causes the Real-Time Clock to reset when power is lost. Checking the voltage with a multimeter or BIOS diagnostics helps identify if the hardware component needs replacement to restore accurate system time.
Understanding the Link Between CMOS and Time Sync
The motherboard of your server relies on a small coin-cell battery, typically a CR2032, to maintain data in the CMOS memory when the main power supply is disconnected. This memory stores critical settings, including the system date and time. If this battery degrades, the clock resets to a default factory date whenever the server loses AC power. Consequently, Windows detects a significant discrepancy between its internal clock and network time sources, leading to authentication failures, Kerberos errors, and general access issues for domain-joined clients.
While software tools can adjust the time, they cannot fix the underlying hardware instability. If you suspect a timedrift issue that persists after rebooting or power cycling, the first step is to verify the health of the power source for the RTC (Real-Time Clock) circuit. This diagnostic approach separates software configuration errors from physical hardware failure.
Determining Voltage Levels Safely
To accurately assess the battery status, you must measure the voltage directly at the battery contacts. A fully charged lithium coin cell should read approximately 3.0 volts. As the battery ages, this voltage drops. Most manufacturers consider a battery depleted when it falls below 2.7 volts, though some systems may continue to function erratically even slightly above this threshold.
Important Safety Note: Before opening the server chassis, ensure you have followed proper electrostatic discharge (ESD) protocols. Disconnect all power cables from the rear I/O panel and wait for the capacitors to discharge. Do not attempt to measure voltage while the system is powered on, as this can damage the motherboard or create a short circuit.
If you do not have immediate access to a multimeter, many modern server motherboards include built-in self-test features. Access the BIOS/UEFI setup utility during boot. Look for a "System Health" or "Hardware Monitor" section. Some enterprise boards display the current battery voltage or a "CMOS Battery Low" warning flag here. If the BIOS reports a low battery or shows an incorrect date immediately after power loss, the hardware diagnosis is confirmed without needing manual voltage measurement.
Using a Multimeter for Precision
For definitive proof, use a digital multimeter set to DC voltage mode. Locate the CMOS battery socket on the motherboard. Gently lift the battery from its holder. Place the red probe on the positive (+) side of the battery and the black probe on the negative (-) side. Record the reading. If the value is significantly lower than 3.0V, particularly if it is near or below 2.5V, the battery is no longer capable of sustaining the RTC circuit reliably.
Replacing the CMOS Battery
Once you have confirmed low voltage, replacing the battery is a straightforward procedure. Ensure you purchase a high-quality CR2032 battery from a reputable supplier. Cheap, generic batteries often have higher internal resistance and shorter lifespans, which can lead to recurring timedrift issues.
- Power down the server completely and unplug the power cords.
- Open the chassis cover according to the manufacturer's service guide.
- Locate the round silver battery on the motherboard.
- Press the metal clip holding the battery to release it.
- Remove the old battery and insert the new one, ensuring the positive side faces up.
- Close the chassis and reconnect power.
After reassembly, enter the BIOS setup. Reset the date and time to the correct values. Save the changes and exit. Upon booting into Windows Server 2019, verify that the time remains stable. You may need to allow a few minutes for the Windows Time Service to synchronize with your configured NTP servers again.
Verifying the Fix
Post-replacement, monitor the server for at least 24 hours. Check the System Event Log for any further time-sync warnings. In Windows, you can run w32tm /query /status in an elevated command prompt to see the current synchronization state. If the offset is minimal and the source is listed as a reliable NTP server, the timedrift issue is resolved.
If the problem persists despite a new battery, investigate other potential causes such as network latency, incorrect NTP configuration, or motherboard chipset issues. However, in most cases where timedrift correlates with power cycles, the CMOS battery was the root cause.
Frequently Asked Questions
Can I just change the time in Windows instead of replacing the battery?
No, changing the time in Windows only masks the symptom. The underlying hardware issue will cause the clock to drift again or reset to a default date every time the server loses power. Permanent resolution requires fixing the hardware power source.
What happens if the CMOS battery dies completely?
When the voltage drops too low, the CMOS memory loses its contents. This resets BIOS settings to defaults and clears the system date/time. The server may fail to boot properly or display a "CMOS Checksum Error" message during startup.
Is it safe to remove the CMOS battery while the server is plugged in?
Absolutely not. Removing the battery while power is connected can cause electrical surges that damage the motherboard components. Always disconnect all power sources before handling internal hardware components like the CMOS battery.
How often should I replace the CMOS battery on a server?
Lithium coin cells typically last 3 to 5 years, depending on operating temperature and usage. For critical servers, it is good practice to replace them proactively during scheduled maintenance windows to prevent unexpected downtime due to timedrift.
Will replacing the CMOS battery affect my Windows installation?
No, the CMOS battery only powers the real-time clock and BIOS settings. It does not store user data, operating system files, or application configurations. Your Windows Server 2019 installation and data remain completely intact.