Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Update Rollup 5 for System Center 2016 Orchestrator


View products that this article applies to.

Introduction

This article describes the issues that are fixed in Update Rollup 5 for Microsoft System Center 2016 Orchestrator. This article also contains the installation instructions for this update.

↑ Back to the top


Issues that are fixed

  • When you view the activity details of a job instance, the Orchestrator Web Console displays the input parameter as a GUID instead of the Display Name of the parameter.
  • Job fails to execute when PowerShell reserved characters are passed as parameters to runbook.
  • RunbookServerMonitorService.exe and aspt.exe processes run successfully but create entries in the error logs.
  • Changes that you make to activities in a runbook are not saved consistently if the activities are not edited when they are added for the first time.
  • After you upgrade to Update Rollup 4 for System Center 2016 Orchestrator, the RunbookServerMonitorService service stops working because it cannot connect to the database.
  • The purge-the-logs command in the Runbook Designer fails after you apply Update Rollup 4 for System Center 2016 Orchestrator.
  • The Query Database task fails after you apply Update Rollup 4 for System Center 2016 Orchestrator.
  • Runbooks that use the Run Process task cause the Orchestrator server to slow down and face connectivity and performance issues.

↑ Back to the top


Known issues

  • When you use the Send Platform Event activity to create notifications (whether for problems or general information) that occur in a runbook, the activity is apparently successful. However, the event is not created.

    To work around this issue, run the following SQL script on the Orchestrator database:
    GRANT EXECUTE ON object::dbo.sp_insertevent TO [Microsoft.SystemCenter.Orchestrator.Runtime]
    GRANT EXECUTE ON object::dbo.sp_insertevent TO [Microsoft.SystemCenter.Orchestrator.Admins]

↑ Back to the top


How to obtain Update Rollup 5 for System Center 2016 Orchestrator

Important Before you install this update, make sure that the SQL Server Native Client is installed on the Management server role. For more information, see the Installing SQL Server Native Client topic on the Microsoft Docs website.

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

Windows Update

To obtain and install an update package from Windows Update, follow these steps on a computer that has an Orchestrator component installed:

  1. Select Start, and then select Control Panel.
  2. In Control Panel, double-click Windows Update.
  3. In the Windows Update window, select Check Online for updates from Microsoft Update.
  4. Select Important updates are available.
  5. Select the Update Rollup package, and then select OK.
  6. Click Install updates to install the update package.

Manual download

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

 Download the Orchestrator update package now.

Virus-scan claim

Microsoft scanned this file for viruses, using the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to it.

↑ Back to the top


Installation instructions for Orchestrator

Download the update packages that Microsoft Update provides for each computer. Microsoft Update provides the appropriate updates according to the components that are installed on each computer. Or manually download the update from the Microsoft Update Catalog.

If you upgrade Orchestrator 2016 to Update Rollup 5 without first having applied Update Rollup 4, the Orchestrator database must be reconfigured. After the Orchestrator updates are installed, reconfigure the Orchestrator database by using the existing database according to these guidelines.

↑ Back to the top


Files updated in this update rollup

Files that are updated in the Orchestrator update

The following is a list of files that have changed in this update rollup. If you do not have all previous update rollups installed, files other than those listed here may also be updated. For a complete list of files that are updated, see the "Files Updated in this update rollup" section of all update rollups that were released after your current update rollup.

File name

Version

Size

ManagementService.exe

7.3.273

807KB

RunbookServerMonitorService.exe

7.3.273

1.73 MB

RunbookService.exe

7.3.273

2.77 MB

RunbookDesigner.exe

7.3.273

3.03 MB

RunbookTester.exe

7.3.273

1.11 MB

aspt.exe

7.3.273

1.31 MB

PermissionConfig.exe

7.3.273

1.37 MB

OrchestratorRunProgramService.exe

7.3.273

85.4 KB

DBDataStore.dll

7.3.273

1.30 MB

Database-14-40801.op4saw

NA

249 KB

Database-14-40801.op4caw

NA

144 KB

Microsoft.SystemCenter.Orchestrator.Upgrade.sql

NA

↑ Back to the top


Keywords: kbqfe, kbfix, kbnotautohotfix, kbexpertiseinter, kbsurveynew

↑ Back to the top

Article Info
Article ID : 4094928
Revision : 21
Created on : 9/11/2018
Published on : 9/11/2018
Exists online : False
Views : 327