1. From the Control Panel, open the Date and Time applet. This can also be accomplished by double-clicking the clock on the system tray or running timedate.cpl from the command line.
2. You can configure the year, month, day, and time on the Date & Time tab and the time zone on the Time Zone tab.
3. On Windows Server 2003, you can configure clock synchronization (Network Time Protocol (NTP) settings) from the Internet Time tab if the system is not part of a domain. If it is member of a domain, then the clock is synchronized automatically from an Active Directory domain controller.

Using a command-line interface

The following commands set the time to 11:02 p.m. and the date to November 1, 2005:

> time 23:02:00

> date 11/01/2005

The date format may vary depending on your locale.

Run this command to display the current date, time, and time zone:

> date /t & time /t & w32tm -tz

You can use this command to display time zone information from the registry:

> reg query \\<ServerName>\HKLM\SYSTEM\CurrentControlSet\Control\TimeZoneInformation

This command sets the SNTP server list:

> net time /setsntp:<ServerList>

For example:

> net time /setsntp:mytime.rallencorp.com,time.windows.com

This command queries the SNTP server:

> net time /querysntp

This command forces the local system to sync its time from the time source:

> net time /set

Using VBScript

' This code displays the local date, time, and time zone on a target computer' ------ SCRIPT CONFIGURATION ------strComputer = "."   ' e.g. rallen-srv01' ------ END CONFIGURATION ---------WScript.Echo "Current time using Now function: "WScript.Echo vbTab & Now

set dicDaysOfWeek = CreateObject("Scripting.Dictionary")dicDaysOfWeek.Add 0, "Sun"dicDaysOfWeek.Add 1, "Mon"dicDaysOfWeek.Add 2, "Tue"dicDaysOfWeek.Add 3, "Wed"dicDaysOfWeek.Add 4, "Thu"dicDaysOfWeek.Add 5, "Fri"dicDaysOfWeek.Add 6, "Sat"

set objWMI = GetObject("winmgmts:\\" & strComputer & "\root\cimv2")set objDateTime = objWMI.Get("Win32_Localtime=@")WScript.Echo "Current time using WMI: "WScript.Echo vbTab & dicDaysOfWeek.Item(objDateTime.DayOfWeek) & " " & _         objDateTime.Month & "/" & objDateTime.Day & "/" & _         objDateTime.Year & " " & objDateTime.Hour & ":" & objDateTime.MinuteWScript.Echo "Time zone:"set colTZ = objWMI.ExecQuery("select * from Win32_TimeZone")for each objTZ in colTZ    Wscript.Echo vbTab & objTZ.Captionnext

The easiest way to set the time and date via a script is by shelling out to the time and date commands, but this means the script must be run locally. Here is an example:

WScript.Echo "Current time: " & Now

strCommand = "cmd.exe /c time 23:02:00"set objWshShell = WScript.CreateObject("WScript.Shell")intRC = objWshShell.Run(strCommand, 0, TRUE)if intRC <> 0 then   WScript.Echo "Error returned from time command: " & intRCelse   WScript.Echo "time command completed successfully"end if

strCommand = "cmd.exe /c date 11/01/2004"intRC = objWshShell.Run(strCommand, 0, TRUE)if intRC <> 0 then   WScript.Echo "Error returned from date command: " & intRCelse   WScript.Echo "date command completed successfully"end if

WScript.Echo "New time: " & Now

If your server is part of a workgroup or NT 4 domain, you must manually configure the time and date settings on it. You can either set the time and date based on some external time source (such as your watch) or you can configure the server to synch from a time server. The latter is the preferred method because as long as the time server you are pointing your servers to has the correct time, your servers will have the correct time. If your server is part of an Active Directory domain, it will automatically sync its time from a domain controller.

Time and date synchronization is handled by the Windows Time service (W32Time), which was originally developed for Windows 2000 and is a compliant implementation of RFC 1769Simple Network Time Protocol (SNTP). For Windows Server 2003, W32Time was updated to support NTP, a more accurate protocol than SNTP.

W32Time is highly configurable via the registry. See MS KB 223184 for the list of registry settings you can configure for Windows 2000. A similar KB article has not been produced yet showing the differences for Windows Server 2003.

For a good whitepaper on the Windows 2000 Time service, visit the following URL: http://www.microsoft.com/windows2000/docs/wintimeserv.doc.

For more on the Windows Server 2003 Time service, visit the following URL: http://www.microsoft.com/Resources/Documentation/windowsserv/2003/all/techref/en-us/W2K3TR_times_intro.asp.

# cd /etc/tripwire
# ./twinstall.sh
# tripwire –init
# rm twcfg.txt twpol.txt

The script twinstall.sh performs the following tasks within the directory /etc/tripwire:

• Creates the site key and the local key, prompting you to enter their passphrases. (If the keys exist, this step is skipped.) The site key is stored in site.key, and the local key in hostname-local.key, where hostname is the hostname of the machine.
• Signs the default configuration file, twcfg.txt, with the site key, creating tw.cfg.
• Signs the default policy file, twpol.txt, with the site key, creating tw.pol.

If for some reason your system doesn’t have twinstall.sh, equivalent manual steps are:

Helpful variables:
DIR=/etc/tripwire
SITE_KEY=$DIR/site.key
LOCAL_KEY=$DIR/`hostname`-local.key

Generate the site key:
# twadmin –generate-keys –site-keyfile $SITE_KEY

Generate the local key:
# twadmin –generate-keys –local-keyfile $LOCAL_KEY

Sign the configuration file:
# twadmin –create-cfgfile –cfgfile $DIR/tw.cfg \
–site-keyfile $SITE_KEY $DIR/twcfg.txt

Sign the policy file:
# twadmin –create-polfile –cfgfile $DIR/tw.cfg \
–site-keyfile $SITE_KEY $DIR/twpol.txt

Set appropriate permissions:
# cd $DIR
# chown root:root $SITE_KEY $LOCAL_KEY tw.cfg tw.pol
# chmod 600 $SITE_KEY $LOCAL_KEY tw.cfg tw.pol

(Or chmod 640 to allow a root group to access the files.)

These steps assume that your default configuration and policy files exist: twcfg.txt and twpol.txt, respectively. They should have been supplied with the Tripwire distribution. Undoubtedly you’ll need to edit them to match your system.

Next, tripwire builds the Tripwire database and signs it with the local key:

# tripwire –init

Enter the local key passphrase to complete the operation. If tripwire produces an error message like “Warning: File System Error,” then your default policy probably refers to nonexistent files. These are not fatal errors: tripwire still ran successfully. At some point you should modify the policy to remove these references.

The last step, which is optional but recommended, is to delete the plaintext (unencrypted) policy and configuration files:

# rm twcfg.txt twpol.txt