Export (0) Print
Expand All

Release Notes for Orchestrator in System Center 2012 R2


Updated: May 13, 2016

Applies To: System Center 2012 R2 Preview, System Center 2012 R2 Orchestrator

Before you install and use Orchestrator in System Center 2012 R2, read these release notes.

Description: Signature block comments are present in SMA sample runbooks, which will cause the runbooks to fail to run if called by another runbook.

Workaround: Remove the signature block at the end of the sample runbook. To remove the signature block, edit the runbook and remove the whole signature block, which has a beginning line of # SIG # Begin signature block and an ending line of # SIG # End signature block. After removal, save the runbook and then publish it.

Description: If the computer you are installing the Service Management Automation (SMA) feature on is not part of a domain, the SMA Web service and the SMA Runbook Worker installation will fail.

Workaround: Ensure the computer has been joined to a domain beforehand.

Description: When trying to deploy an IP or execute a runbook on a computer running Windows Server 2012 or Windows Server 2012 R2 on which .NET Framework 3.5 is not enabled, the execution will fail.

Workaround: Enable .NET Framework 3.5 manually on the computer running Windows Server 2012 or Windows Server 2012 R2 and try again.

Description: If you create a custom Enum value that duplicates the name of an existing Enum value, the activity will fail.

Workaround: All customized Enum values must have names that are different from all other Enum values.

Description: After deploying the IP for Service Manager in System Center 2012 SP1 to the runbook server, the Orchestrator server is automatically restarted without any further notice.

Workaround: None. The computer must be restarted so that the Service Manager IP can update some of the binary files that have been used.

Description: For example, on a runbook server that is running Windows Server 2012, start a runbook containing a Run Program activity that has been configured to run notepad.exe in Interactive mode. Notepad.exe is started as a background process instead of as a foreground process.

Workaround: In the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Windows, the value for the NoInteractiveServices subkey defaults to 1, which means that no service is allowed to run interactively, regardless of whether it has SERVICE_INTERACTIVE_PROCESS. When NoInteractiveServices is set to a 0, services with SERVICE_INTERACTIVE_PROCESS are allowed to run interactively. Change the value of the NoInteractiveServices subkey to 0, and then restart the computer.

© 2016 Microsoft