There is a new area on the Operations Manager connect site specifically for reporting management pack bugs.

https://connect.microsoft.com/OpsMgr/feedback/CreateFeedback.aspx

This will get your bug directed to the right people on the product team to get it fixed in a future release.

Great video from Vlad Joanovic talking about vNext

Link

About:
Vlad steps by our hallway studio to talk about the Beta version for OpsMgr v.Next. He informs us about new and rich UI and what has been done to the product to make is more easy to manage. He also tells about performance enhancements. We also discuss AviCode integration.

I frequently help customers install or rebuild their SCOM environment.  I find it difficult to remember every feature and sub feature required for the web console.  The SCOM documentation doesn’t specifically list which roles and features are needed to install the web console on Server 2008 and 2008 R2. 

One way to get the list of needed roles and features for the Web Console is the run the Prerequisite Viewer.

I then select more, under “Microsoft World Wide Web Service should be running and set to automatic startup mode”

Here is what it says:

For Windows Server 2008, you must add the Web Server (IIS) role and then install the following server role services:

• IIS 6 Metabase Compatibility
• IIS 6 WMI Compatibility
• Static Content
• Default Document
• Directory Browsing
• HTTP Errors
• ASP.NET
• .NET Extensibility
• ISAPI Extensions
• ISAPI Filters
• Request Filtering
• Windows Authentication

I could go to Server Manager and add the individual roles and features, but I am running Server 2008 R2 so lets make it super simple with PowerShell V2. 

1.  Launch the PowerShell command prompt

2.  Run this command

Import-Module ServerManager

3. Press Enter

4. Run this command

Add-WindowsFeature NET-Framework-Core,Web-Metabase,Web-WMI,Web-Static-Content,Web-Default-Doc,Web-Dir-Browsing,Web-Http-Errors,Web-Asp-Net,Web-Net-Ext,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Filtering,Web-Windows-Auth, Web-Mgmt-Console –restart

5. Press Enter

I then see

Now all I need to do is install the ASP.NET Ajax Extensions 1.0 from here http://go.microsoft.com/fwlink/?LinkID=89064&clcid=0×409

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=61365290-3c38-4004-b717-e90bb0f6c148&displaylang=en

Changes in This Update

Version 6.1.7695.0 of the Operations Manager Management Pack for Operations Manager 2007 R2 includes the following changes:

• Added the “Agents by Health State” report which will list all agents, management servers, gateway servers and the root management server grouped by their current health state (i.e. unavailable, error, warning or success)
• Added the “An alert subscription has been automatically disabled due to invalid configuration” rule to generate an alert when an alert subscription is disabled due to invalid configuration, such as when the account that created the subscription being deleted.
• Added the “WMI Service Availability” aggregate monitor and the “Windows Management Instrumentation Service” unit monitor to monitor the state of the Windows Management Instrumentation (WMI) service (winmgmt) on agents. By default, the unit monitor samples the WMI service every 125 seconds and generates an alert when the WMI service is not running for 3 consecutive samples. These settings can be changed by using overrides.
• Added rules to that can be enabled in place of monitors that require manual reset of the health state.
• Updated product knowledge for some workflows.
• Changed the "Computer Verification: Verification Error" event collection rule to be disabled by default. The alert from this rule would only be generated when running the discovery wizard, when the user would directly observe that one or more computer verifications failed. The alert is an unnecessary duplication.
• Change the “Collect Configuration Parse Error Events” rule to be disabled by default.
• Changed the parameter used for alert suppression for the following rules:
• Alert generation was temporarily suspended due to too many alerts
• Workflow Runtime: Failed to access a Windows event log
• Workflow Initialization: Failed to initialize access to an event log
• An error occurred during computer verification from the discovery wizard
• A generic error occurred during computer verification from the discovery wizard
• Removed alerting from the “Data Integrity” aggregate monitor and added alerting to its unit monitors:
• Repeated Event Raised
• Spoofed Data Check
• Root Connector Data Validity Check

Kevin Holman has a nice write-up explaining the changes here.

 http://blogs.technet.com/b/kevinholman/archive/2010/11/24/opsmgr-2007-r2-core-mp-s-updated-6-1-7695-0.aspx

I have updated the scripts for SCOM Remote Maintenance Mode Scheduler 2.0 to properly support SCOM R2.


Download: MaintenanceModeV4_R2.zip


The old scripts worked ok but if you had a large group of servers it would take a long time with R2. The old scripts would try to put the HealthService and the HealthServiceWatcher in maintenance mode which is no longer necessary with R2.

Another thing I added to the scripts was to not re-set the maintenance mode of a server if it is already in maintenance mode.  I have seen instances where a particular server is put into maintenance mode for a long period of time and then a scheduled maintenance mode job will re-set the maintenance mode causing noise and skewed reports.

To install the scripts just rename the old scripts and then copy the new scripts into the same “C:\MaintenanceModeV4” directory.

**You will also might need to Remove the Security from the Downloaded PowerShell Scripts

Please let me know if you come across any issues.