Wmi mapper, Wbem indication for windows ipv6 target – HP Systems Insight Manager User Manual
Page 201
WBEM Indication for Windows IPv6 Target
Windows system does not support the indications that are discovered only with automatically
configured 6to4 tunnel adapter IPv6 address (2002::/16).
To fix this problem, ensure that the system is at least discovered with an additional IP address
(either IPv4 or IPv6) that is reachable from the CMS.
WMI Mapper
When WMI Mapper is installed on a Windows 2008 R2 CMS, the WMI Mapper service may
fail to start with the "NT SERVICE\MAPPER" user and the WMI Mapper Indications service might
fail to start with the "NT SERVICE\WbemConsumer" user. This occurs on a Windows 2008 R2
CMS that is part of a domain that's security policy is being controlled by a domain controller, in
which the above two users are not given the log on as service right.
The WMI Mapper and WMI Mapper Indications services fail to start and while trying to start these
services from the services.msc console, the following error appears:
Windows could not start the Pegasus WMI Mapper service on Local Computer.
Error 1069: The service did not start due to a logon failure.
A more detailed error is also listed in the Systems Logs of the Windows Event Viewer.
The problem occurs because in Windows 2008 R2, Mapper and Mapper Indications Services are
started with users having lower privileges. By default a standalone Windows 2008 R2 server will
have these users with the said privileges. However in the case of a server whose security policies
are controlled by a domain controller, these users might be removed from the default set of users
and hence the services will not start.
You can choose to follow any one of the below workarounds based on your requirements:
•
You change the Mapper and Mapper Indications Service to start with a privileged user account
such as the “localSystem” account. This can be made by editing the properties of each of the
service using the “services.msc” console
•
You can choose to give the following two users “NT SERVICE\WMI Mapper” and “NT
SERVICE\WbemConsumer” the “log on as a service” right using the “User Rights Assignment”
option in the Security Policy Editor (secpol.msc).
-------------------------------------------------------------
If you have created subscriptions on a Windows managed system and then elect to change the
WMI Mapper proxy or install a WMI Mapper on the managed system, you must first unsubscribe
for WBEM events, change the proxy, re-identify the systems, and then resubscribe for WBEM
events. If you do not unsubscribe for the WBEM events, HP SIM will no longer receive indications
from the managed system.
WMI Mapper 201