DATACENTER

MANAGEMENT

How to upgrade or migrate

SCOM like a champ

Bob Cornelissen

TopQore

DATACENTER

MANAGEMENT

Bob Cornelissen

SCOM-Bob

bob@topqore.comManaging Consultant at:

7x MVP Cloud & Datacenter

Management

Hobby: Carom Billiards Libre

Charity: facebook.com/sthouseoftails

DATACENTER

MANAGEMENT

Big Question… What SCOM do you have?

MOM 2000 & SP1

MOM 2005 & SP1

SCOM 2007 RTM

SCOM 2007 SP1

SCOM 2007 R2

SCOM 2012

SCOM 2012 SP1

SCOM 2012 R2

SCOM 2016

SCOM 1801

SCOM 1807

SCOM 2019

2001 - 2003

2004 - 2005

2007

2008 - 2010

2008 - 2013

2011 - 2015

2013 - 2015

2014 - 2017

2016 – 2026

2018 - End July 2019

2018 – End Jan 2020

2019 – 2029

Versions Release /Updates /Support

DATACENTER

MANAGEMENT

The first questions you need to ask yourself…

• What is my target SCOM version?

• Looking at LTSB or SAC versions *

• In-place upgrade (single or multiple) or

side-by-side?

• Depends on your current version

• Depends on current health and setup

* Note: SAC has been stopped

DATACENTER

MANAGEMENT

System Center release cadence

LTSC Releases*

SAC Releases**

SC 2016 URs

System Center 2016

October 2016

System Center 1801

Feb 2018

System Center 1807

July 2018

System Center 2019

March 2019

SC2016 UR5

April 2018SC2016 UR6

Oct 2018

SC2016 UR7

April 2019

* LTSC releases are supported for 5 year (mainstream) + 5 year (extended)

** SAC releases are supported for 18 months

DATACENTER

MANAGEMENT

The SCOM Upgrade and install tree

DATACENTER

MANAGEMENT

Other decision points - WindowsW

ind

ow

s Serv

er

Vers

ion

2012

2008 R2

2012 R2

2016

2019

DATACENTER

MANAGEMENT

Other decision points - SQLSQ

L Serv

er

Vers

ion

2012

2008

2014

2016

2017

DATACENTER

MANAGEMENT Other versioning questions

• No Windows 2003 support for agents

• No Windows 2008 support for agents (workaround)

• No more 32 bit SCOM agents (see previous points)

• No RedHat 6 support – end mainstream support (workaround)

• No Aix 6 support – end mainstream support (workaround)

• Windows 2012 R2 on the SQL backend? (not supported, may work in-place)

• Windows 2012 R2 for SCOM infra components not supported

DATACENTER

MANAGEMENT

Upgrade paths multiple SC products

Upgrade sequence:

■ Service Management Automation

■ Orchestrator

■ Service Manager

■ Data Protection Manager

■ Operations Manager

■ Virtual Machine Manager

■ Service Provider Foundation

■ Windows Azure Pack

U

P

G

R

A

D

E

Example for the

2012R2 -> 2016

migration

DATACENTER

MANAGEMENTIn-place vs Side-by-side

Pros• Less configuration work

• Immediately start using

new features

Cons• Prefer to not perform

when upgraded before!

• Anything wrong with the

previous setup stays and

increases

In-place

Only do this for a Healthy management group!

Be prepared to restore all management servers and SQL databases

involved when anything goes wrong.

DATACENTER

MANAGEMENTIn-place vs Side-by-side

Pros• Fresh environment

• No interruption of service

• Move teams after

configuration is done

• Move to new Windows and

SQL versions

Cons•

•

•

•

Side-by-side

DATACENTER

MANAGEMENT

DATACENTER

MANAGEMENT

In-Place upgrade

https://docs.microsoft.com/en-us/system-

center/scom/deploy-upgrade-overview?view=sc-om-2019

DATACENTER

MANAGEMENT Before you upgrade

• Use an account with local administrator rights on:

■ SQL Server (both cluster or always-on scenarios)

