Sophos Central Endpoint and SEC: Computers fail/hang on boot after the Microsoft Windows April 9, 2019 update. Please follow knowledge base article 133945
Learn about the Benefits of Multi-Factor Authentication (MFA). Turn your MFA on now!
After attempting to protect an endpoint computer with Sophos Endpoint Security and Control from the central console the deployment failed.
There are several error codes that can be shown in the console (errors covered in separate articles are linked in the table below).
There are several error messages that can follow the error code. Example:
Could not start installation program on the computer. The network path was not found.
The installation did not start. The computer may have been shut down, renamed or disconnected, or a required service may not be running. It may be running Windows XP Home or Windows Vista, or Windows 2008.
The installation could not be started. The computer may need additional configuration before installation.
The installation could not be started: Access is denied. The computer may need additional configuration before installation. See knowledgebase article 29287.
The installation could not be started: The network name cannot be found.
First seen in Enterprise Console
The common causes of these deployment errors are:
Note: The table at the beginning of this article that lists the error codes have links to other articles detailing specific troubleshooting steps. Follow the steps in those articles (where available). Otherwise follow the steps below.
Use the following checklist to ensure you can deploy endpoint software to the computer successfully:
Note: To understand how the console protects a computer (useful when troubleshooting) see article 12455.
After changing the computer settings with a GPO and then protecting that computer from the console it is important to allow time for the computer to apply the settings. The endpoint computer may require a reboot to reconfigure itself or you can run gpupdate /force from a run box/command prompt to speed up the process.
Ensure the newly-created GPO(s) is linked and enabled in the Group Policy Management Console on the server (click Start | Run | Type: gpmc.msc | Press return)...
On the endpoint computer use the 'Resultant Set of Policy' window (Start | Run | Type: rsop.msc | Press return) to confirm the changes you made central for the Windows services have been implemented on the endpoint...
...and the Windows firewall has been configured to allow creation of the remote scheduled task...
Every comment submitted here is read (by a human) but we do not reply to specific technical questions. For technical support post a question to the community. Or click here for new feature/product improvements. Alternatively for paid/licensed products open a support ticket.