Every once in a while a great management pack hits the community that could really make the SCOM admins out there their lives a little bit easier.
Some are very complex and solve very complex problems others are very simple and add just another functionality to SCOM. Sometimes a community management pack fills a gap that has been left in the product.
This is a nice example of the last category: Let SCOM check for updated management packs.
OK it’s possible to do this periodically by opening up the Management pack catalog in scom and do a search on updated management packs but this management pack gives you proactively an alert when there’s a new management pack available!
How convenient!
So head over to Michaels blog and grab the management pack to free up the time you spend with management pack update checking and let scom do it for you:
http://michelkamp.wordpress.com/2013/04/21/let-scom-check-for-updated-management-packs/
This management pack is also added to my new list of cool community management packs which can be found here: http://scug.be/dieter/2012/12/30/scom-2012-overview-link-blog/
This morning the System Center community is once more buzzing with excitement.
System Center 2012 Service Pack 1 is live since a couple of weeks and already Microsoft has released the first Update Rollup (UR1) for it.
This show great dedication of Microsoft to keep this product up to date and regularly release updates. The good thing these Update Rollups are all cumulative so no need to perform a series of updates.
Although you need to install SP1 first to install the UR1 of course.
More info on the updates is found here: http://support.microsoft.com/kb/2785682
Note: Pay special attention to the “how to install” section as the correct version of the file needed according to your CPU architecture and local is identified:
Example for SCOM:
So if you have an agent on X86 machine you will need to run the file with F2 at the end and not the 5A.
This post will be my (and hopefully yours) one stop to post all the relevant info to SCOM 2012. I will try to generate an overview of all the different steps you need to start from scratch and continue to build your environment to a level that suites your environment.
If you feel there are things missing or you’ve found dead links please do not hesitate to leave a comment and I will update this post. This post has grown out of my favourite list of SCOM related topics and info I found on forums, technet and blogs.
Note:
This section lists all links that will give you a general overview of SCOM.
This section lists all links that will help and guide you to make a proper design and take the correct decisions concerning topology
This section lists all links to the install walkthroughs and possible issues.
This section lists all links to help you quickly setup scom after you have succesfully installed it.
This section lists all the different aspects of SCOM that need additional installation or configuration
This section lists all the links to give you the basics about management packs
This section liste all the links to the more advance management pack tips and tricks.
A list of must have community management packs to increase your productivity and solve some gaps and functionalities in scom.
Note: These management packs are written by members of the community so no warranty is given. Test before you use in production!
This section lists links to different integration possibilities between the different System Center products.
Note: System Center Blogs: Now on iPhone, Android and Windows Phone
On the 22th of November I’m hosting a LiveMeeting on how to integrate the different System Center products.
We’ll go over the different steps to integrate the different System Center products to get past the standard “just monitor it” scenario with SCOM but truly integrate the different products together.
All the products will be positioned within the System Center stack and integrations will be showcased.
If you are looking for a session to convince your boss to install more system center products or just want to convince yourself of the force of system center products brought together…
Register here:https://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032533093&Culture=en-us&community=0
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…
During my Masterclass last monday I showcased the different integration possibilities between the different system center products. One of the integrations I showcased was the integrations between SCVMM 2012 to SCOM2012.
I followed all the different steps to get things up and running but when I wanted to test the actual PRO integration service I found I had an issue.
The connection details showed an error:
“Operations Manager discovery failed with error: “Exception of type ‘Microsoft.VirtualManager.EnterpriseManagement.common.discoverydatainvalidrelationshipsourceexceptionOM10’ was thrown.
Talking about a strange error message. I checked my SCVMM jobs but nothing was out of order.
Reboot of the machine also did not solve the issue. Well here is actually how I solved the issue by following a rather strange trick.
Deselect both “Enable PRO” and “Enable Maintenance mode integration” and click refresh.
Now the connection is OK to my Opsmgr environment.
Well let’s continue with testing my PRO by enabling it and refreshing.
Error 25922 “PRO Diagnostics Target cannot be found” was thrown. A refresh of the connection once more and this was solved.
Error 25923 “PRO Diagnostics Target is not monitored” was thrown. Apparently there was still no SCOM 2012 agent on the SCVMM server due to the fact that it was not yet switched over to the new SCOM2012 environment. So pushed the agent.
After the SCOM agent was pushed another try was successful to initiate a test PRO towards scom and the message appeared in the console:
A good resource to troubleshoot the error messages can be found here:
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.