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

Installing standalone version on Computer that previously hosted the enterprise console

Has anyone ever tried installing the standalone version of Sophos into a computer that used to host the enterprise console? I’ve been able to install the standalone version on 14 of 15 computers that were previously managed by enterprise console, the 15th is the computer that had the enterprise console installed.. this computer in Particular doesn’t seem to be able to update. The iconn.cfg file has been updated to reflect the new unc path C:/SAVACFXP, and the SAVSCFXP is in the C:/ directory, but it’s saying failed to connect to server... could there be old files in program data or program files that are interfering with this? Should I completely delete all of the old files from those directories? Can’t think of any other reason why it can’t just pull the savscfxp from the c drive when the other 14 have no issue



This thread was automatically locked due to age.
Parents
  • Hello Jeff Mann,

    may I ask why this group of computers has been "de-managed"? I assume this folder in C:'s root is a copy of the relevant CID.

    You uninstalled (on the 14 as well as the late management server) all Sophos components or just some before installing the SA version?
    The ALUpdate log should have details for this failed to connect.

    Christian

Reply
  • Hello Jeff Mann,

    may I ask why this group of computers has been "de-managed"? I assume this folder in C:'s root is a copy of the relevant CID.

    You uninstalled (on the 14 as well as the late management server) all Sophos components or just some before installing the SA version?
    The ALUpdate log should have details for this failed to connect.

    Christian

Children
No Data