Devicemanager 4.7 SP3 and SP4 break thinclient HPDM agents

[FrankWest]

After updating to HP Devicemanager 4.7 SP3 (and also SP4) it appears that the update agent task is broken. It reports that the update is successfull, but the client don't connect to Device Manager anymore. When using the HPDM Agent controlpanel applet it reports no version number. When viewing the services applet it appears that the HPDM Agent service is gone.

Looks like the update task is seriously broken. Worse is that it doesn't include a full agent install, so how do I reinstall the agent now on the ThinClients?

Frank

[Chen_HPDM]

is this a single unit failure? or it happend on some or all of your tested unit?

Can you get the agent.log when the things happen?

What's the default DM Agent version on your t610 unit?

The operating system you mentioned - is that from HP? just to confirm as we called it WES7E.

[FrankWest]

It happens on all T610's I've tried. in total we have 100+ units and with the first 10 I tested it happened. All of these are now unmanagable, since I don't have a way to reinstall the client and they lost connection to the Device Manager since the HPDM Agent service is not present any more.

Do you have a full install package of the latest agent?

Old agent version is 4.6.3660.21244 and 4.5.3660.18367

It's indeed WES7E, with image version 6.1.7601.252 (Dutch).

Task log:

agent.log:

2016-08-03 21:25:43 INFO Enhanced Write Filter present.
2016-08-03 21:25:43 INFO File Based Write Filter present.
2016-08-03 21:25:43 INFO Agent starts.
2016-08-03 21:25:43 INFO Sizeof(GrData)=32
2016-08-03 21:25:43 INFO XWFManager: already initialized
2016-08-03 21:25:43 INFO GetXWFStatusAndFilter:2 0
2016-08-03 21:25:43 INFO FBWF Is initialized
2016-08-03 21:25:43 INFO FBWF Is initialized
2016-08-03 21:25:44 WARN Try to get basic network information.
2016-08-03 21:25:44 INFO Succeeded to get basic network information.
2016-08-03 21:25:44 INFO Sizeof(GrData)=32

update.log:

Stop the old Agent successfully.
C:\Windows\xpeagent\..\temp\HPDMAgent.exe
C:\Windows\xpeagent\HPDMAgent.exe -r
Start to delete the old Agent: C:\Windows\xpeagent\HPDMAgent.exe
Start to copy the new Agent: C:\Windows\xpeagent\..\temp\Files\Agent.exe C:\Windows\xpeagent\HPDMAgent.exe.
Run C:\Windows\xpeagent\..\temp\install.cmd
C:\Windows\xpeagent\HPDMAgent.exe -i
Deploy the new Agent successfully.
new Agent index:1
Run c:\windows\xpeagent\wf.cmd
Invoke the new Agent successfully.
argc = 4, argv[3] = 1
bReboot = 1.
reboot in ProcessWriteFilter 2.

But after the update task and subsequent reboot, the HP Device Management Agent service is no longer present and the client looses it's connectivity to HP Device Manager

[FrankWest]

Hi,

could you please reply on my response?

Thanks!

[Jamie_Peterson]

We updated our device manager from 4.6 to 4.7 SP4, thinking it was inclusive of the previous service packs.  Our t5740e Thin Clients are currently WES7E 32-Bit.  Testing two of the units, by uisng the _Update Agent task produced exactly what FrakWest has exerpienced, the task is successful from the HPDM, when you look at the client and run the HP Agent from the control panel, were you would see the Agent version it is blank.  Also looking at the device from HPDM Server the device shows that it is "Off" when it is on and showing the network.

I started to look at the install of HPDM 4.7 folders on the server.  In the following path:

C:\Inetpub\Ftproot\HPDM\Repository\Agents

Are the following Agents:  HPCE, HPThinPro, HPThinPro4, HPThinPro5, HPThinPro6_64, HPThinProZero, HPWE8_64, HPWES7_64, and HPXPe.  The WES7E_32-bit is missing from the install, no folder.

I checked the White Paper for HPDM 4.7 SP2, and in the list of Agents / OS shows the WES7E_32-bit Agent.

My experince with SP's is that usually the latest service pack is inclusive of the previous service packs.

Could the solution be that HPDM 4.7 SP2 needs to be installed to provide the 32 Bit O.S with a 32 Bit Agent?

If so, can HPDM 4.7 SP2 be installed after HPDM 4.7 SP4 to include the missing Agents, or should SP4 be uninstalled first, then install SP2 and follow up with SP4, getting all of the Agents?

Frank, I am having the same issue you are, hopefully this will help us get a solution

Chen, thank you for your help

[Chen_HPDM]

R & D is now investigating the issue, I will post the update if there is any.

[Chen_HPDM]

On the failed unit,

can you please try SC command to recreate the service. If you see any DLL error from library like libeay32.dll.

Please post the error message here.

[FrankWest]

Whats's the exact commandline for the SC command? it does need parameters.

[Chen_HPDM]

Or you can simply go to the Agent folder c:\windows\xpeagent

1. hpdmagent.exe -v to check the version and capture the error message if there is any.

If there is no error from above step, try

hpdmagent.exe -i to reinstall the service, again to capture the error message if there is any.

[FrankWest]

After running hpdmagent -v I'm indeed getting a LIBEAY32.dll error:

Could not find ordinal 4445 in DLL-file LIBEAY32.dll (translated from Dutch).