Top of Page

Registry Settings  Registry Settings
Domain Time II Server
Version 5.2

Domain Time Server keeps its settings in the Windows Registry. Most of the service options are best set using the Domain Time Server Control Panel applet. However, some advanced options can only be set by changing the registry. This page explains many of these special registry entries used by Domain Time Server.

CAUTION:
Modifying Registry entries requires basic familiarity with the Windows Registry and its operations. Incorrect changes to the Registry can result in unpredictable, perhaps non-repairable, damage. We cannot be responsible for registry problems.

The Domain Time II Server settings are located in these keys (click the names to jump to details):

   HKEY_LOCAL_MACHINE
      Software
         Greyware
            Domain Time Server
               Enabled Protocols
               HTML
               Keyring
               Logs and Alerts
               Parameters
               Time Sources

 

Enabled Protocols
     
    The Domain Time II Server Enabled Protocols settings are located in this key:

       HKEY_LOCAL_MACHINE
          Software
             Greyware
                Domain Time Server
                   Enabled Protocols


    The values listed in the Enabled Protocols registry key represent the protocol types Domain Time will listen for. They correspond to checkboxes on the Serve the Time and Status Reports property pages of the Control Panel applet. You should not make manual changes to this key or its subkeys.

 

HTML
     
    The Domain Time II Server HTML settings are located in this key:

       HKEY_LOCAL_MACHINE
          Software
             Greyware
                Domain Time Server
                   HTML


    If you enable the Domain Time over HTTP protocol to be served by the Domain Time II Server, Domain Time will optionally provide both a human-readable stats web page (when the server is visited by a browser) and/or a compact time data packet (when the server is queried by a Domain Time Server or Client).

    You may add a custom header and footer to the human-readable web page. For example, everything on tick.greyware.com and tock.greyware.com outside the rectangular frame is either a custom header or footer.

    The custom header and footer are optional. Add them to the registry as follows (you will have to create the HTML registry key and Header and Footer values manually):

Value Name:
 
Value Type:
 
Default Data:
 
Notes:
Header
 
REG_MULTI_SZ
 
(blank)
 
Any HTML you want to appear above the time display

This key and value do not exist unless you create them. Whatever HTML you place in the Header and Footer values will appear on the web page along with the standard logo and status report. If you include a <body...> statement in the Header value, Domain Time will use your <body...> tag instead of its own.

Value Name:
 
Value Type:
 
Default Data:
 
Notes:
Footer
 
REG_MULTI_SZ
 
(blank)
 
Any HTML you want to appear below the time display

This key and value do not exist unless you create them.

Value Name:
 
Value Type:
 
Default Data:
 
Options:
 
Notes:
Display Network Info
 
REG_SZ
 
True
 
True or False
 
Controls whether or not network information such as IP addresses and the server name are displayed on the web page.

This key and value do not exist unless you create them.

Value Name:
 
Value Type:
 
Default Data:
 
Notes:
robots.txt
 
REG_MULTI_SZ
 
(see Notes below)
 
This sets the contents of the robots.txt file provided by the HTML server.

Use this value to control whether search engines should index your time server's web page.

Default contents:

    User-agent: *
    Disallow /
    Disallow *
Value Name:
 
Value Type:
 
Default Data:
 
Notes:
style.css
 
REG_MULTI_SZ
 
(see Notes below)
 
This value contains the CSS code used to style the HTML status web page.

