Sophos update

Hello Ahilan,

in order to create deployment packages your must install the Enterprise Console (SEC) first (if your license is for Endpoint Security and Control). Maybe you are looking for something else.

The _sa_ download is the endpoint stand-alone (unmanaged) software. You can install it on the endpoint(s) but without SEC it can only update from Sophos directly. You'd have to configure this manually using your license credentials for user/password.

Christian

Hi Christian,

I have downloaded Enterprise Console(sec_541) and installed the software. The package I tried to create is to download the update from sophos directly. What is the primary update location ? I have entered 'Sophos' but the following error message come up - "Primary update location 'sophos' is not in the correct format. Enter either a UNC folder path or HTTP location and try again. Can you please let me know this information?

Thanks

Ahilan

Hello Ahilan,

the package I tried to create is to download the update from sophos directly
neither SEC not the Deployment Packager permit Sophos as Primary update location.

Is this a trial? If yes, then SESC is probably not the product you're looking for. If not, why is a stand-alone package your primary concern if you have licensed SESC?

Christian

Hi Christian,

Thanks for your reply. In our company there is a package automatically installed by scripts on windows compurters if any client ask to install it .  The person who has created this package has left  and I have been asked to check why we have to use secondary update for sophos update. There is an entry in primary update location (http://sophos.update.com/update)  which does not exists. Secondary location has address - sophos and our credentials for username and password. But when you download and install sophos from web (savw_106p_sa_sfx.exe), this is only use primary location information ie: address as Sophos and the credentials.  

As you said "neither SEC nor the Deployment Packager permit Sophos as Primary update location" - is there any documentation shows that, as I have to update our internal documentation about it.

Kind Regards

Ahilan

Hi Christian,

Thanks for your reply. In our company there is a package automatically installed by scripts on windows compurters if any client ask to install it .  The person who has created this package has left  and I have been asked to check why we have to use secondary update for sophos update. There is an entry in primary update location (http://sophos.update.com/update)  which does not exists. Secondary location has address - sophos and our credentials for username and password. But when you download and install sophos from web (savw_106p_sa_sfx.exe), this is only use primary location information ie: address as Sophos and the credentials.  

As you said "neither SEC nor the Deployment Packager permit Sophos as Primary update location" - is there any documentation shows that, as I have to update our internal documentation about it.

Kind Regards

Ahilan

Hello Ahilan,

neither SEC nor the Deployment Packager permit Sophos as Primary update location
it's not explicitly stated AFAIK (there are implicit references to Sophos as source is only mentioned for Secondary - please see to update from Sophos when necessary and Set the secondary update server), the GUI simply doesn't accept it.

download sophos from web
again - this is the stand-alone package (unmanaged), not intended for general on-site deployment. If you don't want to run an on-premise management server (SEC) then maybe Central is better for you.
if any client ask to install it
do I understand correctly that an anti-virus product is an optional choice and not mandatory? Or are the users free to select from different products and vendors? Or?

Christian

Hi Christian,

Thanks for your information. I'll update our document with this findings.

Users are free to select different products but we only offer Sophos for those requested it.

Kind Regards

Ahilan