You are browsing the archive for 2011 September.

SCOM 2012: Webconsole fails to load after upgrade

9:15 pm in Uncategorized by Dieter Wijckmans

In my recent session I’ve showcased an error I encountered when upgrading my SCOM2007R2 environment to SCOM2012beta.

After the upgrade was finished successful I performed my standard after migration health check and opened my web console to check out the new features of the SCOM 2012 console.

Only to find out this very “nice” cryptic error message:


Apparently this is because the ASP.NET version was installed after the IIS role and the new web app “SCOM 2012 Web Console” was never registered to use this version of ASP.NET with the IIS role.

So what are we going to do now… well euhm… Fix it Smile

Open an elevated command prompt (make it a habit, this will save you a lot of trouble in your live)


Open explorer and browse to “c:\windows\\Framework64\v4.0.30319\”

Note: Make sure you use your installed framwork and version


Locate the file aspnet_regiis.exe and drag it into your elevated command prompt and add the switch –iru at the end as shown below. printscreen0053

This actually will reinstall the ASP.NET version into the IIS sites so they can all use the new version. Sites which already use the new version are left untouched.printscreen0054

Finished installing… So we’ll see what happened to our console!


Well it’s loading up fine at this point Smile

Note: You’ll need to have Silverlight installed. If you don’t have it on your machine a nice kind message will appear whether you want to install it. I’ve installed it in advance as it is one of the prerequisites.


There we have our nice brand new shiny Scom 2012 web console which we can start exploring Smile

SCOM 2012: Upgrade failed with error 0x80070005

6:19 am in Uncategorized by Dieter Wijckmans

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…printscreen0036

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 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 Smile

SCOM 2012: Don’t be the IT-Rambo…

9:03 am in Uncategorized by Dieter Wijckmans

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:

The slide deck is also available here:!/view.aspx?cid=F14EDDA98C2A18DE&resid=F14EDDA98C2A18DE%21126

SCOM 2012: Run WebConsole in different application pool

10:04 pm in Uncategorized by Dieter Wijckmans

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!

SCDPM 2012 Beta: How to install

8:40 pm in Uncategorized by Dieter Wijckmans

Well the beta is live now. So let’s start installing it. In this particular case I’m installing it on a Hyper-V machine in my test environment. The SQL is on the same machine as this is just a lab environment.

Always make sure to run the Setup.exe as administrator. When opened we get the familiar install screen of all the System Center products.


Click the “Data Protection Manager”.

Accept the license terms and conditions and click OK.


After this the DPM installer will install all the necessary prerequisites to get the install going. These are not yet the prerequisites for the DPM itself.


When these are finished the familiar DPM install screen appears. Nothing changed here so far. Click next to continue with the Prerequisites check.


As said before I’m running this purely as test in my lab so I’m using a Dedicated Instance of SQL Server and install it on my DPM server. Click “Check and install” dpm2012_beta0005

DPM will install the basic components.


Unfortunately there’s a reboot required after installing the SISFilter. If you want to avoid this you could install the filter in advance by downloading it here: dpm2012_beta0007

After reboot run through the process again and choose Next when all the prerequisites are installed.


Fill in unser name and Company and click next.


I’ve left the defaults here but you can easily change them if you please.dpm2012_beta0010

Put in a strong password to run the SQL Server service and Server Agent Service.dpm2012_beta0011

Use Microsoft Update choice. It’s up to you to use the Microsoft update or not. I prefer to put this on Microsoft Update to receive the updates when they appear.


CEIP data. Again a personal choice to participate or not.


A nice summary before the magic happens.dpm2012_beta0015

Clicking install still launches a Security warning to open the SQL 2008 setup file. Click Run to continue.dpm2012_beta0016

The SQL Server install will take some time. In my case 14 minutes. Note that this can vary in your environment but don’t worry it’ll get there eventually. If you have a remote instance this step is not necessary.dpm2012_beta0017

Everything went fine.


So let’s open the console for the first time to check it out!


Time to start playing and see the new features in action.

I’ll be installing the SCOM extensions as well shortly to check out the new remote manage capabilities.