Update Rollup 2 for System Center Service Manager 2019

Applies to: System Center 2019 Service Manager


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

Issues that are fixed

  • Whenevera customer deletes service offering category, it will check if there are SO’son that category and prevent the category deletion. It will show an alert onconsole to delete the SO if they want to delete the category.
  • Surface devices imported by SCCM connector will not be marked as virtual machines.
  • End userwill still be able to update his other requests even if he is removed as anaffected user from one of his requests through Self Service Portal.
  • Userswill be able to scroll properly on all standard forms under work items tab.
  • Madeenhancements to the start-up time of the SDK service.
  • Endusers will now be able to read/update the manual activity from Self ServicePortal
  • When auser opens manual activity from any IR/CR and execute custom task, it willexecute without any error.
  • EachPortal Trace log now shows thread ID, Process ID, Date and Time in UTC
  • System Center Configuration Manager (SCCM) releases from 1806 to 2006 are supported with System Center Service Manager (SCSM) 2019 Update Rollup 2. However, it is recommended to follow the steps in "After the Installation".
  • Enables support for the MSOLEDBSQL driver on all Management Servers including Primary (Workflow), Data Warehouse and Secondary Management Servers, but only if the MSOLEDBSQL driver is installed. For more information how to install the MSOLEDBSQL driver, see Microsoft OLE DB driver for SQL Server.
          NoteSQLNCLI has been deprecated
  • Manual steps are required to use the MSOLEDBSQL driver together with SQL Server Analysis Server (SSAS). See the next section "Steps to change provider in SQL Server Analysis Server".

How to obtain Update Rollup 2 for System Center Service Manager 2019

Update packages for Service Manager are available by manual download. Go to the following website to manually download the update package from the Microsoft Download Center:

Installation instructions

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 without any Management Packs in “Pending Disassociation”, “Pending Association”, or “Imported” status.
  3. If you have customizations in the portal sidebar, take a backup of the Views\Shared\Sidebar.cshtml file.
  1. Make sure that the update is installed on the Service Manager components in the following order:
    • Data Warehouse Server
    • Primary Management Server
    • Secondary Management Servers
    • Self Service Portal Server
    • All Analyst Consoles
  2. 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.
  3. Open the target folder, and then right-click the downloaded file from step 1.
  4. Select Run as administrator.
  5. 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, merge the required changes in the updated Views\Shared\Sidebar.cshtml file.
     3. Restart the system that is hosting your portal server that is running IIS.
     4. Disable all the Data Warehouse jobs. To do this, open Service Manager shell and run the  following commands:
$DW ='DWMS Servername'
Get-scdwjob -Computername $DW | %{disable-scdwjobschedule -Computername $DW -jobname $_.Name}
Get-scdwjob -Computername $DW 
     5. Open SQL Management Studio with elevated privileges and connect to Analysis server > DWAS Database.
     6. Delete Cubes and Dimensions by following below steps.
  • Open new query window for XMLA query in SSMS as shown below

  • Copy and execute the below query to delete Cubes and Dimensions.
<Batch xmlns='http://schemas.microsoft.com/analysisservices/2003/engine' Transaction='true'>

<Delete xmlns='http://schemas.microsoft.com/analysisservices/2003/engine'>

<Delete xmlns='http://schemas.microsoft.com/analysisservices/2003/engine'>        

<Delete xmlns='http://schemas.microsoft.com/analysisservices/2003/engine'>      

<Delete xmlns='http://schemas.microsoft.com/analysisservices/2003/engine'>        

<Delete xmlns='http://schemas.microsoft.com/analysisservices/2003/engine'>

<Delete xmlns='http://schemas.microsoft.com/analysisservices/2003/engine'>      
<Delete xmlns='http://schemas.microsoft.com/analysisservices/2003/engine'>        


  • In Console, navigate to Administration tab and delete the following Four MPs
      1. Service Manager Power Management CubeLibrary 
      2. Service Manager Change and Activity Management Cube Library 
      3. Service Manager Software Update Cube Library 
      4. Service Manager Configuration Management Cube Library 
  • Synchronize Management Pack again and make sure the above four Management Packs are disassociated in Console > Data Warehouse > Data Warehouse Jobs > MPSyncJob

  • Open SQL Management Studio with elevated privileges and connect to Analysis server.
  • Navigate to DWDataMart > Script Data Source View as > ALTER To > New Query Editor Window.

  • Change the Datatype of PhysicalMemory in OperatingSystemDim table from int to decimal as shown

  • Change the Datatype of Size column under LogicalDiskDim Table from int to decimal

  • Repeat above two steps and change the column values on CMDataMart and OMDataMart
  • Execute the query, the Data Source Viewdatatypes will be changed.
  • In Service Manager console, Import the Cubes.mpb from Service Manager folder (C:\Program Files\Microsoft System Center\Service Manager) and Sync MP. All four Cube MPs should be associated now.
  • Run the MP sync again. Once complete, verify that all four Cube MPs are associated in Console > Data Warehouse > Data Warehouse Jobs > MPSyncJob.
  • Verify all Cubes and Dimensions are recreated in SSAS (Refresh cube folder to view them).

