When I first installed VSE 8.8, I disabled ScripScan because I am afraid webpages will be loading really slow in IE 8 and I rarely use Firefox or other browsers.
So right now, I decided to enable ScriptScan to see how things work out.
If pages are loading really slow due to the ScriptScan being enabled, will it be safe to disable it?
It is now enabled without any URL Exclusions.
In addtion to this, my Windows 7 images do have ScriptScanning disabled and I decided to only enable it on demand.
Now if I do decide to enable it on demand and If I notice any performance impact or any other issues due to this, then I will just disable it again.
And, I cannot recall if the ScriptScan is EMABLED or DISABLED by default in VSE 8.8 (Patch 3)??
ThanksMessage was edited by: anvin0001 on 1/2/14 2:41:13 PM CST
I recommend leaving it turned on all the time.
Well, sure will enable it then. If I have issues, then I will just uncheck it.
At the moment, I did not add any Exclusions. I just left it checked as it is and see how it goes.
Is there an official guide from McAfee that I can look at all the default settings for VSE 8.8 for Workstations (un-managed)?
I would really like to compare those with my current settings.
And also, there is no way one can reset VSE to its main default settings unless it is re-installed.
But I would like a documentation were I can look up those default settings?
I only have the VSE 8.8 Best practices guide. But I actually need a like a table for the default settings for workstations on the folowing settings:
On Access scanner settings
Just reading this post as I experienced similar issue on one of our server (DC). There's no documents that will tell/show you default settings, that's why they are called default. You need to check this yourself and modify to suit your need/requirement or environment. I totally agree with Peter on leaving the settings as they are and change as per need. In our case all enabled for workstation and disabled for all servers. Alternatively see this KB article - McAfee Corporate KB - ScriptScan causes significant performance hit/load delay on websites KB70013
You will have to TEST. There may be SINGLE Applications where Scriptscan does not work. On our side from 120000 EXE or DLL maybe 10 (3 different customer who have that effect from all we have)