How to Work Around Configuration Service Startup Issues

Applies To: System Center 2012 R2 Service Manager, System Center 2012 SP1 - Service Manager

If an upgrade to Service Manager in System Center 2012 R2 fails because startup of the System Center Management Configuration service times out, you can try to resolve the issue by using one of the following workaround procedures:

  • Disable signature verification on the computer that is running Setup.

  • Increase the service time-out setting on the computer that is running Setup.

To disable signature verification

  1. On the computer that is running Setup, open the Microsoft.Mom.ConfigServiceHost.exe.config file, which is located in the Program Files\Microsoft System Center 2012\Service Manager folder.

  2. In the <runtime></runtime> section, add <generatePublisherEvidence enabled="false"/>.

  3. Save the changes to the file.

  4. Attempt the upgrade again.

To increase the service time-out setting

  1. On the computer that is running Setup, create the following registry value to increase the service time-out period.



    Incorrectly editing the registry may severely damage your system. Before you make changes to the registry, you should back up any valued data on the computer.


    You may have to increase this value further if the service still fails to start. The value in this example is in milliseconds. For additional details about the registry key, see A service does not start, and events 7000 and 7011 are logged in Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2.

  2. Restart the computer.

  3. Attempt the upgrade again.

For additional resources, see Information and Support for System Center 2012.

Tip: Use this query to find online documentation in the TechNet Library for System Center 2012. For instructions and examples, see Search the System Center 2012 Documentation Library.