Andrew,
thank you for your reply, again even if i added the domain admin account to the local admin group and select to install the agent under those credentials it says:
Waiting for the required components to be located and copied..
Installing HP Insight Management Agents for Windows Server 2003 x64 Editions Pa
ckage ( 10.0.0.0) using component cp022559.exe.
Installing HP Insight Management WBEM Providers for Windows Server 2003-2008 x6
4 Edition ( 10.0.0.0) using component cp022424.exe.
Installing HP Version Control Agent for Windows ( 7.3.3.0) using component cp0
23743.exe.
Installing HP System Management Homepage for Windows ( 7.4.0.12) using componen
t cp022466.exe.
Install Return Status: [SUCCESS]
////////////////////////////////////////////////////////////////////////////////
// HP Smart Update Manager for Node 10.58.245.1 Started: wo dec 17 2014 14:47:3
8
// HPSUM Version: 7.1.0."18".25197.x64
////////////////////////////////////////////////////////////////////////////////
Inventory started
Inventory completed
Analysis started
Analysis completed
Analysis started
Analysis completed
Deployment started
Deploying component: cp022466.exe
Component Filename: cp022466.exe
Component Name: HP System Management Homepage for Windows x64
Version: 7.4.0.12
Deployment Result: Success
Deploying component: cp022424.exe
Component Filename: cp022424.exe
Component Name: HP Insight Management WBEM Providers for Windows Server x64 Edit
ions
Version: 10.0.0.0
Deployment Result: Success
Deploying component: cp022559.exe
Component Filename: cp022559.exe
Component Name: HP Insight Management Agents for Windows Server x64 Editions
Version: 10.0.0.0
Deployment Result: Success
Deploying component: cp023743.exe
Component Filename: cp023743.exe
Component Name: HP Version Control Agent for Windows x64
Version: 7.3.3.0
Deployment Result: Success
Deployment completed
Deployed Components:
Component Filename: cp022466.exe
Component Name: HP System Management Homepage for Windows x64
Original Version:
New Version: 7.4.0.12
Deployment Result: Success
Component Filename: cp022424.exe
Component Name: HP Insight Management WBEM Providers for Windows Server x64 Ed
itions
Original Version:
New Version: 10.0.0.0
Deployment Result: Success
Component Filename: cp022559.exe
Component Name: HP Insight Management Agents for Windows Server x64 Editions
Original Version:
New Version: 10.0.0.0
Deployment Result: Success
Component Filename: cp023743.exe
Component Name: HP Version Control Agent for Windows x64
Original Version:
New Version: 7.3.3.0
Deployment Result: Success
////////////////////////////////////////////////////////////////////////////////
// Exit Code for Node 10.58.245.1: 0
// HP Smart Update Manager for Node 10.58.245.1 Finished wo dec 17 2014 14:53:1
5
////////////////////////////////////////////////////////////////////////////////
WINDOWS_HPSUM_INSTALL_NOTE,C:\cpqsystem\hp\log\10.58.245.1
1) hpsum_log.txt for brief summary of the installation activity.
2) hpsum_detail_log.txt for installation details, including errors, for each com
ponent installed.
Install Agent .......................................................[SUCCESS]
Re-identifying system to get updated information ...
Re-identification of system .................................... [SUCCESS]
Unable to create a socket connection on the managed system
Managed system must be listening on socket 5989 (WBEM) or 2381 (System Managemen
t Homepage). If the managed system is running Windows, then ensure System Manage
ment Homepage is running. Otherwise ensure WBEM is accessible.
Subscribe to WBEM / WMI Indications ................................. [FAILED]
Setting SNMP trap destination .......................................[SUCCESS]
Update SNMP setting to accept SNMP requests from the HP SIM instance.[SUCCESS]
Re-identifying system to get updated information (START) ...
Re-identification of system .................................... [SUCCESS]
Configure Version Control Agent (START) ...
Configure Version Control Agent .....................................[SKIPPED]
Operation is not supported on the system.
Either VCA agent is not installed in target node or Check the credentials you en
tered for the VCA to use to access the VCRM. For security reasons, the VCA canno
t connect to the VCRM using the default 'Administrator' user. For more informati
on, refer to the Version Control Agent documentation.
can you please assist, is there anything you can see in the log above?
kind regards,