Update Rollup 5 for System Center 2016 Service Manager (original) (raw)

Applies To

System Center 2016 Service Manager

Introduction

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

Issues that are fixed

• System Center Operations Manager (SCOM) Console and System Center Service Manager (SCSM) Console or PowerShell components can now coexist on the same server. Notice that Update Rollup 5 for System Center 2016 Operations Manager must also be installed to resolve this issue.
• The date and time format in some views is made to be consistent with the settings on the local computer.
• SCSM Console is fixed to release the memory that is used as soon as the respective window (UI) is closed.
• Fixes console crashes (non en-us locale) that occur when importing a connector as a CSV file.
• Fixes console crashes that occur when it is brought back into focus after it is left out of focus for some time.
• Introduces indexes to make the workflow status view load faster.
• Data Warehouse (DW) Cube processing is made faster (query enhancement), thereby preventing stale reports.
• DateDim tables in DWDataMart are now extended until 12/31/2050.
• Fixes TargetWarningDate in Service Level Objects (SLO) so that it considers the working hours and days as defined in the associated calendar.
• Fixes an issue that occurs when you create requests that include files as attachments in Self Service Portal that generates erroneous failure messages when the requests are successfully generated.
• For synchronizing the Active Directory connector with a specific Domain Controller, users can now specify the Domain Controller in the LDAP query of the Active Directory connector.
• Service Manager connectors for Configuration Manager now supports Configuration Manager 1802.

Known issues and resolution

The time format in some views, such as Workitems/IncidentManagement/All Incident, is not consistent with the system locale settings. This behavior may occur when you work with views in unsealed Management Packs (MP). To resolve this issue, follow the steps:

1. Export the Service Manager Incident Management Configuration Library management pack.
2. Modify the management pack. Locate the "LastModified" column and modify the binding path as follows:
   Before modification<mux:Column Name="lastModified" DisplayMemberBinding="{Binding Path=$LastModified$, Mode=OneWay}" Width="150" DisplayName="Header_Last_Modified" Property="$LastModified$" DataType="s:DateTime" />After modification<mux:Column Name="lastModified" DisplayMemberBinding="{datebinding:DateBinding Path=$LastModified$, Mode=OneWay}" Width="150" DisplayName="Header_Last_Modified" Property="$LastModified$" DataType="s:DateTime" />
3. Repeat steps 1–2 for columns that are named “LastModified.”
4. Re-import the modified management pack.
5. Restart the console.

How to obtain Update Rollup 5 for System Center 2016 Service Manager

Update packages for Service Manager are available by manual download.

Manual download

Go to the following website to manually download the update package from the Microsoft Download Center:

Download the Service Manager update package now.

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.

Installation instructions for Service Manager

Before the installation

Before you apply this update, follow these steps:

1. Exit all Service Manager-related applications before you apply this update. For example, exit the Service Manager Console, the Self-Service Portal links, and the authoring tool.
2. Make sure that the Data Warehouse Server has successfully synchronized with the Management Server at least one time.
3. Make sure that the update is installed on the Service Manager components in the following order:
   1. Data Warehouse Server
   2. Primary Management Server
   3. Secondary Management Servers
   4. Self Service Portal Server
   5. All Analyst Consoles
4. If you have customizations in the portal sidebar, edit the sidebar by using the steps in the "Customizing the left menu bar" section of Deploy the new Self-Service Portal.
5. Make a backup of the Views\Shared\Sidebar.cshtml file.

Installation

1. Download the update to a target folder. This update contains both the x86-based version and the x64-based version. Download the appropriate version for your system.
2. Open the target folder, and then right-click the downloaded file from step 1.
3. Select Run as administrator.
4. Accept the Microsoft Software License Terms, and then follow the steps in the installation wizard.

After the installation

1. Restart all the consoles as soon as the update is installed.
2. If any customizations were backed up for the portal sidebar (as mentioned in "Before the installation" steps), merge the required changes in the updated Views\Shared\Sidebar.cshtml file.
3. Restart the system that is hosting your portal server running IIS.

Files updated in this update rollup

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.

Need more help?

Want more options?

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