Update Rollup 3 for System Center 2012 R2 Orchestrator

Update Rollup 3 for System Center 2012 R2 Orchestrator

 

Hello IT Pros/Geeks, finally Microsoft has released the UR3 for System Center 2012 R2 and it will be fixing a lot of issues that came up with the UR2. Hope this help you guys, please let me know if you have any issues and I will be happy to help.

Issues that are fixed in this update rollup

Orchestrator

• When a runbook calls other runbooks, Service Management Automation (SMA) concatenates all the participating runbooks into a single script and then passes the script to the PowerShell Workflow engine for compilation. The resulting script may contain multiple signature blocks, and SMA receives a compilation error from the Powershell Workflow.
• When child runbooks contain a signature block, the child runbooks cannot be compiled into inline runbooks. If there is more than one signature block, the resulting runbook will be corrupted.
• Cmdlets should request information from the server, up to a limit on the number of records that are returned, and then request the next "page" of records, until all records are retrieved.
• When a Windows PowerShell user uses the Set-SmaCertificate cmdlet, the user cannot receive private key information when he or she uses the Get-AutomationCertificate activity.
• The Automation menu stops working in Administrator Portal, and you may notice that the Orchestrator ODATA API controller cannot return Modules data. Additionally, you receive the following error message:
  
  Microsoft.Data.OData.OdataInnerError
  Message: The file exists.
  TypeName: System.IO.IOException
• Service Management Automation (SMA) resources are paged. The cmdlets have to evaluate the response from the web service for the presence of a continuation token and then make a sequence of ListNext web requests if a continuation token is present.
• SMA may not return the latest job ID for the runbook. The Invoke-ConfiguratorRunbook activity will have the job ID when it calls the Start-SMARunbook cmdlet, and the job ID should be returned to the caller. This occurs because SMA does not return the most recent job for a runbook. This issue occurs occur in a multiple-run scenario. If the configurator passes the first run, this issue has no effect.
• The Orchestrator Runbook Service (RunbookService.exe) may crash, and you receive the following error message:
  
  Application: RunbookService.exe
  Framework Version: v4.0.30319
  Description: The process was terminated due to an unhandled exception.
  Exception Info: System.ServiceModel.CommunicationException

• If a runbook is large enough to exceed the default Windows Communication Foundation (WCF) channel size, an exception occurs. This issue causes the job to be stuck in the "New" state.

• When Update Rollup 2 is uninstalled, the connection properties to the instance of Microsoft SQL Server are cleared.

Back to the top | Give Feedback

How to obtain and install Update Rollup 3 for System Center 2012 R2 Orchestrator

Download information

Update packages for Orchestrator are available from Microsoft Update or by manual download.

Microsoft Update

To obtain and install an update package from Microsoft Update, follow these steps on a computer that has an applicable System Center 2012 R2 component installed:

1. Click Start, and then click Control Panel.

2. In Control Panel, double-click Windows Update.

3. In the Windows Update window, click Check Online for updates from Microsoft Update.

4. Click Important updates are available.

5. Select the Update Rollup packages that you want to install, and then click OK.
6. Click Install updates to install the selected update packages.

Manual download of the update packages

Go to the following website to manually download the update packages from the Microsoft Update Catalog:

 

Collapse this imageExpand this image

Download the Orchestrator update package now.

(http://catalog.update.microsoft.com/v7/site/Search.aspx?q=2931268)

Back to the top | Give Feedback

Installation instructions

To apply the Orchestrator update, follow these steps:

1. Install the Setup fix. To do this, follow these steps:
1. Download the kb2980272_WorkerInstaller_x64.cab file.
2. Extract the kb2980272_WorkerInstaller_x64.msp file.
3. In Windows Explorer, double-click the kb2980272_WorkerInstaller_x64.msp file. Or, at a command prompt, type the following command, and then press Enter:
   
   msiexec.exe /update kb2980272_WorkerInstaller_x64.msp

2. Install the PowerShell Module Update. To do this, follow these steps:
1. Download the kb2931268_PowerShellModuleInstaller_x64.cab file.
2. Extract the kb2931268_PowerShellModuleInstaller_x64.msp file.
3. In Windows Explorer, double-click the kb2931268_PowerShellModuleInstaller_x64.msp file. Or, at a command prompt, type the following command, and then press Enter:
   
   msiexec.exe /update kb2931268_PowerShellModuleInstaller_x64.msp

3. Install the Web Service Update. To do this, follow these steps:
1. Download the kb2931268_WebServiceInstaller_x64.cab file.
2. Extract the kb2931268_WebServiceInstaller_x64msp file.
3. In Windows Explorer, double-click the kb2931268_WebServiceInstaller_x64.msp file. Or, at a command prompt, type the following command, and then press Enter:
   
   msiexec.exe /update kb2931268_WebServiceInstaller_x64.msp

4. Install the Worker Update. To do this, follow these steps:
1. Download the kb2931268_WorkerInstaller_x64.cab file.
2. Extract the kb2931268_WorkerInstaller_x64.msp file.
3. In Windows Explorer, double-click the kb2931268_WorkerInstaller_x64.msp file. Or, at a command prompt, type the following command, and then press Enter:
   
   msiexec.exe /update kb2931268_WorkerInstaller_x64.msp