[OpsMgr 2012] Free OpsMgr 2012 Virtual Machine Manager Dashboards from the OpsMgr Unleashed team

The System Center Operations Manager Unleashed team is offering a free pack of dashboards designed to provide information for System Center 2012 Virtual Machine Manager hosts and guests.

Read more on http://opsmgrunleashed.wordpress.com/2012/07/13/free-opsmgr-2012-virtual-machine-manager-dashboards-from-the-opsmgr-unleashed-team-scom/

This posting is provided "AS IS" with no warranties.

[OpsMgr 2012] Update Rollup 2 for System Center 2012 Operations Manager

Update Rollup 2 contains a number of fixes for System Center 2012 Operations Manager. See Knowledge Base Article 2706783

Version:

2012 UR2

Date published:

7/24/2012

File name	Size
SystemCenter2012OperationsManager-UR2-KB2731874-X86-X64-IA64-ENU.exe	74.5 MB	Download

Overview

Update Rollup 2 contains a number of fixes for System Center 2012 Operations Manager. See Knowledge Base Article 2706783

A detailed list of fixes can be found on Knowledge Base Article 2706783,

System requirements

Supported operating systems: Windows 7, Windows Server 2008, Windows Server 2008 R2, Windows Server 2008 R2 SP1, Windows Vista
System Center 2012 Operations Manager

Instructions

For details of included fixes and installation procedures see Knowledge Base Article 2706783.



What is fixed in this rollup for Operations Manager ?

Operations Manager (KB2731874)

Issue 1
The Windows PowerShell module runspace configuration cache grows indefinitely. This causes memory usage to increase.

Issue 2

The Set-SCOMLicense cmdlet fails if the management group evaluation expiration time-out has expired.

Operations Manager - UNIX and Linux Monitoring (Management Pack Update)

Issue 1

The System Center Operations Manager agent may crash on Oracle Solaris root zones that are configured to use a range of dedicated CPUs.

Issue 2

The UNIX/Linux agent process provider may not enumerate running processes if a process has arguments that include non-ASCII characters. This prevents process/daemon monitoring.

Issue 3

The .rpm specification file for the agent for Red Hat Enterprise Linux does not specify the distribution.

This posting is provided "AS IS" with no warranties.

[OpsMgr 2007R2][OpsMgr 2012] The System Center Data Access Service fails to start after applying KB2677070

The System Center Data Access Service fails to start after applying KB2677070

Article ID: 2730040 - View products that this article applies to.

 

