Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 7 replies
  • Subscribers 1 subscriber
  • Views 2781 views
  • Users 0 members are here
Options
Suggested
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

Sophos Enterprise Console 3.x - Upgrade Issues

kwy_tech

History:

I am a tech that recently took over control of the technology for a small private school.  I soon discovered that all of the Sophos products were outdated and that the automatic updates.  Most of the computer became infected with various viruses and I have spent a great deal of time working on the machines individually until I discovered we had Sophos Enterprise Console (SEC) on our single Windows 2003 Server.  I proceeded to upgrade the SEC from 3.x to 4.7 based on the instructions provided by the Sophos Upgrade Advisor.  The SEC is now at 4.7 but I have the following issues that I cannot seem to resolve no matter what I try.

Issue 1:

The "Migrate EMLibrary to SUM" procedure did not work for me during the upgrade process.  I have attempted to correct this based on various articles on the Sophos website but I just cannot figure it out.  I get the following warning every time I launch the SEC:  "EM Library is still running the updating hierarchy.  It is recommended that you migrate all your updating settings to Sophos Update Manager.  Click 'View Report' to view the 'Updating hierarchy' report of click 'OK' to close this dialog".  How do I correct this?

Issue 2:

I am unable to get any of the endpoint machines to update becuase I must not be configuring the SEC correctly.  I would like to have the machines pull updates directly from Sophos to avoid the issue of having outdated files on the server but I cannnot seem to get this to work.  When I update the address/URL in the Default Updating window the machines themselves append additional data to the end of the URL and the updates do not work.  What is the best practice for ensuring my machines stay updated?

Issue 3:

Post SEC upgrade I discovered that my C: drive on my server is nearly full now and there is nothing I can remove to free up any significant amount of space.  The Windows Server 2003 box only has an 8 Gig C: drive so I can in a bind now.  Would it be possible to remove all of the SEC product and put it on a Windows XP machine and manage my Sophos environment from another machine (note:  we only have one server and no budget at the moment so having a 2nd server is not an option).  Help!

:18611


This thread was automatically locked due to age.
Parents
  • 0

    Hello kwy_tech,

    let's start with space (3). Am I right to assume that the server has ONLY these 8 Gig? If SEC is up and running and has already successfully downloaded and deployed to the SuphosUpdate share (which I doubt, see: 2) it might "just" be enough space, as you can free up some 100M by removing EM Library. Considering a workstation as management server (which is in principle possible) - how many client computers?

    (2) You can't configure Sophos as the primary location but as Secondary (until you've sorted out your updating problems). I assume you are using a "new" policy, not a "Legacy" (if there is a tab Subscription it's a new one). The additional path (which is BTW not appended by the machines but by SEC) probably ends with SAVSCFXP and it's the equivalent of the CID location in EM Library. What is the error the clients encounter? If you could post a few lines from the updating log we might be able to help you figure out where the problem is.

    If you browse to the server's SophosUpdate share - do you see the folders \Warehouse and \CIDs, and under CIDs \S000\SAVSCFXP? Is the latter populated?

    (1) The warning is normal as long as you haven't completed the migration. Please run the report and post it here if it's not clear what it wants to tell you.

    Christian

    :18661
Reply
  • 0

    Hello kwy_tech,

    let's start with space (3). Am I right to assume that the server has ONLY these 8 Gig? If SEC is up and running and has already successfully downloaded and deployed to the SuphosUpdate share (which I doubt, see: 2) it might "just" be enough space, as you can free up some 100M by removing EM Library. Considering a workstation as management server (which is in principle possible) - how many client computers?

    (2) You can't configure Sophos as the primary location but as Secondary (until you've sorted out your updating problems). I assume you are using a "new" policy, not a "Legacy" (if there is a tab Subscription it's a new one). The additional path (which is BTW not appended by the machines but by SEC) probably ends with SAVSCFXP and it's the equivalent of the CID location in EM Library. What is the error the clients encounter? If you could post a few lines from the updating log we might be able to help you figure out where the problem is.

    If you browse to the server's SophosUpdate share - do you see the folders \Warehouse and \CIDs, and under CIDs \S000\SAVSCFXP? Is the latter populated?

    (1) The warning is normal as long as you haven't completed the migration. Please run the report and post it here if it's not clear what it wants to tell you.

    Christian

    :18661
Children
No Data