The IT Crownd

So one of the attractive features of CU5 was the ability to now use SQL 2008 R2. I also found that Windows reporting was now no longer working - after a quick Google I found that the new reporting pack was only compatible with 2008 Report Services. I was running 2005.  Now before I get going I'd like to point out I am NOT a SQL guy.  I know a bit about databases, enough to get me in trouble but I am NOT a SQL guy. Ho hum.  Time for a SQL upgrade then.  With my paperwork and Change Request (ITIL rules here) in place I dutifully made backups off all the DBs running on the SQL 2005 box. I followed the Microsoft documentation : http://technet.microsoft.com/en-us/library/dd789004.aspx which basically says run, SRSUpdateTool.exe, then run the SQL upgrade and then run SRSUpdateHelpr.msi and finally re-run SRSUpdateTool.exe This all sounded pretty simple, next, next and finish.  I'll have me a shiny new SQL install in no time. A week later and I finally ...

Ok so we've been running SCOM with CU5 for a couple of months now and things are working nicely. We do have a recurring issue when notifications fail, there is not alerting/events raised for this notification just stops.  So we do reboot the services every now and again - no biggy.  However this is a bit annoying. Anyways I followed Kevin Holman's excellent blog here... http://blogs.technet.com/b/kevinholman/archive/2011/08/03/opsmgr-2007-r2-cu5-rollup-hotfix-ships-and-my-experience-installing-it.aspx plenty to read and although it is cut-n-paste job from CU4 (and CU3) it does show how Microsoft are working towards a standard process for upgrading SCOM.   Shame we are nearly at RTM for 2012! We had no surprises and thing went very smoothly. Upgrading the SQL box to 2008 R2 from 2005 was a very different matter...

I'm alive.  Honest.  Just very busy. Struggling to get net 4.0 to install....grrrr....