Export (0) Print
Expand All
1 out of 2 rated this helpful - Rate this topic

Windows Time Service Troubleshooting

Updated: January 21, 2005

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

Troubleshooting

What problem are you having?

Clients are not synchronized with servers.

Cause:  Windows Time Service has been stopped manually.

Solution:  Start Windows Time Service. To start Windows Time Service, follow these steps:

  1. Open Command Prompt.

  2. Type:

    net start w32time

See also:   Start, stop, pause, resume, or restart a service; Configure how a service is started

Windows Time service generates event ID 7023 after upgrading to Windows Server 2003 with Service Pack 1 (SP1).

Cause: The LocalService account has not been granted "Change the system time" permissions. Windows Server 2003 with SP1 changes the startup configuration of the Windows Time service from LocalSystem to LocalService. Therefore, the startup account that the Windows Time service uses must have "Change the system time" permissions.

Solution: Use Domain Controller Security Policy to grant "Change the system time" permissions to the LocalService account. Alternatively, change the logon account of the Windows Time Service. For more information about performing these solutions, see article Q892501 "The Windows Time service may generate event ID 7023 after you upgrade to Windows Server 2003 Service Pack 1," in the Microsoft Knowledge Base.

See also: Change the system time; Permit users to log on locally to a domain controller

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.