How the time flies. With over 2 years since the last post, it is high time we get this blog moving again. Looking at the traffic statistics, there were nearly 50k views of the NET TIME and w32time post , so it is evident that folks are still interested...

It seems there is a bit of ambiguity out there regarding the relationship between w32time and the NET TIME command. Well, here are the answers, straight from the horse's mouth. Taking it from the top As all of you know (or at least should ) know...

The settings for the Windows Time Service exposed through group policy have long been seen as a bit mysterious, and for good reason. Well, today we will take the first steps towards remedying that problem. After spending a good amount of time with one...

Brian Singleton has posted on article on configuring w32time via Group Policy using WMI on the AskDS Blog. You can check it out here: http://blogs.technet.com/askds/archive/2008/11/13/configuring-an-authoritative-time-server-with-group-policy-using-wmi...

For those out there who haven't yet heard, VMWare is experiencing a problem (as of Aug 12) with licensing for ESX and ESXi. You can find out more here: http://kb2.vmware.com/kb/1006716.html The crux of the issue seems to be that a recent update caused...

More than any other, the most often asked question of the Windows Time Service is "How do I configure w32time for high accuracy?" Bob Drake has taken the time to answer this question over at the Ask the Directory Services Team blog. You can read his post...

Of the many things that w32time does, figuring out which host to sync from is one of the most important, and thus, one of the most talked about. In the stand-alone scenario, peer discovery (aka figuring out which host to sync with) is an entirely manual...

Recently, I had a customer ask if they can use w32time as a time source for other computer & devices on their network. The Windows Time Service is fully capable of acting as a time source for anything that is NTPv3 compliant. Before we start firing...

In the last few months of the Windows Server 2008 development, a good friend of mine was discussing a problem they have been seeing with customers. The problem, lovingly titled as the "Large Time Jump" issue involves a machine in the domain (usually the...

The debug log is a powerful tool in the W32Time bag of tricks when you need to figure out why something isn't working. The debug log tell you (for better or worse) what the Time Service is doing under the hood. Where it is connecting to, how long it is...

One of the most talked about configuration options for W32Time has to be the list of time sources that W32Time connects to for synchronization. It is important to note that W32Time will only actively synchronize with one time source at a time, even though...

In the very first post, I tried (for better or worse) to summarize the purpose of the Windows Time Service. The goal for this service is to keep the clock in sync with whatever time source the user prescribes. In this post, I will take a more abstract...

Windows Time Service on a domain (referred to as 'Domain Synchronization' or 'Domain Sync' for short) is a huge topic. I will do my best to cover all of its aspects in this article, but some concepts won't be covered until a later date, and others still...

It sounds a bit egotistical, but in fact, it is quite correct. I was recently reading an interesting article on the Discover Magazine website. If you have the time on your hands, I would recommend reading the original article (linked at the bottom). Here...

Welcome to the Windows Time Service blog. This blog is here to answer some of the questions about the service and show off some of the useful features that it has. Every week, I will try to cover a new topic surrounding Windows Time Service (w32time for...