Upgrade System Center Service Manager

Important

Service Provider Foundation (SPF) is discontinued from System Center 2025. However, SPF 2022 will continue to work with System Center 2025 components.

This article provides the upgrade information for System Center 2025 - Service Manager (SM)

Upgrade to System Center 2025 - Service Manager

The following sections provide information about how to upgrade to System Center 2025 - Service Manager (SM).

Warning

The order in which you perform component upgrades is important. Failure to follow the correct upgrade sequence might result in component failure for which no recovery options exist. The affected System Center components are:

• Orchestrator
• Service Manager
• Data Protection Manager
• Operations Manager
• Configuration Manager
• Virtual Machine Manager
• App Controller

You can only upgrade to System Center 2025 from System Center 2022.

Important

It's assumed in this guide that you're performing an upgrade to an existing System Center version. For information about installing System Center 2025 - Service Manager on a computer where no previous version of Service Manager exists, see deploying System Center - Service Manager.

Plan the upgrade to System Center 2025 - Service Manager

This section outlines the procedures necessary to upgrade to System Center 2025.

An in-place upgrade from Service Manager 2022 is supported. An in-place upgrade is an upgrade of all Service Manager parts on the same hardware. Other approaches, such as side-by-side upgrades or rolling upgrades, aren't supported.

Upgrading to Service Manager 2025 requires preparation. We recommend that you install Service Manager in a lab environment and then replicate your production databases into the lab. After that perform an upgrade of the new installation in the lab.

Evaluation and select versions

The release of System Center 2022 - Service Manager was available in two different versions:

• Evaluation version (180-day time-out)
• Select license version

The following upgrade paths are supported to Service Manager 2025.

Current Version	Upgraded Version	Status
System Center 2022 - Service Manager Eval	System Center 2025 - Service Manager Eval	Evaluation period remains unchanged
System Center 2022 - Service Manager Select	System Center 2025 - Service Manager Select	Licensed

Note

Upgrading from an evaluation version of Service Manager to an evaluation version of Service Manager 2025 doesn't extend the 180 days evaluation period.

Installation location

The default folder for installing Service Manager is \Program Files\Microsoft System Center\Service Manager. However, when you perform the upgrade to Service Manager, the software is installed in the folder that Service Manager previously used.

Hardware requirements for System Center 2025 - Service Manager

All hardware requirements for System Center 2025 - Service Manager are fully documented in Hardware Requirements.

Software requirements for System Center 2025 - Service Manager

All software requirements for System Center 2025- Service Manager are fully documented in Software Requirements.

Preventing MPSync jobs from failing

Before Upgrade

Description: A problem with the upgrade process causes MPSync job to fail after the upgrade is complete. To prevent this problem before you upgrade, you must run the SQL script mentioned below on the DWRepository database to get the actual SQL scripts that drop and add a constraint on the primary key in fact tables in the DWRepository database to correct the problem. Additionally, transform and load jobs might also fail. This error can occur because of erroneous database grooming.

