Larry Rayl a senior consultant at Catapult Systems has created and posted a nice set of SCOM 2012 Visio Stencils creating the possibility to even further customize your SCOM 2012 Visio designs.
There are some really specific Visio stencils in there which were not available out of the box in Visio or in the old Scom 2007 visio stencils.
A pretty cool addition to your standard toolkit if you ask me!
Check the original blog post here: http://blogs.catapultsystems.com/lrayl/archive/2012/11/13/system-center-2012-operations-manager-2012-stencil.aspx
Download them from SystemCenterCentral here: http://www.systemcentercentral.com/Downloads/DownloadsDetails/tabid/144/IndexID/96587/Default.aspx
This afternoon my colleague Alex Smits asked for pointers on a strange problem he faced when he wanted to install a SCOM 2012 reporting server on a previous SCOM 2007 reporting server for a side by side migration.
As soon as he clicked the install button on the Scom 2012 install screen the following error message appeared and the install was aborted:
There was no log written to the machine because in fact the install just did not kick off yet . There were also no indications in the event viewer so we were completely troubleshooting blind on this one.
After some time Alex managed to get the reporting server installed on the machine after taking a backup of the old reporting dbase and then completely removing the SCOM 2007 reporting server dbase components of this server.
After this the install passed the error message and installed perfectly.
I hope we save you some valuable troubleshooting time by finding this out…
NOTE: This blogpost is part of a series of tips and tricks. You can find more tips and tricks on the central blogpost located here; http://scug.be/dieter/2012/10/07/scom-tips-and-tricks-series/
Just a small shortcut tip this time.
As part of the unified console the shortcuts to the tabs in scom have been included in the SCOM 2012 console.
I find this personally particularly handy when you want to switch between the different tabs while browsing through the console.
CAUTION: You’ll need access to the tabs to be able to open them.
So just pressing CTRL + a number will open the tab.
TIP: If you don’t know the exact number there’s always a way to get it by hovering over the specific tab.
No point in using the shortcut when you hover over the tab but you might remember it the next time and save yourself that nanosecond of valuable SCOM time
Stay tuned for more tips and tricks in the series.
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.
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
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!