vWorkspace AntiVirus Best Practice

Well, www.vWorkspace.com is down at the time of this writing.  So I’m scouring the intertubes for some quick guidance.  Here’s what I’m finding.

Guidance from Citrix.  Yes, it’s not vWorkspace, but the fundamentals should be similar:  http://support.citrix.com/article/CTX114522 – The Cliff Notes of this document are:

  • Exclude Spool directory, page file, and ../program files/Citrix  (Not sure if later is required with Quest vWorkspace)
  • Scan write events only
  • Scan local drives only

Hmm, that’s nice.  Still no vWorkspace.com access. On to the next piece.

After installing Trend Micro ServerProtect presentation becomes unresponsive: http://support.citrix.com/article/CTX114137 .  That sounds like us.  Better give Trend Micro a holler on the telephone.

Still no vWorkspace.com, so checking on a good topic on BrianMadden.com that seems to fit the bill perfectly.  Best anti-virus for Terminal Services -  The dude posting the question references Patrick’s recommendation here: http://www.sessioncomputing.com/anti-virus.htm but that is down too!   Is there some kind of DDoS on vWorkspace sites today?  Actually, looks like that might just be an old site.

I guess, I’ll look this up the old-fashioned way.  Email to our SE at Quest.  Will update post with findings and best practice for A/V in vWorkspace Terminal Server environment soon.  :)

UPDATE: Customer is turning off auto-protect.  Kind of feel like if we’re going to do that, why don’t we just focus AV protection on the gateway and just continue to rebuild fully patched clean Terminal Servers with visionapp Server Management on a more regular basis.  With no server-based AV mucking up performance.  Thoughts?

Viewing 2 Comments

 

Trackbacks

(Trackback URL)

close Reblog this comment
blog comments powered by Disqus