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 Greyware 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.
32-bit (x86) and 64-bit (x64) versions available. ARM is not supported. TCP/IP Port Usage
Hardware: Typically, any machine capable of running Windows may run Domain Time.
Machines running Server require sufficient memory for packet buffering and maintaining the
number of TCP/UDP connections used (varies by the number of client machines contacted). See Choose the right machine(s) for more info.
Machines running Manager/Audit Server also require sufficient disk space for holding collected audit records (see the Application Notes below).
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.) provide less accurate results when executed from a virtual OS. They should be run on a physical machine, if possible.
Please see How to configure Domain Time on a virtual machine.
Some functions require file access through administrative file shares and Remote Registry access using Windows Networking.
Manager makes numerous UDP and TCP connections to remote machines. You must have sufficient system resources (memory and processing bandwith) to handle the number
of network connections, which increase proportionally to the number of machines being managed.
Manager and many of the Management Tools will not run on Nano Server.
Installed disk usage (not including database or log files): ~ 14.5 Meg
Audit Server makes numerous UDP and TCP connections to remote machines. You must have sufficient system resources (memory and processing bandwith) to handle the number
of network connections, which increase proportionally to the number of machines being audited. If you use the new PTP Monitor, these requirements can significantly
increase due to the "chatty" nature of the additional PTP protocol and management message traffic.
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.
Installed disk usage (not including log files): ~ 3.6 Meg