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

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
  • we ran into similar issues. It was determined that it was far
    easier in the long run to migrate to a new server.  We built a new server up with the latest
    Endpoint console (at the time), re-created our policies, then did a re-install
    at the client using PS Tools and some home grown scripts (I would be happy to
    provide a source code if you need it). The we simply ran the script through our
    ORG remotely. It took about 2 days to complete and we could track the progress
    by watching the new server get its clients and the old server lose clients. We
    did about 3,800 total machines in two days (including reboots) with a success
    of about 99.21%. Since you only have about 100 clients you would be done in an
    hour or two (after server build of course). It turned out to be far quicker and
    we fought less issues in the long run. Next major release when we are ready for
    a new server we will likely do the same, until then we have plenty of space and
    power on the new server to do in place upgrades.

    :18753
Reply
  • we ran into similar issues. It was determined that it was far
    easier in the long run to migrate to a new server.  We built a new server up with the latest
    Endpoint console (at the time), re-created our policies, then did a re-install
    at the client using PS Tools and some home grown scripts (I would be happy to
    provide a source code if you need it). The we simply ran the script through our
    ORG remotely. It took about 2 days to complete and we could track the progress
    by watching the new server get its clients and the old server lose clients. We
    did about 3,800 total machines in two days (including reboots) with a success
    of about 99.21%. Since you only have about 100 clients you would be done in an
    hour or two (after server build of course). It turned out to be far quicker and
    we fought less issues in the long run. Next major release when we are ready for
    a new server we will likely do the same, until then we have plenty of space and
    power on the new server to do in place upgrades.

    :18753
Children
No Data