[OpsMgr 2012] SP1 upgrade fails with error "Failed to set DW upgrade scenario"

When performing an upgrade to OpsMgr 2012 SP1, the upgrade process fails with the following error:

Failed to set DW upgrade scenario: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: Cannot open database "OperationsManagerDW" requested by the login. The login failed.

In order to be able to relaunch the upgrade, verify that the correct Data Warehouse server name and SRS database instance name exist in the registry on the Management Server:

Data Warehouse server name:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Setup\DatawarehouseDBServerName

NOTE: This is a DWORD value and is the NetBIOS name or FQDN of the server.

SRS database instance name:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Reporting\SRSInstance

NOTE: The default SQL instance name is MSSQLSERVER but may be different in your environment if using a named instance.

Please read the original post on This page

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

[Orchestrator 2012] System Center 2012 – Orchestrator Best Practice Series–Naming Conventions

Jim Britt [MSFT], as promised, has a few blog posts coming on the topic of Best Practices as it relates to System Center 2012 – Orchestrator.  

He calls these Best Practices because He's found these practices work best for the environments he has implemented, supported, troubleshot, and optimized.  Even better, he learned these from one of the gurus in the industry (Charles Joy).  So, you could say he is channeling Charles with a bit of his own "flair". 

The fist article he has posted is called Automation–System Center 2012 – Orchestrator Best Practice Series–Naming Conventions to talk about the naming conventions for your folders, subfolders, Runbooks, Activities, etc in your environment.

Future posts will cover other best practices for System Center 2012 – Orchestrator Runbook design and optimization. 

Stay tuned! 

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

[OpsMgr 2012 SP1] Upgrading Operations Manager 2012 to SP1: The CDM Monitoring and Management Experience

DaveHatton has written an interesting article on his experience upgrading Operations Manager 2012 to SP1 on the environment od Microsoft IT.

You can read the full article >>>>>>>>>> Here <<<<<<<<<<.

Here are some details of the environment :

1 Management group

6200 agents

3 administration servers

24 gateways

2 administration servers with ACS

2 administration servers with  web Console

1 Cluster SQL (Operation DB)

1 Cluster SQL (Data Warehouse, SSRS &Reporting)

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

[OpsMgr 2007 R2][OpsMgr 2012] System Center Monitoring Pack for System Center 2012 - Configuration Manager

This Monitoring Pack monitors both System Center 2012 – Configuration Manager servers and System Center 2012 SP1 - Configuration Manager servers.

Direct link to Microsoft site

Quick details

Version:	5.00.7804.1	Date published:	2/18/2013
Change 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
ConfigMgr_MPGuide_Appendix.docx	111 KB	Download
OpsMgr_MP_ConfigMgr.docx	122 KB	Download
System Center Monitoring Pack for Configuration Manager.msi	852 KB	Download

Overview

This monitoring pack will allow you to monitor the health of Microsoft System Center 2012 – Configuration Manager by monitoring general health; data replication between Configuration Manager sites; server and service availability; SQL Server configurations; Backup and recovery; backlog monitoring; software update synchronization; and other server role configuration.

Feature Summary
This release of monitoring pack delivers improved capabilities for Configuration Manager monitoring, including the following:

• Monitoring the availability status of all server roles
• Monitoring the health status of key services
• Monitoring SQL replication health status
• Collecting and monitoring performance counters from Configuration Manager servers
• A topology diagram of the Configuration Manager site hierarchy
• Reports showing the availability status and performance of Configuration Manager servers
• Monitoring the status of Configuration Manager alerts

Release History

• 2/18/2013 - Original English release, version 5.00.7804.1

System requirements

Supported operating systems: Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Server 2008 R2 SP1, Windows Server 2012

Other Software:

• System Center Operations Manager 2007 R2 or later
• System Center Configuration Manager 2012 or Later

Instructions

1. Click the Download button on this page to start the download
2. Do one of the following:
• To start the installation immediately, click Run.
• To save the download to your computer for installation at a later time, click Save.
• To cancel the installation, click Cancel.

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

[OpsMgr 2012] Patience is a virtue with the System Center 2012 Operations Manager SP1 installation

Published on 2013, January the 16 by J.C. Hornbeck this article is very interesting and please read it before installing SP1 on your SCOM 2012 infrastructure. 

