Upgrading to SCSM 2012–First Hand Customer Experience

Upgrading to SCSM 2012–First Hand Customer Experience

  • Comments 3
  • Likes

Fletcher Kelly (@fskelly), who works at one one of the early adopters customers for SCSM shares his upgrade experience and tips with us below.  You’ll remember Fletcher from his earlier guest blog post on Setting up a Pre-Production Test Environment.

Thanks for sharing more of your experiences with us Fletcher!  You can follow more of his experiences on his blog.

Fletcher is fully in production on SCSM 2012 now.  One of the first customers to do so!  Congrats!

===================================================================

So, my journey with System Centre Service Manager 2012 Beta has begun and so far I have indeed found some funnies.

I will be blogging about them, to make everyone else’s life a little bit easier and in the hope of better product adoption for this product. It is simply put a fantastic product.

Ok, so the first time I ran the upgrade (remember I have a pre-prod environment), so I was able to rollback and did not have to follow Disaster Recovery with the Failure. I will cover the Disaster Recovery steps that I will follow in Production if I have an issue.

clip_image002

So, like I was saying, I ran into a Reporting Services error when upgrading the Data Warehouse. So I rolled back to a previous state as I am using VMS. However, to resolve this particular issue, I ran the upgrade again. However, this time I opened the SQL Reporting Services webpage and allowed the reporting services webpage to load to completion before running the upgrade.

clip_image003

I suspect due to the limited specs on my virtual environment, the slow opening and hence communications with the Reporting Services caused my first failure. The second attempt was perfect.

I now had SCSM 2012 Beta Data Warehouse.

So, here is a breakdown of what I did.

1. Install Cumulative Update 2 for System Centre Service Manager 2010 SP1

2. Install Windows Server 2008 R2 Service Pack 1

3. Backup Encryption Key

4. Restart Server

5. Check the status of SQL Reporting Services (services.msc)

6. Check the status of Reporting Service (web site). First load of this website was VERY slow.

7. Disabled Data Warehouse Jobs http://technet.microsoft.com/en-za/library/hh495610(en-us).aspx

8. Waited 10 Minutes

9. Run the Upgrade

10. We have successfully upgraded the Data Warehouse Server.

11. The only thing I did differently this time, I left the reporting services website open the whole time of the upgrade process.

More to follow soon on the Management Server.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • A quick added value note here: If you are using the 2010 SP1 CU(x) Console from your local machine, You will most likely have built out a NEW 2010 test environment and matched it to your 2010 prod environment. This probably required that you connect to your new 2010 test environment to mirror it to your production environment (e.g. back  up and import your MPs) before you upgrade. Word of warning... on your local machine, make sure that you change your connection BACK to your 2010 Prod server. The reason? If you keep your 2010 test environment connection in place,  then upgrade, when you launch your console again from your local machine it will be all confused because it will be pointing to your now new 2012 environment on a 2010 SP1 Cu(x) client. It doesnt like this. I had to uninstall my client, re-install 2010 SP1 and the upgrade to Cu3 again. Didnt take me that long, but more of pain in the butt. So... so make sure you switch your connection string BACK to your 2010 Prod environment if you are prepping your 2012 environment from the console on your local machine. :)

  • Can anyone comment on the details around the Self Service Portal? The documentation clearly states that the 2010 SSP is NOT compatible with the 2012 SSP. However, during the upgrade we did in our lab, the set up wizard sets up the SSP!! And of course it didnt work because it wasnt compatible. The upgrade documentation is very vague on this. Do we need to un-intall the SSP FIRST before we run the upgrade? Or, how do we install the SSP AFTER the upgrade outside of the setup wizard??

  • @Greg -

    If you are installing the web content server role onto the same server where you had the SCSM 2010 portal installed, yes, I would strongly recommend uininstalling the portal first and then installing 2012.