Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 3 replies
  • Subscribers 2 subscribers
  • Views 7066 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 Error "Failed to install Sophos Management Communications System: Error code 8007007e."

Stem Admin

Good Morning,

Enterprise Console is reporting an update error on some of my clients "Failed to install Sophos Management Communications System: Error code 8007007e.". Has anyone seen this before?

SEC Version 5.4.1

Thanks

Ben



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

    Hello Ben,

    MCS is the cloud equivalent for the on-premise RMS and is used with the Central, Home, and UTM products, and perhaps with a Web Appliance. The AutoUpdate logs (in ProgramData) and the installer logs should give some insight. You aren't about to migrate to Central, are you? Or has some local admin attempted to install ... naw, I think the bootstrapper should refuse to proceed.   

    Christian

  • 0 in reply to QC

    Hi Christian,

     

    I believe cloud was originally installed but was licensed incorrectly so they moved to SEC. That makes sense why they are getting that error. Will this have any effect on pushing out updates from the console? As far as I can see the clients seem to be updating successfully.

    Thanks

    Ben

Reply
  • 0 in reply to QC

    Hi Christian,

     

    I believe cloud was originally installed but was licensed incorrectly so they moved to SEC. That makes sense why they are getting that error. Will this have any effect on pushing out updates from the console? As far as I can see the clients seem to be updating successfully.

    Thanks

    Ben

Children
  • +1 in reply to Stem Admin

    Hello Ben,

    pushing out updates from the console
    updates are never pushed, the endpoints download the updates. If the update location is correct it doesn't matter whether management (be it RMS or MCS) works (you "just" don't get informed about an endpoint's status and can't change the settings). Apparently management (via RMS) is working - otherwise you wouldn't get notified. AutoUpdate doesn't care about the semantics of a particular component it is instructed to download and install. Dunno where this information is stored for MCS - for RMS it's a config file (idata.cfg) but this should have been overwritten when ESC was installed. Perhaps it's under HKLM\SOFTWARE\Wow6432Node\Sophos\AutoUpdate\Products\     (I'm sure can tell), if you find a subkey (normally there's one for AutoUpdate and one for Anti-Virus) which mentions MCS simply delete the key.

    Your endpoints should be fine (if SEC says they are up to date then they are) apart from they annoying message which can be safely ignored until you find out how to remove MCS from AutoUpdate's list of products to install.

    Christian

Unfiltered HTML