Default contents:

    body {background:#e0ddd0; margin:15px 0px}
    table.main {background-color:#ffe; border-collapse:collapse; border:solid #000 0px; width:95%; margin:0px; margin-left:auto; margin-right:auto;}
    table.main td {padding:0px 1%; line-height:130%;}
    .maintop {font: bold small sans-serif; text-align:left; color:#fff; background-color:#18204f; height:40px;}
    .mainleft {font:x-small sans-serif; text-align:center; vertical-align:top; background-color:#ffe;}
    .mainright {font:x-small sans-serif; text-align:center; color:black; vertical-align:middle; background-color:#ececee;}
    .mainbottom {font:bold x-small sans-serif; text-align:right; background-color:#18204f; height:40px;}
    table.left {background-color:#ffe; width:100%;}
    table.right {background-color:#ececee; width:100%;}
    .l {text-align:right;}
    .r {text-align:left;}
    .refresh {display:block; float:right; margin:0 5px 0 0; background-color:#18204f; cursor:pointer; padding:5px 1%; border-top:1px solid #999; border-left:1px solid #888; border-right:1px solid #444; border-bottom:1px solid #666; line-height:120%; text-decoration:none; color:#ccc;}
    a:hover {background-color:#456; color:#ffe;}
    hr {border:0; color:#000; background-color:#999; height:1px; width:70%; text-align:center; vertical-align:top;}

 

Keyring
     
    The Domain Time II Server Keyring settings are located in this key:

       HKEY_LOCAL_MACHINE
          Software
             Greyware
                Domain Time Server
                   Keyring


    The values listed in the Keyring registry key contain various items related to authentication. They correspond to settings on the Symmetric Keys property page of the Control Panel applet. You should not make manual changes to this key or its subkeys.

 

Logs and Alerts
     
    The Domain Time II Server Logs and Alerts settings are located in this key:

       HKEY_LOCAL_MACHINE
          Software
             Greyware
                Domain Time Server
                   Logs and Alerts


    The values listed in the Logs and Alerts registry key contain various items related to logging and alerting functions. They correspond to settings on the Logs, Windows Event Viewer, Syslog, SNMP, and Status Reports property pages of the Control Panel applet. You should not make manual changes to this key or its subkeys.

 

Parameters
     
    The Domain Time II Server Parameter settings are located in this key:

       HKEY_LOCAL_MACHINE
          Software
             Greyware
                Domain Time Server
                   Parameters


    The values listed in the Parameters registry key control a wide variety of Domain Time functions. In most cases, they are auto-generated or correspond to settings on the property pages of the Control Panel applet. In general, you will not need to make manual changes to this key or its subkeys.

    However, some values require additional explanation or control functions not exposed on the Control Panel. Those items are listed here.

Value Name:
 
Value Type:
 
Default Data:
 
Options:
 
Notes:
Allow Browser-based HTTP requests
 
REG_SZ
 
True
 
True or False
 
Controls whether or not this Server will allow browsers to contact the server's built-in web server to view the running server statistics.

The Domain Time II over HTTP protocol must also be enabled on the Serve the Time property page of the Control Panel applet.

Value Name:
 
Value Type:
 
Default Data:
 
Options:
 
Notes:
Allow Client-based HTTP requests
 
REG_SZ
 
True
 
True or False
 
Controls whether or not this Server will allow Domain Time II Clients to obtain the time via the Domain Time over HTTP protocol.

The Domain Time II over HTTP protocol must also be enabled on the Serve the Time property page of the Control Panel applet.

Note: This setting has a more limited scope than in versions prior to 5.1; it only applies to Client access. In earlier versions it also controlled Server and browser access. See the Allow Server-based HTTP requests and Allow Browser-based HTTP requests values for enabling these items individually in v5.1 and above.

Value Name:
 
Value Type:
 
Default Data:
 
Options:
 
Notes:
Allow Server-based HTTP requests
 
REG_SZ
 
True
 
True or False
 
Controls whether or not this Server will allow Domain Time II Servers to obtain the time via the Domain Time over HTTP protocol.

The Domain Time II over HTTP protocol must also be enabled on the Serve the Time property page of the Control Panel applet.

Value Name:
 
Value Type:
 
Default Data:
 
Options:
 
Notes:
Allow Remote Timezone Change
 
REG_SZ
 
True
 
True or False
 
Enables Domain Time II Manager to change the timezone on this machine.
Value Name:
 
Value Type:
 
Default Data:
 
Notes:
Allow Stepping
 
REG_DWORD
 
Varies
 
New as of v5.1, this value is a hex bitmap representing the settings made on Stepping Options dialog of the Clock Control property page. Do not edit this value.

These values will be overridden if the Never Step Clock setting (see below) is enabled.

Value Name:
 
Value Type:
 
Default Data:
 
Range:
 
Notes:
Clock Adjustment Bucket Size
 
REG_DWORD
 
7
 
3-32
 
The bucket size is the number of time samples collected before a particular clock adjustment rate is evaluated. The specified value is used except during accelerated clock training, where a fixed value of 5 is employed.

You should not change this number unless instructed by techsupport.

Important: This is a machine-specific setting and should not be included in installation templates or copied to other machines via mass registry imports.

Value Name:
 
Value Type:
 
Default Data:
 
Notes:
Clock Adjustment Statistical Method
 
REG_SZ
 
Automatic
 
Sets the type of statistical analysis Domain Time performs on collected time samples from a time source when deciding whether and how much to adjust the clock rate to compensate for drift. Domain Time then uses the calculated clock performance to evaluate and remember each integral clock adjustment rate it tries. Changing this value may improve or degrade timing accuracy (or have no effect).

Changes to this setting take effect immediately after the next group of collected samples is ready for analysis. You do not need to restart the service. You should clear your clock history using the command dtcheck -resettimings before changing this value. Allowed values are:

  • Automatic - On Vista/2008/Win7/2008r2 machines, Automatic will use the median value from each group of samples. On all other versions of Windows, it will use the arithmetic mean (average) of each group of samples.
  • Average - The arithmetic mean of values
  • Median - The median number in the array of values
  • Toss - average of values excluding the highest high and lowest low
  • RMS - the quadratic mean (signed root-mean-square) of the array of values
  • Disabled - no statistical analysis is retained for future comparison

Important: This is a machine-specific setting and should not be included in installation templates or copied to other machines via mass registry imports.

Value Name:
 
Value Type:
 
Default Data:
 
Options:
 
Notes:
Clock Change Monitor
 
REG_SZ
 
True
 
True or False
 
If enabled, Domain Time monitors changes to the system clock made by other programs (including the foreground user changing the time or date with the Control Panel applet or the command-line TIME and DATE commands). When the Clock Change Monitor is enabled on a Server and the clock changes unexpectedly, the Server will immediately resynchronize with its time source(s).

You may turn the Clock Change Monitor off if your setup requires having machines with different times (usually only in labs or testing environments). If Clock Change Monitor is disabled and you change a machine's time, it will stay changed until the next cascade signal or regular sync interval. Changes take effect immediately, and may be made by editing the registry or remotely from Domain Time II Manager.

Value Name:
 
Value Type:
 
Default Data:
 
Range:
 
Notes:
Clock Change Sensitivity
 
REG_DWORD
 
0
 
0-255
 
This value represents the number of seconds the system clock must differ from the expected value in order for Clock Change Monitor to decide an unauthorized change has been made to the system clock.

If not present or set to zero, Domain Time will use a value of 2 seconds.

Increase this value only if Clock Change monitor is triggering on normal clock drift (unlikely). Decrease this value only if Clock Change Monitor is not flagging known clock change events by another user or process.

Value Name:
 
Value Type:
 
Default Data:
 
Notes:
Current Version
 
REG_SZ
 
Varies
 
This value is set by the system for informational purposes. Changing it has no effect.

Value Name:
 
Value Type:
 
Default Data:
 
Options:
 
Notes:
Critical Timing Processor Limit
 
REG_SZ
 
Depends on processor type (see below)
 
True or False
 
This value is set to False during installation on machines with processors that have an Invariant TSC or if they are a Hyper-V guest; otherwise it is set to True. When True, Domain Time uses the last-processor-but-one for time-critical events, and any available processor for all other work. If set to False, Domain Time does not prefer one processor over another for any task.

Modern CPUs (ones with Invariant TSC) generally have better timing performance with this value set to False. You can check to see if you have an Invariant TSC by running the command-line DTCheck program:

   dtcheck -cpuid

Value Name:
 
Value Type:
 
Default Data:
 
Notes:
Daytime Format
 
REG_SZ
 
NIST
 
Specifies that Server will adhere to the NIST format for the Daytime (RFC-868) protocol.

Value Name:
 
Value Type:
 
Default Data:
 
Notes:
Daytime Identifier String
 
REG_SZ
 
UCT(DOMTIME)
 
Sets the text identifier string sent in responses to time requests using the Daytime (RFC-868) protocol.

Value Name:
 
Value Type:
 
Default Data:
 
Options:
 
Notes:
Dependent Services
 
REG_MULTI_SZ
 
(blank)
 
Blank, or a list of one or more IP addresses for use with DT2/udp and DT2/tcp protocols
 
Requires version 5.2.b.20150516 or later. Any services listed here will be started by Domain Time after the first successful timecheck, as long as the services are set to manual start. This is an alternative to using the built-in service database's dependencies. If you use the built-in functions, dependent services will wait for Domain Time to start, but won't know to wait until the first synchronization has completed.

You may list services by their display names (e.g. "Disk Defragmenter") or by their internal service names (e.g. "defragsvc"). List services one per line, without quotation marks. Domain Time will only attempt to start services that are listed, not yet running, and set to manual startup.

Important: If Domain Time cannot set the clock for some reason (invalid sources, firewall settings, etc.), then services you have set to manual start will not be started.

Value Name:
 
Value Type:
 
Default Data:
 
Range:
 
Notes:
DT2 Bias in Milliseconds
 
REG_SZ
 
+0
 
-3600000 to +3600000
 
Corresponds to offset from the correct time, in milliseconds, the server will use when serving the time to clients or other servers using the Domain Time II or Domain Time over HTTP protocols. Useful chiefly for situations where you need the network to lead or trail the server by a set amount. This setting does not affect the server's own time, or the time it serves using protocols other than DT2.

This is a REG_SZ value, not a binary or DWORD value. Express the offset using a plus sign or a minus sign, followed by the number of milliseconds you want. Note: Variance reports are not affected by this setting. Do not set up multiple servers with different offsets! Changes to this setting take effect upon restart. The domtimes.log will indicate a warning message if this value is set to anything other than +0.

Value Name:
 
Value Type:
 
Default Data:
 
Notes:
Ephemerides
 
REG_DWORD
 
N/A
 
This value is used by the system. Do not edit.

Value Name:
 
Value Type:
 
Default Data:
 
Range:
 
Notes:
ICMP TTL (hop limit)
 
REG_DWORD
 
32 (decimal)
 
1 to 255 (decimal)
 
This value controls the number of router hops that are allowed in an ICMP echo ("ping") request. Domain Time pings machines first to help eliminate long waits for machines that are unreachable. You should only need to adjust this value if you have an LAN/WAN configuration requiring more than the default 32 hops.
Value Name:
 
Value Type:
 
Default Data:
 
Notes:
Machine Statistics
 
REG_BINARY
 
N/A
 
This binary value contains the statistics, as of the last update, that can be viewed from DTCheck, the Domain Time II Manager, or the system tray icon. Do not edit.

Value Name:
 
Value Type:
 
Default Data:
 
Range:
 
Notes:
Max Slew Correction (milliseconds)
 
REG_DWORD
 
30000 (decimal)
 
1 to 36000000 (decimal)
 
This value specifies the upper limit, in milliseconds, of variance that Domain Time will attempt to correct by slewing instead of stepping the clock. This setting affects both forward and backward clock adjustments.

The older registry entry controlling this function, Max Slew Correction (seconds), has been deprecated.

If the correction to be made is larger than this setting but less than the allowed MaxDisparity setting (Correction Limit), Domain Time II will step the correction (unless Never Step Clock is enabled, at which point no correction is made and a note to this effect will be entered in the Domain Time logs). See the Never Step Clock and Override Max Disparity registry settings for more info.

Value Name:
 
Value Type:
 
Default Data:
 
Options:
 
Notes:
Never Step Clock
 
REG_SZ
 
False
 
True or False
 
When enabled, causes Domain Time to make clock corrections only by slewing. This prevents the clock from being stepped to make corrections such as those normally done during startup or from Clock Change Monitor, manual sync triggers, etc.

CAUTION: Enable this option with care. Use of this option may prevent Domain Time from successfully being able to synchronize with a time source if the time correction is too large to accomplish using slewing. See the Max Slew Correction (milliseconds) registry setting for more info.


IMPORTANT: Unlike with versions prior to v5.1, the behavior of this setting is NOT modified by the Override Max Disparity registry setting. If Never Step Clock is enabled, the clock will never be stepped, regardless of any other settings.

As of v5.1,, Domain Time uses the Allow Stepping setting (see above) to provide greater control of the stepping process. If your machine running an older version of Domain Time had Never Step Clock specified in the registry, the value will be translated to an Allow Stepping value of zero when upgrading to v5.x or later. See the Stepping Options dialog of the Clock Control property page to set the options.

In most cases, it is better to set the Stepping Options with the behavior you want than to enable Never Step Clock.


Value Name:
 
Value Type:
 
Default Data:
 
Range:
 
Notes:
NTP Client Version
 
REG_DWORD
 
4 (was 3 on versions prior to 5.2.b.20150516)
 
1 to 7
 
Controls the reported NTP version. Any value from 1 to 7 is legal, although using anything but 3 or 4 is not recommended.

Value Name:
 
Value Type:
 
Default Data:
 
Options:
 
Notes:
NTP Server RefID
 
REG_SZ
 
Dynamic
 
Dynamic or Static
 
Determines how the NTP RefID field (used to indicate the reference time source) is populated in NTP packets. Dynamic is the appropriate setting under most circumstances, which lets Domain Time decide what is a correct response. Change this value only if the automatically-selected RefID causes problems for NTP clients.

Note: This value is related to and may be overwritten in some circumstances based on the NTP Server Stratum value described below. When the NTP Server Stratum is set to 0 (Automatic) and NTP Server RefID is set to Dynamic, Domain Time will typically populate the RefID field with the IP address of its last known time source if the time was derived from a single machine, or 0.0.0.0 if multiple machines were included in the time analysis. LOCL may sometimes appear under certain configurations for compatibility with Active Directory.

If the NTP Server RefID value is set to Static, the RefID field will typically contain word GREY (or the dotted-quad numeric equivalent). Setting the NTP Server Stratum to 1 will force the NTP Server RefID to be Static. You may use either Dynamic or Static with any other value of NTP Server Stratum (2 - 15).

Note that when you set the Domain Time Server to "Do not set this machine's time" on the Obtain the Time property page, there is no external time source, so the RefID field will contain zeros. Some older NTP clients interpret this as the machine not being a valid time source and therefore refuse to synchronize with the Server. In this case, set the NTP Server Stratum value to 1 and restart the service.

Value Name:
 
Value Type:
 
Default Data:
 
Options:
 
Notes:
NTP Server Stratum
 
REG_DWORD
 
0
 
0 through 15 (decimal)
 
Specifies the NTP Stratum of this Server. A value of 0 means automatic assignment.

As of 5.2.b.20150516, when set to automatic assignment Domain Time selects a stratum number based on on strata reported by its time sources (including PTP, which uses "stepsAway" to correspond, roughly, with NTP strata).

Since Domain Time can use multiple sources with multiple protocols, there may not be an ultimate single stratum from which time was received. In these cases, Domain Time takes the highest-level stratum reported by all used sources, and adds one to derive its own stratum number. So, for example, if Domain Time obtains its time from a PTP grandmaster directly, it will report itself as stratum 2. If it receives its time from three NTP sources, two of which report stratum 1, and one of which reports stratum 2, Domain Time will report itself as stratum 3. If all three NTP sources reported stratum 1, Domain Time would report stratum 2, and so forth.

Versions prior to 5.2.b.20150516, automatic assignment applied a default Stratum depending on the type of Server Role selected:

  • Master Server: Stratum 2
  • Slave Server: Stratum 3
  • Independent Server: Stratum 2

You may specify a different value if it better fits your time distribution configuration.

Value Name:
 
Value Type:
 
Default Data:
 
Options:
 
Notes:
Override Max Disparity
 
REG_DWORD
 
Not present (same as zero)
 
0, 1, 2, 3, or 4
 
Controls how Domain Time decides when to override the Correction Limits set in the Control Panel applets for Server, Slave, or Client Timings as explained below. This allows for setting the clock under certain conditions that would otherwise prevent a correction.


IMPORTANT:
As of v5.1, none of these settings modify the Never Step Clock setting (see above). Note that this is a change in behavior from older versions. Enabling Never Step Clock effectively limits corrections to the Maximum Slew Correction (milliseconds) value, even if a larger correction would otherwise be permitted by Override Max Disparity.

  • 0 or not present (Auto)
    Domain Time will override the disparity settings during startup, on Clock Change Monitor event detection, receiving sync triggers/cascades from management components, or from Control Panel applet (CPL) signals.

  • 1 (Always)
    Domain Time will always override the disparity settings. This is the same as not having disparity settings at all. Always honors Never Step Clock setting.

  • 2 (Never)
    Domain Time will never override the disparity settings. Always honors Never Step Clock. This option may prevent your machine from syncing until you manually set the time to within the set Min/Max disparity range. If the machine is a Domain Time Server, it will normally refuse to serve the time until its own time has been set, so selecting a value of 2 may impact your entire network.

  • 3 (Startup only)
    Domain Time will override the disparity settings only until the first time after startup that it has set its own time correctly. Thereafter, it behaves as if you had set the option to 2.

  • 4 (Limit CCM)
    Clock Change Monitor signals do not override the disparity settings. Startup, management, or CPL signals will override the disparity settings.

Changes to this value take effect immediately. You do not have to stop and restart the service or reboot the machine.

Value Name:
 
Value Type:
 
Default Data:
 
Options:
 
Notes:
Override Sanity Checks
 
REG_DWORD
 
False
 
True or False
 

To prevent accepting obviously-wild time corrections, Domain Time will (by default) refuse to set the time outside of a defined range of acceptable correction. Backwards-correction is limited to the build date of the software - 1 year. Forward-correction is limited to 11:59:59 on 12/31/2036 due to NTP and UNIX Year 2038 date calculation issues.

However, Windows itself will allow setting the local clock outside of this sanity-checked range. Set this value to True to permit Domain Time to set the clock to any time/date the operating system will allow.

CAUTION: Change this value only if you have a clear requirement to do so.

Value Name:
 
Value Type:
 
Default Data:
 
Notes:
Send Port Generic
 
REG_DWORD
 
0
 
Domain Time uses several sockets for generic outgoing messages. By default, the port used is an ephemeral port assigned by the system. This is the proper behavior for client-server systems; only the server should have a fixed listening port, and clients should use ephemeral ports. However, in rare cases, other applications have high-number ephemeral ports hard-coded as their communications ports. If Domain Time happens to start first, and happens to obtain those particular ports, the hard-coded applications may fail.

Set this value to the beginning port number (n) of a range you want Domain Time to use for its generic outgoing sockets. Domain Time will attempt to use (n) through (n + 50) to bind its generic outgoing sockets. If none of the ports (n) through (n + 50) are available, Domain Time will revert to letting the system choose an ephemeral port.


IMPORTANT:
Be very careful not to specify any well-known ports or IANA-registered ports for your range, and only set this value if you have a specific problem that you know will be solved by changing the ephemeral ports Domain Time uses.
Value Name:
 
Value Type:
 
Default Data:
 
Options:
 
Notes:
Server Answer IP
 
REG_MULTISZ
 
(blank)
 
Blank, or a list of one or more IP addresses
 
This value corresponds to the "Listen only on these addresses" list on the Network tab of the Control Panel applet. If this value is not present or is blank, Domain Time will answer on all IP addresses bound to all interfaces present on the machine. Otherwise, Domain Time will only bind to the IP addresses you provide. You may provide IPv4 or IPv6 addresses, and may also use NetBIOS or DNS names. The addresses/names you provide must exist and be permanantly assigned to the machine. This setting is useful chiefly in situations where the machine is multihomed and you want Domain Time restricted to particular interface(s). This setting affects all listening ports for Domain Time Server, unless individual protocols are overridden (see below). You must restart the service (or reboot the machine) for changes to take effect.

Note: Because this value is highly machine-specific, it is not included in template imports or exports. You must set it individually on each machine.

As of version 5.2.b.20130221, you may also use CIDR notation to specify ranges of addresses. For example, 192.168.10.0/24 would bind to any address between 192.168.10.1 and 192.168.10.254, as long as one or more of those addresses was assigned to the machine. This is useful for machines using DHCP: you may restrict Domain Time to a particular network without knowing what IP the machine will have.

Value Name:
 
Value Type:
 
Default Data:
 
Options:
 
Notes:
Server Answer IP Override DT2
 
REG_MULTI_SZ
 
(blank)
 
Blank, or a list of one or more IP addresses for use with DT2/udp and DT2/tcp protocols
 
Requires version 5.2.b.20130221 or later. If this value is not blank, Domain Time will use it to bind to the IP addresses you specify for use by DT2 traffic. As with "Server Answer IP" above, you may use CIDR notation to specify networks without specifying individual IPs. Unlike "Server Answer IP," this value is included in template imports and exports. This value is not configurable using the Control Panel applet. You must restart the service (or boot the machine) for changes to take effect.

Value Name:
 
Value Type:
 
Default Data:
 
Options:
 
Notes:
Server Answer IP Override NTP
 
REG_MULTI_SZ
 
(blank)
 
Blank, or a list of one or more IP addresses for use with NTP
 
Requires version 5.2.b.20130221 or later. If this value is not blank, Domain Time will use it to bind to the IP addresses you specify for use by NTP traffic. As with "Server Answer IP" above, you may use CIDR notation to specify networks without specifying individual IPs. Unlike "Server Answer IP," this value is included in template imports and exports. This value is not configurable using the Control Panel applet. You must restart the service (or boot the machine) for changes to take effect.

Value Name:
 
Value Type:
 
Default Data:
 
Options:
 
Notes:
Server Answer IP Override PTP
 
REG_MULTI_SZ
 
(blank)
 
Blank, or a list of one or more IP addresses for use with PTP
 
Requires version 5.2.b.20130221 or later. If this value is not blank, Domain Time will use it to bind to the IP addresses you specify for use by PTP traffic. As with "Server Answer IP" above, you may use CIDR notation to specify networks without specifying individual IPs. Unlike "Server Answer IP," this value is included in template imports and exports. This value is not configurable using the Control Panel applet. You must restart the service (or boot the machine) for changes to take effect.

Value Name:
 
Value Type:
 
Default Data:
 
Notes:
Server Settings
 
REG_BINARY
 
N/A
 
Used internally. Do not edit.

Value Name:
 
Value Type:
 
Default Data:
 
Options:
 
Notes:
Service Installed
 
REG_SZ
 
N/A
 
True or False
 
Used internally. Do not edit.

Value Name:
 
Value Type:
 
Default Data:
 
Notes:
Service Log Filename
 
REG_SZ
 
[not present]
 
Sets the location and name of the service log file. If this value is not present or is blank, the log file will be created with the default filename domtimes.log in the %SystemRoot%\System32\ folder. The complete path and filename must be specified (i.e. C:\Windows\System32\domtimes.log) and the drive specified must be a local drive.

Value Name:
 
Value Type:
 
Default Data:
 
Options:
 
Notes:
Service Running
 
REG_SZ
 
N/A
 
True or False
 
Used internally. Do not edit.

Value Name:
 
Value Type:
 
Default Data:
 
Options:
 
Notes:
Set Processor Affinity
 
REG_DWORD
 
0
 
00-FF (hex)
 
Note: This value has been deprecated in version 5.x and later; see the Critical Timing Processor Limit value instead.

If not present or set to zero, Domain Time will not attempt to restrict time-sensitive operations to any particular processor in a multi-processor system. In some systems, the majority of hardware interrupt handling occurs on only one processor (typically processor 0), so it may provide increased accuracy if Domain Time uses only other processors during time-sensitive operations. This value is a hex bitmap representing the processors in the system, with bit 0 representing the first processor, bit 1 representing the second processor, and so forth.

Value Name:
 
Value Type:
 
Default Data:
 
Options:
 
Notes:
Test Mode
 
REG_SZ
 
False
 
True or False
 
Corresponds to the Test Mode checkbox on the Advanced property page of the Control Panel applet. If enabled (True), Domain Time will go through all the motions of obtaining the time and calculating variances, but will not actually set the clock. If disabled (False, the default value), Domain Time will set the clock after obtaining the time from its time source(s). Changes to this value only take effect after restarting the service.
Value Name:
 
Value Type:
 
Default Data:
 
Notes:
TIME/ITP Offset (seconds)
 
REG_DWORD
 
2208988800 (decimal)
 
Used internally by the system. Do not change this value unless instructed to do so by tech support.

Value Name:
 
Value Type:
 
Default Data:
 
Options:
 
Notes:
Time Sample PreFilters
 
REG_SZ
 
HighLow
 
Allowed options are HighLow, Latency, Delta, and Stratum. Prefilters are applied in the order listed; separate filter names with a comma or semi-colon.
 
Requires version 5.2.b.20150828 or later. This value controls the prefilters used to discard samples before applying statistical analysis. Prefilters only operate when there are five or more samples available for analysis, and are chiefly useful when the number of samples is very large, or the sources are unstable. It is best to leave this value at the default, which eliminates only egregious spikes. Statistical analysis of the entire group of samples usually performs better than prefiltering more samples out of the mix.

For example, HighLow,Latency would apply first the Highlow filter, then if at least five samples remain, the latency Filter. Stratum,Latency,Delta would first apply the Stratum filter; then if at least five samples remain, the Latency filter; then, if at least five samples remain, the Delta filter. Changes to the list of prefilters are recognized only when parameters are reloaded (server stop/restart, machine reboot, a CPL-initiated sync, or a DTCheck /reload).

Prefilter operations are:

  • HighLow (default) - Rejects the most extreme samples, based on absolute magnitude delta (max of 2 samples rejected)
  • Latency - Rejects highest latency samples (max 1/3 of samples rejected)
  • Delta - Rejects highest magnitude delta (max 1/3 of samples rejected)
  • Stratum - Rejects all but the lowest-stratum samples present. Be very careful with this filter. Example 1: If your selection of samples includes one sample from a stratum 1 server, and ten more from a mix of stratum 2 and stratum 3 servers, then all but the single stratum 1 sample would be rejected. Example 2: If your lowest-stratum samples are a mix of stratum 2 servers, then all the stratum 2 samples would survive, but all your samples from strata 3 and up would be rejected. It is probably better to use the "NTP Client Max Stratum" value introduced in version 5.2.b.20110224 to control the highest stratum acceptable for NTP sources. The Stratum filter introduced here applies to all sources that report a stratum, including NTP, DT2, and PTP (the PTP "stepsAway" value is used to mimic NTP strata, as documented in the release notes for 5.2.b.20150516). Samples that do not report a stratum are not eliminated by this filter.

Value Name:
 
Value Type:
 
Default Data:
 
Options:
 
Notes:
Wait for Network Startup
 
REG_SZ
 
True
 
True or False
 
Present in version 5.2.b.20151102 or later. If set to True, Domain Time will wait up to 30 seconds after boot for an IPv4 address to be assigned to the machine. At boot time, some network adapter drivers report ready before assigning IP addresses to an interface, even if the IPs are pre-configured as fixed addresses. DHCP-obtained addresses can take several seconds longer. The wait period helps ensure that Domain Time's initial enumeration of adapters and IPs is correct before protocol listeners or timechecks are started.

Change this value only if instructed by Technical Support

Time Sources
     
    The Domain Time II Server Time Sources settings are located in this key:

       HKEY_LOCAL_MACHINE
          Software
             Greyware
                Domain Time Server
                   Broadcast
                   PTPv2 (IEEE 1588)
     


    The values listed in the Time Sources registry key represent the time sources Domain Time uses to obtain the time. They correspond to settings on the Obtain the Time property page of the Control Panel applet or are otherwise automatically set. You should not change items in this section unless instructed by Tech Support or you are familiar with the specific function.

    PTPv2 (IEEE 1588) key

Value Name:
 
Value Type:
 
Default Data:
 
Notes:
Current Master
 
REG_SZ
 
N/A
 
Introduced as of version 5.2.b.20160415. Read-only key for use with the Software Development Kit (SDK), purchased separately.

Value Name:
 
Value Type:
 
Default Data:
 
Notes:
Current Offset (signed 64-bit)
 
REG_SZ
 
N/A
 
Introduced as of version 5.2.b.20160415. Read-only key for use with the Software Development Kit (SDK), purchased separately.

Value Name:
 
Value Type:
 
Default Data:
 
Options:
 
Notes:
Current Offset Enabled
 
REG_SZ
 
False
 
True or False
 
Introduced as of version 5.2.b.20160922. When false, Domain Time will not update the current offset value in the registry (Current Offset (signed 64-bit) described above) or fire the offset-changed event. Note, this reverses the behavior introduced in version 5.2.b.20160415. To regain this behavior, set Current Offset Enabled to True, then trigger a sync or issue dtcheck -reload. See the SDK.DOC file included with the Software Development Kit (SDK) for details.

Value Name:
 
Value Type:
 
Default Data:
 
Notes:
Current PortState
 
REG_SZ
 
N/A
 
Introduced as of version 5.2.b.20160415. Read-only key for use with the Software Development Kit (SDK), purchased separately.

Value Name:
 
Value Type:
 
Default Data:
 
Options:
 
Notes:
Duplicate Node Detection Enabled
 
REG_SZ
 
True
 
True or False
 
Introduced as of version 5.2.b.20160415. Controls whether Domain Time will detect and prevent duplicate Clock Indentities on the network.

Value Name:
 
Value Type:
 
Default Data:
 
Options:
 
Notes:
TAI-UTC Offset Locked
 
REG_SZ
 
False
 
True or False
 
Introduced as of version 5.2.b.20160922. If changed to True, DT will not adjust its discovered TAI-UTC offset to match a new master advertising a different offset. The service must be stopped/restarted for this change to take effect. You should use this setting only if you have a broken PTP master advertising an incorrect TAI-UTC offset.

 

Back Back to the System Tray Applet page

Domain Time II Software distributed by Microsemi, Inc.
Documentation copyright © 1995-2017 Greyware Automation Products, Inc.
All Rights Reserved
All Trademarks mentioned are the properties of their respective owners.