Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
Using NET TIME for all Workstations and Servers
Article ID: 120944 - View products that this article applies to.
This article was previously published under Q120944
For a Microsoft Windows XP version of this article, see 314090
In a network with different network client software, different workgroups, and different domains, maintaining a logon script that issues a NET TIME command can become complex. This article offers a simple solution to keep the time for all clients in the network synchronized.
The solution to keeping all workstations' time synchronized with a particular server can be solved by either running a logon script for each workstation or by having each workstation run a batch file on their own after logging on to the network.
For example, assume you have a server named TIMESRV that has a reliable system clock. An example batch file that would run either from the workstation, or get called from or be part of a logon script, would look like this:
NET TIME \\TIMESRV /SET /YESUsing just a server name instead of the /DOMAIN or /WORKGROUP parameter avoids the complexity of maintaining different logon scripts or batch files for the different types of network client software. Please keep in mind that if all of your workstations are running the same type of network client software, you may choose instead to use the /DOMAIN or /WORKGROUP parameter. But, in a network with a variety of network client software, it might be easiest to use the "\\computername" (without quotation marks) parameter.
NOTE: NET TIME is enabled by default on all Windows NT workstations and servers.
For additional information, click the article numbers below to view the articles in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/216734/EN-US/ )How to Configure an Authoritative Time Server in Windows 2000
(http://support.microsoft.com/kb/307897/EN-US/ )HOW TO: Synchronize the Time Using the Windows Time Service
Article ID: 120944 - Last Review: February 20, 2007 - Revision: 2.2