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

exe created by Sophos Deployment Packager (1.2)... unable to install on Windows 2012 server virtual machine.

douglas168@yahoo.com

Hi all,

 

I running into problem trying to run the SophosEndpoint.exe created by Sophos Deployment Packager (1.2) on a Windows 2012 server virtual machine.   When I run as administrator on Windows 2012 server virtual machine, nothing happens.   If I run the same SophosEndpoint.exe on a Windows 7 virtual machine, it installs Sophos Endpoint just fine.   Anyone experienced the same issue or have a solution for it?   Appreciate the help!  Thanks in advance.



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

    Hello douglas168,

    the package isn't magic, basically it just runs setup.exe with the appropriate switches and arguments. Depending on the selected options it might not display anything at all, but the usual logs are written.  The bootstrapper log (Sophos ES setup.log.txt) and the output from the CRT (avremove.log) are written to your user's %TEMP% directory, component installer logs to SYSTEM's %TEMP% (%windir%\Temp). You should find the reason for the apparently failed install in one of them.
    Did you select NTP (Network Threat Protection, aka MTD - Malicious Traffic Detection)? AFAIK it's not (yet) available for server OSs managed by SEC thus selecting NTP for the package might cause setup.exe to fail (haven't tested it though). 

    Christian

Reply
  • 0

    Hello douglas168,

    the package isn't magic, basically it just runs setup.exe with the appropriate switches and arguments. Depending on the selected options it might not display anything at all, but the usual logs are written.  The bootstrapper log (Sophos ES setup.log.txt) and the output from the CRT (avremove.log) are written to your user's %TEMP% directory, component installer logs to SYSTEM's %TEMP% (%windir%\Temp). You should find the reason for the apparently failed install in one of them.
    Did you select NTP (Network Threat Protection, aka MTD - Malicious Traffic Detection)? AFAIK it's not (yet) available for server OSs managed by SEC thus selecting NTP for the package might cause setup.exe to fail (haven't tested it though). 

    Christian

Children
No Data
Unfiltered HTML