FIX: Threat Management Gateway 2010: A Windows Server 2008 R2-based computer stops responding at startup, or no Automatic services start after the computer restarts


A Windows Server 2008 R2-based computer that is running Microsoft Threat Management Gateway (TMG) 2010 stops responding for a period of time when the computer settings are applied at startup, or some of the Automatic services do not start after the computer restarts.


This problem may occur because of a missing service dependency that causes a deadlock condition in isactrl (mspadmin). When this occurs, isactrl (mspadmin) cannot set its state to SERVICE_RUNNING.


To resolve this problem, install the service pack that is described in the following Microsoft Knowledge Base article:
2555840  Microsoft Forefront Threat Management Gateway 2010 Service Pack 2


To work around this problem, change the HTTP dependency settings on isactrl on TMG servers. To do this, run the following command: 
sc config isactrl depend=RasMan/SSTPSVC/FwEng/ISASTG/bfe/mpssvc/HTTP


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

If you do not require SSTP-based VPN, you can help prevent the deadlock from occurring by using the registry change that is described in the following Microsoft Knowledge Base article:
2004121 Windows Server 2008 computers hang during startup while "applying computer settings" and services configured to start automatically fail to start


For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates


رقم الموضوع: 2599064 - آخر مراجعة: 17‏/10‏/2011 - المراجعة: 1