Now that System Center 2012 Service Pack 1 is released, you need to take care when applying this to your Operations Manager servers. As part of the Service Pack installation we make some changes to the OperationsManager database objects, adding additional indexes, etc... As all the management servers share the same database, these changes only need to be made when installing the Service Pack on the very first server you install to. When you run the Service Pack 1 installation it communicates with the database to determine if this is the first installation, and then decides if it needs to run a SQL update script or not.

This means that you need to be patient with your installation and wait for the first management server to have Service Pack 1 installed before beginning the next installation. If you don’t then the SQL script will run again and issues may occur. It is very early on in the Service Pack installation process that the management server checks to see if the DB has already been upgraded, so do not be tempted to tee up your other management servers and run through the initial wizard while you wait for the first server to install because by then it will be too late.

Read the full article directly on technet.

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

[Orchestrator 2012] Orchestrator (SCORCH) 2012 Reference Guides

Eswar Koneti has posted on his blog today an interesting page related to Orchestrator 2012. He has listed out all the SCORCH guides integrated with Configuration manager 2012 to make us able to start building our SCORCH environment to integrate with System center products(Configmgr 2012).

Direct link to Eswar Koneti's blog

A quick summary of the different link posted :

Start with the TechNet Documentation and the SCORCH Standard Activities.

System Center Orchestrator 2012: An Overview Video
Orchestrator 2012: a quick start deployment guide from Kelvin Holman

List of Step by Step series guides on Over View ,installation,runbook etc.

• Orchestrator 2012 Deployment & Configuration Step by Step – Part 1 “Overview and Architecture”
• Orchestrator 2012 Deployment & Configuration Step by Step – Part 2 “System Requirements”
• Orchestrator 2012 Deployment & Configuration Step by Step – Part 3 “Installation”
• Orchestrator 2012 Deployment & Configuration Step by Step – Part 4 “Build, Testing and Monitoring a Runbook
• Orchestrator 2012 Deployment & Configuration Step by Step – Part 5 “Integration Pack
• More Videos from YouTube are here
• Orchestrator Engineering Blog
• Integration Packs for System Center 2012 – Orchestrator 
• Active Directory Integration Pack for System Center 2012 - Orchestrator
• Exchange Admin Integration Pack for Orchestrator in System Center 2012 SP1
• Exchange Users Integration Pack for Orchestrator in System Center 2012 SP1
• FTP Integration Pack for Orchestrator in System Center 2012 SP1
• HP iLO and OA Integration Pack for System Center 2012 - Orchestrator
• HP Operations Manager Integration Pack for System Center 2012 - Orchestrator
• HP Service Manager Integration Pack for System Center 2012 - Orchestrator
• IBM Tivoli Netcool/OMNIbus Integration Pack for System Center 2012 - Orchestrator
• Representational State Transfer (REST) Integration Pack Guide for Orchestrator in System Center 2012 SP1
• Windows Azure Integration Pack for Orchestrator in System Center 2012 SP1
• VMware vSphere Integration Pack for System Center 2012 - Orchestrator
• Integration Packs for System Center
• Orchestrator Integration Toolkit
• System Center 2012 – Orchestrator Component Add-ons and Extensions
• System Center Orchestrator 2012: Migration Plan
• System Center Orchestrator 2012: how to build your first run book
• How to create local Variables in Run Book

Integrated with System Center Configuration Manager (configmgr) 2012:

• System Center Orchestrator Console Extension for Configuration Manager using run book commander 2.0
• How to Automate Configuration manager Application Request Via Email Using Orchestrator
• Configmgr 2012 and Orchestrator – Using Status Message as a Run book Trigger Mechanism
• Updating a SQL Cluster using Configmgr 2012 and Orchestrator (System Center 2012 Updated)
• Tracking Automatic Software Removals using Orchestrator in Configmgr /SCCM 2012

From my part, I would add a link to technet on How to Create an Orchestrator Connector that can be usefull.

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

[OpsMgr 2007 SP1 and R2] Microsoft Security Bulletin MS13-003 - Important - KB 2748552

Vulnerabilities in System Center Operations Manager Could Allow Elevation of Privilege (2748552)

http://support.microsoft.com/kb/2748552

Published: Tuesday, January 08, 2013 http://technet.microsoft.com/en-us/security/bulletin/ms13-003

Version: 1.0

General Information

Executive Summary

This security update resolves two privately reported vulnerabilities in Microsoft System Center Operations Manager. The vulnerabilities could allow elevation of privilege if a user visits an affected website by way of a specially crafted URL. An attacker would have no way to force users to visit such a website. Instead, an attacker would have to convince users to visit the website, typically by getting them to click a link in an email message or Instant Messenger message that takes users to the affected website.

This security update is rated Important for all supported editions of Microsoft System Center Operations Manager 2007. For more information, see the subsection, Affected and Non-Affected Software, in this section.

The security update addresses the vulnerabilities by modifying the way that Microsoft System Center Operations Manager accepts input. For more information about the vulnerabilities, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.

Recommendation. Microsoft recommends that customers apply the update at the earliest opportunity using update management software, or by checking for updates using the Microsoft Update service.

Known Issues. None

Affected and Non-Affected Software

The following software have been tested to determine which versions or editions are affected. Other versions or editions are either past their support life cycle or are not affected. To determine the support life cycle for your software version or edition, see Microsoft Support Lifecycle.

Affected Software

Software	Maximum Security Impact	Aggregate Severity Rating	Updates Replaced
Microsoft System Center Operations Manager 2007 Service Pack 1[1]	Elevation of Privilege	Important	None
Microsoft System Center Operations Manager 2007 R2[2][3] (KB2783850)	Elevation of Privilege	Important	None

^[1]The security update for Microsoft System Center Operations Manager 2007 Service Pack 1 is unavailable at this time.

^[2]This update is available from the Microsoft Download Center only.

^[3]This update is cumulative and replaces previous cumulative updates for the specified software.

Note: Microsoft System Center 2012 Operations Manager is Non-Affected !

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

[System Center 2012 Service Pack 1] Update Rollup 1 for System Center 2012 Service Pack 1 has been released

Description of Update Rollup 1 for System Center 2012 Service Pack 1

Article ID: 2785682

This article discusses the installation instructions for Update Rollup 1 for Microsoft System Center 2012 Service Pack 1 and the issues that are fixed in the update rollup.

Follow the installation instructions to download and install the update packages for System Center 2012 Service Pack 1.

Issues that are fixed in Update Rollup 1

App Controller (KB2790935)

Issue 1

Copying a .vhd file between Windows Azure storage accounts may be unsuccessful, and you receive a "Retrieved data is complete" warning message. This issue occurs if the .vhd file already exists on the destination or if the .vhd file is mapped to an existing virtual machine.

Issue 2

The import of Virtual Machine Manager (VMM) library server certificates may be unsuccessful for VMM library servers that are clustered.

Data Protection Manager (KB2791508)

Issue 1

Client backups fail when there is a case difference between the client computer name on the computer and the client computer name that is stored in Active Directory.

Operations Manager (KB2784734)

Issue 1

Agentless Exception Monitoring (AEM) in Operations Manager may provoke an increase in reporting threads and choke points.

Issue 2

After the Alert Attachment Management Pack (Microsoft.SystemCenter.AlertAttachment.mpb) is imported, you create a dashboard that contains an alert widget. When you click an alert, the Operations Manager console may crash.

Issue 3

When a Windows PowerShell module uses the Monitoringhost.exe process on an x86-based client that is running Windows 8, more than 800 megabytes (MB) of memory may be consumed.

Issue 4

After an application domain is created, adding another application domain may be unsuccessful.

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

Issue 1

When multiple process monitors are used to target the same computer or group, processes may incorrectly monitor some template instances. Additionally, problems with the monitored processes may not be detected. This issue occurs when each process monitor uses the same name as the process even though different argument filters are used in each process monitor.

Note After the updated Microsoft.Unix.Process.Library.mpb file is imported, all existing Process Template instances must be edited and saved for the fixed behavior to take effect.

Service Provider Foundation (KB2785476)

Issue 1

The OperatingSystemId property on a virtual hard disk (VHD) object is always set to NULL.

Issue 2

Virtual machine usage metrics are not aggregated at hourly intervals and are missing basic usage metrics such as network sent and receive I/O operations per second (IOPS).

Virtual Machine Manager (KB2792925 - Console; KB2792926 - VMM Server)

Issue 1

