WS2008R2 – Windows Time service doesn’t start during server boot on Windows 2008 R2 server in a work group environment

Even if you set Windows Time service to Automatic start, it stops within a few seconds. Why?

Event ID 7042 is logged in system event logs on windows 2008 R2 server which is part of work group environment and this can lead to time sync issues on the server that hosts critical applications in the DMZ environment.

In Windows 2008 R2 the newly implemented time service is by default set as trigger start-up service which means the service will start when a specific event is triggered in the system depending on the trigger info configured in the registry for that service.
Background services and processes can have a substantial impact on the overall performance of the system. Trigger activation service has been implemented as a new feature, and reduce the total number of services that start automatically In 2008 R2 Windows Server, and the like to reduce the power consumption to improve performance, and increase the stability of the whole system . It is extended by this, the Service Control Manager, to be able to perform the start and stop the service by certain system events.

For example the trigger info might contain start service when the client is domain joined or start the service when the client has IP address assigned to it.

The name of the log: System
Source: Service Control Manager
Event ID: 7042
Level: Information
Stop control has been sent successfully to the Windows Time service. Reason it is specified: 0x40030011 [Operating System: Network connection (planned)]

The setting contents of the trigger service, which can be determined by running the command sc qtriggerinfo following.

sc qtriggerinfo w32time
Service Name: w32time










To start the Windows Time service from the system start-up, we can use one of the following methods.

Method 1:
Run the following command to remove the trigger events that are registered by default, change the from Manual to Automatic startup type of the Windows Time service.
sc triggerinfo w32time delete

Method 2:
Run the following command, you can define the trigger events that are appropriate for your environment.
As an example, it is determined if the IP address is granted to the host, and stop or start service here.

sc triggerinfo w32time start / networkon stop / networkoff


About asifkhandevadi

Hello, I have been working on windows since 9 years and currently working as windows, VMware and MS clustering SME at IBM. Whenever I get free time I participate in Microsoft forums and write some blogs to enhance my technical and communication skills through knowledge sharing. Please contact me on FB or Linkedin if you need any assistance on troubleshooting, implementation and virtualizaton.
This entry was posted in Windows, Windows Troubleshooting and tagged , , , , , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s