After applying KB2677070 (http://support.microsoft.com/kb/2677070), the System Center Data Access Service may fail to start with a Timeout error.

 

This issue occurs because the update changes the URLs used to contact Windows Update to download the trusted and untrusted CTLs. If the old URLs were hardcoded as exceptions in the firewall or proxy, the server running the Data Access Service will fail to download the new CTLs because it can't reach the updated web address.

The workaround for this is to ublock the updated URLs in the firewall or proxy or disable CRL checking for the Data Access Service.

The updated URLs are:

http://ctldl.windowsupdate.com/msdownload/update/v3/static/trustedr/en/disallowedcertstl.cab

(http://ctldl.windowsupdate.com/msdownload/update/v3/static/trustedr/en/disallowedcertstl.cab)

http://ctldl.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab

(http://ctldl.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab)

To disable CRL checking for the Data Access Service, open Microsoft.Mom.Sdk.ServiceHost.exe.config in a text editor and add the following line in the <runtime> section:

<generatePublisherEvidence enabled="false"/>

Below is an example of this tag being added for System Center 2012 Operations Manager:

 <runtime>
<generatePublisherEvidence enabled="false"/>
      <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
        <dependentAssembly>
          <assemblyIdentity name="Microsoft.EnterpriseManagement.HealthService" publicKeyToken="31bf3856ad364e35" />
          <publisherPolicy apply="no" />
          <bindingRedirect oldVersion="6.0.4900.0" newVersion="7.0.5000.0" />
        </dependentAssembly>
        <publisherPolicy apply="no" />
        <probing privatePath="" />
      </assemblyBinding>
      <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
        <dependentAssembly>
          <assemblyIdentity name="Microsoft.Mom.Common" publicKeyToken="31bf3856ad364e35" />
          <publisherPolicy apply="no" />
          <bindingRedirect oldVersion="6.0.4900.0" newVersion="7.0.5000.0" />
        </dependentAssembly>
        <publisherPolicy apply="no" />
        <probing privatePath="" />
      </assemblyBinding>
      <gcServer enabled="true"/>
    </runtime>


The next example shows the same parameter added in the configuration file for System Center Operations Manager 2007 R2:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
    <runtime>
<generatePublisherEvidence enabled="false"/>
        <gcServer enabled="true"/>
    </runtime>


Microsoft.Mom.Sdk.ServiceHost.exe.config is found in the following directories (where x is the drive on which Operations Manager is installed):

·         System Center Operations Manager 2007 R2: x:\Program Files\System Center Operations Manager 2007
·         System Center 2012 - Operations Manager: x:\Program Files\System Center 2012\Operations Manager\Server

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use

(http://go.microsoft.com/fwlink/?LinkId=151500)

for other considerations.

 

Article ID: 2730040 - Last Review: July 9, 2012 - Revision: 2.0

APPLIES TO

• Microsoft System Center 2012 Operations Manager
• Microsoft System Center Operations Manager 2007 R2

Keywords:

kbtshoot KB2730040

This posting is provided "AS IS" with no warranties.

[OpsMgr 2007R2][OpsMgr 2012] System Center Monitoring Pack for SQL Server Base Appliance

The System Center Monitoring Pack for SQL Server Base Appliance helps you manage your SQL Server Appliances by discovering different types of SQL Server Appliances in your network and distinguishing them from other Windows Servers.

Version:	1.0.5.0	Date published:	7/12/2012
Language:	English

Files in this download

The links in this section correspond to files available for this download. Download the files appropriate for you.

File name	Size
OM2007_MP_SQLApplianceBase.doc	407 KB	Download
SQL Server Appliance Base Monitoring MP en-us.msi	508 KB	Download

Overview

​The System Center Monitoring Pack for SQL Server Base Appliancehelps you manage your SQL Server Appliances by discovering different types of SQL Server Appliances in your network and distinguishing them from other Windows Servers.

Feature Summary
The following features are new in this release of the SQL Server Appliance Base Management Pack:

• Support for remote appliance discovery
• Support for discovering Appliance clusters
• Support for different appliance hardware manufacturers and model number
• Support for System Center 2012

Existing Features

• Discover and navigate all the types of SQL Server Appliance units.
• Provide two state views: with Appliance Units and with contained servers.
• Provide alert view which focus user on SQL Appliance monitoring problems

Release History

• 7/12/2012 - Update release, version 1.0.5.0
• 2/1/2011 - Original English release, version 1.0.3.0

System requirements

Supported operating systems: Windows Server 2008 R2

• Other Software: SQL Server Appliance and System Center Operations Manager 2007 SP1 or later

This posting is provided "AS IS" with no warranties.

[OpsMgr 2012] Installing OpsMgr 2012 Agents with CU1 with a command Line

I've just read this article from  Tommy Gunn : OpsMgr 2012: Installing OpsMgr 2012 Agents from the Command Line

The script provided by Joe Thompson allow you to install the SCOM 2012 Agent and the CU1 with a single command line :

msiexec /i MOMAgent.msi /qn /l*v %TEMP%\install.log PATCH="C:\MyPath\KB2674695-amd64-Agent.msp USE_SETTINGS_FROM_AD=0 USE_MANUALLY_SPECIFIED_SETTINGS=1 MANAGEMENT_GROUP=MYNEWMG MANAGEMENT_SERVER=SCOM2012.MYDomain.net SECURE_PORT=5723 ACTIONS_USE_COMPUTER_ACCOUNT=1"

  

 Be sure parameter are correct to launch the command line.

Here is the script :

1. ' OMINSTALL.VBS
2. ' Version 1 (2012-06-27)
3. ' Joe Thompson, EP Energy LLC
4. ' OM 2012 vbs installer with CU1 agent patch and MGMT Group reconfig
5.   
6. Option Explicit
7.   
8. Dim sho, sCurPath, oReg, strKeyPath, strValueName, strComputer, strCmd, strVal, objMSConfig, intSleep, intRet
9.   
10. Set sho = Wscript.CreateObject("Wscript.Shell")
11. sCurPath = CreateObject("Scripting.FileSystemObject").GetAbsolutePathName(".")
12. strComputer = "."
13. intSleep = 15000
14. wscript.echo "Running installer..."
15. strCmd = "msiexec /i MOMAgent.msi /qn /l*v %TEMP%\install.log PATCH=" & sCurPath & "\KB2674695-amd64-Agent.msp USE_SETTINGS_FROM_AD=0 USE_MANUALLY_SPECIFIED_SETTINGS=1 MANAGEMENT_GROUP=MYNEWMG MANAGEMENT_SERVER=SCOM2012.MYDomain.net SECURE_PORT=5723 ACTIONS_USE_COMPUTER_ACCOUNT=1"
16. wscript.echo strCmd
17. intRet = sho.run(strCmd,0,True)
18.   
19. ' Let things calm down
20. wscript.echo "Sleeping..."
21. WSCript.Sleep intSleep
22.   
23. ' Check registry for OM Mgmt Group info
24. If intRet <> 0 Then
25.                 wscript.Echo "Install error occurred.... "
26.                 wscript.quit(intRet)
27. Else
28.                 On Error Resume Next
29.                 wscript.echo "Checking registry for OM 2012 EPE Mgmt Group info..."
30.                 strVal = sho.RegRead("HKLM\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Agent Management Groups\MYNEWMG\")
31.                 If Err <> 0 Then    ' regkey doesn't exist
32.                                 wscript.echo "Didn't find OM 2012 EPE Mgmt Group info, setting config..."
33.                                 Set objMSConfig = CreateObject("AgentConfigManager.MgmtSvcCfg")
34.                                 'Add a management group
35.                                 Call objMSConfig.AddManagementGroup ("MYNEWMG", "SCOM2012.MYDomain.net",5723)
36.                                 WSCript.Sleep intSleep
37.                                 wscript.echo "Reloading agent Mgmt Group configuration..."
38.                                 Call objMSConfig.ReloadConfiguration
39.                 End If
40. End If
41.   
42. wscript.quit(intRet)

This posting is provided "AS IS" with no warranties.