HP Systems Insight Manager 5.2 Update 2 Technical Reference Guide

7. The Step 3: Configure or Repair Agents page enables you to select options to configure the target
system.
The following options are available:
• Configure WBEM / WMI. This section enables you to configure the target Linux, Windows, or
HP-UX system to send WBEM indications or events to HP SIM.
For this section, the following must be considered:
• Create subscription to WBEM events so that WBEM events will be sent to the CMS.
• Send a sample WBEM / WMI indication to this instance of HP SIM to test that events
appear in HP SIM in the Event List> or All Event User Interface for the selected system.
Note: This indication will appear as an Informational Event in the Event List of HP SIM.
If you do not receive test WBEM indications in the Event List, see “Troubleshooting”.
Note: This indication is supported only on HP-UX and Windows managed systems with WBEM
provider installed.
• Use an HP SIM WBEM certificate (good for 10 years) rather than username/password
to manage the system.. This option deploys a WBEM certificate to the managed system
and is only valid for HP-UX systems.
• Configure a non-administrative account for HP SIM to access WMI data. This option is
applicable to Windows systems with HP WBEM providers. The configuration of the managed
system will be updated to allow the specified user to access WMI information over the network.
This user will be used by HP SIM to read inventory and configuration information from the
system and will be configured as the WBEM user in the System Protocol settings. This
configuration step is not necessary if HP SIM is configured with a user with administration
rights. This user is not created by HP SIM. The user should already exist as either a domain
user or one local to the managed system.
The user will be added to the "DCOM Users” group on the managed system and will be
given read-only access to WMI information, plus read-write permissions to the HPQ name
space. This user does not need to be an administrator of the managed system and need not
have logon rights. A special purpose domain account is recommended, and should be created
by the domain administrator.
64 Getting started