Steps to change provider in SQL Server Analysis Server

Important: Follow the below steps only after you have installed latest SQL driver (MSOLEDBSQL) on the SQL Server Analysis Server role. For more information how to install the MSOLEDBSQL, see Microsoft OLE DB driver for SQL Server.

  • Open SQL Server Management Studio and connect to Analysis Services role
  • Expand Databases > [Analysis Service DB] > Data Sources.
   Note: In this path, replace [Analysis Service DB] with the name of the actual Analysis Service database (usually DWASDataBase).
   Repeat the below steps for all listed Data Sources: 
  • Right-click a Data Source (like DWDataMart), and then select Properties.
  • Under General, select Connection String and replace the provider name from "SQLNCLI11" to "MSOLEDBSQL".
  • Under Security Settings. select Impersonation Info.
  • Provide the username and password if you are using Windows authentication, and then select OK.
  • Select OK.
  • Restart SQL Server Analysis Service from services.msc.

Files updated in this update rollup

The following is a list of files that have changed in this update rollup.

File nameFile versionFile size
MakeForm.cshtmlNot Applicable29KB
Index.cshtmlNot Applicable14KB
Sidebar.cshtmlNot Applicable6KB
RequestDetails.cshtmlNot Applicable18KB
SelfServicePortalResources.resxNot Applicable22KB
SelfServicePortalResources.pt-BR.resxNot Applicable23KB
SelfServicePortalResources.cs.resxNot Applicable23KB
SelfServicePortalResources.da.resxNot Applicable23KB
SelfServicePortalResources.de.resxNot Applicable23KB
SelfServicePortalResources.el.resxNot Applicable26KB
SelfServicePortalResources.en.resxNot Applicable22KB
SelfServicePortalResources.es.resxNot Applicable23KB
SelfServicePortalResources.fi.resxNot Applicable23KB
SelfServicePortalResources.fr.resxNot Applicable23KB
SelfServicePortalResources.hu.resxNot Applicable23KB
SelfServicePortalResources.it.resxNot Applicable23KB
SelfServicePortalResources.ja.resxNot Applicable24KB
SelfServicePortalResources.ko.resxNot Applicable23KB
SelfServicePortalResources.nl.resxNot Applicable23KB
SelfServicePortalResources.no.resxNot Applicable22KB
SelfServicePortalResources.pl.resxNot Applicable23KB
SelfServicePortalResources.pt.resxNot Applicable23KB
SelfServicePortalResources.ru.resxNot Applicable26KB
SelfServicePortalResources.sv.resxNot Applicable23KB
SelfServicePortalResources.tr.resxNot Applicable23KB
SelfServicePortalResources.zh-CHS.resxNot Applicable22KB
SelfServicePortalResources.zh-CHT.resxNot Applicable22KB
Config.xmlNot Applicable1KB
build_scdm_db.sqlNot Applicable505KB
build_scdw_db.sqlNot Applicable569KB
build_sm_db.sqlNot Applicable6965KB
build_mom_db_postMPimportSM.sqlNot Applicable88KB
Microsoft.Windows.Library.mpNot Applicable697KB
Microsoft.Windows.Peripheral.Library.mpNot Applicable61KB
Microsoft.EnterpriseManagement.ServiceManager.Connector.Sms.mpNot Applicable73KB
Microsoft.EnterpriseManagement.ServiceManager.Connector.Sms2011.mpNot Applicable73KB
Microsoft.SystemCenter.InstanceGroup.Library.mpNot Applicable37KB
System.AdminItem.Library.mpNot Applicable53KB
ConfigManagementPack.mpbNot Applicable380KB
System.Software.Library.mpbNot Applicable80KB
System.Library.mpNot Applicable53KB
Authoring.mpbNot Applicable281KB
Incident.mpbNot Applicable976KB