Discover windows 2008 R2 server

ashish1 — Wed, 30 Mar 2016 12:27:31 GMT

Installed HP SIM 7.5 and setup to discover windos 2008 r2 server.

Here is the discovery results

********* Significant issues and overall target discovery/identification
status:
Major: The system cannot be identified properly for HP SIM to manage;
unable to get one or more of the following: model, serial number or
unique identifier (UUID). For management processors, verify the
system is running the latest firmware. For Linux based operating
systems, you must have dmidecode installed, enable the
PermitRootLogin and PasswordAuthentication in sshd, and use root
sign-in credential. For HP-UX, verify the sign-in credential. For
Windows, check if WMIMapper is configured correctly on the CMS and
verify the sign-in credential.
Normal: Identification status is only available for servers, workstations,
or desktops, where monitoring is enabled.

********* Additional results (listed for information only):

* Starting identification process...
* Checking for known running web servers...
* Checking for SNMP protocol support on system...
Normal: The system did not respond to SNMP. Verify security settings and
community strings in Options->Security->Credentials->System
Credentials
* Checking for SNMPv3 protocol support on system...
Normal: The system did not respond to SNMPv3. Verify security settings and
v3 credentials in Options->Security->Credentials->System
Credentials
* Running HP ProLiant management agent identification...
Normal: The system does not support SNMP.
* Running SNMP base cluster identification using common cluster
MIB...
Normal: SNMP is not supported or globally disabled, skipping SNMP cluster
identification.
* Checking for WBEM protocol support on system...
Minor: This system does not have any SMI-S CIMOMs installed. No storage
systems will be found on this system.
Minor: The Central Management System (CMS) cannot communicate with the
CIMOM locally installed on the managed system using the WBEM
protocol, Identification will try to identify Windows systems using
the WMI Mapper as proxy; for Linux and HP-UX systems, check
credentials by going to Options->Security->Credentials->System
Credentials. For Linux systems also check if the HP WBEM provider
is installed.
* Running WBEM rules based identification...
Minor: Identification cannot get computer system hardware data from the
WBEM / WMI providers.
* Running Virtual Machine (VM) Host (non HP Integrity VM Host)
Identification...
Normal: The system is not a VM Host (non HP Integrity VM Host), or WBEM
credentials may not be specified so skipping VM Identification.
* Running Storage identification...
* Did not detect the WBEM protocol support on this system. SMI
storage identification will be skipped.
* Storage identification completed.
* Running HP NetServer identification...
Normal: The system does not support SNMP.
* Running HP-UX SNMP identification...
Normal: The system does not support SNMP.
* Running OA Identifier which will discover systems in an enclosure
if the automatic enclosure discovery option for OA is enabled...
Normal: The system is not an Onboard Administrator, skipping automatic
discovery of systems in the enclosure.
* Running XMLReply Identifier which will discover systems in a
rack/enclosure if the automatic discovery option for the container
node is enabled...
* Running iLO Identifier which will discover the server if the
automatic server discovery option for iLO is enabled...
Minor: The system responds to the HTTP request but cannot get the XML
output. It is normal for servers not to get the XML data.
Minor: If the http communication from CMS to target is working, but if it
is found to be slow then try increasing the Default connection
timeout parameter for http in global protocol settings.
* Running p-Class Identifier...
Normal: The system is not a p-Class so skipping p-Class identification.
* Running IPMI protocol identification...
Normal: IPMI protocol not detected so skipping IPMI Identification.
* Running SSH Protocol identification...
Minor: The system(s) do not have Secure Shell (SSH) installed or it is not
running on the managed system(s).
* Running SSH Identification...
Normal: SSH Protocol is not enabled so skipping SSH Identification.
* Running WS-Man identification...
Minor: The system did not respond to WS-Management (WS-Man) request.
* Running Monarch OA Identification...
Normal: The system is not a monarch OA so skipping monarch OA
identification.
* Checking for System Management Homepage and other HP web agents...
Normal: The system is not a server, storage or desktop. Skipping the check
for System Management Homepage.
* Running HP Serviceguard Identification...
* Running SNMP System Type manager ...
Normal: The system does not support SNMP.
* Running SNMP subtypes identification...
* Resolving DNS names...
Normal: The fully qualified domain name was successfully resolved for the
system.
* Checking if the Node is a Virtual Center...
Normal: Skipping Virtual Center Identifier.
* Running Virtual Machine Management (VMM) Plug-in Identification...
* Building system relationships...
Minor: System Management Homepage (SMH) is not installed or is not
responding on the system(s).
* Running system Manage Communication diagnosis...
* System identification finished on system.

Do I need to enable on HPSIM and target windows server.

Re: Discover windows 2008 R2 server

Andrew_Haak — Wed, 30 Mar 2016 19:14:19 GMT

What type of hardware is the server, what version on Windows 2008 is the server and sis you install any agent on the 2008 server ?

Did you imclude any Admin account when discovering the server. Without any info expert a log this is only guessing but by looking at the log you might not have an agent installed and did mot use an Admin account to discover the server.

Re: Discover windows 2008 R2 server

ashish1 — Thu, 31 Mar 2016 13:29:04 GMT

Thanks for reply.

Yes I did added account (which is used for discovery) in the admin group on the target server.

OS installed is Windows 2008 R2 with SNMP and WMI enabled ( added the account in security group of wmi configuration) but still seeing this error

Minor: Identification cannot get computer system hardware data from the
WBEM / WMI providers.
Minor: The system did not respond to WS-Management (WS-Man) request.
Is any configuration require for WBEM/WMI and WS-MAN to work ??

Also I have not installed agent on the target server.

Thanks

Re: Discover windows 2008 R2 server

Andrew_Haak — Mon, 11 Apr 2016 08:42:20 GMT

An admin in the Windows group should be enough, then add the credentials in the discovery job and add then in the WBEM/WMI tab in the credentials part. You can also use a non admin account but then you need an admin account to run the repair and click the option Configure a non-administrative account for HP SIM to access WMI data in the second repair option field.

topic Re: Discover windows 2008 R2 server in Server Management - Systems Insight Manager

Discover windows 2008 R2 server

Re: Discover windows 2008 R2 server

Re: Discover windows 2008 R2 server

Re: Discover windows 2008 R2 server