This content has been marked as final. Show 4 replies
You didn't inadvertently update Java on that server, did you?
I had a similar issue with the Trusted Networks policy after Java was updated on the server. It was fantastic; after adding a new network and clicking save it completely wiped the policy and made it uneditable. That brought a couple thousand machines to their knees pretty quickly.
Thanks for the answer.
I don't think so...
Just checked and Java is at version 6 update 7 (1.6.0-07), so quite old.
I've opened a case with McAfee since this is a big problem here.
go back to Java 5...hips policies and epo361 have serious issues with with Java6...
Thankfully in epo4 you won't have to worry about java...maybe one day java will go away completely!
Thanks, in the end, it wasn't Java... I suspect it was a DB error somewhere(*).
The only workaround I found was to rewrite all those rules...
Had to use a laptop to see what the rules actually were as I couldn't even view the rules on the server... Then rewrote new rules copying the old ones. Luckily I only had about 20 different rulesets.
I managed to also merge a few special cases so as to have less different rulesets. And I did learn a bit about HIPS in the process (also found some weird things, see other thread on localhost handling).
Problem solved, somehow (**).
(*) I had "DB Full" messages on this server, so I purged and cleaned the evenst from the DB.
(**) I'd opened a case with McAfee support about this. After three days, they just closed the case and considered it solved, even though they never provided any solution :mad: