Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Adobe Connect and Realtime scanning

Updated: 22 May 2010 | 3 comments
Rick Bywalski's picture
0 0 Votes
Login to vote

We recently upgraded our Adobe Connect Server to ver 7 SP3.   Since then we have been having issues people playing back recordings that were recorded prior to the upgrade.  We previously had just excluded the folder that connect was installed to from being scanned.   The only solution Adobe has offered to date is to turn off realtime scanning and run scheduled scans during off hours.  When we turn off realtime Connect does perform better.  Realtime is configured to only scan when a file is created or modified. Prior to the upgrade to we were on ve 7 sp2 and excluding the connect folders allowed realtime to be on and function.    SEP was on mr4mp2 and we even tried upgradeing to RU5 with no difference.   Has anyone else ran it to this or anything similar?

Comments

Thomas K's picture
02
Oct
2009
2 Votes +2
Login to vote

Check out this Adobe KB - It

Check out this Adobe KB - It states Adobe does not support real-time virus checking. Instead, Adobe recommends scheduled scanning of the file system for viruses. Refer to your virus scan software documentation for more information on how to setup scheduled scanning.

Some possible side effects of real-time virus checking on a Connect Enterprise system include:

  • Degraded performance
  • Corrupt indexes
  • Meeting core crashes
  • Application server restarts
  • General system instability

http://kb2.adobe.com/cps/400/kb400986.html

Thomas

Rick Bywalski's picture
02
Oct
2009
1 Vote +1
Login to vote

hoping to find exceptions to add in and keep realtime

hoping to find some exceptions we can add in and keep realtime running.  Find it interesting that excluding the connect folder worked until the most recent upgrade of connect.

 

Jeremy Dundon's picture
02
Oct
2009
1 Vote +1
Login to vote

I suggest

Using procmon or some other process monitoring utility to find out what new location the new version of Adobe is using.