#opsmgr: upgrading from 2007 to 2012 (Planning)

Now that the RTM-release of most System Center 2012 components are behind the corner, it is likely that early adopters using older versions are starting to think about an upgrade.

The reason for an early upgrade might be to get the features SCOM 2007 lacked (natively):

 

SCOM 2012 is one of the few products supporting an in-place upgrade. However, there is one exception: since the engine beneath SCOM 2012 has changed, any connector or application that is built for SCOM 2007 will likely not work.

As a sidenote, Microsoft will promote the integration with System Center Orchestrator over the use with connectors. However it is still possible to create connectors with the SCOM 2012 SDK.

So only expect this upgrade to be an overnight type of action if you are using native management packs exclusively, without add-on connectors or utilities.

 

Although documentation is still being worked on, there is already a comprehensive section about upgrading: Upgrading to System Center 2012 – Operations Manager.

There is even a range of 2007-2012 upgrade checklists which can greatly help to perform a speedy upgrade: http://technet.microsoft.com/en-us/library/hh241293.aspx.

 

Before we start the upgrade, there are some things we must check:

  • New system requirements
    • 2008 R2 SP1 is required for the RMS
    • Server 2003, SQL 2005 and x86 is not supported anymore save for the agents
    • .NET 4.0 is now a requirement
    • The table below shows the new hardware requirements for each role (subject to change as these are beta requirements)

Processor

RAM

Disk

.NET 3.5 SP1

.NET 4.0

Management Server

2.8 GHz

2 GB

1 GB

X

X

Operations Console

2.8 GHz

2 GB

512 MB

X

X

Web Console

2.8 GHz

2 GB

X

X

Operational Database

2.8 GHz

4 GB

1 GB

X

X

Operations Manager Reporting

2.8 GHz

2 GB

1 GB

X

X

Operations Manager DW

2.8 GHz

4 GB

1 GB

X

X

Operations Manager Gateway

2.8 GHz

2 GB

1 GB

Source

  • Existing network monitoring

If you were using SCOM 2007’s SNMP monitoring previously, it will keep working in 2012. However, this must be seen as a legacy functionality. There is a new networkdevice-model supporting IPv6 and SNMP v4. This is also the model used for the nifty network monitoring.

So extra work might be needed to migrate your devices from the legacy model to the new one.

 

If we are sure our SCOM 2007 infrastructure is 2012-applicable we can start the preparations for our upgrade!

This will be showcased in part 2 of this blog series. To be continued…

Advertisements
This entry was posted in #scom, #sysctr, Uncategorized and tagged , , , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s