This page explains the recommended versions and basic system requirements for using Domain Time II.
This table shows the recommended version for use on the indicated operating systems.
Note: Older versions may be available for compatibility on the indicated platforms, however
support and documentation are provided only for the current release version (v5.2).
Many of the older versions will run on other operating systems than the ones shown here, however,
the indicated version provides the best performance for the operating system listed.
Older versions are provided for backwards-compatibility only. Fixes, updates, and technical support are available only for the supported version. * If you need this older version, please write to Microsemi Tech Support.
Version 5.2 Basic Requirements
These are the system requirements for the current version of Domain Time II (except where noted). System requirements for older versions are here.
The Management Tools consist of Domain Time II Manager plus a number of special-use utilities and services.
Any tools that calculate comparative time variances (such as Domain Time II Manager, Domain Time II Monitor Service,
DTCheck utility, etc.) cannot be relied upon to provide accurate results when executed from a virtual OS.
These should be run on physical machines. 1
Some functions require file access through administrative file shares and Remote Registry access using Windows Networking.
Manager and many of the Management Tools will not run on Nano Server.
Audit Server requires both Domain Time II Server and Manager.
All three components must installed on the same physical machine and be the same version.
Audit Server acts as a plug-in to Domain Time Manager and shares its view of the network.
Domain Time II Audit Server is not supported on virtual machines. 1
The Audit Server machine must have sufficient disk space to hold all audit records and sync
logs collected. You may use the Audit Disk Space Estimator
to calculate disk usage for Audit Records. Sync log sizes can be estimated based on ~20 bytes of log space per synchronization.
Some functions require file access through administrative file shares using Windows Networking.
Collected Sync Log files, Daily Audit Summaries, and Audit records cannot be viewed from Audit Server running on Windows Server Core.
LMCheck uses Windows Networking LanMan protocols to give a rough variance report of the local subnet.
NetBIOS (Windows Networking Browse List) must be enabled on each machine being sampled.
Included with the Domain Time II Management Tools. It is also available as a stand-alone freeware utility.
LMCheck will not run on Nano Server.
1 As of Windows Server 2012, Microsoft has made significant improvements in Hyper-V guest clock handling, such that on sufficient hardware,
Hyper-V guests may be suitable for running time services such as Domain Time Server, Audit Server, Manager, tools, etc. for general purpose use.
Highly time critical environments should (such as those requiring sub-millisecond timing) should continue to use physical machines for these systems.
Older Hyper-V environments (i.e. Server 2008) are not suitable for serving time.