Endpoint Security Client Install Package

Hi,

You don't mention if you have Sophos Enterprise Console (SEC) or Sophos Control Center (SCC) but the update architecture is the same.  Typically the server, running either SEC or SCC pulls down files from Sophos databanks into a "Warehouse" directory:

\\SERVER\SophosUpdate\Warehouse \

These files are then converted into the software packages and made available here to the clients on the network:

 \\SERVER\SophosUpdate\CIDs \

Note: There is a Sxxx directory for each subscription you have.  If you have SCC you only hae one, for SEC you can have many.

So as an example, when you protect a client, either via the console or manually protecting it, you are running setup.exe from one of these directories, e.g.

\\server\SophosUpdate\CIDs\S000\SAVSCFXP \setup.exe

This installs all of the software on the client, i.e. AutoUpdate, RMS, SAV, SCF, Patch, etc..  The client then typically keeps checking back to this location of updates.  So the software in the location the client is checking should be the latest version.

Note: "C:\ProgramData\Sophos\AutoUpdate\Config \iconn.cfg "  or if on 2000/XP/2003 "C:\Program files\Sophos\AutoUpdate\Config \iconn.cfg " will tell you where the client is updating from.

You can also check the version of the Windows package by looking in the file:

\\Server\SophosUpdate\CIDs\S000\SAVSCFXP\savxp \SVF.xml
if needed.

You can also configure a secondary location for the client to check, which maybe Sophos.  So when the primary location can not be found, i,e, the client goes away from the network it can keep updating with the latest identities.

The other options for installing software on the client is:

1. To use the standalone installer.  This is typically for unmanaged machines and the client updates just from Sophos.
This is downloaded from Sophos in the downloads section of the website
 

2. To use a package, typically built by the administrator.  This tends to be a copy of a CID (\\Server\SophosUpdate\CIDs\S000\SAVSCFXP\ ) at a point in time packaged up, this is then installed on a client, and on next update it pulls down the latest software and installs.  How often that package is rebuilt by the admin would determine how many versions you would jump up on update if that makes sense.

I hope this helps answer you question on how to get the latest version on your client.

I suspect either, you are installing an old packaged software deployment,, which as long as configured correctly should update to the latest version or have run setup.exe from the wrong Sxxx location on the server.  

Hope it helps.

Regards,

Jak

Hi and thanks.

Our environment is a workgroup and we have a Windows 2003 Server that serves as a file server, email server, etc.

We do run the latest version of the SCC. When I do a discovery on the network (Protect New Computers), the new client doesn't show up, however, it is listed in the list but is grayed out with an unknown OS.

Are there some special instructions that are available that will allow me to configure the Windows 7 client so that the SCC can discover it and push the install?

Thanks.

Steve S

Hello Steve,

the applicable article should be How to prepare computers for installation of security software (instructions for Workgroup networks) (there's also a small table for pointing to the relevant articles for other environments).

HTH

Christian