;WITH FactName  
AS (  
       select w.WarehouseEntityName from etl.WarehouseEntity w  
       join etl.WarehouseEntityType t on w.WarehouseEntityTypeId = t.WarehouseEntityTypeId  
       where t.WarehouseEntityTypeName = 'Fact'  
),FactList  
AS (  
    SELECT  PartitionName, p.WarehouseEntityName,  
            RANK() OVER ( PARTITION BY p.WarehouseEntityName ORDER BY PartitionName ASC ) AS RK  
    FROM    etl.TablePartition p  
       join FactName f on p.WarehouseEntityName = f.WarehouseEntityName  
)  
, FactPKList  
AS (  
    SELECT  f.WarehouseEntityName, a.TABLE_NAME, a.COLUMN_NAME, b.CONSTRAINT_NAME, f.RK,  
            CASE WHEN b.CONSTRAINT_NAME = 'PK_' + f.WarehouseEntityName THEN 1 ELSE 0 END AS DefaultConstraints  
    FROM    FactList f  
    JOIN    INFORMATION_SCHEMA.KEY_COLUMN_USAGE a ON f.PartitionName = a.TABLE_NAME  
    JOIN    INFORMATION_SCHEMA.TABLE_CONSTRAINTS b ON a.CONSTRAINT_NAME = b.CONSTRAINT_NAME AND b.CONSTRAINT_TYPE = 'Primary key'  
)  
, FactWithoutDefaultConstraints  
AS (  
    SELECT  a.*  
    FROM    FactPKList a  
    LEFT JOIN FactPKList b ON b.WarehouseEntityName = a.WarehouseEntityName AND b.DefaultConstraints = 1  
    WHERE   b.WarehouseEntityName IS NULL AND a.RK = 1  
)  
, FactPKListStr  
AS (  
    SELECT  DISTINCT f1.WarehouseEntityName, f1.TABLE_NAME, f1.CONSTRAINT_NAME, F.COLUMN_NAME AS PKList  
    FROM    FactWithoutDefaultConstraints f1  
    CROSS APPLY (  
                    SELECT  '[' + COLUMN_NAME + '],'  
                    FROM    FactWithoutDefaultConstraints f2  
                    WHERE   f2.TABLE_NAME = f1.TABLE_NAME  
                    ORDER BY COLUMN_NAME  
                FOR  
                   XML PATH('')  
                ) AS F (COLUMN_NAME)  
)  
SELECT  'ALTER TABLE [dbo].[' + f.TABLE_NAME + '] DROP CONSTRAINT [' + f.CONSTRAINT_NAME + ']' + CHAR(13) + CHAR(10) +  
        'ALTER TABLE [dbo].[' + f.TABLE_NAME + '] ADD CONSTRAINT [PK_' + f.WarehouseEntityName + '] PRIMARY KEY NONCLUSTERED (' + SUBSTRING(f.PKList, 1, LEN(f.PKList) -1) + ')' + CHAR(13) + CHAR(10)  
FROM    FactPKListStr f  

Workaround 1: If you've already upgraded and you don't have problems with transform or load job failures but do have a management pack deployment failure, then follow the steps in the Before Upgrade section. In addition, after the default primary keys have been restored, restart the failed management pack deployment in the Service Manager console by navigating to the Data Warehouse workspace and then select Management Pack.

Workaround 2: If you've upgraded and you've problems with transform or load job failures, then determine if the SystemDerivedMp.Microsoft.SystemCenter.Datawarehouse.Base management pack exists in the DWStagingAndConfig database by running the following query.

select * from ManagementPack where mpname like '%SystemDerivedMp.Microsoft.SystemCenter.Datawarehouse.Base%'  

If the management pack doesn't exist, you need to restore your database to a state prior to upgrade. To restore your database, perform the following steps.

1. Perform disaster recovery steps for the database backups.

2. Disable the MPSyncJob schedule.

3. Restore all the missing primary keys in the DWRepository manually. You can drop and recreate the primary key using the SQL script from the Before Upgrade section.

4. Restart the failed base management pack deployment using the Service Manager console.

Test the upgrade in a lab environment

We recommend that you test the upgrade to System Center 2025 - Service Manager in a lab environment.

Upgrade order and timing

The order of your upgrades is important. Perform the upgrade steps in the following order:

1. Back up your databases and your management packs. See the sections Backing Up Service Manager Databases and Backing Up Unsealed Management Packs in the Disaster Recovery Guide for System Center - Service Manager.

2. Start with the data warehouse management server.

3. After the upgrade to the data warehouse management server is complete, upgrade the initial Service Manager management server. If you created more than one Service Manager management server, the initial Service Manager management server is the first one that you created.

4. Then upgrade all Secondary management servers, Self-Service Portals, and Service Manager consoles.

After the installation, do the following:

1. Disable all the Data Warehouse jobs. To do this, open the Service Manager shell, and then run the following commands:

   $DW ='DWMS Servername'
   
   Get-scdwjob -Computername $DW | %{disable-scdwjobschedule -Computername $DW -jobname $_.Name}
   

