Protecting endpoints from your Sophos Console appears to do nothing when using an HTTP based primary update location

  • Article ID: 119004
  • Updated: 25 Mar 2013


When protecting endpoints in your Sophos Console nothing appears to happen, the icon on the endpoint(s) does not change to show a orange arrow. Leaving the console for a period of time shows no progress or a response to the deployment. The event log on the endpoint and console have no relevant entries.

First seen in
Sophos Enterprise Manager 4.7.0
Sophos Control Center 4.0.0
Enterprise Console 4.5.0


Your updating policy used by the endpoints you are protecting has no Initial Install Source set, or just has 'Use primary server address'. Advanced trace logging will show entries that are similar to the following:

00007666 1.20214355 [4404] Error [0x00001220] path `http://server/UpdateManager/CIDs/S000/SAVSCFXP` not UNC or HTTP
00007667 1.20226765 [4404] Error [0x00001220] path `` not UNC or HTTP
00007668 1.20234025 [4404] Error [0x00001220] path `` not UNC or HTTP
00007669 1.20239055 [4404] Error TraceEEComputerInstall[0x00001220] Could not install computer 2 because the config is empty

What To Do

  1. Open the Sophos Console, double click on the updating policy used on the endpoints you are attempting to protect.
  2. On the Primary Server tab, check to see if an HTTP path is being used in the Address box.
  3. If so, move to the Initial Install Source tab, deselect Use primary server address.
  4. Change the Initial install source to a the following UNC path:

Note: Replace <server> with the actual name of the server hosting a distribution location from Sophos Update Manager, in most situations you can use the server name hosting your Sophos Management Service.

If you need more information or guidance, then please contact technical support.

Rate this article

Very poor Excellent