Microsoft Windows is the most widely used desktop operating system in the world. For many of us, supporting it is how we make our living.One of the endearing and annoying features of this ubiquitous OS is the monthly patch update process. It just kind of works in the background when you're not looking. I'll install the updates on a non-critical server during the week to test them. But for the workstations it does a pretty good job - most of the time.Version 3.14 - Current Stable Version: Previous versions as well as the source code can be downloaded from the Source Forge project page Note: When upgrading from a previous version, you will need to shut down both the Net Time Service as well as the Tray Icon before running the installer.If you uninstall the old version first, you will need to restart your computer before starting the new installer.
In our company we run WSUS - Windows Server Update Services - to keep all our Windows desktops updated. I have trained my users over the years to ALWAYS leave their computers on to accommodate the patch process, the weekly AV scans and so that I can get into their workstations any time I need to work on them in the evening. Microsoft likes WSUS because it cuts down on the number of users hitting the Windows Update site. Microsoft has been slowly moving everyone over to Microsoft Update instead of Windows Update.So I do a Remote Desktop session to the machine in question and run the process manually. I used to spend hours looking up ways to get around these errors. This process of switching from the newer method to the older one and then back again seems to fix a host of registry errors and other wastes of time.I know something is really messed up when I get a 0x8024001D error or some other stupid hex number. At one time I liked Scott Hanselman's method of renaming the c:\windows\Software Distribution\Download to c:\windows\Software Distribution\ Click on "Disable Microsoft Update software and let me use Windows Update only" and then click on "Apply changes now." After the silly thing asks if you are sure (duh! It is simple and fast and has almost always worked for me.My way of configuring wasn’t easy, so I created the troubleshooting section that gives solutions to common problems (I had one of those).In the very end, I created section within the forest, set only PDC Emulator in the root of the forest to synchronize with an external time source.In my case, every workstation synchronizes with corresponding domain controller, and domain controllers synchronize with the server, in the root of the forest, with the PDC Emulator role enabled.You can create your configuration via: [Configuration] Event Log Flags: 2 (Local) Announce Flags: 5 (Local) Time Jump Audit Offset: 28800 (Local) Min Poll Interval: 6 (Local) Max Poll Interval: 10 (Local) Max Neg Phase Correction: 172800 (Local) Max Pos Phase Correction: 172800 (Local) Max Allowed Phase Offset: 300 (Local) Frequency Correct Rate: 4 (Local) Poll Adjust Factor: 5 (Local) Large Phase Offset: 50000000 (Local) Spike Watch Period: 900 (Local) Local Clock Dispersion: 10 (Local) Hold Period: 5 (Local) Phase Correct Rate: 7 (Local) Update Interval: 100 (Local) [Time Providers] Ntp Client (Local) Dll Name: C:\Windows\system32\w32(Local) Enabled: 1 (Local) Input Provider: 1 (Local) Allow Nonstandard Mode Combinations: 1 (Local) Resolve Peer Backoff Minutes: 15 (Local) Resolve Peer Backoff Max Times: 7 (Local) Compatibility Flags: 2147483648 (Local) Event Log Flags: 1 (Local) Large Sample Skew: 3 (Local) Special Poll Interval: 3600 (Local) Type: NTP (Local) Ntp Server: 192.168.x.x,0x8 (Local) See  if you want all these parameters and relevant reg keys explained in depth.It is free for personal use but commercial users will require to purchase a license at each.What we like about Dimension 4 is it comes with a huge list of time servers, able to load the program at Windows startup through services, run a time sync once and then automatically exiting the program.When the battery runs out, you will start seeing error messages such as “System CMOS checksum bad – Default configuration used” when starting up the computer and the date and time getting reset back to the default BIOS manufacturer date.You can still start up the computer by pressing a button to resume the boot process and Windows will load as normal.