Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >
article

KB-9551: Centrify Agent for Windows does not start after reboot

Authentication Service ,  

13 December,17 at 09:33 PM

Problem:

After restarting the server the Centrify agent for Windows does not start automatically as configured on the service. The service can be manually started without issue. 


Cause:

60 seconds is the default wait time for services. The service will fail to start if the dependent service is not started. In some instances the dependent service takes longer than the default wait time. 


Resolution:
 
  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
  3. In the right pane, locate the ServicesPipeTimeout entry. 
Note If the ServicesPipeTimeout entry does not exist, you must create it. To do this, follow these steps:​
  1. Type ServicesPipeTimeout, and then press ENTER.
  2. On the Edit menu, point to New, and then click DWORD Value
  • Right-click ServicesPipeTimeout, and then click Modify.
  • Click Decimal, type 180000, and then click OK.
    This value represents the time in milliseconds before a service times out.
  • Restart the computer.
 
For more information, please refer to the Microsoft KB article (provided as a courtesy):
http://support.microsoft.com/kb/922918
 

Still have questions? Click here to log a technical support case, or collaborate with your peers in Centrify's Online Community.