This chapter is a compilation of some of the frequently asked questions in SCOM integration and their responses.
Can the SCOM connector work with a redundant eG manager setup? If so, how to configure it?
Yes. The SCOM connector can work in a redundant eG manager setup.
If you want to configure a SCOM connector for a redundant manager setup that pre-exists in an environment – i.e., a redundant manager setup that was operational before the eG manager was integrated with SCOM – then, post the integration, you just have to point the connector to use the primary manager's URL. The plugin automatically discovers secondary managers and if there is a failure in the redundancy, it will automatically switch to the available manager.
On the other hand, if you configure a redundant manager setup post the eG-SCOM integration, then, you will first have to point the connector to use the primary manager’s URL, and then, restart the eG SCOM Connector – i.e., stop and then start the eG SCOM Connector. Only after the restart will the eG SCOM connector automatically discover the secondary managers.
I have configured an eG user account in the SCOM connector and the integration has already been done. Can I now reconfigure the setup to use a different eG user? If so, how?
Yes, you can reconfigure the setup to use a different eG user. The steps in this regard are as follows:
- Stop the connector.
- Launch the Configuration & Setup Tool by following the menu sequence: Start -> Programs -> eG SCOM Connector
Switch to the Setup tab page of the Connector Configuration & Setup dialog box that then appears (see Figure 5). Click the Uninstall button therein to uninstall the configuration.
Then, switch to the eG Manager tab page. Provide a unique manager ID, specify the URL of the manager with which the connector has to integrate, and then provide the credentials of the new eG user for the integration.
Figure 6 : Configuring a new eG user
Finally, return to the Setup tab page, and this time, click on the Install button (see Figure 7) to install the configuration for the new eG user.
- Finally, click the Apply and ok buttons in Figure 7.
I have two eG user accounts in a manager that needs to be integrated with SCOM? How do I achieve integration for two users?
As per design, a single eG SCOM Connector can only integrate with a single eG user. If you want the SCOM Connector to integrate with all components managed by two different eG users, and each of these users require separate access rights to the SCOM console, then it is recommended that you install two different SCOM Connectors on two separate machines and configure each of them to integrate with a different user.
How do I enable the eG SCOM Connector to integrate with multiple eG managers?
In my SCOM 2012 environment, the SCOM connector is configured to report to a specific SCOM management server in a management group. If the configured management server is down, will the SCOM connector automatically report to the next available management server in the management group ?
Yes. The SCOM connector keeps track of the available management servers in the management group that it is currently reporting to. If the configured management server is down, the plugin automatically starts reporting to the next available management server. For this scenario to work, the connector should be able to connect to all management servers in the management group.
In my SCOM environment, I have deployed SCOM agents in an untrusted domain. These SCOM agents are being managed by a SCOM server in a different domain via a gateway server. Can the eG SCOM Connector that is deployed along with the SCOM agents be able to communicate with the SCOM server via this gateway server?
Yes. The eG SCOM Connector is capable of integrating with the SCOM server in a different domain via a gateway server. No configuration changes need to be made to enable this communication.
Am I required to install the eG SCOM Connector on all SCOM agent hosts?
No. It would suffice to install the connector in any one of the SCOM agent hosts.