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 Suggested Answer
  • Replies replies
    2
  • Answers answer
    1
  • Subscribers subscribers
    6
  • Views views
    467
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Patch Policy for Google Chrome

Adam Balakier

Hi All,

I have such situation.

I would like to patch 2 workstations witth patch for Chrome.

Build new patch policy, chose relantionships to 2 wks, one of them is test, both has Chrome installed with older versionvendor, in the next step chose vendor google and after that I can see  1 patch.

Than I chose rebuild, and auto approve.

After I finished configgure that patch policy I can see Version as sandbox. My wks should apply new patches after refreshing.

My test station showing that patch is applied but not launched or installed

This patch has status Patched 0, not patched 0.

What should I do to process that patch on test wks, and then publish and install on the other wks?

Thank You for reading. :-)

Parents
  • 0  

    Hi Adam,

    A few questions for you:

    1. Have the results been reported to the server? You can verify in ZCC by going to the device's Patches page and looking at the Last Patch Scan Time entry. That time should be after you applied the policy on the device.
    2. Has the policy really been applied? In other words, should the policy have been applied according to the the Schedule Enforcement setting in the Patch Policy Settings for the device? 
    3. Have you tried running "zac pap" at the command line of the device to ensure that the policy has been enforced?
    4. If you look at the .state file in the %ZENWORKSHOME%\ZPM directory (c:\Program Files (x86)\Novell\ZENworks\ZPM on Windows), does the Chrome patch show as "NOT_APPLICABLE", "DETECT_PATCHED", or "DETECT_NOTPATCHED". If it shows as NOT_APPLICABLE, the results you are seeing in ZCC are correct. If it shows as one of the other states, the ZCC results are not being updated correctly. If it shows as NOT_APPLICABLE and you believe that it should be applicable, you need to enter a support ticket to troubleshoot the issue more with our Support folks.

    Thanks. -Darrin

    ZENworks Product Manager

Reply
  • 0  

    Hi Adam,

    A few questions for you:

    1. Have the results been reported to the server? You can verify in ZCC by going to the device's Patches page and looking at the Last Patch Scan Time entry. That time should be after you applied the policy on the device.
    2. Has the policy really been applied? In other words, should the policy have been applied according to the the Schedule Enforcement setting in the Patch Policy Settings for the device? 
    3. Have you tried running "zac pap" at the command line of the device to ensure that the policy has been enforced?
    4. If you look at the .state file in the %ZENWORKSHOME%\ZPM directory (c:\Program Files (x86)\Novell\ZENworks\ZPM on Windows), does the Chrome patch show as "NOT_APPLICABLE", "DETECT_PATCHED", or "DETECT_NOTPATCHED". If it shows as NOT_APPLICABLE, the results you are seeing in ZCC are correct. If it shows as one of the other states, the ZCC results are not being updated correctly. If it shows as NOT_APPLICABLE and you believe that it should be applicable, you need to enter a support ticket to troubleshoot the issue more with our Support folks.

    Thanks. -Darrin

    ZENworks Product Manager

Children

  • Suggested Answer

    0   in reply to   

    Also, verify where CHROME is installed.  If Chrome.exe resides in the UserProfile, then ZPM would not likely patch it because the patch software needs to run as the logged-on user.  If Chrome.exe is in the ProgramFiles directory, then it is a machine install that can install as someone other than the specific owner of a specific profile.

    If Chrome is installed in the 'User Profile', I would suggest looking into how to do a "Per Machine" install of Chrome versus "Per User" to allow simpler patching and prevent the need to have the software installed over and over again on each profile.

    --

    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button

    Be sure to "Like" My (and a few others) Cool Solutions below! 

    https://community.microfocus.com/members/craigdwilson/bookmarks

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.