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

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

  • 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

Reply
  • 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

Children
No Data