Please Open a Case if Possible.

It seems for MOST Customers, everything just works w/o issue as expected and updates.

We have a small number of customers where the update is failing.  We are actively investigating that issue with our Anit-Malware OEM Provider.

It's possible you missed a step and support can help you figure it out, but if I were to guess you are part of the group seeing the update issue.  We have not yet isolated what environmental factors cause it to not work for all.

did you reboot the computers after they got the FTF 334 updates?  one of the files can't be updated with the system running.

C:\Program Files (x86)\Novell\ZENworks\zav>dir zav* /s

Volume in drive C has no label.

Volume Serial Number is A063-5439

 

Directory of C:\Program Files (x86)\Novell\ZENworks\zav

 

09/05/2023 01:27 PM           385,648 ZavConfigure.exe

08/05/2023 04:00 AM            27,928 ZavListener.exe

09/05/2023 01:27 PM            34,920 ZavListener.exe.ztmp

09/05/2023 01:34 PM               128 ZavOutput.log

               4 File(s)        448,624 bytes

See ZavListener.exe.ztmp?  That's the new file waiting to go in at restart.  ZavConfigure.exe updates ok, but not ZavListener.

Strangely I found a small percentage (<5%) of computers were able to install ZavListener.exe without a reboot, 

... also, you might have to force update the ZES agent (bitdefender):

"c:\program files\micro focus\zenworks\product.console.exe" /c StartUpdate

if you want that make that run with a zenworks bundle, for some reason it doesn't like to run when launched directly from zenworks so I had to launch cmd and feed the product.console command to cmd as below:

program to launch: c:\windows\system32\cmd.exe

command line: /c "c:\program files\micro focus\zenworks\product.console.exe" /c StartUpdate

Normally zenworks anti-malware triggers the update process hourly via ZavListener, but that's broken until you get everything updated.

David can try that and it may work.....

But we have customers where this is not triggering any type of update....We are working with the OEM Vendor to figure out why.

Many thanks for it, this helped me a lot. Problem is solved now.