-
×InformationWindows update impacting certain printer icons and names. Microsoft is working on a solution.
Click here to learn moreInformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center.
-
×InformationWindows update impacting certain printer icons and names. Microsoft is working on a solution.
Click here to learn moreInformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center.
- HP Community
- Desktops
- Business PCs, Workstations and Point of Sale Systems
- Devicemanager 4.7 SP3 and SP4 break thinclient HPDM agents
Create an account on the HP Community to personalize your profile and ask a question
08-17-2016 05:39 PM
Thanks Frank.
R & D was not able the reproduce the issue. Hopfully they could find something from the screenshot you provided.
I will keep you update whenever there is any progress.
My opinions are my own, and do not express those of HPI.
**Click the White Thumbs Up Button on the right to say Thanks**
08-17-2016 08:20 PM
Thanks for your detailed information.
From the logs file you provided, I saw that Agent was updated correctly. There might be a write filter issue.
Please execute these commands on the failed device, and provide me the screenshot:
1) ewfmgr c:
2) ewfmgr c: -persist="111"
3) fbwfmgr /displayconfig
My opinions are my own, and do not express those of HPI.
08-18-2016 03:09 AM
I don't think the Agent package in HPDM Repository was broken, but would you mind zip and upload it?
The WES7 Agent package is in <Repository Path>Repository\Agents\HPXPe (By default: C:\Inetpub\Ftproot\HPDM\Repository\Agents\HPXPe). Please compress the folder.
My opinions are my own, and do not express those of HPI.
08-18-2016 01:03 PM
I don't think it's an EWF issue since all clients I tried so far have the issue. Indeed the log reports that the update is succesful, but even then the HPDM Agent service is missing. So it's not succesful after all. Isn't it possible that for some reason LIBEAY32.dll is in use during the update and can't be updated?
Here are the results for the commands you specified:
08-19-2016 01:35 AM
Hi Frank,
A little update from R & 😧
- We do have bug that in specific circumstance, update.exe will report a fake success.
- We're not able to reproduce the Agent service disable issue - library file not replaced
In order to put this case as higher priority, could you please contact the support team in your reagion to submit an impact case?
We can provide some debug version for trouble shooting through that offical channel.
My opinions are my own, and do not express those of HPI.
**Click the White Thumbs Up Button on the right to say Thanks**
Didn't find what you were looking for? Ask the community