Reboot needed. Reason: Scanning engine update Vmware horizon

MTjee393 · 2023-02-24T08:44:00+00:00

There was an error rendering this rich post.

hello,

We use Vmware horizon view with non-persistent desktops.

When logging off the session, the VDI desktop is refreshed with the state of the golden image.

Sometimes EPP gives a message: Reboot needed. Reason: Scanning engine update. This does not make much sense in a VDI environment with non-persistent desktops. the user can log out, but then ends up on a different desktop.

I understand that engine updates do not require a reboot, why is this message being given?

Unfortunately, you can't turn off notification of reboots for the user either, because then you turn off all notifications for the user.

is there anything to do about this?

Regards,

Michael

Find more posts tagged with

Accepted answers

All comments

JamesC

Hi @MTjee393

This looks like Scanning engine needs an update and you have to reboot it , so the host is protected.

MTjee393

it is dutch, but the message is :

there is a critical update for withsecure agent.

restart your computer to keep the protection up to date.

JamesC

Hi @MTjee393

It depends what the error message is. Can you share a screenshot of the Agent user interface ?

If the reboot message says 'Protection Malfunction' - we can't guarantee the protection unless the host is rebooted.

For Capricorn yes, if the latest is not installed, we still have the previous virus definition database that will be used.

MTjee393

Then what is the status of this machine if it is not restarted? as unprotected?

MTjee393

https://community.withsecure.com/discussion/comment/129665#Comment_129665

Then what is the status of this machine if it is not restarted? If unprotected?

JamesC

Hi Michael

Some of our engines such as Capricorn and Ultralight may sometimes request to reboot to be updated.

This does not happen all the time if it's just a virus definition update, but sometimes the update is for the engine itself. If so, an engine update may require access to Windows Binaries, and if it so happen that the binaries was being locked by another process during the time of updating, the reboot request will prompt.

If an update requiring reboot arrived to host during the non-permanent existence -- it will require reboot since we are not distinguishing between temporary and permanent desktops.