Hi experts, I am using HP Operations manager for windows version 9.0. I can not find SCOM connector for HP Operations Manager for windows 9. Do you know link download this connector? help me please,

Regards, Tutv

If don't have SCOM connector for HP Operations Manager for windows version 9 so how can i configure integrating SCOM with HP OMW9 through SNMP Trap (forward from SCOM to HP OMW9).

Any one know this solution please help me,

Thanks and regards,

Tutv

Tutv,

HP OM 9.X is supported and can be downloaded from here:

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

Regards,

-Steve

Hi Steve,

Thank you for your help.

I needing Interop Connector for HP Operations manager for Windows version 9, but your links for HP Operations Manager for UNIX v9

Rgds,

Tutv

Tutv,

HP OM 9.x on Windows is not supported. It was not released at the time CU2 was released so it did not make it in the CU.

That said, HP OM 9.x works with the connector but there are issues getting it installed if HP OM 9 is installed on a 64 bit version of Windows. You can get around this issue by creating the 32 bit registry key on the HP OM server under HKLM\SOFTWARE\Hewlett-Packard\HP OpenView\InstallDir (this key should already exist under the 64 bit tree) and point it to the appropriate directory HP OM is installed under before installing the provider for the connector.

Note that this is known to work but support will be limited as it is not a supported configuration.

Regards,

-Steve

Hi Steve,

SciProviderSetup can running on Windows server 2008 64 bit but it can not check HP OM for Windows version 9 running on this server,

Below is a image captured when i install :SciProviderSetup.exe" file

Rgds,

Tutv

Tutv,

Yes - this is what I mentioned above. The provider is a 32 bit application and HP OM was only supported as a 32 bit application prior to HP OM 9.X so the provider is looking for it under the 32 bit registry. Just create a new key (see previous post) under the 32 bit tree of the registry and it will work.

Regards,

-Steve

Hi Steve,

Please help me, how can i create new key under the  32 bit tree  because key name "InstallDir" already exist?

Thanks and best regards,

Tutv

Tutv,

Try under the HKLM\Software\Wow6432Node

See here for details - http://msdn.microsoft.com/en-us/library/ms724072%28v=VS.85%29.aspx

-Steve

Hi Steve,

I already create key installDir on HKLM\Software\Wow6432Node\Hewlett-Packard\HP OpenView\InstallDir

Contant of InstallDir key is "C:\Program Files (x86)\HP\\HP BTO Software\" and re-install SciProviderSetup but it still same error?

Rgds,

Tutv

Tutv,

Just ran the installer on a new build of HP OM 9 for Windows after creating the following key in the registry. Installer ran without issues.

-Steve

• Edited by Steve Weber [MSFT]Microsoft employee, Moderator Wednesday, October 19, 2011 3:51 PM

Tutv,

Just ran the installer on a new build of HP OM 9 for Windows after creating the following key in the registry. Installer ran without issues.

-Steve

• Edited by Steve Weber [MSFT]Microsoft employee, Moderator Wednesday, October 19, 2011 3:51 PM

Tutv,

Just ran the installer on a new build of HP OM 9 for Windows after creating the following key in the registry. Installer ran without issues.

-Steve

• Edited by Steve Weber [MSFT]Microsoft employee, Moderator Wednesday, October 19, 2011 3:51 PM

Tutv,

Just ran the installer on a new build of HP OM 9 for Windows after creating the following key in the registry. Installer ran without issues.

-Steve

• Edited by Steve Weber [MSFT]Microsoft employee, Moderator Wednesday, October 19, 2011 3:51 PM

Tutv,

Just ran the installer on a new build of HP OM 9 for Windows after creating the following key in the registry. Installer ran without issues.

-Steve

• Edited by Steve Weber [MSFT]Microsoft employee, Moderator Wednesday, October 19, 2011 3:51 PM

Tutv,

Just ran the installer on a new build of HP OM 9 for Windows after creating the following key in the registry. Installer ran without issues.

-Steve

• Edited by Steve Weber [MSFT]Microsoft employee, Moderator Wednesday, October 19, 2011 3:51 PM

Tutv,

Just ran the installer on a new build of HP OM 9 for Windows after creating the following key in the registry. Installer ran without issues.

-Steve

• Edited by Steve Weber [MSFT]Microsoft employee, Moderator Wednesday, October 19, 2011 3:51 PM

Tutv,

Just ran the installer on a new build of HP OM 9 for Windows after creating the following key in the registry. Installer ran without issues.

-Steve

• Edited by Steve Weber [MSFT]Microsoft employee, Moderator Wednesday, October 19, 2011 3:51 PM

Tutv,

Just ran the installer on a new build of HP OM 9 for Windows after creating the following key in the registry. Installer ran without issues.

-Steve

• Edited by Steve Weber [MSFT]Microsoft employee, Moderator Wednesday, October 19, 2011 3:51 PM

Tutv,

Just ran the installer on a new build of HP OM 9 for Windows after creating the following key in the registry. Installer ran without issues.

-Steve

• Edited by Steve Weber [MSFT]Microsoft employee, Moderator Wednesday, October 19, 2011 3:51 PM

Tutv,

Just ran the installer on a new build of HP OM 9 for Windows after creating the following key in the registry. Installer ran without issues.

-Steve

• Edited by Steve Weber [MSFT]Microsoft employee, Moderator Wednesday, October 19, 2011 3:51 PM

Tutv,

Just ran the installer on a new build of HP OM 9 for Windows after creating the following key in the registry. Installer ran without issues.

-Steve

• Edited by Steve Weber [MSFT]Microsoft employee, Moderator Wednesday, October 19, 2011 3:51 PM

Tutv,

Just ran the installer on a new build of HP OM 9 for Windows after creating the following key in the registry. Installer ran without issues.

-Steve

• Edited by Steve Weber [MSFT]Microsoft employee, Moderator Wednesday, October 19, 2011 3:51 PM

Tutv,

