My experience upgrading to OpsMgr R2 RTM

Ops Manager R2 Upgrade

Orchestrated Chaos — Sat, 23 May 2009 22:19:42 GMT

Here’s a great, great walk through of the R2 Upgrade process. A must read if the upgrade is on your horizon

re: My experience upgrading to OpsMgr R2 RTM

John Wieda — Sat, 23 May 2009 23:40:57 GMT

Very clear and well documented upgrade experience, thanks!

Should individuals that have just the Ops Mgr 2007 SP1 console installed, uninstall that console and then install Ops Mgr 2007 R2 console?

Or is there an upgrade path?

Also, if someone, such as myself, is running Windows Server 2008 on their workstation and the Ops Mgr 2007 agent is installed - should both the console and the agent be uninstalled prior to the upgrade to Ops Mgr R2?

Thanks,

John in Chicago (Fiserv)

re: My experience upgrading to OpsMgr R2 RTM

dmuscett — Sun, 24 May 2009 09:09:12 GMT

The error about the service stop or start is just a timeout. i have hit that occasionally on multiple SP1 and R2 beta setups... but reall, everything works anyway after that.

The KMS error is known (at least to the community - I hope there is at least a bug filed for it): that stored procedure does not exist, and we never groom the KMS stuff from the DW. It was fond by Daniele Gandini (a partner) and it is described here: http://nocentdocent.wordpress.com/2009/02/14/kms-management-pack-bug/

re: need to remove consoles?

kevinhol — Sun, 24 May 2009 17:15:25 GMT

No - there is no requirement to remove consoles. Per the upgrade guide - you just need to remove the agent - in order to upgrade a console from SP1 to R2. I just chose to remove the console in my lab... because I had a lot of SP1 stuff loaded. Normally - you would follow the upgrade guide - remove agents from stand-alone console machines - then upgrade the stand alone consoles.... then later install the agent again. If you dont have an agent running on a machine with a stand alone console - you simply upgrade it.

re: My experience upgrading to OpsMgr R2 RTM

Layne — Sat, 30 May 2009 01:51:22 GMT

Kevin, excellent work as usual. Nice meeting you at MMS as well. Silly question about agent upgrades, as it is not clear to me from the various upgrade docs. How soon after you upgrade server roles are you supposed to upgrade your agents?

If after upgrading the server roles the agents appear in the Agent Requires Update section under Pending Management, they will not be monitored until you approve or reinstall manually, correct?

re: Agent upgrade

kevinhol — Sat, 30 May 2009 02:01:05 GMT

You can upgrade agents whenever you want. As you apply R2 to each Management server - we will place those agents into pending actions - that report to that management server as primary. This is just flipping a bit in the database essentially. You can approve or reject those anytime you want.

So - my recommendation would be to apply R2 to the entire management core infrastructure first (RMS, all MS/Gateway, reporting, etc...) and THEN start your agent upgrades.

When an agent is shown in pending actions - it is ABSOLUTELY still monitored as an SP1 agent. We do not stop or interrupt monitoring for any reason like this.

If you are not planning on upgrading those agents soon - then I would reject the pending action for the agents, and later - when you are ready - simply execute a "repair" routine from the console - which is essentially the same thing as approving an agent for a pending upgrade.

We just put them into pending to make this process a bit easier.

Upgrade Agents Via SMS

Brian Hansen — Mon, 15 Jun 2009 07:25:17 GMT

I need to upgrade agents using SCCM rather than the console. I ran into problems upgrading to SP1 and had to actually uninstall and reinstall agents rather than upgrading.

Has anyone tried command line upgrades to R2? Any recomdations for command line (SCCM) upgrades?

re: My experience upgrading to OpsMgr R2 RTM

Nicole Welch — Mon, 22 Jun 2009 20:49:52 GMT

For Brian-

We upgraded agents (~5K) to SP1 via SMS without issues. Below is the cmd I used in my VBS wrapper.

If ADInt = FALSE then

set objExecObject = objShell.Exec("msiexec.exe /i " &MSI& " SP1UPGRADE=1 SET_ACTIONS_ACCOUNT=0 REINSTALLMODE=vomus REINSTALL=All /quiet /norestart /l*v c:\ntutils\WASUP-SCOMAgentMSIUpgrade.log")

End IF

If ADInt = TRUE then

set objExecObject = objShell.Exec("msiexec.exe /i " &MSI& " SP1UPGRADE=1 SET_ACTIONS_ACCOUNT=0 REINSTALLMODE=vomus REINSTALL=All USE_MANUALLY_SPECIFIED_SETTINGS=0 USE_SETTINGS_FROM_AD=1 /quiet /norestart /l*v c:\ntutils\WASUP-SCOMAgentMSIUpgrade.log")

End IF

I'm working to confirm what the SP1Upgrade=1 switch is now for the R2 upgrade. Changing it to "R2Upgrade=1" appears to work in my lab -- still testing though.

re: My experience upgrading to OpsMgr R2 RTM

JWieda — Fri, 17 Jul 2009 23:31:10 GMT

Kevin -

I referenced your blog entry in a posting I made about upgrading to OpsMgr R2.

Thanks again for sharing, it made my upgrade pretty easy...

Cheers,

John

re: My experience upgrading to OpsMgr R2 RTM

vratix — Tue, 11 Aug 2009 22:02:34 GMT

Kevin,

Like you we are seeing this error from event 31552 repeatedly. I thought this was due to an issue with the KMS MP I read about so we removed the MP, but the error has persisted. Did you ever resolve this in your environment?

Vratix

re: KMS

kevinhol — Tue, 11 Aug 2009 22:15:19 GMT

This is caused by a few issues with the current KMS MP.

When you remove the MP - it does not remove the database objects, so the error persists. If you open a case with MS - they can help you remove this or keep the KMS MP and fix it - but it requires editing your database table.... which they dont like to do. :-) I had planned a blog post on this issue but haven't heard from a lot of people affected by it. You can ping me via the email contact form if you want the explicit instructions.

re: My experience upgrading to OpsMgr R2 RTM

Jim Kiniry — Mon, 24 Aug 2009 20:05:21 GMT

We're in the planning stage of performing the upgrade from SP1 to R2. We're also wanting to upgrade the OS from WS2003 SP2 to WS2008 R2. Any recommendations as to when it would be best to perform the OS upgrades? Should we upgrade to WS2008 first or can we go direct to WS2008 R2. We have split the OpsMgr roles to individual servers: RMS, DB, DW, RS, MS, MS2, and ND (Network Devices MS).

Thanks,

Jim

re: My experience upgrading to OpsMgr R2 RTM

Nick — Wed, 30 Sep 2009 17:12:14 GMT

we have a clean build of Ops Mngr R2 (ie we did not upgrade from earlier version) with no additional mgt packs installed other than the defaults and are getting 31552 events logged. just to add that to the mix - was it ever resolved - can you please post resolution if so.

thanks

Nick

re: My experience upgrading to OpsMgr R2 RTM

kevinhol — Wed, 30 Sep 2009 17:56:14 GMT

Yes - I already blogged about resolving the 31552 from KMS:

http://blogs.technet.com/kevinholman/archive/2009/09/23/new-kms-mp-released-version-6-0-7234-0-and-some-things-you-should-know.aspx

re: My experience upgrading to OpsMgr R2 RTM

Babu — Tue, 27 Oct 2009 16:50:30 GMT

How to Migrate from Single RMS to Clustered RMS in OpsMgr R2.

I cant see any documentation on web for this.