Thursday, 15 December 2011

Operations Manager 2007 R2 (SCOM) Version Numbers

Just a quick post to help me remember what release numbers relate to which cumulative update version:

Version (numeric)Version (name)
6.1.7221.13RTM with CU1 Applied
6.1.7221.15RTM with CU2 Applied
6.1.7221.49RTM with CU3 Applied
6.1.7221.61RTM with CU4 Applied
6.1.7221.81RTM with CU5 Applied
6.1.7221.99RTM with CU6 Applied
6.1.7221.110RTM with CU7 Applied

Monday, 5 December 2011

Configuration Manager 2012 RC now supports SQL 2008 R2

As of 03/12/11 you'll be pleased to know that SQL Server 2008 R2 Service Pack 1 is now supported for use with Configuration Manager 2012 Release Candidate 1. 

In addition to Service Pack 1, you will also need to install Cumulative Update 3 (CU3) for SQL Server 2008 R2 SP1, as well as the hotfix described in KB2603910:

However, please note that the hotfix for SQL 2008 R2 has currently been pulled again for some reason and isn't available at the link above, I'll update this post when it is, until then you would need to contact MS to obtain the hotfix.

*Updated 12/12/11* The hotfix for SQL 2008 R2 is now available.  Thanks Mr Anonymous commentor.

Friday, 2 December 2011

How to move a SCVMM 2012 database to another SQL server

I'm not exactly re-inventing the wheel here as it's the same process for Virtual Machine Manager 2012 as it was for 2008 R2, but I thought I'd post about it anyway.

This isn't a common thing to need to do, but I found myself in the position today where I wanted to move the database that was on a local SQL install on a SCVMM 2012 server up onto a new SQL Cluster I had just finished building.

So these are the steps I took to move the database:
  1. Take a snapshot of the server (assuming it's a VM)
  2. Take a backup of the existing VMM DB
  3. Uninstall VMM and choose the Retain Database option
  4. Detach the VMM DB from the local SQL instance
  5. Copy the VMM DB files across to the new SQL Server
  6. On the remote SQL server, attach the VMM db
  7. Re-install SCVMM 2012 and when prompted, point it at the new SQL server, selecting to use an existing database (the one you imported) 
Easy!  Now you're free to uninstall SQL as and when.