You are browsing the archive for 2012 October.

SCOM 2012: shortcut tip

6:55 am in operations manager, SCOM, sysctr by Dieter Wijckmans

 

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. SNAG-0128

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 Smile

 

CTRL+ 1: SNAG-0129

CTRL+ 2:SNAG-0130

CTRL+ 3: SNAG-0131

CTRL +4: SNAG-0132

CTRL +5: SNAG-0133

 

Stay tuned for more tips and tricks in the series.

System Center 2012 RU3 released

11:41 pm in SCOM, sysctr by Dieter Wijckmans

 

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?

8:40 pm in Uncategorized by Dieter Wijckmans

 

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:

SNAG-0028

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 Smile

SCOM: How to change port of SCOM reporting

11:27 pm in Uncategorized by Dieter Wijckmans

 

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:

SNAG-0013

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”

SNAG-0012

Connect to your reporting services install

SNAG-0014

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

SNAG-0015

Click the advanced button

SNAG-0016

Change the port here as well by selecting the correct line and clicking edit

SNAG-0017

Change the port:

SNAG-0019

As soon as you click ok the url will be reserved on the new port and the old port reservation will be removed.

SNAG-0020

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.

SNAG-0022

Click advanced and change the port to a desired port. In this case I use a different port: 809

SNAG-0024

Again when you click ok the reservation is made and the old reservation is being removed.

SNAG-0025

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:

SNAG-0026

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.

SNAG-0027

 

Stay tuned for more tips and tricks!

SCOM: Tips and tricks series

11:26 pm in Uncategorized by Dieter Wijckmans

 

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.

1. How to change the port of SCOM monitoring

2. SCOM 2012 shortcut tip