Thread Info
  • State Verified Answer
  • +2 person also asked this people also asked this
  • Locked Locked
  • Replies 16 replies
  • Subscribers 18 subscribers
  • Views 7665 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

InterceptX and Citrix Virtual Apps and Desktop (Daas) 7.15 lTSR

Matthew Sherman1

Since we've switched from SEP to Sophos. We've had many random issues with users connecting and receiving various connecting errors. I know that this is a Sophos issue because I removed Sophos from all of our Citrix VDAs and all problems go away. last night I added Sophos back to 2 of our 6 VDAs and all of today's errors are from the 2 that have Sophos installed

I added all of the exclusions recommended by Citrix from the following link, even the one that don't apply to our environment. I made sure that the policy applied to the 2 servers that have Sophos installed. 

https://docs.citrix.com/en-us/tech-zone/build/tech-papers/antivirus-best-practices.html

Lastly, we are using UPM (profile management) so I attempted to disable the following scan, but the registry entry does not exist in our environment 

https://support.citrix.com/article/CTX238012

I'm sure I can't be the only person experiencing this issue. 

Any assistance would be greatly appreciated.

Matthew Sherman



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

    Hi Matthew,

    on a customer we have the same issue, with UPM that loads profile from file server, the logon is very long and logging off the session some files remain on server.

    The VDA is 2203 and the OS is Windows Server 2019.

    We tried the same configuration without Sophos and all work fine.

    The exclusions are all present. We tried to set your same registry key and the result not change.

    Do you have found a solution?

    Thank you

    -DS-

  • 0 in reply to DavideSchiavoni

    Hi Davide,

    Did you find a solution? On a customer with the same environment we the same issues

    Thanks

  • 0 in reply to Rho82

    Hi Sove,

    we found that there isn't Sophos that causes issue. Our slow logon process was caused by policy "Direct connections to print servers". This because new VLAN created for MCS was not contacting print server VLAN. We found this turning on/off some ICA Channels.

    I hope you will find the problem.

    Thannk you

Reply
  • 0 in reply to Rho82

    Hi Sove,

    we found that there isn't Sophos that causes issue. Our slow logon process was caused by policy "Direct connections to print servers". This because new VLAN created for MCS was not contacting print server VLAN. We found this turning on/off some ICA Channels.

    I hope you will find the problem.

    Thannk you

Children
No Data
Unfiltered HTML