Sophos UTM: Decommissioning of obsolete URL categorization services CFFS.Click here for important info.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 13 subscribers
  • Views 1018 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 setup (Silent) in a PowerShell (Windows 10) hangs

ITService_Berlin

Hello,

we want to install the Sophossetup.exe with the unattended Installation of windows 10.

The installation went well. But the PowerShell windows is still open ...it hangs.

The Sophossetup.exe is not seen in the taskmanager.

The Logs seems to be ok: Install result: Succeeded

The command:

Start-Process -Filepath ($ScriptDir + "\" + $PEXE) -Argumentlist "--products=antivirus,intercept --quiet" -Wait

When I close the PowerShell windows the unattended Installation goes ahead.

Has someone an Idea?

Best Regards
Frank



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

    Hi ITService_Berlin,

    Thanks for reaching out to the Sophos Community Forum. 

    May I ask why you have the "-Wait" argument at the end of the command? Is this necessary for the script to run as expected? 

    Kushal Lakhan
    Team Lead, Global Community Support
    Connect with Sophos Support, get alerted, and be informed.
    If a post solves your question, please use the "Verify Answer" button.
    The New Home of Sophos Support Videos!  - Visit Sophos Techvids
  • 0 in reply to Qoosh

    Hello, I am also running into this situation.  I want to add /wait to my script because in the past when I installed Sophos, it was very dependent on restarting.  In MDT, the installer would restart unprompted with silent commands.  The current installer doesn't prompt for a restart so I am wanting to "wait" until the process is done and restart. I am not currently using MDT for imaging, but I am deploying through remote software. 

    Does the current installer need to be restarted?

  • 0 in reply to Jake Dumont

    A restart is encouraged but not required.  Reason being, the solution injects modules such as SophosED.DLL and Hmplaert.DLL into processes as they launch in order for some of the protection layers to fully function.  Mainly exploit mitigation.

    For the processes already running, the modules therefore aren't loaded so this is the main reason.

    Realtime-scanning, behavioural, Cryptoguard are all fine.

Reply
  • 0 in reply to Jake Dumont

    A restart is encouraged but not required.  Reason being, the solution injects modules such as SophosED.DLL and Hmplaert.DLL into processes as they launch in order for some of the protection layers to fully function.  Mainly exploit mitigation.

    For the processes already running, the modules therefore aren't loaded so this is the main reason.

    Realtime-scanning, behavioural, Cryptoguard are all fine.

Children
No Data
Unfiltered HTML