■ SCOM Management Servers

■ SCOM Web and Reporting Servers

• Sysadmin role on the SQL Server

• SCOM Administrator

Tip: Often the SDK/DAS account would have these rights or the account

used to install the existing SCOM

!

DATACENTER

MANAGEMENT BEFORE you upgrade

• All SCOM infrastructure is healthy before continuing!

• SCOM infrastructure version

• Windows and SQL versions

• Clean up ETL Table using a script

DATACENTER

MANAGEMENT Before you upgrade (more...)• OperationsManager database 50% free space

• OperationsManager transaction log 50% size of database size

• Remove agents from Pending Management

• Disable Notification Subscriptions

• Disable the IIS Web Console site in IIS

• Disable Connectors

DATACENTER

MANAGEMENT Before you upgrade (more...)

• Optional: agents cache size

• Check an additional 2 times: complete backups of

management servers, and all SCOM databases!

• Upgrade management servers 1 by 1 starting with the RMSe

■ While upgrading each MS make sure ALL SCOM services are

stopped on all the other MS.

DATACENTER

MANAGEMENT Perform in-Place upgrade

• Stop SCOM services on all MS

• Start with RMSe management server

■ Microsoft CLR types for SQL Server 2014

■ Microsoft Report Viewer 2015 runtime

■ Upgrade of SCOM components installed

■ Credentials of service accounts needed!

• Upgrade the next management server(s)

DATACENTER

MANAGEMENT Perform in-Place upgrade

• Initialize for half an hour OR MORE

• Implement the latest SCOM Update Rollup

• Check if everything is still healthy!

• SCOM gateway servers

• Web Console Server(s)

• Report Server

• SCOM Consoles installed on other servers/machines

• Upgrade agents

DATACENTER

MANAGEMENT Perform in-Place upgradePost-Upgrade tasks

• Enable Notification Subscriptions

• Enable Connector services

• Re-Enable ACS for the agents

• Check the health of SCOM again

• Remaining consoles and agents to upgrade: that’s OK

DATACENTER

MANAGEMENT

DATACENTER

MANAGEMENT

Side-by-side upgrade

DATACENTER

MANAGEMENT Perform Side-by-Side upgrade

• Install SCOM 2016/2019 environment

• Configure SCOM default settings (like enable Proxy for

all agents and set reg keys for Mgmt Servers)

• Multi-Home agents

DATACENTER

MANAGEMENT Perform Side-by-Side upgrade

• Import Management Packs bit by bit and configure/tune

• Bring the override management packs which are good from the

old SCOM

• Setup other components, like ACS, AEM, Dashboarding, Log

Analytics connection, Reports, Subscriptions, Connectors etc.

DATACENTER

MANAGEMENT Perform side-by-side upgrade

• Retire old SCOM

• Clean out the old SCOM by first removing the agent multi-homing

• Next old SCOM server infra can be broken down if no access to the

old data is needed.

DATACENTER

MANAGEMENT

DATACENTER

MANAGEMENT

More stuff!

DATACENTER

MANAGEMENT SCOM Logon as a Service

• SCOM Management Servers -> the 4 SCOM service accounts

• SCOM Management Servers -> SCOM Admins if push deploy

• SCOM agent -> If a runas account is used (example: SharePoint MP)

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\System Center\Health Service

Worker Process Logon Type (REG_DWORD)

2 = Log on locally

5 = Log on as a service

DATACENTER

MANAGEMENT

SCOM Management MP from Holman

https://kevinholman.com/2017/05/09/scom-

management-mp-making-a-scom-admins-life-a-

little-easier/

DATACENTER

MANAGEMENT PowerShell some manual steps – by Ruben Zimmermann

https://anaops.com/2019/01/12/scom-2012-r2-to-1801-side-by-side-migration-the-powershell-way-by-ruben-zimmermann/

■ Resolution states and settings

■DB grooming

■User Roles

■User profiles

DATACENTER

MANAGEMENT Questions?

29

DATACENTER

MANAGEMENT

Next Session at 09:00

Tech Panel