Skip to main content

os: time sync information

UPDATE: added some information regarding syncing to non-windows time sources.

i hate dealing with time synchronization. the tools for windows are so hokey. you know, little nuances like deprecating net time in favor of w32tm just doesn't get enough press. oh well. recently, i had to look through this stuff again. i decided i'd write up a little blog note as a reminder for myself the next time i have to look at this stuff. to start off with, very useful links.

how to turn on debug logging in the windows time service
how to configure an authoritative time server in windows server 2003
windows time server and internet communication
time synchronization may not succeed when you try to synchronize with a non-windows ntp server in windows server 2003

... and now, some very useful commands:

setting a time sync source:

w32tm /config /update / /syncfromflags:MANUAL

verifying the settings:

w32tm /dumpreg /subkey:parameters
... following the commands above, if you're syncing time successfully, and you've turned on time sync debug logging as specified in the first link above, a successful entry in the log will look like the entry snippet below...
148232 19:09:40.0266456s - /-- NTP Packet: 
148232 19:09:40.0266456s - | LeapIndicator: 0 - no warning; VersionNumber: 3; Mode: 4 - Server; LiVnMode: 0x1C 
148232 19:09:40.0266456s - | Stratum: 2 - secondary reference (syncd by (S)NTP) 
148232 19:09:40.0266456s - | Poll Interval: 7 - 128s; Precision: -6 - 15.625ms per tick 
148232 19:09:40.0266456s - | RootDelay: 0x0000.1BFEs - 0.109344s; RootDispersion: 0x0000.CC68s - 0.798462s 
148232 19:09:40.0266456s - | ReferenceClockIdentifier: 0xC02BF412 - source IP: 
148232 19:09:40.0266456s - | ReferenceTimestamp: 0xC8FA05E75E673B78
148232 19:09:40.0266456s - - 12807313511368762700ns - 
148232 19:05:11.3687627s 
148232 19:09:40.0266456s - | OriginateTimestamp: 0xC8FA06F406D23EFC
148232 19:09:40.0266456s - - 12807313780026645600ns - 
148232 19:09:40.0266456s 
148232 19:09:40.0266456s - | ReceiveTimestamp: 0xC8FA06F406986261
148232 19:09:40.0266456s - - 12807313780025762700ns - 
148232 19:09:40.0257627s 
148232 19:09:40.0266456s - | TransmitTimestamp: 0xC8FA06F406986261
148232 19:09:40.0266456s - - 12807313780025762700ns - 
148232 19:09:40.0257627s 
148232 19:09:40.0266456s - >-- Non-packet info: 
148232 19:09:40.0266456s - | DestinationTimestamp: 
148232 19:09:40.0266456s - 0xC8FA06F406D23EFC
148232 19:09:40.0266456s - - 12807313780026645600ns
148232 19:09:40.0266456s - - 
148232 19:09:40.0266456s 
148232 19:09:40.0266456s - | RoundtripDelay: 000ns (0s) 
148232 19:09:40.0266456s - | LocalClockOffset: -882900ns - 0:00.000882900s 
148232 19:09:40.0266456s - \--
w32tm /config /update /,0x8 /syncfromflags:MANUAL


Popular posts from this blog

how to retrieve your ip address with powershell...

update: this is how it’s performed in powershell v3 as demonstrated here.(get-netadapter | get-netipaddress | ? addressfamily -eq'IPv4').ipaddress update: this is by far the easiest.PS C:\temp> (gwmi Win32_NetworkAdapterConfiguration | ? { $_.IPAddress -ne $null }).ipaddress
are you laughing yet?  i know you probably find this topic amusing.  it's really interesting though.  whenever you get over it, i'll do this in the standard cmd.exe interpreter and then in powershell to show you what kind of coolness powershell does.done?  okay, good.  this is an interpretation of a demo that bob wells did at our smug meeting.  hope you like it.i should tell you, it's not as simple as the title would lead you to believe.  i like doing that little slight-of-hand thing since it gives the impression that i'm painting a very easy target on my back for your criticism (though it's probably true in other ways)!  the idea is that we want to retrieve just the ip ad…

understanding the “ad op master is inconsistent” alert

i use the term “understanding” loosely.  this is by far no definitive guide on this particular alert, just a few things i have picked up in my attempt to understand it.let’s look at the context of the alert:The Domain Controller's Op Master is inconsitent. See additional alerts for details.
first of all, it gives very little information.  the only particularly useful detail is that it indicates which server is having the issue.  other than that, just a spelling error as there are no additional critical alerts to look at for details.this rule, as you know, comes from a sealed mp.  therefore, we can’t modify anything in it except the overrides.  the couple i’ve tinkered with are:interval (sec) log success event to begin with, interval (sec) is just set way too high.  the default is 60 seconds.  why on earth would anyone want to know that your op master consistency may be off, every minute?  actually, i could think of a few reasons, but really, it’s overkill.  the way the script works…

sccm: content hash fails to match

back in 2008, I wrote up a little thing about how distribution manager fails to send a package to a distribution point. even though a lot of what I wrote that for was the failure of packages to get delivered to child sites, the result was pretty much the same. when the client tries to run the advertisement with an old package, the result was a failure because of content mismatch.I went through an ordeal recently capturing these exact kinds of failures and corrected quite a number of problems with these packages. the resulting blog post is my effort to capture how these problems were resolved. if nothing else, it's a basic checklist of things you can use.DETECTIONstatus messagestake a look at your status messages. this has to be the easiest way to determine where these problems exist. unfortunately, it requires that a client is already experiencing problems. there are client logs you can examine as well such as cas, but I wasn't even sure I was going to have enough material to …