Release Notes for Orchestrator in System Center 2012 SP1
Updated: November 1, 2013
Applies To: System Center 2012 R2 Orchestrator, System Center 2012 SP1 - Orchestrator
These release notes contain information that is required to successfully install Orchestrator in System Center 2012 Service Pack 1 (SP1). They contain information that is not available in the product documentation.
Before you install and use Orchestrator, read these release notes. These release notes apply to Orchestrator in System Center 2012 SP1.
If you are looking for the Release Notes for the original release of System Center 2012 - Orchestrator, see Release Notes for System Center 2012 - Orchestrator.
Setup program will fail when deploying IPs or executing runbooks on a computer running Windows Server 2012 without .NET 3.5 enabled.
Description: When trying to deploy an IP or execute a runbook on a computer running Windows Server 2012 on which .NET 3.5 is not enabled, the execution will fail.
Workaround: Enable .NET 3.5 manually on the computer running Windows Server 2012 and try again.
System Center 2012 - Service Manager IP: Custom Enum value that duplicates an existing Enum value causes activity to fail.
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.
System Center 2012 - Service Manager IP: the Orchestrator server restarts after deploying the IP
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.
When running Orchestrator on Windows Server 2012, the Run Program activity doesn't work in Interactive mode
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.
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.