SCOM 2007 R2 upgrading to SCOM 2012.Now with SCOM 2012 SP1 being GA it can be even more a challenge. Let’s not forget Windows Server 2012 and SQL Server 2012 (SP1)And how about the announced R2 release, expected Q4 this year?Also: SHOULD you really upgrade? Only because you can? Or shouldn’t you? When to make what decision?And what are the pitfalls, challenges and so on?
Some remarksEven though SCOM 2012 RTM supports Windows Server 2008 SP2 as Server OS for the SQL Server used by SCOM, don’t use it! (SCOM 2012 SP1 and later…)Same goes for the version of SQL Server. DON’T INSTALL SQL Server 2008 SP1 but SQL Server 2008 R2 SP2 instead. SQL Server 2012 isn’t supported by SCOM 2012 RTMSCOM 2012 RTM MS servers requireWindows Server 2008 R2 SP1. Windows Server 2012 RTM isn’t supported!Simple ≠ a small scaled SCOM 2007 environmentComplex ≠ an enterprise scaled SCOM 2007 environment
Some MPs don’t function properly in SCOM 2012:OpsLogix Ping MP: dll ‘kills’ the SCOM 2012 Console. Remove that file (OpsLogix.IMP.Base.UI.dll). When on SCOM 2012: upgrade MP and dll to the SCOM 2012 versionxSNMP: devices will be monitored in SCOM 2012 but you can’t add new devices to it. So it’s a dead end
Installing a new SQL Server based on SQL Server 2008 R2 SP2 isn’t to be taken lightly either. Many additional steps are required in order to move the SCOM databases to this new server:Install a new dedicated SQL Server 2008 R2 SP2 server with all requirements needed by SCOM 2007 R2 AND SCOM 2012 SP1Use as Server OS Windows Server 2008 R2 SP1!Install CU#7 for SCOM 2007 R2 if not already presentBackup the custom reports you made yourself with the community tool, http://thoughtsonopsmgr.blogspot.nl/2011/12/exporting-linked-reports-to-another.html Backup the SCOM databasesRemove SCOM 2007 ReportingStop all SCOM 2007 services on RMS and MSRestore the SCOM databases to the new SQL ServerChange the registry keys on the SCOM 2007 R2 RMS and MS serversChange the tables in the SCOM 2007 R2 OpsMgr DBStart all SCOM 2007 services on RMS and MSReinstall SCOM 2007 R2 Reporting on the new SQL ServerInstall the same CU# for SCOM 2007 R2 Reporting component, already applied to the other SCOM 2007 R2 componentsRestore the customized Reports
RMS, MS servers, Gateways, Agents (pushed/manually installed), SCOM service accounts and their credentialsLicensesSC 2012 is licensed as a SINGLE product. You can save €€€ when running multiple SC 2012 components. In situations you ‘only’ run SCOM 2007 R2, license costs are highCheck your reseller whether all the current versions of your 3rd party MPs and/or add-ons are supported in SCOM 2012Make it a project. Allocate the proper resources, budget and time to it. An upgrade is more than NEXT>NEXT>FINISHWriting a business case might help to get support from the management teamBreakdown of all the upgrades I did: 70% of the total amount of time was spent on preparation, 20% on the upgrade itself and 10% cleaning up, final documentation included.RFC’sCommunication: when is what going to take placeHas the upgrade ever been tested?Are all the official documents read & understood?Is the upgrade described (high level/details)?An upgrade doesn’t fix problemsThis is the ONE and only supported SQL Collation settings for SCOM 2012. MPs like Ex2010 and Veaam require it in order to function properly Can be anything: up from SPoKs, loaded SQL databases, overcommitted virtualization hosts, overcomitted/underperforming SAN, dead lines which are way too hard to meet, Specific, Measurable, Acceptable, Reasonable, bound to a schedule/timeframe
Add a MS server to your MG topology before the upgrade. Not only for robustness but also to enhance the chance to a successful upgradeDON’T RUN PRODUCTION ON ALL-IN-ONE SCOM SERVERS (SQL and RMS on one box). Start NEW!Make a new backup of the encryption key and write down the passwordSnapshots are KILLING for the performance of the VMS = killing the upgrade process all together. Make CLONES!BackupsMake sure the backups can be restored for a full 100%Backup everything. RMS, MS servers and SQL databases and SQL servers alikeOpsMgr DB requires at least 50% free space. DW requires a bit of free space as well. 5% isn’t enough….Eventhough thoroughly documented, people tend to forget:Connectors & subscribtions still functionalUpgrade Helper MP isn’t importedSSRS is outdated
Can take way too much time, effort and resources to upgrade it allToo much history/luggage?These types of MGs aren’t really the best upgrade candidatesGarbage in = garbage outUsing wrong settings in the configuration of SCOM
Big Bang is moving directly from SCOM 2007 R2 to SCOM 2012 SP1.And/or to upgrade the Server OS directly to Windows Server 2012 and SQL to SQL Server 2012 SP1.
Mainstream support Windows Server 2008 R2 ends on: 13th of January 2015Mainstream support SQL Server 2008 R2 end on: 8th of July 2014DON’T FORGET THE UPGRADE SEQUENCE!!! http://technet.microsoft.com/en-us/library/jj628203.aspxSCOM 2012 RTM > SCOM 2012 SP1: http://thoughtsonopsmgr.blogspot.nl/2013/01/upgrade-experiences-from-om12-ur3.htmlWindows Server 2008 R2 SP1 > Windows Server 2012: http://thoughtsonopsmgr.blogspot.nl/2013/01/hello-om12-sp1-goodbye-windows-server.htmlSQL Server 2008 R2 SP2 > SQL Server 2012 SP1: http://thoughtsonopsmgr.blogspot.nl/2013/01/om12-sp1-upgrading-sql-server-2008-sp1.htmlWhen on SCOM 2007 R2 CU#4 (or higher), Windows Server 2003 and SQL Server 2005 > SCOM 2012 SP1, Windows Server 2012 and SQL Server 2012 SP1: http://thoughtsonopsmgr.blogspot.nl/2013/02/high-level-steps-migrating-from-scom.html
Zoals beschreven door Cameron Fuller! Hem benoemen!!!
A new SCOM2012 environment is installed on brand new servers running the latest Server OS and usingExsisting SCOM 2007 R2 Agents are upgraded SCOM 2012 AgentsThese Agents report to both MGs (SCOM 2007 R2 MG & SCOM 2012 MG)Sealed MPs – present in the SCOM 2007 R2 MG - are mirrored in the SCOM 2012 MGEnables movement ofoverrides created in the SCOM 2007 R2 MG to the SCOM 2012 MG
In the XML instead of the server name or FQDN a GUID is used instead. This GUID is unique. So when the SCOM 2012 MG uses another GUID for the same server then this override will fail.Cameron tested A and B and those overrides are neatly transferred with the MP to the SCOM 2012 MG. These overrides work perfectly.As it turns out, the SCOM 2007 Agent is upgraded to the SCOM 2012 Agent but the GUID of the SCOM 2007 Agent is retained by the SCOM 2012 Agent. So this GUID is fed in the SCOM 2012 database as well.For C, not tested yet.
The only valid reason for an inplace-upgrade:The data warehouse data HAS to be maintained in the SCOM 2012 data warehouse. Maintaining the original OpsMgr 2007 R2 environment just fore this purpose isn’t allowed.
Upgrade Process Flow DiagramsUpgrading from SCOM 2007 R2 to SCOM 2012Upgrading from SCOM 2012 to SCOM 2012 SP1SCOM 2012 SCOM 2012 SP1Upgrade Sequencing for System Center 2012 SP1Kevin HolmanStefan StrangerSystem Center: Operations Manager Engineering BlogCameron FullerBob CornelissenDaniele Grandiniblog posts on upgrading