Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 3 subscribers
  • Views 2505 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

Manual Install failure

Spud Murphy

Trying to manually install SEC on lWindows 7 Laptop, (not on network) browse to setup.exe and run it nothing appears to happen. Sophos ES Setup file contains the following:

23/10/2018,12:08:59,ERROR,An unexpected error occurred, no translation available: boost::filesystem::status: The network name cannot be found: "\\<Servername>\OPMHMPA\hmpa64",

I can't find this folder on on Sophos Server, and ideas?



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

    Hello Spud Murphy,

    not on network
    what is the source you are using? A copy of the CID on the server? Do you run setup.exe with switches or using the GUI?

    Christian

  • 0 in reply to QC

    Apologies should have read "not on Domain" Laptop was standalone but connecting back to the Sophos server to run setup.exe using the GUI.

    I have a workaround, I joined the laptop to the domain and went through the discovery and Protect route and all seems to be fine?

    But still apprehensive as I will want to install Sophos on several other standalone laptops in the future!

  • 0 in reply to Spud Murphy

    Hello Spud Murphy,

    dunno why it indicated HMPA. SEC isn't really domain-aware and not domain-bound. The endpoint software relies on the usual Windows features and functions. The network name cannot be found is a normal and old Windows net (not .Net) message. The cause is often that a non-domain computer needs the FQDN to find a domain computer. Given the necessary access rights and available name resolution it doesn't matter which domains and workgroups are involved.

    As far as the Sophos software is concerned you have to use FQDNs instead of NetBIOS names.

    Christian

Reply
  • 0 in reply to Spud Murphy

    Hello Spud Murphy,

    dunno why it indicated HMPA. SEC isn't really domain-aware and not domain-bound. The endpoint software relies on the usual Windows features and functions. The network name cannot be found is a normal and old Windows net (not .Net) message. The cause is often that a non-domain computer needs the FQDN to find a domain computer. Given the necessary access rights and available name resolution it doesn't matter which domains and workgroups are involved.

    As far as the Sophos software is concerned you have to use FQDNs instead of NetBIOS names.

    Christian

Children
No Data
Unfiltered HTML