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

Central Endpoint install error - Management console is installed. SEC us not installed?!

Hi

I am trying to install Central endpoint server on a Windows Server 2012 Standard system, but I get the below message

SEC is NOT installed on this server. It was at one point but was removed some time ago. 

No services are lingering, reg keys have been cleaned out and there is no trace in program files folders or program data folders.

Logs attached.

Can anyone advise please?

Thanks.

/cfs-file/__key/communityserver-discussions-components-files/3/SophosCloudInstaller_5F00_20210217_5F00_112242.log

Dan.



This thread was automatically locked due to age.
Parents Reply Children
  • No worries - thanks for your help anyway!

    I have a case open with Support but they're taking ages to get back to me.

  • If you look in the Central Installer log (\programdata\sophos\cloudinstaller\logs\) you will see the checks, e.g.:

    2021-02-17T18:55:50.7846233Z INFO : Running System Property Check: NotSecServer ...
    2021-02-17T18:55:50.7886119Z INFO : System Property Check: NotSecServer - PASSED

    For example, now this is a MSI based component so the best way to check for the presence of a MSI component is the upgrade code as product codes can change.

    If you run Process Monitor at the same time (Sysinternals/Microsoft) you will see the registry check for the upgrade codes by the Cloud installer.

    Add a couple of filters:

    • ProcessName contains SophosSetup
    • Registry Events only
    • Path contains upgradecodes

    You will see at the same time a Success rather than a Name Not Found

    The upgrade code it finds at the time of the failing test will be the issue.

  • If it helps I found a copy of the SEC installer: C:\sec_551\ServerInstaller\

    UpgradeCodes

    {C2419059-C131-46CB-922A-E823587552BA} is Server64.msi

    {271306A7-5799-4B1B-AEC1-8DC159D2613E} is Server32.msi

    If you just open a MSI up in Orca, you can view the Property table to see the UpgradeCode property for a MSI file.

    These GUIDs are actually referenced in the registry slightly differently:

    C2419059-C131-46CB-922A-E823587552BA = 9509142C131CBC6429A28E32855725AB in the registry.

    Note each part is backwards.

  • Hi 

    I have found the below key from SysInternals

    Do I need to delete the highlighted key then?

    Thanks

  • Hello Dan,

    Do I need to delete
    of course - apparently this is one of the things the installer is looking for. As it belongs to a product that is no longer installed it should be pretty safe to delete.

    Christian

  • That's done it!

    Thank you both!