Share via

  • Article

How to Configure Runbook Servers to Optimize Performance of .NET Activities

 

Updated: May 13, 2016

Applies To: System Center 2012 SP1 - Orchestrator, System Center 2012 - Orchestrator, System Center 2012 R2 Orchestrator

If a runbook contains an activity that references the .NET libraries, the first reference to the .NET libraries takes additional time to initialize. This delay can be as much as 30 seconds. All remaining activities that reference the .NET libraries run immediately. This delay can also occur when a runbook is started on a computer without Internet access, because then Windows cannot verify the Microsoft Authenticode signature for the .NET libraries, and this causes a delay during the initialization of the activity.

The solution to removing the delay is to deactivate generatePublisherEvidence in PolicyModule.exe or to create a profile for the service account.

To deactivate generatePublisherEvidence in policymodule.exe.config

  1. On the runbook server where runbooks that contain an activity referencing the .NET libraries run, locate the file C:\Program Files (x86)\Microsoft System Center 2012\Orchestrator\Runbook Server\policymodule.exe.config.

  2. Add the following code to policymodule.exe.config:

    <runtime>  
      <generatePublisherEvidence enabled="false"/>  
</runtime>

To create a profile for the service account

  • On the runbook server where runbooks run that contain an activity referencing the .NET libraries, log on to the computer that is using the service account credentials. A profile is created on first logon.

See Also

Administering System Center 2012 - Orchestrator