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 time zone 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
for details)
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
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
once.
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
the public time server, and will almost certain violate the terms of use for that server.
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
explicitly enabled.
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 time zone
of the machine running Domain Time II Manager.
Added active link to Microsemi'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).
