Scom 2012 Visio Stencils
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
SCOM: Cannot locate resource ‘momr2db.xaml’
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…
SCOM: Event id 21406: file name or class not found
Yesterday I had an issue at one of my clients with a server which was unable to check the task scheduler eventlog.
The operations log was packed with different alerts but mostly with the infamous id 21406 which in fact can mean a lot of things.
The exact message: VBScript runtime error: File name or class name not found during Automation operation: "oAPI.CreateTypePropertyBag”
My standard course of action did not solve the issue:
- Clear the cache and restart the agent
- Check the management pack and see whether it gets delivered to the agent
- Remove the agent software and reinstall.
Again these steps did not solve the issue the Events kept coming in.
Eventually I started to dig deeper and started to register the differtent dll’s again on the machine and apparently registering the MOMScriptAPI.dll solved the issue.
Probably a bad registration / link during install or upgrade caused the issue.
Hope this helps someone out there in saving his valuable troubleshooting time 🙂
SCOM 2012: shortcut tip
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 
CTRL+ 1: 
CTRL+ 2:
CTRL+ 3: 
CTRL +4: 
CTRL +5: 
Stay tuned for more tips and tricks in the series.
System Center 2012 RU3 released
Today the RU (Rollup) package 3 for System Center 2012 was released.
Improvements for the different products in the suite included minor fixes for DPM / SCOM and SCSM.
All the RU packages are cumulative so if you install RU3 the previous fixes are also included.
An overview per product:
Source the official mom team blog (=> bookmark this valuable blog!) http://blogs.technet.com/b/momteam/archive/2012/10/10/system-center-2012-update-rollup-3-ur3-released.aspx
You can find more details and instructions for obtaining and installing the update rollup on the associated KB article here:
http://support.microsoft.com/kb/2756127
Update Rollup 3 for System Center Data Protection Manager 2012 (KB2751230)
Issue 1
After you upgrade System Center Data Protection Manager 2010 to System Center Data Protection Manager 2012, the tape management report does not display overdue tapes.
Issue 2
System Center Data Protection Manager 2012 Client Protection does not scale to the limits that are expected.
Issue 3
When you try to specify a client computer name in the DPMServerName attribute by using Windows PowerShell, Windows PowerShell crashes.
Issue 4
When the name of a Microsoft SharePoint site collection contains a space, and you perform a SharePoint item-level recovery operation in System Center Data Protection Manager 2012, the operation fails.
Issue 5
After you rename a SharePoint site in System Center Data Protection Manager 2012, you cannot restore the site.
Issue 6
The SharePoint Recovery Point Status Report displays incorrect data in System Center Data Protection Manager 2012.
Issue 7
A bare metal recovery fails in certain situations.
Update Rollup 3 for System Center Operations Manager 2012 (KB2750631)
Issue 1
When you use the 32-bit version of Windows Internet Explorer to start a web console, the Microsoft.EnterpriseManagement.Presentation.Controls.SpeedometerGaugeUIController controller does not work correctly.
Issue 2
When you run a Windows PowerShell cmdlet, you receive the following error message:
Get-BPAModel is not recognized as the name of a cmdlet.
Issue 3
When you try to change a URL in the “web application availability monitoring” template instance, the change is not applied.
Update Rollup 3 for System Center Service Manager 2012 (KB2750615)
Issue 1
When you open or close the Incident form in the System Center Service Manager 2012 console, a memory leak occurs.
Issue 2
When form control objects are rooted in the Garbage-Collected (GC) Heap, the System Center Service Manager 2012 console crashes, and you receive an OutOfMemoryException exception.
Issue 3
After you change the SharePoint site language to Turkish in the System Center Service Manager 2012 portal, the display strings are displayed in English unexpectedly.
Issue 4
When you open the System Center Service Manager 2012 console by using a Citrix application, and then you open the Incident form, you experience slow performance.
Check out the blog post of kevin Greene on how to deploy this update: http://kevingreeneitblog.blogspot.ie/2012/10/scom-2012-deploying-cumulative-update.html
MMS 2013 in vegas next year teaser?
Hmmm who knows Microsoft has a sense of humor or the page has been hacked but MVP Kenny Buntinx pointed me to the page of mms2012… http://www.mms-2012.com/
After a lot of rumors that MMS2013 was going to happen in New Orleans in the beginning of June this came up on the website:
So if this is true MMS will stay loyal to the Vegas venue next year as well…
You don’t here me complaining. I can recycle my Las Vegas travel guide next year 
SCOM: How to change port of SCOM reporting
Recently I came across a customer who wanted to change the port of the Reporting server hosting the SCOM reporting services because they had no choice but to run the web console on port 80.
To do this you need to make the necessary changes to:
- Reporting services
- Firewall
- Scom
1. Change Reporting services.
If you are not sure which server is running your reporting services at the time go to Administration => Settings => reporting. In my case this shows up:
So in this case my server is VSERVER03 and it’s currently using port 8080 which I want to change to 808 in this case.
So connect to the reporting server and open the “Reporting Services Configuration Manager”
Connect to your reporting services install
NOTE: Never try to change the port in IIS itself but ALWAYS use the Reporting services config tool!
Open the web service url on the left and change the port to the desired port. In this case it’s 808
Click the advanced button
Change the port here as well by selecting the correct line and clicking edit
Change the port:
As soon as you click ok the url will be reserved on the new port and the old port reservation will be removed.
For safety also check the Report manager site identification url. Most of the time this is also at the default port 80 as shown below.
Click advanced and change the port to a desired port. In this case I use a different port: 809
Again when you click ok the reservation is made and the old reservation is being removed.
Firewall
Make sure to make the necessary changes to the firewall if there’s a firewall present between you Management servers and your reporting server. You need to open the port in both directions.
Configuring SCOM
If all went well your reporting instance is already moved to the new port but you need to let scom know that it’s on a different port. Open the Global management group settings – reporting tab by going to Administration => Settings => reporting.
Fill in the new port like shown below:
Now click ok and restart your scom console.
Try to open the reporting tab.
Note: Don’t be alarmed when it’s stuck at “loading” for a while. It will take some time to load the reports the first time.
If all went well you’ll see your shiny list of reports like shown below.
Stay tuned for more tips and tricks!
SCOM: Tips and tricks series
I’m starting a small series (or a large series who knows) of all tips and tricks while configuring and using SCOM. Some of them are very obvious for the somewhat more experienced scom admins but then again they can be useful for the people who are just getting to know the sheer power of scom.
I’ll be linking all the small tips and tricks back to this page so If you bookmark this page / RSS feed it you’ll get all the different tips and tricks right here at your fingertips.
Note: That most of these tricks are based on SCOM 2012 but will also be valuable for SCOM 2007.
SCVMM PRO integration: InvalidRelationshipSourceExceptionOM10
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.
Solution:
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:
SCOM: Monitoring Server 2012
With the recent release of the new Microsoft Windows Server 2012 many questions were raised on how to monitor the environment with your current System Center Operations Manager environment.
Well yesterday the official SCOM blog released a lot of answers to these questions in the community. Some were rather surprising others not really.
In chronological order:
System Center operations Manager 2007 R2: does not support monitoring Server 2012. There’s absolutely no way to monitor this environment with your current SCOM 2007R2 environment. The only temporary solution is to use a SCOM 2012 agent and multihome it to your SCOM 2007 environment. This however is just to get you going on the upgrade process but not really a long term solution
System Center operations manager 2012: Is supporting the monitoring of Server 2012 except from APM applications which run on IIS8.
HOWEVER: It’s not supported to install SCOM2012 components on a Server 2012 other than the agent. Also the console will not work on Win8.
System Center Operations Manager 2012 SP1: Will support all the different components, monitoring and agents.
Management packs:
Management packs for monitoring Windows Server 2012 roles which are typically made available 60 to 90 post RTM of the Windows Server Role will start to be made available from mid-September and we expect most roles to have shipped their English language MPs by the end of September. Localized MPs will start to be delivered from October for most roles. (Localized MPs will be delivered in the 8 Languages that is supported by OM2012 to begin with.)
There are no plans to ship a Management Pack for monitoring Windows 8 client machines.
So another reason to start your upgrade process to the SCOM 2012 SP1 platform if you want to monitor your brand new Server 2012 environment!
Special thanks to Oskar Landman for the tip.