Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it! Learn more

  • State Not Answered
  • Replies replies
    5
  • Subscribers subscribers
    6
  • Views views
    347
  • Users 0 members are here
Related
Options

advanced ZPM scan & return incorrect data

wencheng

My ZPM Server is 23.4 and transfer ZPM fnction from legacy to advanced ZPM.

recently customer response , some win2022 devices patch list could not list edge version 120.0.2210.122/133 patch.

These devices's edge version from 116.x ~120.0.2210.62/91 version.

no matter that admin scan much time...these devices still return same patch list. at the same time. admin try to install edge 120.0.2210.133 to these version by using patch policy. it seem work to try install. but edge still keep the same version without update to new version.

I try to rename zpm folder on these devices then re-run DAU agent to recreate zpm folder again.

after analy zpm report generate & send to zpm ....these device patch list show the latest edge version. and the edge patch policy that I crated yet. deploy it again...it could install well and return "patched" well.

the procedure only one key point that I regenerate zpm folder...I do not know which file or record stuck / incorrect to cause report record not completed/incorrect ...the incorrect patch record also affect patch policy install edge.

Who has similar experience about zpm folder recreated ??

Thanks!!

Wencheng

  • 0  

    Did you happen to get a zeninfo before removing the folder and when you were seeing the issue?  If so, can you please open a new support case and upload the zeninfo to the case?    Deleting the .state file and scanstatus.json then running patch scan will force reevaluation of the device on the backend but you sholdn't need to do that.  The only other thought was that the WindowsPatchCatalog.zip was old but again you shouldn't need to delete to get it updated, so having more inforation about the state of the failing agent (zeninfo) would help.  If you did get that, then maybe also get a zeninfo from after you fixed to compare.

    thank you

  • 0 in reply to   

    HI

        This issue has been tested repeatedly
    On the host where the problem occurs, no matter how many times DAU Scan is executed, the same incorrect data is uploaded.
    When the administrator executes rename folder and executes DAU Scan again to generate a new zpm folder...the data uploaded by the client will be normal. If you temporarily change the originally renamed Folder back at this time (of course, the new zpm folder will be renamed first), it will be normal no matter how the client executes DAU Scan...

    Wencheng

  • 0   in reply to 

    Hi, I'd like to ask that you open a support ticket for this.  Thank you

  • 0 in reply to   

    Yes....

       I had Create a case #02782552

    Wencheng

  • 0   in reply to 

    Yes,thank you for that.  I think i's sufficient to delete just the scanstatus.json file then do a complete scan.  I believe that they have determined the cause for the issue.

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.