LiveMeeting 20th September: Management pack tuning wars
Missed my session at the Experience days last June? No fear I’ll rerun my session during a live meeting the 20th of September. It will be packed with demos of the new wave of authoring tools which will make your life much easier in maintaining, creating and upgrading your management packs in the SCOM environment.
The abstract of this LiveMeeting:
Do you feel like installing, maintaining and developing management packs feels like a mission? Why not make it a mission! Join me in this session to efficiently tune and create your own management pack with military precision and no room for failure. Get the right tools to arm yourself for the job, get the best approach and fire away. The new secret weapon in Management pack authoring will be revealed and showcased so you can complete every management pack design mission quick and effectively. Attention!
Make sure to sign up here:
https://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032523394&Culture=en-us&community=0
In addition Microsoft BELUX is launching the “Technet Tuesdays and Thursdays”. Two days in the week filled with LiveMeetings + you’ll get 50 MVA (Microsoft Virtual Academy points) when attending.
Check out the full list of LiveMeetings here to receive all the info you need first hand from the experts in the field: http://technet.microsoft.com/nl-be/bb291010/
SCOM 2012: Error 0x80131500 when installing Reporting server
Today I received a rather strange error message when I wanted to install a reporting server in an already existing OM 2012 environment.
Symptoms:
The install took ages and was running on “Creating SRS source” forever however it was still running.
After 2 hours it gave an error and rolled back to the original situation.
After going over the prerequisites again it failed again. Rebooted the machine, checked everything again but no dice.
The error message was: Exception Error Code: 0x80131500. The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.
Solution
Turned out that there were proxy settings filled in in Internet Explorer. Apparently the install process is using these proxy settings to connect to the IIS in the background. However my user did not have rights on the proxy. Therefore the connection was denied and the install could not continue. Removing the Proxy settings resolved the issue and Reporting was installed successfully.
System Center 2012 CU2 available
Microsoft is continuously developing and improving the System Center 2012 suite. A proof is the recent release CU2.
The majority of fixes are for DPM, Service manager and orchestrator but other minor fixes are also available for SCOM.
For a detailed overview of all the problems this CU2 fixes take a look here: http://support.microsoft.com/kb/2706783/en-us
Download for
DPM: http://www.microsoft.com/en-us/download/details.aspx?id=30413
SCOM: http://www.microsoft.com/en-us/download/details.aspx?id=30421
As more blog posts about installing CU2 emerge I’ll update the list below:
Kevin Greene already wrote a detailed blog post about installing the CU2 update on a SCOM installation: http://kevingreeneitblog.blogspot.be/2012/07/scom-2012-deploying-cumulative-update.html
SCOM: Install both SCOM2007R2 and SCOM2012 console
In this blog post I’m going to show you how you install both consoles on your workstation. I visit a lot of customers lately who have either SCOM2007R2 or SCOM2012 installed. So I recently also installed the SCOM2012 management console on my laptop to have them both on my machine.
By default it’s not possible to install the SCOM2012 console on a workstation which have already SCOM2007R2 installed.
It will propose to upgrade the existing console but unfortunately there’s no option to install side by side.
So first upgrade the SCOM2007R2 console to SCOM2012.
Afterwards you need to reinstall the SCOM2007R2 console:
Select only the “User interfaces” option which is in fact the SCOM console:
So after you’ve installed open up the 2 consoles.
CAUTION: Because you have performed an upgrade the old connection to the SCOM2007R2 management group were still saved. So connect towards your new SCOM2012 management group and you’re all set:
So fill in your new server and hit connect:
Success!
