|Domain Time II |
Version 2.5 Changelog
Version 2.4 Changelog
- 2.4.b.20010420 - optional upgrade.
Added code to DTManager to help it view mixed networks (Microsoft
networking plus Novell, or other) more accurately.
- 2.4.b.20010405 - optional upgrade.
Added fix for remote registry access error when remotely controlling
from a Windows 2000 machine. Also added support for running the control panel applets from a virtual
session on Terminal Server.
- 2.4.b.20010403 - optional upgrade.
Increased accuracy of variance calculations by the Full and Thin
Clients by ensuring that both process and thread priorities are at "real time" levels during the
calculations. Formerly, only Server did this consistently, and the Full Client did it only for
the Domain Time II protocol. Also added a work-around for a Microsoft C runtime oddity that
could produce a local time display that did not account for daylight savings time in all cases.
This problem only manifested in the displays produced by DTCheck, DTManager, and the system tray icon,
and only for certain timezones. This problem did NOT affect getting or setting the time -- only the local
time display option.
- 2.4.b.20010307 - internal changes only. Upgrade optional.
- 2.4.b.20010306 - optional upgrade.
Fixed misspelling on DTMonitor's control panel applet advanced
page; improved DTManager's variance report display on Win2000; fixed bug that prevented the system
tray icon client statistics page from showing changed timezone immediately; added /variance command-line
switch to DTManager to make it go directly to the variance report on startup. Added continue on error
to DTManager's batch processing.
- 2.4.b.20010223 - recommended upgrade.
Fixed two bugs induced by the last version -- DT Server's
Control Panel applet did not retain the Use Specified Port setting for the Domain Time over HTTP
protocol, and the workaround for non-existent APC timers under Win95 did not work with every
version of Win95 (Win98, NT, and 2000 were not affected by this problem). Also enhanced the
DT Manager remote Control Panel applet emulators to gray-out features not present on remote
machines. Tightened the Thin Client's accuracy-seeking method to yield better results when the
average variance is less than 50 milliseconds. Fixed minor display error on
NTPCheck. Other small internal changes.
(Note: This version was originally released as 2.4.b.20010222 in error. The version number
was corrected to 2.4.b.20010223.)
- 2.4.b.20010210 - recommended upgrade.
Several minor bug fixes in Domain Time II Manager, new features
added to Domain Time II Monitor. Improved slewing accuracy by using APC timer on both server and
client. Extended max backward slew capability (set in registry) to one hour, although we still
recommend not changing this setting. New splash screens. Improved balloon help on dialogs. Other
minor internal changes. Added foreign slave option to server.
- 2.4.b.20010130 - minor changes.
Fixed display bug in Domain Time II Manager variance report screen.
Color legend (visible only when sorting by variance) had "within 25 ms" instead of "within 55 ms" for
the black range. Times reported were correct; only the legend and color was wrong. Also added registry
entries to allow end-users to set the limits for the color ranges to something other than the defaults
if desired. Upgrade optional.
- 2.4.b.20010126 - minor changes.
Added HTML email capability to Domain Time II Monitor. Restored
previous minimum setting for the Full Client check interval to 1 minute. Monitor now has an interface
in its control panel applet for setting broadcast addresses, and can share settings with Manager.
Monitor now provides individual event log entries for every machine that exceeds the tolerance you
specify (in addition to the summary report it has always provided). Upgrade optional.
- 2.4.b.20010122 - thin client changes only.
Removed beeps when clock-change monitor signals a resync;
corrected system tray icon problem in signaling thin client to resync on demand. Upgrade optional.
- 2.4.b.20010119 - version 2.4 released. Recommended upgrade.
- Increased accuracy of Domain Time II protocol's variance calculation
- Increased accuracy of LAN/WAN latency calculations (affects all protocols)
- Improved clock-change monitor to detect changes made from 16-bit and non-compliant programs
- Variances maintained in hectonanoseconds internally, converted to milliseconds immediately before setting the clock
- Added clock granularity detection, so time is set immediately after millisecond rollover
- Reduced master-slave network traffic by adding new message that combines parms, security, and version information into one transaction
- Master security settings now (optionally) replicated to slaves
- Full clients may choose to ignore advisory or cascade signals
- Added optional chime sound to Server and Full Client when time is set
- Improved machine list detection in Domain Time II Manager
- Added tooltips to Domain Time II Manager
- Added color text to Domain Time II Manager's variance report
- Added "Sync All Now" button to Domain Time II Manager
- Added machine type, machine NetBIOS name, serial number, and install date to Domain Time II Manager details screen
- Domain Time II Manager batch function now installs/upgrades servers in PDC->BDC->Server->Client order
- Domain Time II Manager batch function pauses after installing/upgrading PDC to allow config before continuing
- Increased accuracy of Domain Time II Monitor's variance calculation routines
- Added support for multiple SMTP servers (separate by commas) in Domain Time II Monitor's email configuration
- Added -vq (very quiet) switch to command-line setups programs. If -vq is specified, setup will not pop up dialogs or warnings even if an error occurs
- Exposed Max Slew Correction (REG_DWORD) registry setting. This setting controls how many seconds Domain Time II
will attempt to correct the time by slewing instead of just changing the clock backward. The default
value is 30.
- Added optional NTP broadcast sending for interoperation with third-party clients
- Added optional NTP broadcast reception
Version 2.3 Changelog
- 2.3.b.20001218 - internal changes. Upgrade optional.
- 2.3.b.20001213 - replaced prompt text in several dialogs to increase clarity of instructions. No other
changes. Upgrade optional.
- 2.3.b.20001206 - fixed error in Thin Client setup using SystemTrayIcon value in domtime.ini file. The
Thin Client did not honor the option upon first installation if the option were set to FALSE (i.e.,
setup behaved as if this option were always TRUE). This change only affects the Thin Client, and
only during installation. No changes to other components.
- 2.3.b.20001128 - fixed display error in Domain Time Manager properties page that showed the wrong time
zone name for Domain Time Manager. Times displayed were correct, and client timezone names were
correct. Also added check for TCB ("Act as part of the operating system") privilege as an additional
method of determining whether the logged-on user has administrative privileges.
- 2.3.b.20001101 - added "Open with Notepad" button to log display dialog; optimized and documented internal
discovery procedures (see Discovery Process
- 2.3.b.20001030 - removed workstation dependency; increased log-viewer file size; improved system tray
icon's detection of time-not-set conditions. Also, when upgrading management tools, the new domtime.ini
file is merged with your existing file instead of replacing it. This preserves your customizations
while also adding any new parameters.
- 2.3.b.20001006 - added DTDialup utility and
added support for n-way trusts to Domain Time II Manager.
- 2.3.b.20001002 - first release of 2.3.
Changes in Version 2.3 -- All Components
Since version 2.2, we have examined each component of Domain Time II, incorporating customer
suggestions, adding features that were delayed by production schedules, and streamlining the
operation based on extensive network monitoring and analysis.
- Support for non-Microsoft DHCP servers.
- Times shown in reports are marked UTC or local (removed ambiguity).
- Added optional system-tray icon.
- Removed ambiguity from wording of certain log messages.
- Added unique serial number, set upon installation/upgrade.
- Added auditing support (for use with forthcoming Audit Server).
- The Sync Now button no longer dismisses the Control Panel applet.
- Replaced C-Runtime function time() to eliminate a bug that manifests when
the timezone changes but the machine is not rebooted.
- Logfile viewer in Control Panel applets no longer uses notepad; instead it has
an auto-refreshing window on the last 32K of the log file.
Changes in Version 2.3 -- Domain Time II Server
- Slaves check with the master multiple times and average the results when setting their
own clocks. This behavior helps prevent propagation of clock jitter (small back-and-forth
changes due to system clock granularity rather than real time changes). This behavior is
controlled by the new registry setting:
HKEY_LOCAL_MACHINE \ Software \ Greyware \ Domain Time Server \ Parameters
Redundancy Checks: REG_DWORD
Default value: 0
Allowed values: 0 - 10
If Redundancy Checks is set to zero (the default), then slaves will check three times
with the master and average the results. Other servers will check with their sources only
If Redundancy Checks is set to 1 through 10 on any type of server, the server will check
that many times with its source, averaging the results.
Warning! Do not set your master server or independent server to use multiple checks
if your source is a public time server! This will result in excessive network traffic for
Use Redundancy Checks only between masters and slaves, or when obtaining the time from your
own GPS or atomic clock.
Changes in Version 2.3 -- Domain Time II Clients
- Reduced network traffic by utilizing progressive discovery techniques. Previous
versions would collect information about all known servers and DHCP options before
trying any of them. The current version queries only as necessary. Overall network
traffic reduced by 33-66 percent on most networks.
- Triggers from slaves or independent servers cause the client to first attempt
to get the time from the last-known-good server. Previous versions would cause
the client to get the time from the machine sending the trigger, causing client
machines to switch from server to server throughout the day. Now clients only
change servers (and perform the discovery broadcasts to locate a server) if the
last-known-good server is unavailable.
- Clients will ignore broadcast triggers received within five seconds of the last
trigger to cause a time set. This prevents clients from resynchronizing to each
slave (or resynchronizing with the last-known-good server) when a domain-wide
sync happens (i.e., master changes, then each slave changes).
- Clients will ignore limits (minimum change and maximum change) on startup and
when receiving a directed synchronization request. Directed synchronization
requests are generated by the Control Panel applet (Full Client only), the
command-line took DTCHECK, the system tray icon, or Domain Time II Manager.
Synchronization requests that come from broadcast triggers, or regularly
scheduled synchronization requests, honor the min-max limits. This allows
an administrator or end-user to re-sync a machine that is badly off-time without first
changing the limits and then changing them back.
- Added a checkbox to the Full Client's Control Panel applet to determine if,
when not using automatic mode, the client should query the local subnet for
servers if all listed servers fail. Previous versions of the Full Client
always fell back to broadcast discovery; now, this capability must be
Changes in Version 2.3 -- Domain Time II Manager
There are several major improvements to Domain Time II Manager. Most notable is the ability to
control Win95/Win98/ME workstations and change timezone settings remotely.
- Supports remote install/upgrade/removal/control for Win95/Win98/ME machines.
Win9x machines must be configured for
remote control first.
- Supports remote reading/setting of Timezones. This capability is enabled
by default, but may be turned off through a registry setting Allow Remote Timezone change
on the Client or Server. This function requires the remote machine to be running Domain Time 2.3.
- Uses pings to determine availability of remote machine rather than wait for
RPC timeout. (RPC timeouts can take up to 2 minutes and cannot be adjusted.)
- Variance report will use current machine as standard if no master or slave can
be located. In addition the REG_SZ value Reference NTP Clock may be entered
in the registry. This value defaults to blank. If set to a machine name or IP address,
the Variance report will use the designated NTP server as the reference clock.
- All reports show time in UTC unless specifically noted otherwise. Previous
versions would report a remote machine's data according to the local timezone
of the machine running Domain Time II Manager.
- Added active link to Greyware's home page to front of dialog box.
- Added registry value Send Advisories (default TRUE) to allow disabling of
server advisory broadcasts. Advisories have been present since version 2.1, but
are only used by diagnostic tools and monitoring software. Advisories may be
disabled without changing Domain Time's current functionality.
- License Scan will upgrade/install Win9x machines when possible, or continue
recommending action when not (i.e. permission denied or required components not
installed on remote machine).
Version 2.2 Changelog
- 2.2.b.20000819 - added code to handle non-Microsoft DHCP servers.
- 2.2.b.20000711 - increased number of servers from two to four for Client; exposed TIME/ITP
offset value in registry for Server; added automatic decompression and cleanup of temporary
files for Setup. No other components affected.
- 2.2.b.20000615 - added code to handle invalid responses from the PDC while enumerating
trusted domains. This is an optional upgrade. Upgrade only if you see invalid domain
names in Domain Time II Manager or LMCheck. No other components affected.
- 2.2.b.20000602 - added code to prevent clock-change monitor routine from believing that
a test-mode check was actually a time correction. The previous behavior could cause a
brief loop (checking the time over and over) when test mode was enabled. This is an
optional upgrade. Upgrade only if you are experiencing this particular problem in your
test lab environment.
- 2.2.b.20000524 - cosmetic changes to management tools; added DT1 and LANMan discovery
to DTProbe. Minor internal improvements to Domain Time Server to improve efficiency (no
changes to functionality or configuration). This is an optional upgrade.
- 2.2.b.20000517 - added ERRORLEVEL result code to DTSet for use in batch files. DTSet
returns ERRORLEVEL 0 if the time was not set, or ERRORLEVEL 1 if the time was set. Also
corrected problem with management tools setup where the default link to DTSet was to
the system directory instead of the install directory. This is an optional upgrade.
- 2.2.b.20000516 - modified /w switch in DTCheck to mean "wait for success" rather than
"wait for any results." Also made DHCP searching optional for DTSet. DTSet now will
only use DHCP-specified servers (if any) if the /dhcp switch is specified. No changes
to other products. This is an optional upgrade.
- 2.2.b.20000512 - added multi-domain support to LMCheck. Fixed potential problem in domain
browsing within Domain Time II Manager if the Computer Browser service is deliberately
turned off on the Primary Domain Controller. Added /w switch to DTCheck. This is an optional upgrade.
- 2.2.b.20000510 - added robots.txt handling to server's built-in web server. This will keep
your Domain Time over HTTP server from showing up in most public search engines. This is an optional upgrade.
- 2.2.b.20000508 - version 2.2 released. Thin Client and management tools introduced.
Version 2.1 Changelog
- 2.1.b.20000329 - added LMCHECK. No changes in Domain Time functionality. Minor improvements to
reduce load and improve efficiency of logging under extremely high load (more than 5 events within
any one millisecond).
- 2.1.b.20000305 - minor enhancements. Added master-changed broadcast message, responded to by clients
only when no slaves are present. This allows master-client sync when no slaves are configured or running,
with automatic fallback to master-slave and slave-client when slaves come back online. Also enhanced
log messages to indicate when client is waiting for a dial-up connection.
- 2.1.b.20000203 - minor enhancements. Added automatic logfile size-limiting (default 32K for clients,
unlimited for servers; can be adjusted in the registry and in DOMTIME.INI). Added RespondToDTCheck
to DOMTIME.INI. Added ability to specify port numbers in the server definition fields of the
control panel applet (e.g., servername:portnumber). This port number is only used by Domain Time over HTTP.
Added ability to specify port numbers in the proxy definition field on the control panel applet (only
used for Domain Time over HTTP). Added ability to specify Domain Time over HTTP listen port number
to force Domain Time Server to listen on a port other than 80 when Domain Time over HTTP service is
enabled. If port is not specified and port 80 is already used, the server will hunt for a free port,
starting with 81 and incrementing by one. Relaxed accuracy-seek requirements for clients running on
Windows NT or Windows 2000 with slewing enabled.
- 2.1.b.20000115 - minor enhancements. Increased internal cache size for Denial of Service
protection routine; added code to auto-config client to allow it to respond to master broadcasts
in the event that no slaves are present; added registry setting to allow control of how many
threads are used by server for DT2 protocol; added registry setting to allow client to respond
to DTCheck /V requests.
- 2.1.b.20000112 - recommended upgrade. Corrected minor bug in Denial of Service protection routine that
could cause temporary interruption of service.
- 2.1.b.20000109 - added support for SOCKS4 proxy servers, Denial of Service
protection, and access control.
- 2.1.b.19991218 - minor upgrade. Added support for Windows for Workgroups client to Domain Time Server. Added
code to support control panel's Add/Remove Programs functions. Fixed omission in remote
removal code (NT only) to delete the Domain Time control panel applet on the remote machine.
- 2.1.b.19991215 - cosmetic changes only. Added splash screen to registered version at customer request. The eval
version has always had a splash screen (which cannot be disabled). The
registered version's splash screen can be disabled from the Advanced
dialog on the control panel. Also updated wording on control panel applets to make
slewing options clearer.
- 2.1.b.19991213 - added proxy authentication support.
- 2.1.b.19991210 - added setup.exe and remote installation/removal for NT/Windows 2000 machines.
Fixed bug that could cause looping if Tardis2000 with broadcast enabled is installed on the
same subnet with Domain Time Server running SNTP server.
- 2.1.b.19991207 - enhanced log messages for error conditions; split log messages for HTTP to
record accesses by clients separately from accesses by browsers; fixed bug
in client that could cause client to skip update if auto-config was turned
off and RAS-awareness was enabled.
- 2.1.b.19991205 - added backward-correction-by-slewing and streamlined window size calculation.
- 2.1.b.19991129 - first release of Domain Time II; major update; all code completely rewritten.
Copyright © 1995-2021 Greyware Automation Products, Inc. All Rights Reserved
All Trademarks mentioned are the properties of their respective owners.
Greyware Automation Products, Inc.
308 Oriole Ct, Murphy, TX 75094
972-867-2794 (voice) 972-208-1479 (fax)
Close Printer-Friendly Version