Sign in with Microsoft
Sign in or create an account.
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.


This article describes the issues that are fixed in Update Rollup 2 for Microsoft System Center 2012 R2 Orchestrator and Service Management Automation (SMA). Additionally, this article contains the installation instructions for Update Rollup 2 for System Center 2012 R2 Orchestrator and SMA.

Note This update is not currently available for download. If you have already installed the update, you must take steps to work around an issue that has been discovered. For more information, please see the "Installation instructions" section.

More Information

Issues that are fixed in this update rollup


Issue 1

After you add more than nine variable bindings to a Send SNMP Trap activity, the variable binding orders change immediately when you exit the Send SNMP Trap Activity Properties dialog box.


The Monitor Service activity does not allow the configuration to be saved if it cannot resolve the hostname that is populated into the Computer input property. Therefore, if you use a variable or computer group to populate the Computer input property, you receive a “Connection to the selected computer has failed” error message, and you cannot save the activity configuration. This prevents you from using variables or computer groups with this activity.

Service Management Automation (SMA)

Issue 1

When you use the Automation menu in the Service Management Administration portal, you notice that the controller does not return modules data. Additionally, SMA may not clean up the temp files. Therefore, you may hit the maximum allowed number of temp files.

Issue 2

When a runbook calls other runbooks, SMA concatenates all the participating runbooks into a single script and then passes it to the Windows PowerShell workflow engine for compilation. The resulting script may contain multiple signature blocks. If this occurs, SMA receives a compilation error from PSFW.

Issue 3

When child runbooks contain a signature block that they cannot compile into inline runbooks, all runbooks are compiled into a single runbook. However, if there is more than one signature block, the resulting runbook will be corrupted.

Issue 4

Cmdlets make a single request for information from the server instead of making requests in paginated form up to an allowable limit until all information is retrieved. A single request that exceeds the allowable limit can time out.

Issue 5

SMA resources are paged. The cmdlets have to evaluate the response from the web service for the existence of a continuation token. If the token exists, the cmdlets have to make a sequence of ListNext web requests.

Issue 6

When a PowerShell user runs a Set-SmaCertificate cmdlet, they cannot obtain its private key information when they use the Get-AutomationCertificate activity.

Installation instructions

We have found an issue that affects the Runbook worker update for Update Rollup 2 for Microsoft System Center 2012 R2 – Orchestrator Service Management Automation Runbook Worker (KB 2904689). Therefore, we have temporarily removed this update from the Microsoft Update Catalog. The update incorrectly resets the Microsoft SQL Server connection from the Runbook Worker to the database so that new jobs do not get processed by the Runbook Worker.

If you have already downloaded and installed this update, you must perform the following task:

  • If you are using Windows Authentication from the runbook worker to the SMA database:

    • Change the \Program Files\Microsoft System Center 2012 R2\Service Management Automation\Orchestrator.Settings.config file to restore the correct information to your SMA server and database, as follows. <!--SQL connection information--> <add key="Server" value="SQL-Server-Computer"/> <add key="Database" value="SMA Database Name"/> <add key="Authentication" value="Windows"/>

    • Alternatively, you can uninstall and reinstall the Runbook Worker to obtain the correct connection settings.

  • If you are using SQL authentication from the runbook worker to the SMA database, uninstall the Runbook Worker, and then reinstall it to correctly set these connection settings.

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?

Thank you for your feedback!