Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

Skip to main content

My Subscriptions

Loading

Knowledge Base

Timekeeping best practices for Windows, including NTP (1318)

Last Updated: 8/5/2020Categories: Best PracticesTotal Views: 539093Language:
Chinese (Simplified)JapaneseSpanishEnglish

51 like this article

Subscribe to get an email
newsletter with new updates

51 people found this helpful Please provide article feedback:

Details

This article provides best practices for achieving accurate timekeeping in Windows guest operating systems. These recommendations include a suggested configuration for time synchronization in the guest and on the host.

Solution

For achieving accurate timekeeping in Windows guest operating systems, there are two main issues to consider: correctly configuring time synchronization and avoiding excessive CPU and memory overcommitment. Time synchronization utilities are necessary to correct time drift introduced by hardware time drift and guest operating system timekeeping imprecision. Excessive overcommitment can cause timekeeping drift at rates that are uncorrectable by time synchronization utilities. This best practices document covers time synchronization recommendations.

Time Synchronization

Use either w32time or NTP as the primary time synchronization utility.

Note: w32time is the time synchronization utility that ships with Windows. NTP (the Network Time Protocol daemon) is available for Windows through a variety of third-party ports to Windows.

Configuring w32time

When using w32time, there are a number of configuration parameters that can be changed. The table below describes the relevant parameters and gives a recommended value. All of the parameters are stored in the registry. Some of them can also be modified through the w32tm utility instead of directly editing the registry. This best practices guide covers running w32time in NTP mode. w32time can also use the windows domain hierarchy as time servers, which is not covered in this best practices guide.

After changing w32time's settings it is necessary to restart w32time. Either reboot the virtual machine, run net stop w32time && net start w32time from the command line, or stop and start the w32time service. After restarting the w32time service, run the command w32tm /resync to force w32time to resync the time.

Key

Details

HKEY_LOCAL_MACHINE\

SYSTEM\CurrentControlSet\

Services\W32Time\

TimeProviders\NtpClient\

SpecialPollInterval

Recommended Value: 900

Type: REG_DWORD

Description: This parameter controls how often w32time will poll the time server to check whether time on the client needs to be corrected. The parameter is specified as number of seconds to wait between polling. The recommended value of 900 specifies that the time server should be polled once every 15 minutes.

HKEY_LOCAL_MACHINE\

SYSTEM\CurrentControlSet\

Services\W32Time\Parameters\

NtpServer

Recommended Value:

pool.ntp.org,0x1

pool.ntp.org,0x1

pool.ntp.org,0x1

Type: REG_SZ

Description: This parameter specifies the time servers to use. It is specified as a string of space separated servers. Specifying ",0x1" after the server name indicates that the server should be contacted at the frequency specified by the SpecialPollInterval setting.

Note: Modify the recommended value to point to the ntp servers available in your environment.

w32tm Command:

w32tm /config "/manualpeerlist:

pool.ntp.org,0x1

pool.ntp.org,0x1

pool.ntp.org,0x1"

Note: Modify the command to use the ntp servers available in your environment.

HKEY_LOCAL_MACHINE\

SYSTEM\CurrentControlSet\

Services\W32Time\Parameters\

Type

Recommended Value: NTP

Type: REG_SZ

Description: This parameter specifies the mode that w32time should use. A value of NT5DS indicates that w32time should use the Windows domain hierarchy as its time servers rather than the NTP servers specified in the NtpServer key.

w32tm Command:

w32tm /config /syncfromflags:

MANUAL

VMware Tools Time Synchronization and Configuration

When using w32time or NTP in the guest, disable VMware Tools periodic time synchronization.

To disable VMware Tools periodic time sync, use one of these options:

Set tools.syncTime = "0" in the configuration file ( .vmx file) of the virtual machine.

or

Deselect Time synchronization between the virtual machine and the host operating system in the VMware Tools toolbox GUI of the guest operating system.

or

Run the VMwareService.exe -cmd "vmx.set_option synctime 1 0" command in the guest operating system. VMwareService.exe is typically installed in C:\Program Files\VMware\VMware Tools.

or

Run the vmtoolsd.exe timesync {enable|disable} command from the guest operating system and located at c:\Program Files\VMware\VMware Tools\vmtoolsd.

These options do not disable one-time synchronizations done by VMware Tools for events such as tools startup, taking a snapshot, resuming from a snapshot, resuming from suspend, or vMotion. These events synchronize time in the guest operating system with time in the host operating system even if VMware Tools periodic time sync is disabled, so it is important to ensure that the host operating system's time is correct. For more information about ESX 4/ESXi 4 or Workstation 7, see Timekeeping in VMware Virtual Machines. For vSphere 5, Workstation 8 or Fusion 4, see http://www.vmware.com/vmtn/resources/238.

To ensure the host operating system’s time is correct for VMware ACE, VMware Fusion, VMware GSX Server, VMware Player, VMware Server, and VMware Workstation run time synchronization software such as NTP or w32time in the host. For VMware ESX, run NTP in the service console. For VMware ESXi, run NTP on the VMkernel.

Necessary Patches

Time runs too fast in a Windows virtual machine when the Multimedia Timer interface is used (1005953) describes a known issue that may cause problems when running Windows in a virtual machine. This issue is addressed in recent VMware products. The table below specifies the actions required to ensure that you are using a product version that contains the fix:

Product

Action

ESX 3.5 and later

No action required

ESX 3.0.3

Ensure patch ESX303-200910401-BG is applied

ESX 3.0.2

Ensure patch ESX-1002087 is applied

ESX 3.0.1

Ensure patch ESX-1002082 is applied

ESX 3.0.0

Ensure patch ESX-1002081 is applied

ESX 2.5.x and earlier

Upgrade to ESX 3.0.0 or later

Fusion 2.0 and later

No action required

Fusion 1.x

Upgrade to Fusion 2.0 or later

Player 2.0 and later

No action required

Player 1.x

Upgrade to Player 2.0 or later

Workstation 6.0 and later

No action required

Workstation 5.x

Upgrade to Workstation 6.0 or later

Additional Information

Note :

If the windows virtual machine is not on the domain, run this command to ensure that the Windows and the Domain Controller time are in sync after a reboot:

sc triggerinfo w32time start/networkon stop/networkoff

Using Windows Group Policy to set the NTP settings for the virtual machines decreases the administration required for time synchronization.

For information regarding setting up an NTP server on an ESX host, see Guide to configure NTP on ESX servers(1003063).

For more information on configuring an authoritative time server in Windows, see Microsoft Knowledge Base article 816042.

Note: The preceding links were available as of October 11, 2018. If you find the links to be broken, provide feedback on the article and a VMware employee will update the article as necessary.

For information on Linux systems, see Timekeeping best practices for Linux guests (1006427).

Related Information

For translated versions of this article, see:

Spanish: Mejores prácticas de cronometraje para Windows, incluso NTP (2016707)

日本語: Windows の時刻管理のベスト プラクティス（NTP 含む） (1034484)

简体中文: Windows 的计时最佳实践，包括 NTP (2040909)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseSpanishEnglish

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Workstation

VMware vSphere ESXi

VMware Server

VMware Fusion

VMware ESX Server

VMware ACE

Related Versions:

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant