The System Center Advisor Connector for Operations Manager preview enables Operations Manager users to receive ongoing assessment of configuration for their windows computers. After installing the connector and selecting computers to be analyzed, Operations Managers users will be able to receive Advisor alerts in the Operations Manager console.
Supported operating systems: Windows Server 2012 This Preview requires Operations Manager 2012 SP1 with Update Rollup 2 installed.
Complete Operations Manager system requirements can be found at : http://technet.microsoft.com/en-us/library/jj656654.aspx
Instructions
In order to install the Advisor Connector preview:
Download the MSI provided in this page
Extract the contents to a folder in your computer
Import the extracted MPBs into the Operations Manager Console
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).
Removing an old product connector from System Center Operations Manager may be necessary if the product connector is no longer used in the environment. There is no Delete option in admin console UI for product connectors so the script below can be used to achieve the desired results.
Microsoft Support bring us a powershell script to do it in KB2626670 in Operations Manager 2007 R2
The Alert Update Connector can modify alert custom fields with additional information useful for situations like controlling alert forwarding to incident management systems and help reduce noise in the incident creation process.
Feature Summary:
Specify custom field values, owner, and ticket id for alerts generated by monitors
Override custom field values, owner, and ticket id for alerts generated by rules
System requirements
Supported operating systems: Windows Server 2008 R2
System Center 2012 Operations Manager Management Server or Console (The Alert Update Connector requires the System Center Operations Manager SDK)
Instructions
Click on the link to the right, and download SCOM2012_AlertUpdateConnector.msi
On a computer with System Center Operations Manager 2012 Management Server or Console installed, click on the MSI to extract the connector files
Navigate to the folder/directory where the connector files are extracted to and open AlertUpdateConnector.rtf
Follow the instructions in AlertUpdateConnector.rtf to install and configure the connector
This posting is provided "AS IS" with no warranties.
Orchestrator is the tool everyone should use to export/Import Alerts from Operations Manager 2012 SDK and of course there is a reason of why Microsoft does not deliver a connector as they did with 2007.
It's not really a new link - Microsoft has published this in 2009 but I had to retrieve this information for my own work and I would like to share it on my blog.
The System Center Operations Manager 2007 R2 Connectors provide System Center Operations Manager 2007 R2 alert forwarding to remote systems, such as an Enterprise Management System (EMS) or service desk system.
Operations Manager 2007 R2 Connectors provide Operations Manager 2007 R2 alert forwarding to remote systems, such as an Enterprise Management System (EMS) or a service desk system. After Operations Manager 2007 R2 forwards an alert to a remote system, that alert data is synchronized throughout the lifetime of the alert. The result of that data synchronization is a robust and seamless systems management environment. Such an environment enables cross-organization support processes to take advantage of the resources and strengths of formerly independent support groups. The ultimate effect is improved enterprise systems health through improved organizational communication.
Sharing data between Operations Manager 2007 R2 and remote systems enables enterprise correlation of events from Windows-based systems, hardware, network, and UNIX and Linux systems. Correlating these events allows IT staff to determine the causes of issues and reduce the time to resolution of IT outages.
Synchronization of data between Operations Manager 2007 R2 and remote systems also enables operational groups to use familiar management interfaces. Users update an alert by using their management tool, and the data is updated in tools that are used by other operational groups.
This release of the Operations Manager 2007 R2 Connectors includes the following Connectors:
Microsoft System Center Operations Manager 2007 R2 Connector for IBM Tivoli Enterprise Console
Microsoft System Center Operations Manager 2007 R2 Connector for HP OpenView Operations for Unix
Microsoft System Center Operations Manager 2007 R2 Connector for HP OpenView Operations for Windows
Microsoft System Center Operations Manager 2007 R2 Connector for BMC Remedy ARS
Microsoft System Center Operations Manager 2007 R2 Universal Connector
Feature Summary:
Operations Manager 2007 R2 alerts are forwarded to a remote system.
Operations Manager 2007 R2 alerts are synchronized with remote systems throughout the lifetime of the alert.
Failover to backup remote system servers is supported.
The High Availability feature supports failover to secondary Connectors that are installed on other servers in the Operations Manager 2007 R2 domain.
Multiple Operations Manager 2007 R2 management groups that are communicating with a single remote system are supported.
Multiple different remote systems can be supported with multiple Connectors that are installed in one Operations Manager 2007 R2 management group.
Delivery of Operations Manager 2007 R2 alerts is guaranteed by requiring acknowledgement from remote systems.
The Connector user interface that is integrated into the Operations Manager 2007 R2 console provides the following functionality:
Connector health status can be monitored in the Operations Manager 2007 R2 console by using Connector management packs.
Connector configuration is limited to Operations Manager 2007 R2 administrators.
Operations Manager 2007 R2 servers, remote system servers, and High Availability Connectors can be configured for communications.
Alerts forwarding is configured by selecting alert fields, mapping severity, and mapping resolution states to equivalents in a remote system.
Selected alerts can be forwarded manually from the Operations Manager 2007 R2 console.
The Operations Manager 2007 R2 Product Connector Subscription wizard allows automatic forwarding of Operations Manager 2007 R2 alerts.
The Product Connector Subscription wizard allows separate alert forwarding for multiple Connectors.
System Center Operations Manager 2007 R2 Connectors Cumulative Update 2 (KB2274165)
The Systems Center Operations Manager 2007 R2 Connectors Cumulative Update 2 is the second update for the System Center Operations Manager 2007 R2 Connectors.
The System Center Operations Manager 2007 R2 Connectors Cumulative Update 2 includes the System Center Operations Manager 2007 R2 Connectors Update (KB975774) and additional bug fixes.
Feature Summary:
This updated release includes all features that were in the previous update release (KB975774) and additional fixes in this release:
Fixes for the following issues (in previous release KB975774):
Potential high CPU usage of HP OVO Event Consumer for Windows (scinteropd.exe)
The Scinteropd.exe process of HP OVO Event Consumer for Windows sometimes increases CPU usage to a very high level. This problem occurs only in System Center Operations Manager 2007 R2 Connectors for HP Operations Manager on Windows. It occurs in all language versions of the connectors.
Synchronization issue in HP OVO Connector
HP Operations Manager and System Center Operations Manager 2007 R2 may be in an asynchronous state when alerts are forwarded that have already been resolved. Open events are still present in HP Operations Manager even though the corresponding alerts in System Center Operations Manager 2007 R2 are already resolved.
Remedy connectors do not populate the Computer Name and Domain fields
When an alert is forwarded from System Center Operations Manager 2007 R2 to Remedy, the Computer Name field and the Domain field are left blank in the Remedy notes field. This issue occurs in the release version of System Center Operations Manager 2007 R2 Connector for Remedy 6.3 and Remedy 7.1.
Unresponsiveness of the Interop provider when an Enterprise Management Service (EMS) API call returns an error
The Interop provider may stop responding and not recover when an API calls to the EMS and returns an error.
Note Usually, the API calls to Remedy.
This issue typically occurs when large localized text strings in the Custom Field Alert properties are forwarded to Remedy. However, it can also occur with other properties.
Additional issues addressed in this release:
Added Support for Remedy 7.5
This update enables support for Remedy 7.5 with the Operations Manager 2007 R2 Connector for Remedy.
Added Support for HP Operations Manager for UNIX v9
This update enables support for HP Operations Manager for UNIX v9 with the Operations Manager 2007 R2 Connector for HP Operations Manager. The Connector supports HP Operations Manager for UNIX v9 on the following platforms:
HPUX 11i v3 Itanium
Solaris 10 SPARC
RedHat Enterprise Linux 5.2 x64
Incorrect dates are passed to the remote system by the connector
The Connector performs an incorrect date conversion and forwards the incorrect date to the remote system.
Product Knowledge is not forwarded when the locale is Canadian English
If the locale on the Operations Manager server is set to Canadian English, the Product Knowledge will not be forwarded from Operations Manager to remote system, even if it is configured to do so.
This posting is provided "AS IS" with no warranties.
