Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I ask as I have become part of a network where they have w32 time disabled on machines, and use Domain Time II. Product info here:

Just curious if anyone else has experience. My question is really is it justifiable to have on your network, and has anyone used it that can say if it truly has helped or hindered the forest?


locked by HopelessN00b Jan 21 '15 at 19:51

This question exists because it has historical significance, but it is not considered a good, on-topic question for this site, so please do not use it as evidence that you can ask similar questions here. This question and its answers are frozen and cannot be changed. More info: help center.

closed as primarily opinion-based by HopelessN00b Jan 21 '15 at 19:51

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise.If this question can be reworded to fit the rules in the help center, please edit the question.

The question started because with w32 time service is actually disabled through a GPO by previous admins. Their are products that fail to start when a server restarted due to w32 time being disabled and has to be done manually. The company has left doing it this way for a few years. – mangloide Apr 12 '11 at 12:54
up vote 3 down vote accepted

What products fail due to w32tm being disabled?

Time synchronization is critical for Kerberos authentication, but the use of the built in Windows Time service isn't required as far as I know. The use of third party products to manage the domain/network time isn't discouraged if time accuracy outside of the capabilities of the Windows Time service is needed.


Accurate time keeping is important on any larger network. Fx Active Directory needs accurate time for logins to work properly. But "Domain Time II" isn't the only way to accomplish this.

In a modern Active Directory environment, there is basic but working time synchronization already built in.

For non-Windows devices (switches, routers, appliances) you can use the NTP protocol. You can leverage your existing investment in "Domain Time II" by using it as an NTP server for your non-Windows devices, or you could set up a Linux/BSD server with NTPd.

Be sure to set the clock of your root time server from a trusted source. The common solution there would be 3 or 5 upstream NTP servers from .

The built-in Active Directory time sync isn't that accurate -- generally it syncs better than +/- 1 second, and often a few hundred milliseconds. Domain Time II is probably more accurate than that. So it really comes down to how much precision you need, and which platform you're more comfortable with/know best.


Not the answer you're looking for? Browse other questions tagged or ask your own question.