Service Control Manager times out at 30 seconds, when starting Agent Client CollectorIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } When its host server/computer restarts, Agent Client Collector may not start. Symptoms<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Error 1053: The service did not respond to the start or control request in a timely fashion Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Any. Cause<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } When Windows starts, as well as the OSes own services, and any application server services running, there are usually a lot of 3rd party services, such as management and security agents, and other applications that will run on startup at the same time. Agent Client Collector runs as a Windows Service, set to start Automatically, with Delayed Start. A service marked as 'Automatic (Delayed Start)' will start shortly after all other services designated as 'Automatic' have been started. That already should help with computers that are under high load during startup. However Windows Service Manager will only give the service 30 seconds by default to start. That may not be long enough. And if the Agent is not running, ServiceNow code can do nothing about retrying that startup. Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Several registry changes might help: Table of Contents Increase the global service start timeout from 30s, to perhaps 60s Delay the start even longerUse 3rd party software to Retry the startup after it has failedUse a scheduled script to Start it if it is stopped Increase the global service start timeout from 30s, to perhaps 60s Searching 'ServicesPipeTimeout' will allow you to find many articles on the internet on this topic. Note: This is a global setting affecting all services. Name: ServicesPipeTimeoutType: REG_DWORDData: The number of milliseconds that you want to give the services to start in. To create this registry entry, follow these steps: Click Start, click Run, type regedit, and then click OK.Locate and then click the following registry subkey:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ControlRight-click Control, point to New, and then click DWORD Value.In the New Value #1 box, type ServicesPipeTimeout, and then press ENTER.Right-click ServicesPipeTimeout, and then click Modify.Click Decimal, type the number of milliseconds that you want to wait until the service times out, and then click OK.For example, to wait 60 seconds before the service times out, type 60000.Quit Registry Editor, and then restart the computer. Delay the start even longer Searching 'AutoStartDelay' will allow you to find many articles on the internet on this topic. Globally by default this is 120s. This can be set on just the Agent Client Collector service. Click Start, click Run, type regedit, and then click OK.Locate and then click the following registry subkey:Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\AgentClientCollectorRight-click Control, point to New, and then click DWORD ValueIn the New Value #1 box, type AutoStartDelay, and then press ENTER.Right-click AutoStartDelay, and then click Modify.Click Decimal, type the number of milliseconds that you want to wait, and then click OK.e.g. 240000 is 240 secondsQuit Registry Editor, and then restart the computer. Use 3rd party software to Retry the startup after it has failed Applications exist to manage Windows Services. A quick google finds e.g. PRTG Network Monitor, ManageEngine Free Windows Service Monitor, and Netwrix Service Monitor. Warning: In theory this might interfere with self-upgrades, or planned maintenance of the configuration of the Agent by your own automation. Use a scheduled script to Start it if it is stopped 'net start' will start a service. If it is already running, it does nothing, so it is safe to run as many times and as often as you need. In a regularly scheduled script, this would start it again if it was stopped or hadn't started yet. net start AgentClientCollector Warning: In theory this might interfere with self-upgrades, or planned maintenance of the configuration of the Agent by your own automation.