Just ran the installer on a new build of HP OM 9 for Windows after creating the following key in the registry. Installer ran without issues.

-Steve

• Edited by Steve Weber [MSFT]Microsoft employee, Moderator Wednesday, October 19, 2011 3:51 PM

Tutv,

Just ran the installer on a new build of HP OM 9 for Windows after creating the following key in the registry. Installer ran without issues.

-Steve

• Edited by Steve Weber [MSFT]Microsoft employee, Moderator Wednesday, October 19, 2011 3:51 PM

Tutv,

Just ran the installer on a new build of HP OM 9 for Windows after creating the following key in the registry. Installer ran without issues.

-Steve

Tutv,

Just ran the installer on a new build of HP OM 9 for Windows after creating the following key in the registry. Installer ran without issues.

-Steve

• Edited by Steve Weber [MSFT]Microsoft employee, Moderator Wednesday, October 19, 2011 3:51 PM

Tutv,

Just ran the installer on a new build of HP OM 9 for Windows after creating the following key in the registry. Installer ran without issues.

-Steve

• Edited by Steve Weber [MSFT]Microsoft employee, Moderator Wednesday, October 19, 2011 3:51 PM

Tutv,

Just ran the installer on a new build of HP OM 9 for Windows after creating the following key in the registry. Installer ran without issues.

-Steve

• Edited by Steve Weber [MSFT]Microsoft employee, Moderator Wednesday, October 19, 2011 3:51 PM

Tutv,

Just ran the installer on a new build of HP OM 9 for Windows after creating the following key in the registry. Installer ran without issues.

-Steve

• Edited by Steve Weber [MSFT]Microsoft employee, Moderator Wednesday, October 19, 2011 3:51 PM

Tutv,

Just ran the installer on a new build of HP OM 9 for Windows after creating the following key in the registry. Installer ran without issues.

-Steve

• Edited by Steve Weber [MSFT]Microsoft employee, Moderator Wednesday, October 19, 2011 3:51 PM

Hi Steve,

I can install interop provider on HP OMW 9 server, I will test and update result for you.

Thanks for your helps,

Tutv,

Rgds

Hi Steve,

Are you able to advice:

My hp omw9 is running on cluster. Have you tried your solution on a cluster before and does it work if my scom is scom sp1?

Thanks

Regards

lyh 

Lyh,

Are we talking SCOM 2007 R2? The connectors are only supported on SCOM 2007 R2 so if it's just SCOM 2007 SP1 it will not work.

If SCOM 2007 R2, it should work but I have not tried it so you are in uncharted waters here. Below is what will be required to make it work in a HP OM cluster.

- Install provider on all HP OM servers in the cluster.

- Generate a self-signed certificate with the FQDN name of the cluster (makecert.exe is the tool you will need). Make sure the cluster name is in DNS (forward and reverse lookup).

- Install the self-signed key onto all HP OM servers.

- Remove any existing certificates in the connector install directory - Default is - C:\Program Files (x86)\System Center Operations Manager 2007 Providers\Operations Manager 2007 Connector to HP OVO Provider. The existing certificate is generally the <node name of the server>.cer.

- Copy the public key of the self-signed cluster name certificate into the connector install directory on all HP OM servers. Default is - C:\Program Files (x86)\System Center Operations Manager 2007 Providers\Operations Manager 2007 Connector to HP OVO Provider

- Once complete install the connector on the SCOM 2007 R2 server or any other server in the same domain as the SCOM 2007 R2 server and when you go to configure the connector use the cluster name for the HP OM server.

- If all goes well it should use the cluster certificate and connect to whatever node is active in the cluster.

 Regards,

-Steve

Hi Steve,