2. Make the required changes in the following PowerShell script based on the data source views in your environment, and then run the script by using elevated privileges:

   $SSAS_ServerName = "ssas servername" # - to be replaced with Analysis Service instance Name
   
   [System.Reflection.Assembly]::LoadWithPartialName("Microsoft.AnalysisServices")
   $Server = New-Object Microsoft.AnalysisServices.Server
   $Server.Connect($SSAS_ServerName)
   $Databases = $Server.Databases
   $DWASDB = $Databases["DWASDataBase"]
   
   #update DWDatamart dsv. Comment the below 3 commands if DWdatamart dsv is not present 
   
   $DWASDB.DataSourceViews["DwDataMart"].Schema.Tables["OperatingsystemDim"].Columns["PhysicalMemory"].DataType  =  [decimal] 
   
   $DWASDB.DataSourceViews["DwDataMart"].Schema.Tables["LogicalDiskDim"].Columns["Size"].DataType  =  [decimal] 
   
   $DWASDB.DataSourceViews["DwDataMart"].Update([Microsoft.AnalysisServices.UpdateOptions]::ExpandFull) 
   
   #update CMDatamart dsv.Comment the below 2 commands if cmdatamart dsv is not present 
   
   $DWASDB.DataSourceViews["CMDataMart"].Schema.Tables["OperatingsystemDim"].Columns["PhysicalMemory"].DataType  =  [decimal] 
   
   $DWASDB.DataSourceViews["CMDataMart"].Update([Microsoft.AnalysisServices.UpdateOptions]::ExpandFull) 
   
   #update OperatingsystemDim
   $DWASDB.Dimensions["OperatingsystemDim"].Attributes["PhysicalMemory"].KeyColumns[0].DataType =  [System.Data.OleDb.OleDbType]::Double 
   
   $DWASDB.Dimensions["OperatingsystemDim"].Update([Microsoft.AnalysisServices.UpdateOptions]::ExpandFull + [Microsoft.AnalysisServices.UpdateOptions]::AlterDependents)
   #update LogicalDiskDim 
   
   $DWASDB.Dimensions["LogicalDiskDim"].Attributes["Size"].KeyColumns[0].DataType =  [System.Data.OleDb.OleDbType]::Double 
   
   $DWASDB.Dimensions["LogicalDiskDim"].Update([Microsoft.AnalysisServices.UpdateOptions]::ExpandFull + [Microsoft.AnalysisServices.UpdateOptions]::AlterDependents) 
   
   

3. Enable the job schedules by running the following commands:

   $DW ='DWMS Servername'
   
   Get-scdwjob -Computername $DW | %{enable-scdwjobschedule -Computername $DW -jobname $_.Name}
   

4. Restart the Data Warehouse management server.

5. Apply the System Center 2025 Service Manager to the Data Warehouse management server, Primary management server, Secondary management server(s), Self-Service Portal(s), and all Analyst consoles.

Database impacts

With System Center 2025 - Service Manager, you've the option to install Operations Manager and Configuration Manager data marts. Selecting this option will result in additional space requirements on the hard disk drive for the two databases, as well as associated file groups and log files.

Back up Service Manager before you upgrade

Before you start any upgrade, we recommend that you back up your Service Manager and data warehouse databases and the encryption key. If you've already backed up your databases and encryption key, you can continue to run the upgrade. Otherwise, review the backup procedures in the Disaster Recovery Guide for System Center - Service Manager before you continue the upgrade.

Register the Service Manager data warehouse

If you've installed a data warehouse management server in your environment, as part of the upgrade process, you must be able to view the status of the data warehouse jobs. You can't perform this task if you've not registered with the Service Manager data warehouse. If the Data Warehouse button isn't visible in the Service Manager console, complete the procedure in Registering with the Service Manager Data Warehouse to Enable Reporting in the Deployment Guide for System Center - Service Manager.

Encryption keys

When you've finished running Setup to either install or upgrade to System Center 2025 - Service Manager, you're prompted to open the Encryption Backup or Restore Wizard. If you've previously backed up the encryption keys, no additional action is required. If you never backed up the encryption keys, use the Encryption Key Backup or Restore Wizard to back up the encryption keys on the Service Manager management servers.

Next steps

• Review Prepare remote SQL Server Reporting Services for upgrade to prepare your environment if SSRS is remote from the data warehouse management server.