in the relevant hostchecker policy, do a new rule of type "Custome: File"
give it a name (no spaces), and in the criteria box type the path & file name.
(In the case of Sophos, I use "c:\program files\sophos\sophos anti-virus\*.ide" )
Tick "required", and in the optional settings put a "file modified less than X days ago"
save that, and back in the hostchecker policy tick "require: any of the above rules"
Alternatively, rather than doing a file check you could just do a process check for the appropriate AV process - but that doesn't check when it was last updated.
I have encountered this issue with a number of customers today, This only seems to be effecting users accessing via web browsers. we have a number of users connecting via Pulse that are not effected.So if you have that option it could be another work around!
Happy new year everyone!
There is very little information and more updates are required to provide an estimate to our customers as to when this issue will be resolved.
Juniper have now identified the issue and will be pushing out a new ESAP package in the next 48 hours although I would expect somepoint today!
Please read http://kb.pulsesecure.net/InfoCenter/index?page=content&id=TSB16290 for an update on the issue.
Please fix this ASAP we're getting a ton of calls this morning and it's embarassing to tell people to turn their date back.
Another impacted customer.
Pulse did not work for us (Same error) but turning the date back did. we're waiting patiently for the new ESAP. Our current ESAP is 2.4.9, will there be any problem going to 2.5.1?
Wow this is pretty pathetic if you ask me.
"estimated release date for the fix is between 12/31/2013 (PST) and 1/3/2014 (PST)."
We have had to disable hostchecker entirely, toss the security out the window for a few days.