I already install provider and enable WS on all HP OM server, then i install Connector Components for Operations Manager 2007 R2, at Connector Configuration UI components i put information about HP OM server (Include Server Name which added on Hosts file and user/password but its show error " Can not connect <Server_name> with the provided user name and password.. "

I can ping HP OM server through Hostname and user/password right from SCOM server

Capture on SCOM server

I already remove and re-install provider and connector but its still error,

Do I need configuring more?

Rgds,

Tutv

Tutv,

Verify port 1270 is open to the provider server than try the following command from a command prompt on the SCOM 2007 R2 box:

winrm e http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scx/* -r:https://<HP OM server>:1270 -u:administrator -p:<Local admin password> -auth:basic -encoding:utf-8 -skipCAcheck -skipCNcheck -filter:"select * from SCX_Connector where ManagementGroupName = 'test'"

If the command works it will return nothing, if it fails post the error message.

Regards,

-Steve

• Edited by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, October 25, 2011 12:30 PM

Tutv,

Verify port 1270 is open to the provider server than try the following command from a command prompt on the SCOM 2007 R2 box:

winrm e http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scx/* -r:https://<HP OM server>:1270 -u:administrator -p:<Local admin password> -auth:basic -encoding:utf-8 -skipCAcheck -skipCNcheck -filter:"select * from SCX_Connector where ManagementGroupName = 'test'"

If the command works it will return nothing, if it fails post the error message.

Regards,

-Steve

• Edited by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, October 25, 2011 12:30 PM

Tutv,

Verify port 1270 is open to the provider server than try the following command from a command prompt on the SCOM 2007 R2 box:

winrm e http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scx/* -r:https://<HP OM server>:1270 -u:administrator -p:<Local admin password> -auth:basic -encoding:utf-8 -skipCAcheck -skipCNcheck -filter:"select * from SCX_Connector where ManagementGroupName = 'test'"

If the command works it will return nothing, if it fails post the error message.

Regards,

-Steve

• Edited by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, October 25, 2011 12:30 PM

Tutv,

Verify port 1270 is open to the provider server than try the following command from a command prompt on the SCOM 2007 R2 box:

winrm e http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scx/* -r:https://<HP OM server>:1270 -u:administrator -p:<Local admin password> -auth:basic -encoding:utf-8 -skipCAcheck -skipCNcheck -filter:"select * from SCX_Connector where ManagementGroupName = 'test'"

If the command works it will return nothing, if it fails post the error message.

Regards,

-Steve

• Edited by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, October 25, 2011 12:30 PM

Tutv,

Verify port 1270 is open to the provider server than try the following command from a command prompt on the SCOM 2007 R2 box:

winrm e http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scx/* -r:https://<HP OM server>:1270 -u:administrator -p:<Local admin password> -auth:basic -encoding:utf-8 -skipCAcheck -skipCNcheck -filter:"select * from SCX_Connector where ManagementGroupName = 'test'"

If the command works it will return nothing, if it fails post the error message.

Regards,

-Steve

• Edited by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, October 25, 2011 12:30 PM

Tutv,

Verify port 1270 is open to the provider server than try the following command from a command prompt on the SCOM 2007 R2 box:

winrm e http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scx/* -r:https://<HP OM server>:1270 -u:administrator -p:<Local admin password> -auth:basic -encoding:utf-8 -skipCAcheck -skipCNcheck -filter:"select * from SCX_Connector where ManagementGroupName = 'test'"

If the command works it will return nothing, if it fails post the error message.

Regards,

-Steve

• Edited by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, October 25, 2011 12:30 PM

Tutv,

Verify port 1270 is open to the provider server than try the following command from a command prompt on the SCOM 2007 R2 box:

winrm e http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scx/* -r:https://<HP OM server>:1270 -u:administrator -p:<Local admin password> -auth:basic -encoding:utf-8 -skipCAcheck -skipCNcheck -filter:"select * from SCX_Connector where ManagementGroupName = 'test'"

If the command works it will return nothing, if it fails post the error message.

Regards,

-Steve

• Edited by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, October 25, 2011 12:30 PM

Tutv,

Verify port 1270 is open to the provider server than try the following command from a command prompt on the SCOM 2007 R2 box:

winrm e http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scx/* -r:https://<HP OM server>:1270 -u:administrator -p:<Local admin password> -auth:basic -encoding:utf-8 -skipCAcheck -skipCNcheck -filter:"select * from SCX_Connector where ManagementGroupName = 'test'"

If the command works it will return nothing, if it fails post the error message.

Regards,

-Steve

• Edited by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, October 25, 2011 12:30 PM

Tutv,

Verify port 1270 is open to the provider server than try the following command from a command prompt on the SCOM 2007 R2 box:

winrm e http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scx/* -r:https://<HP OM server>:1270 -u:administrator -p:<Local admin password> -auth:basic -encoding:utf-8 -skipCAcheck -skipCNcheck -filter:"select * from SCX_Connector where ManagementGroupName = 'test'"

If the command works it will return nothing, if it fails post the error message.

Regards,

-Steve

• Edited by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, October 25, 2011 12:30 PM

Tutv,

Verify port 1270 is open to the provider server than try the following command from a command prompt on the SCOM 2007 R2 box:

winrm e http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scx/* -r:https://<HP OM server>:1270 -u:administrator -p:<Local admin password> -auth:basic -encoding:utf-8 -skipCAcheck -skipCNcheck -filter:"select * from SCX_Connector where ManagementGroupName = 'test'"

If the command works it will return nothing, if it fails post the error message.

Regards,

-Steve

• Edited by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, October 25, 2011 12:30 PM

Tutv,

Verify port 1270 is open to the provider server than try the following command from a command prompt on the SCOM 2007 R2 box:

winrm e http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scx/* -r:https://<HP OM server>:1270 -u:administrator -p:<Local admin password> -auth:basic -encoding:utf-8 -skipCAcheck -skipCNcheck -filter:"select * from SCX_Connector where ManagementGroupName = 'test'"

If the command works it will return nothing, if it fails post the error message.

Regards,

-Steve

• Edited by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, October 25, 2011 12:30 PM

Tutv,

Verify port 1270 is open to the provider server than try the following command from a command prompt on the SCOM 2007 R2 box:

winrm e http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scx/* -r:https://<HP OM server>:1270 -u:administrator -p:<Local admin password> -auth:basic -encoding:utf-8 -skipCAcheck -skipCNcheck -filter:"select * from SCX_Connector where ManagementGroupName = 'test'"

If the command works it will return nothing, if it fails post the error message.

Regards,

-Steve

• Edited by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, October 25, 2011 12:30 PM

Tutv,

Verify port 1270 is open to the provider server than try the following command from a command prompt on the SCOM 2007 R2 box:

winrm e http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scx/* -r:https://<HP OM server>:1270 -u:administrator -p:<Local admin password> -auth:basic -encoding:utf-8 -skipCAcheck -skipCNcheck -filter:"select * from SCX_Connector where ManagementGroupName = 'test'"

If the command works it will return nothing, if it fails post the error message.

Regards,

-Steve

• Edited by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, October 25, 2011 12:30 PM

Tutv,

Verify port 1270 is open to the provider server than try the following command from a command prompt on the SCOM 2007 R2 box:

winrm e http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scx/* -r:https://<HP OM server>:1270 -u:administrator -p:<Local admin password> -auth:basic -encoding:utf-8 -skipCAcheck -skipCNcheck -filter:"select * from SCX_Connector where ManagementGroupName = 'test'"

If the command works it will return nothing, if it fails post the error message.

Regards,

-Steve

• Edited by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, October 25, 2011 12:30 PM

Tutv,

Verify port 1270 is open to the provider server than try the following command from a command prompt on the SCOM 2007 R2 box:

winrm e http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scx/* -r:https://<HP OM server>:1270 -u:administrator -p:<Local admin password> -auth:basic -encoding:utf-8 -skipCAcheck -skipCNcheck -filter:"select * from SCX_Connector where ManagementGroupName = 'test'"

If the command works it will return nothing, if it fails post the error message.

Regards,

-Steve

• Edited by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, October 25, 2011 12:30 PM

Tutv,

Verify port 1270 is open to the provider server than try the following command from a command prompt on the SCOM 2007 R2 box:

winrm e http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scx/* -r:https://<HP OM server>:1270 -u:administrator -p:<Local admin password> -auth:basic -encoding:utf-8 -skipCAcheck -skipCNcheck -filter:"select * from SCX_Connector where ManagementGroupName = 'test'"

If the command works it will return nothing, if it fails post the error message.

Regards,

-Steve

Tutv,

Verify port 1270 is open to the provider server than try the following command from a command prompt on the SCOM 2007 R2 box:

winrm e http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scx/* -r:https://<HP OM server>:1270 -u:administrator -p:<Local admin password> -auth:basic -encoding:utf-8 -skipCAcheck -skipCNcheck -filter:"select * from SCX_Connector where ManagementGroupName = 'test'"

If the command works it will return nothing, if it fails post the error message.

Regards,

-Steve

• Edited by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, October 25, 2011 12:30 PM

Tutv,

Verify port 1270 is open to the provider server than try the following command from a command prompt on the SCOM 2007 R2 box:

winrm e http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scx/* -r:https://<HP OM server>:1270 -u:administrator -p:<Local admin password> -auth:basic -encoding:utf-8 -skipCAcheck -skipCNcheck -filter:"select * from SCX_Connector where ManagementGroupName = 'test'"

If the command works it will return nothing, if it fails post the error message.

Regards,

-Steve

• Edited by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, October 25, 2011 12:30 PM

Tutv,

Verify port 1270 is open to the provider server than try the following command from a command prompt on the SCOM 2007 R2 box:

winrm e http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scx/* -r:https://<HP OM server>:1270 -u:administrator -p:<Local admin password> -auth:basic -encoding:utf-8 -skipCAcheck -skipCNcheck -filter:"select * from SCX_Connector where ManagementGroupName = 'test'"

If the command works it will return nothing, if it fails post the error message.

Regards,

-Steve

• Edited by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, October 25, 2011 12:30 PM

Tutv,

Verify port 1270 is open to the provider server than try the following command from a command prompt on the SCOM 2007 R2 box:

winrm e http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scx/* -r:https://<HP OM server>:1270 -u:administrator -p:<Local admin password> -auth:basic -encoding:utf-8 -skipCAcheck -skipCNcheck -filter:"select * from SCX_Connector where ManagementGroupName = 'test'"

If the command works it will return nothing, if it fails post the error message.

Regards,

-Steve

• Edited by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, October 25, 2011 12:30 PM

Tutv,

Verify port 1270 is open to the provider server than try the following command from a command prompt on the SCOM 2007 R2 box:

winrm e http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scx/* -r:https://<HP OM server>:1270 -u:administrator -p:<Local admin password> -auth:basic -encoding:utf-8 -skipCAcheck -skipCNcheck -filter:"select * from SCX_Connector where ManagementGroupName = 'test'"

If the command works it will return nothing, if it fails post the error message.

Regards,

-Steve

• Edited by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, October 25, 2011 12:30 PM

Hi Steve,

I tried command on SCOM 2007 R2 server, its show below error

And check port 1270 listenning on HP OMW9 server. You can see emage capture bellow its dosen't have port number 1270 listenning on HP OMW server but process ScInteropd running on this server

Rgds,

Tutv

Hi Steve,

I edited your command and running again, Bellow is out put

Rgds,

Tutv

Tutv,

The scinteropd is a secondary service that monitors HP OM for updates to SCOM 2007 alerts. This is not the provider itself which is built into WMI and you will not specifically see it running via 'Windows Task Manager'.

Your best bet for troubleshooting the connector is to go here --> http://technet.microsoft.com/en-us/library/ee809020.aspx and 'Enable Tracing for the Windows Provider'. Once set reboot the server and monitor the c:\sci.log. Post your results if you are still having issues.

Regards,

-Steve

• Proposed as answer by Steve Weber [MSFT]Microsoft employee, Moderator Thursday, November 17, 2011 1:31 PM

Tutv,

The scinteropd is a secondary service that monitors HP OM for updates to SCOM 2007 alerts. This is not the provider itself which is built into WMI and you will not specifically see it running via 'Windows Task Manager'.

Your best bet for troubleshooting the connector is to go here --> http://technet.microsoft.com/en-us/library/ee809020.aspx and 'Enable Tracing for the Windows Provider'. Once set reboot the server and monitor the c:\sci.log. Post your results if you are still having issues.

Regards,

-Steve

• Proposed as answer by Steve Weber [MSFT]Microsoft employee, Moderator Thursday, November 17, 2011 1:31 PM

Tutv,

The scinteropd is a secondary service that monitors HP OM for updates to SCOM 2007 alerts. This is not the provider itself which is built into WMI and you will not specifically see it running via 'Windows Task Manager'.

Your best bet for troubleshooting the connector is to go here --> http://technet.microsoft.com/en-us/library/ee809020.aspx and 'Enable Tracing for the Windows Provider'. Once set reboot the server and monitor the c:\sci.log. Post your results if you are still having issues.

Regards,

-Steve

• Proposed as answer by Steve Weber [MSFT]Microsoft employee, Moderator Thursday, November 17, 2011 1:31 PM

Tutv,

The scinteropd is a secondary service that monitors HP OM for updates to SCOM 2007 alerts. This is not the provider itself which is built into WMI and you will not specifically see it running via 'Windows Task Manager'.

Your best bet for troubleshooting the connector is to go here --> http://technet.microsoft.com/en-us/library/ee809020.aspx and 'Enable Tracing for the Windows Provider'. Once set reboot the server and monitor the c:\sci.log. Post your results if you are still having issues.

Regards,

-Steve

• Proposed as answer by Steve Weber [MSFT]Microsoft employee, Moderator Thursday, November 17, 2011 1:31 PM

Tutv,

The scinteropd is a secondary service that monitors HP OM for updates to SCOM 2007 alerts. This is not the provider itself which is built into WMI and you will not specifically see it running via 'Windows Task Manager'.

Your best bet for troubleshooting the connector is to go here --> http://technet.microsoft.com/en-us/library/ee809020.aspx and 'Enable Tracing for the Windows Provider'. Once set reboot the server and monitor the c:\sci.log. Post your results if you are still having issues.

Regards,

-Steve

• Proposed as answer by Steve Weber [MSFT]Microsoft employee, Moderator Thursday, November 17, 2011 1:31 PM

Tutv,

The scinteropd is a secondary service that monitors HP OM for updates to SCOM 2007 alerts. This is not the provider itself which is built into WMI and you will not specifically see it running via 'Windows Task Manager'.

Your best bet for troubleshooting the connector is to go here --> http://technet.microsoft.com/en-us/library/ee809020.aspx and 'Enable Tracing for the Windows Provider'. Once set reboot the server and monitor the c:\sci.log. Post your results if you are still having issues.

Regards,

-Steve

• Proposed as answer by Steve Weber [MSFT]Microsoft employee, Moderator Thursday, November 17, 2011 1:31 PM

Tutv,

The scinteropd is a secondary service that monitors HP OM for updates to SCOM 2007 alerts. This is not the provider itself which is built into WMI and you will not specifically see it running via 'Windows Task Manager'.

Your best bet for troubleshooting the connector is to go here --> http://technet.microsoft.com/en-us/library/ee809020.aspx and 'Enable Tracing for the Windows Provider'. Once set reboot the server and monitor the c:\sci.log. Post your results if you are still having issues.

Regards,

-Steve

• Proposed as answer by Steve Weber [MSFT]Microsoft employee, Moderator Thursday, November 17, 2011 1:31 PM

Tutv,

The scinteropd is a secondary service that monitors HP OM for updates to SCOM 2007 alerts. This is not the provider itself which is built into WMI and you will not specifically see it running via 'Windows Task Manager'.

Your best bet for troubleshooting the connector is to go here --> http://technet.microsoft.com/en-us/library/ee809020.aspx and 'Enable Tracing for the Windows Provider'. Once set reboot the server and monitor the c:\sci.log. Post your results if you are still having issues.

Regards,

-Steve

• Proposed as answer by Steve Weber [MSFT]Microsoft employee, Moderator Thursday, November 17, 2011 1:31 PM

Tutv,

The scinteropd is a secondary service that monitors HP OM for updates to SCOM 2007 alerts. This is not the provider itself which is built into WMI and you will not specifically see it running via 'Windows Task Manager'.

Your best bet for troubleshooting the connector is to go here --> http://technet.microsoft.com/en-us/library/ee809020.aspx and 'Enable Tracing for the Windows Provider'. Once set reboot the server and monitor the c:\sci.log. Post your results if you are still having issues.

Regards,

-Steve

• Proposed as answer by Steve Weber [MSFT]Microsoft employee, Moderator Thursday, November 17, 2011 1:31 PM

Tutv,

The scinteropd is a secondary service that monitors HP OM for updates to SCOM 2007 alerts. This is not the provider itself which is built into WMI and you will not specifically see it running via 'Windows Task Manager'.

Your best bet for troubleshooting the connector is to go here --> http://technet.microsoft.com/en-us/library/ee809020.aspx and 'Enable Tracing for the Windows Provider'. Once set reboot the server and monitor the c:\sci.log. Post your results if you are still having issues.

Regards,

-Steve

• Proposed as answer by Steve Weber [MSFT]Microsoft employee, Moderator Thursday, November 17, 2011 1:31 PM

Tutv,

The scinteropd is a secondary service that monitors HP OM for updates to SCOM 2007 alerts. This is not the provider itself which is built into WMI and you will not specifically see it running via 'Windows Task Manager'.

Your best bet for troubleshooting the connector is to go here --> http://technet.microsoft.com/en-us/library/ee809020.aspx and 'Enable Tracing for the Windows Provider'. Once set reboot the server and monitor the c:\sci.log. Post your results if you are still having issues.

Regards,

-Steve

• Proposed as answer by Steve Weber [MSFT]Microsoft employee, Moderator Thursday, November 17, 2011 1:31 PM

Tutv,

The scinteropd is a secondary service that monitors HP OM for updates to SCOM 2007 alerts. This is not the provider itself which is built into WMI and you will not specifically see it running via 'Windows Task Manager'.

Your best bet for troubleshooting the connector is to go here --> http://technet.microsoft.com/en-us/library/ee809020.aspx and 'Enable Tracing for the Windows Provider'. Once set reboot the server and monitor the c:\sci.log. Post your results if you are still having issues.

Regards,

-Steve

• Proposed as answer by Steve Weber [MSFT]Microsoft employee, Moderator Thursday, November 17, 2011 1:31 PM

Tutv,

The scinteropd is a secondary service that monitors HP OM for updates to SCOM 2007 alerts. This is not the provider itself which is built into WMI and you will not specifically see it running via 'Windows Task Manager'.

Your best bet for troubleshooting the connector is to go here --> http://technet.microsoft.com/en-us/library/ee809020.aspx and 'Enable Tracing for the Windows Provider'. Once set reboot the server and monitor the c:\sci.log. Post your results if you are still having issues.

Regards,

-Steve

• Proposed as answer by Steve Weber [MSFT]Microsoft employee, Moderator Thursday, November 17, 2011 1:31 PM

Tutv,

The scinteropd is a secondary service that monitors HP OM for updates to SCOM 2007 alerts. This is not the provider itself which is built into WMI and you will not specifically see it running via 'Windows Task Manager'.

Your best bet for troubleshooting the connector is to go here --> http://technet.microsoft.com/en-us/library/ee809020.aspx and 'Enable Tracing for the Windows Provider'. Once set reboot the server and monitor the c:\sci.log. Post your results if you are still having issues.

Regards,

-Steve

• Proposed as answer by Steve Weber [MSFT]Microsoft employee, Moderator Thursday, November 17, 2011 1:31 PM

Tutv,

The scinteropd is a secondary service that monitors HP OM for updates to SCOM 2007 alerts. This is not the provider itself which is built into WMI and you will not specifically see it running via 'Windows Task Manager'.

Your best bet for troubleshooting the connector is to go here --> http://technet.microsoft.com/en-us/library/ee809020.aspx and 'Enable Tracing for the Windows Provider'. Once set reboot the server and monitor the c:\sci.log. Post your results if you are still having issues.

Regards,

-Steve

• Proposed as answer by Steve Weber [MSFT]Microsoft employee, Moderator Thursday, November 17, 2011 1:31 PM

Tutv,

The scinteropd is a secondary service that monitors HP OM for updates to SCOM 2007 alerts. This is not the provider itself which is built into WMI and you will not specifically see it running via 'Windows Task Manager'.

Your best bet for troubleshooting the connector is to go here --> http://technet.microsoft.com/en-us/library/ee809020.aspx and 'Enable Tracing for the Windows Provider'. Once set reboot the server and monitor the c:\sci.log. Post your results if you are still having issues.

Regards,

-Steve

Tutv,

The scinteropd is a secondary service that monitors HP OM for updates to SCOM 2007 alerts. This is not the provider itself which is built into WMI and you will not specifically see it running via 'Windows Task Manager'.

Your best bet for troubleshooting the connector is to go here --> http://technet.microsoft.com/en-us/library/ee809020.aspx and 'Enable Tracing for the Windows Provider'. Once set reboot the server and monitor the c:\sci.log. Post your results if you are still having issues.

Regards,

-Steve

• Proposed as answer by Steve Weber [MSFT]Microsoft employee, Moderator Thursday, November 17, 2011 1:31 PM

Tutv,

The scinteropd is a secondary service that monitors HP OM for updates to SCOM 2007 alerts. This is not the provider itself which is built into WMI and you will not specifically see it running via 'Windows Task Manager'.

Your best bet for troubleshooting the connector is to go here --> http://technet.microsoft.com/en-us/library/ee809020.aspx and 'Enable Tracing for the Windows Provider'. Once set reboot the server and monitor the c:\sci.log. Post your results if you are still having issues.

Regards,

-Steve

• Proposed as answer by Steve Weber [MSFT]Microsoft employee, Moderator Thursday, November 17, 2011 1:31 PM

Tutv,

The scinteropd is a secondary service that monitors HP OM for updates to SCOM 2007 alerts. This is not the provider itself which is built into WMI and you will not specifically see it running via 'Windows Task Manager'.

Your best bet for troubleshooting the connector is to go here --> http://technet.microsoft.com/en-us/library/ee809020.aspx and 'Enable Tracing for the Windows Provider'. Once set reboot the server and monitor the c:\sci.log. Post your results if you are still having issues.

Regards,

-Steve

• Proposed as answer by Steve Weber [MSFT]Microsoft employee, Moderator Thursday, November 17, 2011 1:31 PM

Tutv,

The scinteropd is a secondary service that monitors HP OM for updates to SCOM 2007 alerts. This is not the provider itself which is built into WMI and you will not specifically see it running via 'Windows Task Manager'.

Your best bet for troubleshooting the connector is to go here --> http://technet.microsoft.com/en-us/library/ee809020.aspx and 'Enable Tracing for the Windows Provider'. Once set reboot the server and monitor the c:\sci.log. Post your results if you are still having issues.

Regards,

-Steve

• Proposed as answer by Steve Weber [MSFT]Microsoft employee, Moderator Thursday, November 17, 2011 1:31 PM

Tutv,

The scinteropd is a secondary service that monitors HP OM for updates to SCOM 2007 alerts. This is not the provider itself which is built into WMI and you will not specifically see it running via 'Windows Task Manager'.

Your best bet for troubleshooting the connector is to go here --> http://technet.microsoft.com/en-us/library/ee809020.aspx and 'Enable Tracing for the Windows Provider'. Once set reboot the server and monitor the c:\sci.log. Post your results if you are still having issues.

Regards,

-Steve

• Proposed as answer by Steve Weber [MSFT]Microsoft employee, Moderator Thursday, November 17, 2011 1:31 PM

Hi,

im also getting the same authentication message.

Can you anyone advice:

Under "OpsMgr Connector for HP OpenView Operations Configuration"

Servername:

Operations Manager Server: <Is this the hp Operation Servername?>

HP Openview Operations Manager Provider name: <What is this name? How do i check the provider name?> 

Thanks

Best Regards

lyh

Lyh,

Servername:

Operations Manager Server: This will be your Microsoft System Center Operations Manager 2007 R2 server name.

HP OpenView Operations Manager Provider Name: This will be the name of the HP Operations Manager [AKA OVO] server name

There are 2 pieces to installing the Microsoft OVO Connector:

- The connector piece which is generally installed on the RMS server in your SCOM 2007 R2 environment

- The provider piece which is always installed on your HP OM [OVO] server.

When configuring the connector you must provide the host names for each piece in the configuration UI.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, January 03, 2012 3:06 PM

Lyh,

Servername:

Operations Manager Server: This will be your Microsoft System Center Operations Manager 2007 R2 server name.

HP OpenView Operations Manager Provider Name: This will be the name of the HP Operations Manager [AKA OVO] server name

There are 2 pieces to installing the Microsoft OVO Connector:

- The connector piece which is generally installed on the RMS server in your SCOM 2007 R2 environment

- The provider piece which is always installed on your HP OM [OVO] server.

When configuring the connector you must provide the host names for each piece in the configuration UI.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, January 03, 2012 3:06 PM

Lyh,

Servername:

Operations Manager Server: This will be your Microsoft System Center Operations Manager 2007 R2 server name.

HP OpenView Operations Manager Provider Name: This will be the name of the HP Operations Manager [AKA OVO] server name

There are 2 pieces to installing the Microsoft OVO Connector:

- The connector piece which is generally installed on the RMS server in your SCOM 2007 R2 environment

- The provider piece which is always installed on your HP OM [OVO] server.

When configuring the connector you must provide the host names for each piece in the configuration UI.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, January 03, 2012 3:06 PM

Lyh,

Servername:

Operations Manager Server: This will be your Microsoft System Center Operations Manager 2007 R2 server name.

HP OpenView Operations Manager Provider Name: This will be the name of the HP Operations Manager [AKA OVO] server name

There are 2 pieces to installing the Microsoft OVO Connector:

- The connector piece which is generally installed on the RMS server in your SCOM 2007 R2 environment

- The provider piece which is always installed on your HP OM [OVO] server.

When configuring the connector you must provide the host names for each piece in the configuration UI.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, January 03, 2012 3:06 PM

Lyh,

Servername:

Operations Manager Server: This will be your Microsoft System Center Operations Manager 2007 R2 server name.

HP OpenView Operations Manager Provider Name: This will be the name of the HP Operations Manager [AKA OVO] server name

There are 2 pieces to installing the Microsoft OVO Connector:

- The connector piece which is generally installed on the RMS server in your SCOM 2007 R2 environment

- The provider piece which is always installed on your HP OM [OVO] server.

When configuring the connector you must provide the host names for each piece in the configuration UI.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, January 03, 2012 3:06 PM

Lyh,

Servername:

Operations Manager Server: This will be your Microsoft System Center Operations Manager 2007 R2 server name.

HP OpenView Operations Manager Provider Name: This will be the name of the HP Operations Manager [AKA OVO] server name

There are 2 pieces to installing the Microsoft OVO Connector:

- The connector piece which is generally installed on the RMS server in your SCOM 2007 R2 environment

- The provider piece which is always installed on your HP OM [OVO] server.

When configuring the connector you must provide the host names for each piece in the configuration UI.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, January 03, 2012 3:06 PM

Lyh,

Servername:

Operations Manager Server: This will be your Microsoft System Center Operations Manager 2007 R2 server name.

HP OpenView Operations Manager Provider Name: This will be the name of the HP Operations Manager [AKA OVO] server name

There are 2 pieces to installing the Microsoft OVO Connector:

- The connector piece which is generally installed on the RMS server in your SCOM 2007 R2 environment

- The provider piece which is always installed on your HP OM [OVO] server.

When configuring the connector you must provide the host names for each piece in the configuration UI.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, January 03, 2012 3:06 PM

Lyh,

Servername:

Operations Manager Server: This will be your Microsoft System Center Operations Manager 2007 R2 server name.

HP OpenView Operations Manager Provider Name: This will be the name of the HP Operations Manager [AKA OVO] server name

There are 2 pieces to installing the Microsoft OVO Connector:

- The connector piece which is generally installed on the RMS server in your SCOM 2007 R2 environment

- The provider piece which is always installed on your HP OM [OVO] server.

When configuring the connector you must provide the host names for each piece in the configuration UI.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, January 03, 2012 3:06 PM

Lyh,

Servername:

Operations Manager Server: This will be your Microsoft System Center Operations Manager 2007 R2 server name.

HP OpenView Operations Manager Provider Name: This will be the name of the HP Operations Manager [AKA OVO] server name

There are 2 pieces to installing the Microsoft OVO Connector:

- The connector piece which is generally installed on the RMS server in your SCOM 2007 R2 environment

- The provider piece which is always installed on your HP OM [OVO] server.

When configuring the connector you must provide the host names for each piece in the configuration UI.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, January 03, 2012 3:06 PM

Lyh,

Servername:

Operations Manager Server: This will be your Microsoft System Center Operations Manager 2007 R2 server name.

HP OpenView Operations Manager Provider Name: This will be the name of the HP Operations Manager [AKA OVO] server name

There are 2 pieces to installing the Microsoft OVO Connector:

- The connector piece which is generally installed on the RMS server in your SCOM 2007 R2 environment

- The provider piece which is always installed on your HP OM [OVO] server.

When configuring the connector you must provide the host names for each piece in the configuration UI.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, January 03, 2012 3:06 PM

Lyh,

Servername:

Operations Manager Server: This will be your Microsoft System Center Operations Manager 2007 R2 server name.

HP OpenView Operations Manager Provider Name: This will be the name of the HP Operations Manager [AKA OVO] server name

There are 2 pieces to installing the Microsoft OVO Connector:

- The connector piece which is generally installed on the RMS server in your SCOM 2007 R2 environment

- The provider piece which is always installed on your HP OM [OVO] server.

When configuring the connector you must provide the host names for each piece in the configuration UI.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, January 03, 2012 3:06 PM

Lyh,

Servername:

Operations Manager Server: This will be your Microsoft System Center Operations Manager 2007 R2 server name.

HP OpenView Operations Manager Provider Name: This will be the name of the HP Operations Manager [AKA OVO] server name

There are 2 pieces to installing the Microsoft OVO Connector:

- The connector piece which is generally installed on the RMS server in your SCOM 2007 R2 environment

- The provider piece which is always installed on your HP OM [OVO] server.

When configuring the connector you must provide the host names for each piece in the configuration UI.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, January 03, 2012 3:06 PM

Lyh,

Servername:

Operations Manager Server: This will be your Microsoft System Center Operations Manager 2007 R2 server name.

HP OpenView Operations Manager Provider Name: This will be the name of the HP Operations Manager [AKA OVO] server name

There are 2 pieces to installing the Microsoft OVO Connector:

- The connector piece which is generally installed on the RMS server in your SCOM 2007 R2 environment

- The provider piece which is always installed on your HP OM [OVO] server.

When configuring the connector you must provide the host names for each piece in the configuration UI.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, January 03, 2012 3:06 PM

Lyh,

Servername:

Operations Manager Server: This will be your Microsoft System Center Operations Manager 2007 R2 server name.

HP OpenView Operations Manager Provider Name: This will be the name of the HP Operations Manager [AKA OVO] server name

There are 2 pieces to installing the Microsoft OVO Connector:

- The connector piece which is generally installed on the RMS server in your SCOM 2007 R2 environment

- The provider piece which is always installed on your HP OM [OVO] server.

When configuring the connector you must provide the host names for each piece in the configuration UI.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, January 03, 2012 3:06 PM

Lyh,

Servername:

Operations Manager Server: This will be your Microsoft System Center Operations Manager 2007 R2 server name.

HP OpenView Operations Manager Provider Name: This will be the name of the HP Operations Manager [AKA OVO] server name

There are 2 pieces to installing the Microsoft OVO Connector:

- The connector piece which is generally installed on the RMS server in your SCOM 2007 R2 environment

- The provider piece which is always installed on your HP OM [OVO] server.

When configuring the connector you must provide the host names for each piece in the configuration UI.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, January 03, 2012 3:06 PM

Lyh,

Servername:

Operations Manager Server: This will be your Microsoft System Center Operations Manager 2007 R2 server name.

HP OpenView Operations Manager Provider Name: This will be the name of the HP Operations Manager [AKA OVO] server name

There are 2 pieces to installing the Microsoft OVO Connector:

- The connector piece which is generally installed on the RMS server in your SCOM 2007 R2 environment

- The provider piece which is always installed on your HP OM [OVO] server.

When configuring the connector you must provide the host names for each piece in the configuration UI.

Regards,

-Steve

Lyh,

Servername:

Operations Manager Server: This will be your Microsoft System Center Operations Manager 2007 R2 server name.

HP OpenView Operations Manager Provider Name: This will be the name of the HP Operations Manager [AKA OVO] server name

There are 2 pieces to installing the Microsoft OVO Connector:

- The connector piece which is generally installed on the RMS server in your SCOM 2007 R2 environment

- The provider piece which is always installed on your HP OM [OVO] server.

When configuring the connector you must provide the host names for each piece in the configuration UI.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, January 03, 2012 3:06 PM

Lyh,

Servername:

Operations Manager Server: This will be your Microsoft System Center Operations Manager 2007 R2 server name.

HP OpenView Operations Manager Provider Name: This will be the name of the HP Operations Manager [AKA OVO] server name

There are 2 pieces to installing the Microsoft OVO Connector:

- The connector piece which is generally installed on the RMS server in your SCOM 2007 R2 environment

- The provider piece which is always installed on your HP OM [OVO] server.

When configuring the connector you must provide the host names for each piece in the configuration UI.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, January 03, 2012 3:06 PM

Lyh,

Servername:

Operations Manager Server: This will be your Microsoft System Center Operations Manager 2007 R2 server name.

HP OpenView Operations Manager Provider Name: This will be the name of the HP Operations Manager [AKA OVO] server name

There are 2 pieces to installing the Microsoft OVO Connector:

- The connector piece which is generally installed on the RMS server in your SCOM 2007 R2 environment

- The provider piece which is always installed on your HP OM [OVO] server.

When configuring the connector you must provide the host names for each piece in the configuration UI.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, January 03, 2012 3:06 PM

Lyh,

Servername:

Operations Manager Server: This will be your Microsoft System Center Operations Manager 2007 R2 server name.

HP OpenView Operations Manager Provider Name: This will be the name of the HP Operations Manager [AKA OVO] server name

There are 2 pieces to installing the Microsoft OVO Connector:

- The connector piece which is generally installed on the RMS server in your SCOM 2007 R2 environment

- The provider piece which is always installed on your HP OM [OVO] server.

When configuring the connector you must provide the host names for each piece in the configuration UI.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, January 03, 2012 3:06 PM

Lyh,

Servername:

Operations Manager Server: This will be your Microsoft System Center Operations Manager 2007 R2 server name.

HP OpenView Operations Manager Provider Name: This will be the name of the HP Operations Manager [AKA OVO] server name

There are 2 pieces to installing the Microsoft OVO Connector:

- The connector piece which is generally installed on the RMS server in your SCOM 2007 R2 environment

- The provider piece which is always installed on your HP OM [OVO] server.

When configuring the connector you must provide the host names for each piece in the configuration UI.

Regards,

-Steve

• Marked as answer by Steve Weber [MSFT]Microsoft employee, Moderator Tuesday, January 03, 2012 3:06 PM

Hi Gang,

Has anyone tried OMw 9.x with the release candidate of SCOM 2012? Are any problems foreseen. Unfortunately it'll be more than a week before I can get a test infrastructure in place!

Thanks

ITO-Boy

ITO-Boy,

The connectors are not supported with SCOM 2012. Under the covers things will most likely work but the Connector UI MP will most likely not install and you will have no way to configure it.

System Center Orchestrator 2012 supports connecting to SCOM 2012 and HPOM/W 9.x so this would be an option moving forward.

Regards,

-Steve

Hi,

Pls advice, i have configured the connector on SCOM.

On HP Operation Manager, what is require for me to perform in order to see the alert forwarded from SCOM?

If the connector is working properly and you have added the SCOM nodes to a Node Group in HP OM that you want to forward alert to HP OM for it should work.

Can you give me a little more detail on what you are having issues with? What OS and version is HP OM running on?

Regards,

-Steve

Hi Steve,

Thanks, the alert is somehow forwarding to my cluster omw9.

i am receiving the alerts now after adding the hp ov mgmt servers in.

Hi Steve,

im facing the access is denied issue for the certificate.

Are you able to advice?

The user must be part of the local system administrators group on the provider server. Please verify this and try again.

Regards,

-Steve

Hello Expert, I am using SCOM 2007 R2, but i got the error which the user and password is incorrect when setting the configuration between SCOM and HP Openview Provider? below is its screenshots:

And the account can login the HP Openview server.

HP Openview OS: Linux

SCOM: windows

Can you SSH into the Linux system with this account? Make sure port 1270 is open on the Linux server is well. By default RHEL has the firewall turned on and this port is blocked.

Regards,

-Steve