How to let disabled patch return enable/detect inadvanced ZPM ?

Hi All;

    Recently, I transfer ZPM from legacy to advacned.

but I find a function seem not work fine.

in the past. if find a patch that we need change to disable status, will create a patch policy then change its status to "enable" then add it to policy.

the click online update...this patch could be add to scan knowledge. to scan and been detect well.

But in Advanced ZPM...this method seem not work fine.

whether advanced ZPM change procedure ?

Wencheng

  • 0

    Who had use advanced ZPM to deploy previous Windows Comulative update (for example: 2023-11 or 2023-10 CU in December Month) to devices ?

    Wencheng

  • 0 in reply to 

    In the legacy feed, if a patch was superseded/disabled, patch policy would not install it, unless the settings for "Delay the disabling of superseded patches for xx days" or "Do not disable superseded patches that are included in a policy" were set.  In the advanced feed, the only change is that if a superseded/disabled patch is included in a patch policy, regardless of the settings, it will continue to install the superseded patch until the policy is rebuilt.

    If there is some other change of behavior that you are seeing, please provide the exact steps to reproduce and what is your expectation after doing the exact steps.

    thank you

  • 0 in reply to 

    One thing to note, is that official support for Advanced feed on superseded patches is that only those already in a policy at the time they are superseded is supported.  Re-enabling a superseded patch or using the disable schedule to enable and then using in patch deployment or policy is not officially supported in 23.4.  That is a story that is being looked at for future.  

  • 0 in reply to 

    My issue is occur on advanced feed.

    at previous legacy feed....no such issue occur.

    Wencheng