Remotely verifying proper operation of components like "F-Secure Scanner Manager Update"?

etomcatetomcat Posts: 1,318 Superuser

Dear Sirs,

 

A corporate customer's sysadmin has contacted us to say that, while centrally updating the version of FSAVCS on endpoints, one workstation failed to install or update the "F-Secure Scanner Manager Update" module. However he only learned of this issue via a phone call from an alert end user, intead of Policy Manager.

(Note: there was no screenshot, diagnostic results package or similar concrete information submited with the incident, so it is possible that the eye witness end-user provided mangled info or even some "alternative facts" to the sysadmin.)

Anyhow, the sysadmin now wishes to know how to verify, using the F-Secure Policy Manager infrastructure, that a particular endpoint has properly installed and activated all F-Secure protecion components? He wishes to do that without needing to visit the endpoint in real life or via a remote desktop. Do you think that's possible in such a great detail?

 

Thanks in advance, Yours Sincerely: Tamas Feher, Hungary.

Best Answer

  • MJ-perCompMJ-perComp Posts: 1,098 Superuser
    Accepted Answer

    AFAIK FSAUA should try to reapply the update after a reboot, so at this point there is only a warning, because the old is continuing to work.

     

    But forwarding warnings to PMS or via mail can be hazardous to PMS or the mailserver. Doing that on selected / important hosts might be an option.

    etomcat

Comments

  • etomcatetomcat Posts: 1,318 Superuser

    Hello,

     

    I now think PMC, Tools menu, Reporting..., select computer, report type: Status, action: View does the trick. There the "Installed packages" table shows e.g. "Installation status = Installed" and "Last installation time = May 10, 2017 11:57 AM" for "F-Secure Scanner Manager Update (fsav_1100_bin).

     

    On the other hand, the status report has much data, about 150kB, which is a bit of inconvenience, but it is still much less data than the average 25MB packed / 200 MB unpacked per computer FSDIAG result (which can now be created and collected on endpoints via a central command from FSPMC).

     

    Best Regards: Tamas Feher, Hungary.

This discussion has been closed.