I did the upgrade today at work from Operations Manager 2007 SP1 to Operations Manager 2007 R2. I followed the upgrade document by Microsoft. It weighs in at 60 pages but that covers all sorts of scenarios. I printed the document out and slowly worked through it. It’s 60 pages so that’s a nice load going into the recycle bin. It’s a very well written document so congrats to the team and the author, Christopher Fox.
I followed their precautionary backup steps. But I also took a snapshot – yeap, our OpsMgr 2007 RMS is a virtual machine. I checked out it’s utilisation of resources and found it was a candidate. So I took a snapshot after the database backups/resizing and then continued the MS upgrade process. I’ll leave the snapshot for a weekend to see how it goes. The AVHD’s are slowing performance of the OpsMgr server but I’ll live with that in order to have a rollback option in the case of a critical issue. If all is well in a few days I will merge the snapshot.
You need to have some disk space for this upgrade. The guide recommends that the Operations and datawarehouse database have 50% free space. The Operations database also needs a log file that is 50% of the size of the database file, e.g. the MDF is 50GB so the LDF should be 25GB.
The agent upgrade can be done a bunch of ways. The easiest is to approve the updates via Pending Management in the console under Administration. Note that agents accessed via a firewall will probably fail so you’ll have to do those manually.
I’m also using the Management Pack Templates to manage 3rd party services. There’s a new option to target this to a group of machines. I like that; it trims the fat. I also use the Web Application templates. They also need to be upgraded (edit properties, click Apply and agree to upgrade the management pack). You’ll have to do that with each application.