The following was done as part of a project to validate that network devices monitored by OpsMgr 2007 R2 using the xSNMP management pack still work when the environment is upgraded to OpsMgr 2012. To test this situation, I installed an all-in-one OpsMgr 2007 R2 environment (similar to what was done in this blog article), added the xSNMP management packs and added a Cisco device as network monitored (using Kevin Holman’s blog post on using the Jalasoft network device simulator). This configuration validates that the current OpsMgr 2007 R2 environment was functional when monitoring at least the one Cisco device using the xSNMP management pack.

[Please pardon my screenshots on this blog post, I used a different method than I normally used when I get screenshots for blog posts.]

Environment Prep:

To prepare the environment for upgrade, the following were the steps required:

1) The first step was to apply a CU version to OpsMgr 2007 R2 which would support the upgrade. For this lab environment I applied CU6 (see Kevin Holman’s notes for details on CU6 installation)

2) Perform a backup or create a checkpoint if it’s a virtual. For this environment it was running on a virtual so I created a checkpoint in System Center Virtual Machine Manager prior to starting the upgrade. This proved to be critically important as my first upgrade attempt failed and I needed to re-run the upgrade process.

3) Make sure that there is plenty of free space in the OperationsManager database prior to upgrading! My first upgrade attempt failed and had to be restored to checkpoint due to free space in the OperationsManager database.

4) Installed .NET framework 4.0: http://www.microsoft.com/en-us/download/details.aspx?id=17851 which is one of the pre-requisites for OpsMgr 2012 installation.

5) Installed Report Viewer: http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=6442 which is one of the pre-requisites for OpsMgr 2012 installation.

6) Start the SQL Server Agent service (if it was set to manual, set to automatic and start the service).

7) After installation of .NET framework 4.0 change ISAPI: Set the ASP.NET v4.0.30319 to Allowed.

clip_image007

Upgrade:

1) Start the Installation process from the OpsMgr 2012 installation media.

clip_image002

clip_image003

clip_image004

clip_image005

clip_image006

2) There are warnings on memory levels (I am using Dynamic Memory in my lab) and that OpsMgr should not be installed on a domain controller but it will still allow the installation to proceed.

clip_image008

3) Specify the web console information.

clip_image009

4) Select authentication for the web console.

clip_image010

5) Specify the credentials for OpsMgr to use.

clip_image011

6) Upgrade proceeds.

clip_image012

clip_image013

clip_image014

clip_image015

7) The upgraded OpsMgr 2012 console is shown below!

clip_image016

8) After this I validated that my xSNMP management packs were still in place and that I was still able to monitor the test Cisco device I had put in place prior to the start of the upgrade.

Summary: The upgrade process for an All-In-One OpsMgr 2007 R2 system to an OpsMgr 2012 system is pretty straight-forward. Be sure to backup the system before performing the update, and make sure that there is plenty of free space in the OperationsManager database before performing the update. The xSNMP devices discovered prior to the upgrade continued to be available after the upgrade to 2012.