SCOM Remedy connectors

Hi

I just thought of sharing my experience recently had on SCOM Remedy Integration...

SCOM Integration with 3^rd Party Product (BMC Remedy ARS 6.3)… using  connectors.

        The environment I've used is officially not tested by Microsoft ...

My environment consist of SCOM 2007 R2 running on Windows 2008 R2 SP1, ARS 6.3. I’ve tested both on SQL DB 2005 & SQL 2008 DB

ü 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.

ü  Following are the minimum requirement for SCOM Remedy Integration. As part of integration two components gets installed

§  Provider, runs on remedy environment

§  Connector, runs on SCOM environment

ü  Tool can be downloaded from below Microsoft url. The SCInterop_R2_RTM.exe has ref guide and connector & provider for all supported 3^rd party systems.

http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=20333

Pre-requisite for Provider & Connector components:

•             A server with Remedy User application (v6.3 or higher) at least (don’t need Remedy Server specifically). Minimum OS Windows 2003 + SP2  (for provider)

•             The English version of Microsoft Visual C++ 2008 Redistributable Package (x86) if Visual C++ 2008 is not installed. (for both connector and provider)

•             WS-Management 1.1 (for both connector and provider)

•             Local admin permission for Domain account on the given Remedy server

•             A User in Remedy with administrative privileges

•             .NET Framework 3.0 SP1 or a later version (connector)

•             Server running SCOM console at least and DB Instance running on SQL 2005 minimum.     OS Windows 2003 + SP2 minimum

Installation order:

i. First install provider on a windows 2003 server. For that execute SciProviderSetup.exe and click next to begin Installation.

ii. Select BMC Remedy ARS 6.3 Provider, click next next and finish the installation.

iii. Reboot the server after provider installation.

iv. Install connector on the server by executing SciConnectorSetup_x64.exe.

v. select BMC Remedy connector service and connector configuration option and click next.

vi. On SQL server configuration wizard specify your Database server. Database Name would remain default as (SCInterop) with default SQL Server port (1433) and click next.

vii. On next screen specify connector login service name and password click next and complete the installation.

viii. Now opsmgr configuration wizard comes up here specify the configuration for Remedy server, version and ws-man server credentials. Click next and complete the configuration.

ix. on next screen click next for connector certificate installation. Reboot the server after successful installation.

x. Provider and connector are installed now. It’s time to import Interface Forms, Filters, and Data Files

on Remedy server.  The .xml file that contains these forms and filters are copied to the Interop Provider installation folder.

The files are SCIOpsMgr2007Interface-63.xml and SCIStateTransitions.xml. For import of files please follow step by step process on the below link:

http://technet.microsoft.com/en-us/library/ee210412.aspx

xi. Once definition files are imported on the Remedy server you can check forwarding alerts to the Remedy server.

xii. Now remedy dll file need to be updated on the server running provider component. ScInteropRemedy63.dll file needs to be updated (if running ARS 6.3 only). For updating the dll file stop WMI service à go to %windows%\system32\wbem and replace the ScInteropRemedy63.dll. Reboot the server after overriding the file.

xiv. Check forwarding alerts to the Remedy server by right clicking on any alert in SCOM console à right click à forward to à opsmgr connector for  BMC Remedy.

xvi. Check the status in Remedy for the ticket created against the alert.

xvii. Install SCOM 2007 R2 connector hotfix OM2007R2Connectors-KB2274165 on both provider and connector to stay updated.

Thanks,

Varun Kaura

Updated SCOM Active Directory Management Pack Released

Recently updated ADMP released - version 6.0.7822.0

The March 2012 revision of the Monitoring Pack for Active Directory includes the following changes:

• Corrected some Publisher names (for example, changed from PublisherName=KDC to PublisherName=Microsoft-Windows-Kerberos-Key-Distribution-Center)
• Updated rules to generate Alerts and not only go to the Event Viewer
• Removed unnecessary check for Event Source Name for all NTDS rules (for example, removed EventSourceName=”NTDS General”)
• Corrected event parameter validation
• Updated queries to search for correct event IDs
• Fixed spelling errors
• Added missing descriptions to rules
• Fixed problems with Health Monitoring scripts
• Removed user name checks from Userenv rules

Use below url for more information and to download the MP
 http://www.microsoft.com/download/en/details.aspx?id=21357


Thanks,

Varun

System Center 2012 Operations Manager Survival Guide

Survival Guide can be used to learn the fundamentals; increase your current knowledge; or stay current on Operations Manager and events... so connect to
http://social.technet.microsoft.com/wiki/contents/articles/7809.system-center-2012-operations-manager-survival-guide-en-us.aspx


Thanks & Regards,

Varun Kaura

SCOM 2007 R2 SLD Service Level Dashboard

I just want to share my experince on SCOM SLD which I configured on a machine in test env. I specfically used test environment as I was not sure whether it would work or not on a single server.

Before this test I've already installed these products/applications on different servers and it just work .. no issues...

So, my env has a Server running Windows 2003 + SP2 + SQL 2005 and SQL SP2, SCOM 2007 R2 + CU5 everything on one machine.


SCOM SLD/WSS on a same server and some consideration if you are testing
-Everything was working fine (from SCOM perspective) before instaling WSS and SLD configuration. SCOM was running fine.. reports were accessible
-Then i installed WSS 3.0 + SP2/SLD 2.0 on the same server and configured as required using SLD doc. Though i was little apprehensive but then thought of just giv a try setting up on same server
-So after installation I checked WSS and could configure SLD in sharepoint
-Now, when i went to scom monitoring section and tried to open report directly for the alert generated then it failed ... oh!... then i relaized the mistake i did. I came back to reporting section and tried opening reports frm there as well.. no luck... it just failed with the long error message.

Steps taken for identifying the issue
-----------------------------------
-Report url did not run
-Default web site and report sites were stop in IIS which was after WSS installation

Solution
--------
Changed Default web site port
Checked setting under Reporting Service Configuration .. which was ok
Most important change report url port in SCOM console under admin tab
restart the server --- tested again and worked


Hope this helps anyone who is using the same kind of scenario as used by me here

Varun

Download System Center 2012 Release Candidate for your Private Cloud

Download Microsoft Private Cloud Evaluation Software. Microsoft private cloud solutions are built on System Center and Windows Server 2008 R2 SP1 available at below url:

http://technet.microsoft.com/en-us/evalcenter/hh505660.aspx

scom 2012 RC

Step by step information for installing SCOM 2012 RC can be found at below link.....

Step by step guide for SCOM 2012 RC installation with screenshots


Cheers ...

Varun

Agents not updated with SCOM CU5

If scom agents are installed after applying SCOM CU5 and in case you find not updated with the CU5 patch. In that case just repair those agents. This will update agents with CU.