This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Configuring SophosUpdateManager without Internet Access

Can anyone advise me, or point me in the direction of a white paper, that describes how to update the Sophos Update Manager on a Network which is not connected to the Internet ?

So far I have managed to install the Sophos Enterprise Console 4.5.1, installed the Sophos database, and have successfully searched for other computers on the Network by importing from Active Directory.

Now I want to protect these PCs / Laptops, but at the moment there is nothing in my SUM because when I run the Download Security Software wizard I can not connect to the Sophos website.  (i.e. the machine running Sophos EndPoint Security and Control is not on the Internet).

What do I do next ?

:10609


This thread was automatically locked due to age.
Parents
  • On my non-internet Windows 2003 Server I copied "Warehouse" and "CIDs" into the "SophosUpdate" share which is at "C:\Documents and Settings\All Users\Application Data\Sophos\Update Manager\Update Manager"

    Now - this is the location used by SUM for

    storing (Warehouse) the data "downloaded" from the SophosUpdateManager share

    deploying (CIDs) the decoded software to make it available to the clients

    So I'd say you don't need to copy anything there. Has SUM successfully completed downloading and deploying? In SEC use View->Bootstrap Locations ... to check if SAVXP is available in the expected location.

    Code 0000006b Download of SAVXP failed from server C:\Documents and Settings

    Ideally this should be a share on your server (\\server\SophosUpdate\...) and not a local path. Setup.exe configures the path it  is run from (if you don't use any switches) and using Protect computers this is the share. But as the clients also fail this is likely not the problem. So it might be that the CID has not (yet) been successfully deployed.

    As 0000006b is rather general you should check the ALUpdateyyyymmddTtt...tt.log in C:\Program Files\Sophos\AutoUpdate\Logs for the specific reason.

    Christian

    :11237
Reply
  • On my non-internet Windows 2003 Server I copied "Warehouse" and "CIDs" into the "SophosUpdate" share which is at "C:\Documents and Settings\All Users\Application Data\Sophos\Update Manager\Update Manager"

    Now - this is the location used by SUM for

    storing (Warehouse) the data "downloaded" from the SophosUpdateManager share

    deploying (CIDs) the decoded software to make it available to the clients

    So I'd say you don't need to copy anything there. Has SUM successfully completed downloading and deploying? In SEC use View->Bootstrap Locations ... to check if SAVXP is available in the expected location.

    Code 0000006b Download of SAVXP failed from server C:\Documents and Settings

    Ideally this should be a share on your server (\\server\SophosUpdate\...) and not a local path. Setup.exe configures the path it  is run from (if you don't use any switches) and using Protect computers this is the share. But as the clients also fail this is likely not the problem. So it might be that the CID has not (yet) been successfully deployed.

    As 0000006b is rather general you should check the ALUpdateyyyymmddTtt...tt.log in C:\Program Files\Sophos\AutoUpdate\Logs for the specific reason.

    Christian

    :11237
Children
No Data