We have been seeing alot of reboot required on our systems/servers in the environment, with a message that computer is not protected. I understand that updates do require an update from time to time to update the software on the systems, but confused about why we are seeing these so frequently? Is there a way to set groups to have the software schedule a reboot at a certain time for a group of computers and then prompt (with popup), or reboot on logoff for the others by default action (with the exception of servers). This is just making me worried that all of our systems are not protected, due to reliance on the users to do the reboot, or for us to catch it and push a reboot manually (which is very dangerous when dealing with viruses).

Thanks,
Mike

Currently in Sophos Central we can add servers to a Test Group and prevent all other servers from having their agent update.
This is completely inadequate. Need to be able to create more Server Groups and be able to update to the new version by server group.

Should be able to download a manual install for the new version and apply it to the servers while Controlled Updates is turned on.

This would allow us to update critical servers at a time of our choosing.

Right now, the option is Update All Servers - This is equivalent to pushing the Nuclear Button, especially if the update requires a reboot.

I tried to rerun the SophosSetup and the SophosInstall with a new update available on my Portal. No luck. Server stayed stuck at the previous version!

It seems that the higher up the ladder that the user is, the harder it is to get them to reboot. The disruption that closing their many, many, multi-tasking windows left open as project or task placards, makes it extremely difficult for them to pick up where they left off.

Then a week after I had convinced all of my users to reboot for an update, I had another warning in the console to reboot all of the clients again.

And now two weeks later, I have a new warning to reboot the endpoint users for Hitman.

If we keep requiring the users to reboot, they loose their urgency, and could compromise the security of the network.

Could we find a way to update the client without a reqired reboot, as many competitors have?

We get a lot of medium warnings "Reboot required" after Sophos Endpoint updates on Windows10 machines.

Users do shut down tehir machines every night. But Standard Power up seems to be insufficient as FastBoot does not install the Sophos drivers after some updates.

Manual Reboot "Neu Starten" is required from the users. But users do not notice any Sophos "Reboot required" notices and the do not understand that Manual reboot is different from Power down / Power up procedure.

It would be better if Sophos Endpint Updater can set a Windows boot parameter after update so that after next shutdown a propper cold boot is carried out instead of FastBoot - only for this one time.

The Sophos engineer suggeted I post this idea here and hope for more user votes

Whenever the endpoint updates are installed that require a reboot to complete the installation - please prompt the user to reboot their computer at least 1 or 2 times a day. Currently, there will only be a red X on the Sophos Icon on the system tray stating that the update failed. The only way they can see that a reboot is required, is by looking in the update logs. When a reboot is required it should show that to the user and not just show an error. This goes for the console as well. When a reboot is needed this should not show up as an error. It should show up everywhere that a reboot is needed to complete the installation.

When an object is deleted from the Sophos Cloud console and Sophos isn't removed from the endpoint beforehand, the endpoint stops being able to update.

MCS Communication reports in Endpoint Self Help that the updating failed due to Error 401: Unauthorized.

The Sophos Client doesn't reflect an error or problem with updating and doesn't alert the end user to the fact that the Sophos Client is compromised. This causes the possibility of "lost endpoints" with no obvious indications of a need for repair.

Please modify the behavior of the endpoint to raise an alert on the local system so the user will be informed of a failure and the need to contact support.

We have reports of users on slow or expensive network connections (ie: Airplane, Hotel, Train, Cellular) that they would like to temporarily suspend updates until they are on an unmetered connection.

We are requesting that a 'suspend updates' toggle switch be enabled in the client. We have found the cancel updates option is not totally reliable. Sometimes it will cancel the download after it has used the network (possibly at great expense).

This affects our MacOS users mostly, but it would also apply to windows also. Windows has an API for handling network interface metering, so this is less pressing on this platform.