Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 14 subscribers
  • Views 4730 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 Intercept X Terminal server 2019 best Practices

Marvio Botticielli

Hello,

We have just deployed a new TS2019 for a client of ours. The Sophos install went on no issues. The server is "feeling it" however. We have about 20 users on that server, we have assigned the proper resources as per MS to that many sessions, but the server is slugish. I see that every session spawns a new instance of Sophos, that can't be correct, can it? Are there any switches, configurations specific to terminal servers so Sophos is not running for every session created? As it stands no HOST would be powerful enough to run TS with Sophos depending on how many users you have.

I must be doing something wrong here, right? Even a moderate user load on an RDP farm, say 50-80 users, would require a whole host to run all those sessions with sophos starting a new instance for every user, at that point, well there is no point in any virtualization platform, might as well install windows to the bare metal.

Help! :)



This thread was automatically locked due to age.
  • 0

    You are talking about the Sophos UI.exe process.  This is launched from the Run key to give the user desktop notifications should web pages be blocked, malware detected, etc..  If you don't feel the need for these to be shown to the end users and the saving seems worth while, I guess you could disable the startup item it in Task Manager.  You can equally tun "sophos ui.exe" /exit to close the current process but maybe the run key would be simpler and see how the performance is then.

Unfiltered HTML