When a logical unit number (LUN) is unmasked on an iSCSI array, the VMM service may crash.

Issue 2

When a node is put in maintenance mode, virtual machines in the cluster change to a status of "Unsupported Cluster Configuration."

Issue 3

When an add-in that uses multiple DLL files is imported into the VMM console, the add-in is not imported. Additionally, you receive the following error message:

Add-in cannot be installed

Issue 4

When an add-in is imported into the VMM console on a server that is running Windows Server 2008 R2, the add-in is not imported.

Issue 5

When an add-in is imported into the VMM console, the console may crash.

How to obtain and install Update Rollup 1 for System Center 2012 Service Pack 1

The update packages for App Controller, Data Protection Manager, Operations Manager, Service Provider Foundation, and Virtual Machine Manager are available from Microsoft Update.

The UNIX and Linux Monitoring Pack update for Operations Manager is available from the following Microsoft Download Center website: http://www.microsoft.com/download/details.aspx?id=29696

• To obtain and install the update packages from Microsoft Update, follow these steps on a system that has an applicable System Center 2012 component installed:
  1. Click Start, and then click Control Panel.
  2. In Control Panel, double-click Windows Update.
  3. In the Windows Update window, click Check Online for updates from Microsoft Update.
  4. Click Important updates are available.
  5. Select the Update Rollup 1 packages that you want to install, and then click OK.
  6. Click Install updates to install the selected update packages.

To manually download the update packages from Microsoft Update Catalog, go to the following Microsoft websites:

