During the prep of my lab I came across an error which was in fact not this very common so I’ve decided to share my solution with you to save you some trouble when performing this in your environment.
After running through the entire installation wizard my upgrade process started fine… But after 10 minutes…
After restarting the process I was left with a broken SCOM2007R2 and SCOM2012 not installed. SQL Reporting services were broken so I had to revert my machine back to a snapshot I took earlier on and started all over again…
Now the solution so you shouldn’t have to go through the whole process of troubleshooting.
After checking the log file I found the following cause of my initial failing of the upgrade:
“System.UnauthorizedAccessException, Exception Error Code: 0x80070005, Exception.Message: Access to the path ‘MOMAspNet.msi’ is denied.”
This in fact is your ASP.net msi which is used when you install the agents. I’ve checked the rights and they were all good.
Delete folder: “C:\Program Files\System Center Operations Manager 2007\AgentManagement”
The installation went through after this.
After your upgrade this folder will be replaced anyway by the new SCOM2012 agent install packages so it’s safe to delete this before upgrade.
Another little step towards our brand new shining SCOM2012 environment
The title says it all…
Don’t be the IT-Rambo but prepare yourself for the move to SCOM2012 by checking my session which I gave the 20th of September and is now available online.
Check it here: http://technet.microsoft.com/en-us/edge/Hh443650
The slide deck is also available here: https://skydrive.live.com/?sc=documents&cid=f14edda98c2a18de#!/view.aspx?cid=F14EDDA98C2A18DE&resid=F14EDDA98C2A18DE%21126
During my session on how to prepare yourself I’ve showcased some tips and tricks which will make your live much easier when you upgrade your existing SCOM 2007 R2 installation to SCOM2012.
One of the tricks I’ve mentioned was to run the SCOM2012 web console in it’s own app pool. During the upgrade of your web console the application pool will be removed and you can only choose the default application pool to install the website which is in my opinion not a best practice.
So before installing the Web Console on your webserver perform the following tasks in IIS:
Open the IIS manager on your machine
Right click the application pools and choose “Add Web Site…”
Fill in the details:
Note: At this point you need to choose another port than the default 51908. You can change this again after the upgrade.
The site is up and running.
During the wizard for pre installation you’ll get at one point at the following dialog to choose your application pool. Here’s the reason explained why we can’t reuse the “old” site:
The Operations Manager WebConsole will be deleted during the upgrade so it will default to the default application pool.
Select the new created website and continue.
After the upgrade you’ll notice that the old site has been removed. At this point you can edit the binding of the application pool again to the default port to keep the same transparency towards your users.
More tips to follow so stay tuned!
A new milestone in the development of System Center Operations Manager 2012 (SCOM2012) today. The release of the beta to the public.
More info on the team blog here:
A small portion of the SCOM 2012 FAQ which is something most people are very curious about:
“We’ve made significant investments to help our customers build more comprehensive monitoring for their private cloud environments, while integrating their existing datacenter investments.
Here’s the direct download link:
http://www.microsoft.com/download/en/details.aspx?id=26804
Technet info link:
http://technet.microsoft.com/nl-be/library/hh205987(en-us).aspx
The final release is still planned for the first half of 2012. But you can evaluate it now already.
Caution:
As this is beta software it’s not supported to run this in a production environment.
We’ll be blogging more on the install process and first findings soon.