• App Controller (KB2790935)
  

  Download the update package now.

  (http://catalog.update.microsoft.com/v7/site/Search.aspx?q=2790935)
• Data Protection Manager (KB2791508)
  

  Download the update package now.

  (http://catalog.update.microsoft.com/v7/site/Search.aspx?q=2791508)
• Operations Manager (KB2784734)
  

  Download the update package now.

  (http://catalog.update.microsoft.com/v7/site/Search.aspx?q=2784734)
• Service Provider Foundation (KB2785476)
  

  Download the update package now.

  (http://catalog.update.microsoft.com/v7/site/Search.aspx?q=2785476)
• Virtual Machine Manager (KB2792925 - Console, KB2792926 – VMM Server)
  

  Download the Console update package now.

  (http://catalog.update.microsoft.com/v7/site/Search.aspx?q=2792925)

Download the VMM Server update package now.

(http://catalog.update.microsoft.com/v7/site/Search.aspx?q=2792926)

To manually install the update packages, run the following command from an elevated command prompt:

msiexec.exe /update packagename

For example, to install the Virtual Machine Manager Server Update (KB2792926), run the following command:

msiexec.exe /update KB2792926-AMD64-Server.msp



For installation instruction, please read the http://support.microsoft.com/kb/2785682 page

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

System Center 2012 Service Pack 1 - Orchestrator Component Add-ons and Extensions

A collection of tools including the System Center 2012 SP1 - Orchestrator Integration Toolkit, and the System Center 2012 SP1 - Orchestrator Integration Packs

Direct link to Microsoft Site

Quick details

Version:	7.1	Date published:	1/3/2013
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
System_Center_2012_SP1_Integration_Packs.EXE	9.3 MB	Download
System_Center_2012_SP1_Orchestrator_Integration_ToolKit.exe	3.0 MB	Download

Overview

​The following System Center 2012 SP1 - Orchestrator add-ons and extensions are available for download:

System Center 2012 SP1 - Orchestrator Integration Toolkit
This toolkit contains wizard-based utilities for creating new activities and integration packs for System Center 2012 SP1 - Orchestrator . It also allows developers utilizing the Orchestrator SDK to create new custom integration packs for System Center 2012 SP1 - Orchestrator . New feature in this release- Cascading Dependencies:
Allow the user to have a progressive disclosure of information based on settings they make within the activity- the choice users make in one property affects the available choices in another property.

System Center 2012 SP1 - Orchestrator Integration Packs
System Center 2012 SP1 - Orchestrator Integration Packs extend the core System Center 2012 SP1 - Orchestrator component to enable the authoring of datacenter automation using System Center 2012 SP1 components as well as other Microsoft server products.

This download includes Integration Packs for the following System Center 2012 SP1 Components:

• System Center 2012 SP1 - Virtual Machine Manager
• System Center 2012 SP1 - Operations Manager
• System Center 2012 SP1- Data Protection Manager
• System Center 2012 SP1- Service Manager
• System Center 2012 SP1- Configuration Manager

The following Integration Packs are also included in this download.

• System Center 2012 SP1 - Orchestrator Integration Pack for REST
The Integration Pack for REST is an add-on for System Center 2012 SP1 - Orchestrator that enables you to create activities within runbooks that make requests to REST web services to get data or perform functions.
The Invoke REST Service activity is used in a runbook to make requests to RESTful web services and retrieve data or execute functions.


• System Center 2012 Service Pack 1 Integration Pack for Exchange User
The Integration Pack for Exchange Users is an add-on for System Center 2012 SP1 - Orchestrator that enables you to facilitate the automation of user centric tasks, such as sending e-mail messages, creating appointments and updating tasks


• System Center 2012 Service Pack 1 Integration Pack for Exchange Admin
The Integration Pack for Exchange Admin is an add-on for System Center 2012 SP1 - Orchestrator that enables you to facilitate the automation of Exchange administration tasks, such as mailbox management, for on-premise, remote or cloud based environments in Microsoft Exchange and Office 365.


• System Center 2012 Service Pack 1 Integration Pack for FTP
The Integration Pack for FTP enables you to automate FTP operations which include creating a folder, deleting a file or folder, downloading, uploading, file and folder listing and synchronization.


• System Center 2012 Service Pack 1 Integration Pack for Active Directory
The Integration Pack for Active Directory is an add-on for System Center 2012 - Orchestrator that enables you to connect Orchestrator to your Active Directory Server to automate its management.


• System Center 2012 Service Pack 1 Integration Pack for Windows Azure
The Integration Pack for Windows Azure is an add-on for System Center 2012 SP1 - Orchestrator that enables you to automate Windows Azure operations related to certificates, deployments, cloud services, storage, and virtual machines.

Top of page

System requirements

Supported operating systems: Windows Server 2008 R2, Windows Server 2012

Recommended Configuration for System Center 2012 SP1 Orchestrator Integration Toolkit

• RAM – minimum 1GB recommended 2GB
• Disk space minimum 200MB
• CPU Dual Core or better
• Windows 7, Windows Server 2008 R2 SP1, Windows 8 or Windows server 2012
• .Net 3.5

System Center 2012 SP1 - Orchestrator should be installed prior to installing the System Center Integration Packs.

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

[Orchestrator 2012 SP1] System Center 2012 Service Pack 1 Integration Pack for IBM Tivoli Netcool/OMNIbus

The Integration Pack for IBM Tivoli Netcool/OMNIbus is an add-on for System Center 2012 SP1 - Orchestrator that enables you to automate actions in response to alerts that are raised within IBM Tivoli Netcool/OMNIbus.

http://www.microsoft.com/en-us/download/details.aspx?id=34618



Quick details

Version:	7.1	Date published:	1/3/2013
Language:	English

File name	Size
System_Center_2012_SP1_Integration_Pack for_IBM_Netcool_OMNIbus.EXE	529 KB	Download

Overview

​The Integration Pack for IBM Tivoli Netcool/OMNIbus is an add-on for System Center 2012 SP1 - Orchestrator that enables you to automate actions in response to alerts that are raised within IBM Tivoli Netcool/OMNIbus.

Feature Summary
The Integration Pack includes the following activities:

• Create Alert
• Delete Alert
• Get Alerts
• Monitor Alert
• Update Alert

Release History

• 1/3/2013 - Original English release for System Center 2012 SP1, version 7.1
• 9/10/2012 - Beta release for System Center 2012 SP1 beta

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

[Orchestartor 2012 SP1] System Center 2012 Service Pack 1 HP Integration Packs

System Center 2012 Service Pack 1 Integration Pack for HP iLO and OA

The Integration Pack for HP Lights-Out (iLO) and Onboard Administrator (OA) is an add-on for System Center 2012 SP1 - Orchestrator that enables you to automate HP iLO and OA commands.

More details on http://www.microsoft.com/en-us/download/details.aspx?id=34616

Quick details

Version:	7.1	Date published:	1/3/2013
Language:	English

File name	Size
System_Center_2012_SP1_Integration_Pack_ for_HP_iLO_OA.exe	383 KB	Download

System Center 2012 Service Pack 1 Integration Pack for HP Service Manager

The Integration Pack for HP Service Manager is an add-on for System Center 2012 SP1 - Orchestrator that enables you to retrieve, create, update and monitor tickets in HP Service Manager.

More details on http://www.microsoft.com/en-us/download/details.aspx?id=34606

Quick details

Version:	7.1	Date published:	1/3/2013
Language:	English

File name	Size
System_Center_2012_SP1_Integration_pack_ for_HP_Service_Manager.exe	692 KB	Download

System Center 2012 Service Pack 1 Integration Pack for HP Operations Manager

The Integration Pack for HP Operations Manager is an add-on for System Center 2012 SP1 - Orchestrator that enables you to automate the consolidation and correlation of fault and performance events across you entire physical and virtual IT infrastructure

More details on http://www.microsoft.com/en-us/download/details.aspx?id=34610

Quick details

Version:	7.1	Date published:	1/3/2013
Language:	English

File name	Size
System_Center_2012_SP1_Integration_Pack_ for_HP_Operations_Manager.exe	765 KB	Download

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

[Orchestrator 2012 SP1] Runbook servers in different time zones by Anders Bengtsson

Anders Bengtsson has published on last december an interesting article to explain how Orchestrator works with schedules and different time zones.

Read his post on http://contoso.se/blog/?p=3420



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

[OpsMgr 2012] Update Rollup 1 for System Center 2012 - Operation Manager SP1

 Article ID: 2686249 - Last Review: May 7, 2012 - Revision: 3.1

 

Less than a month after the general availability of the product, Microsoft is delivering a first cumulative update package (CU1) for System Center Operations Manager 2012. He brings including support for Solaris 11 (x86 and SPARC).

This cumulative update (KB2686249) addresses the following issues :

 

 

 

Operations Manager Update (KB2674695) – Windows monitoringEnvironment crashes in Operations Manager because of RoleInstanceStatusProbe module in AzureMP.

2. When multiple (two or three) consoles are running on the same computer under the same user account, the consoles may crash.
3. You cannot start or stop tracing for Reporting and Web Console if they were installed to a stand-alone server that is running IIS.
4. Connected Group alert viewing is not working, but no error is given in console.
5. Task result - CompletedWithInfo not supported with the SDK2007 assemblies.
6. SeriesFactory and Microsoft.SystemCenter.Visualization.DatatoSeriesController have to be public to give the controls extensibility and reuse.
7. WebConsole is not FIPS compliant out of the box.
8. Network Dashboard should overlay Availability when displaying health state.
9. Dashboards: Group picker does not show all groups in large environment.
10. IIS Discovery: Prevent GetAdminSection from failing when framework version was detected incorrectly by IIS API.
11. Performance Counters are not displayed in the Application list view of AppDiagnostics.
12. Console crashes when state view with self-contained object class is opened.
13. PerformanceWidget displays stale "last value" in the legend because of core data access DataModel.
14. Availability Report and "Computer Not Reachable" Monitor display incorrect data.
15. Agent install fails on Win8 Core because of dependency on the .NET Framework 2.0.
16. Web Services Availability Monitoring Wizard - Console crashes if the wizard finishes before a test has finished.
17. Several Windows PowerShell changes are needed:

• Changed License parameter in Get-SCOMAccessLicense to ShowLicense
• Changed SCOMConnectorForTier cmdlets to SCOMTierConnector
• Some formatting changes

 

Operations Manager Update (KB2674695) – Unix and Linux monitoringSchannel error events are logged to the System log on Operations Manager Management servers and on gateways that manage UNIX/Linux agents.

2. On HP-UX, Operations Manager cannot discover and monitor a logical volume composed of more than 127 physical volumes.
3. Upgrade of UNIX and Linux agents fails when using Run As credentials in the Agent Upgrade Wizard or Update-SCXAgent Windows PowerShell cmdlet.

Operations Manager Update (KB2674695) – New featureUpdate Rollup1 for Operations Manager adds support for Oracle Solaris 11 (x86 and SPARC).

 

 

 

How to obtain and install Update Rollup 1 for System Center 2012

To download the update packages for Operations Manager, go to the following Microsoft Download Center website:

http://www.microsoft.com/downloads/details.aspx?FamilyID=c593536c-94f3-4c71-b963-5ab3b7fc05e1 (http://www.microsoft.com/downloads/details.aspx?FamilyID=c593536c-94f3-4c71-b963-5ab3b7fc05e1)

• To obtain and install the update packages from Microsoft Update, follow these steps on a system that has a Virtual Machine Manager or App Controller component installed:
  1. Click Start, and then click Control Panel.
  2. In Control Panel, double-click Windows Update.
  3. In the Windows Update window, click Check Online for updates from Microsoft Update.
  4. Click the important updates are available hyperlink.
  5. Select Update Rollup 1, and then click OK.
  6. Click Install updates to install the update package.

Installation instructions for Operations Manager

Known issues for this update

• No updates items appeared in Control Panel ARP after installing Update Rollup 1 (UR1). After installing UR1 on server and all roles (except Agent and Gateway), no update item appears in Control Panel ARP list.
• The version number of the console does not change after installing Update Rollup 1 in the UI. After installing Update Rollup 1 ,the version number of the console is still 7.0.8560.0 in the UI.
• After installing UR1 on web console, a Server Error in "/OperationsManager" Application appears in Internet Explorer. Closing and restarting Internet Explorer resolves this problem.

Notes on installation

• Operations Manager Update Rollup 1 will at first be available only in English and cannot be applied to non-English products. Fixes included in this UR will be localized in a future release.
• User must run updates as administrator.
• If UAC is enabled, MSPs must be run from an elevated command prompt window.
• System Administrator rights on the database instances for the Operational Database and Data warehouse are required in order to run updates on these databases.
• User has to close console before applying console update to avoid having to restart.
• Restart and clear cache of the browser to obtain new Silverlight instance.
• This UR should not be installed immediately after installing server. Otherwise, user could encounter an issue in which Health Service state remains uninitialized.
• Web console fixes will work after adding the following line to the %windir%\Microsoft.NET\Framework64\v2.0.50727\CONFIG\web.config file:
  
  <machineKey validationKey="AutoGenerate,IsolateApps"
  decryptionKey="AutoGenerate,IsolateApps" validation="3DES" decryption="3DES"/>
  
  The line should be added under <system.web>, as described in the following article in the Microsoft Knowledge Base:
  911722  (http://support.microsoft.com/kb/911722/ ) You may receive an error message when you access ASP.NET Web pages that have ViewState enabled after you upgrade from ASP.NET 1.1 to ASP.NET 2.0

Supported installation order

We recommend that you install this update rollup in the following order.

Note This update rollup can be installed on agents either before or after server infrastructure.

1. Server infrastructure:
   1. Management server or servers
   2. Gateway servers
   3. Reporting servers
   4. Web console server role computer
   5. Operations console role computers
   6. Manually imported management packs
2. Apply the agent update to manually installed agents, or push installation from the Pending view in the Operations console.

Note If Connected MG/Tiering is enabled, the top tier should be patched first.

Installation Information

To extract the files that are contained in this update, follow these steps:

1. Copy the following file to either a local folder or an available network share, and then execute the file to extract it:
   SystemCenter2012OperationsManager-CU1-KB2674695-X86-X64-IA64-ENU.exe
2. Apply the appropriate MSPs to each computer. All MSPs that apply to a given computer must be applied. For example, if a Management Server also has Web Console and Console roles installed, three MSP packages should be applied to the Management Server. The following MSPs are included in the update:
3. • KB2674695-AMD64-Agent.msp
   • KB2674695-AMD64-Console.msp
   • KB2674695-AMD64-Gateway.msp
   • KB2674695-AMD64-Reporting.msp
   • KB2674695-AMD64-Server.msp
   • KB2674695-AMD64-WebConsole.msp
   • KB2674695-i386-Agent.msp
   • KB2674695-i386-Console.msp
   • KB2674695-ia64-Agent.msp
4. Import the following management packs:
   1. Microsoft.SystemCenter.DataWarehouse.Library.mpb
   2. Microsoft.SystemCenter.Visualization.Library.mpb
   3. Microsoft.SystemCenter.WebApplicationSolutions.Library.mpb
      
      For information about how to import a management pack from disk, go to the following Microsoft TechNet website:
      How to Import an Operations Manager Management Pack

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