This is probably the ScriptScan component for Firefox. Too bad McAfee did not supply the product name and version number (looks like they forgot to replace some variables), then we would have been sure. However, Scriptscan is on Mozilla's blocklist: https://addons.mozilla.org/en-US/firefox/blocked/i42 so it probably won't work anyway.
The reason you are seeing this message is because from Firefox 8 onwards, extensions and plugins cannot be installed by applications silently anymore, user interaction/approval is required: http://blog.mozilla.com/addons/2011/08/11/strengthening-user-control-of-add-ons/
Is there any way to install vs 8.8 p1 and not include the firefox plugin?
I´m installing using EPO 4.6
If anything is to work, it would be to install the product without the ScriptScan feature (see the Installation Guide for command line options that control what features get installed). Are you sure you want to do that though, because the feature adds value... for the browsers it supports anyways .
You must add the following command line to your product deployment task for VSE 8.8 in ePO:
Note: This will only work for newly installed client it will not remove ScriptScan from existing VSE installation. Therfore you cann run
with the above command-line paramaters at the workstations.
Also note that this will remove ScriptScan functionality from Internet Explorer as well. Currently only Firefox up to version 4.x is supported for VSE8.8 Patch 1.
I recently updated our systems from Firefox 8 (not sure which minor version) to Firefox 9.0.1, and Firefox 9.0.1 seemed OK with the McAfee Add-In. In other words, it left it enabled and didn't complain about it. This was on a mixture of XP Pro SP3 32-bit, Vista Ultimate SP2 64-bit, and 7 Pro 32-bit.
Looks like Firefox 10.0 doesn't like ScriptScan again. The update from FF9 to FF10 says it will be disabled. Somebody at McAfee and somebody at Mozilla need to get together and figure out how to keep ScriptScan from being disabled in Firefox every six weeks. I tend to blame this on Mozilla because of their ridiculously short upgrade cycle, but either way, they ought to be able to figure out something.
Message was edited by: jguenrdc on 2/2/12 4:26:48 PM CST
Most add-ins should have an install.rdf file. It's in your user profile area. It's a plain text file. It contains a max version string you can edit. I do that with Google Toolbar. The location of the file somewhat varies depending on the version of Windows, as they keep moving and renaming the user directories. It's probably under the Roaming\Mozilla\Firefox\Profiles\default.lws\extensions. You then need to figure out the CLSID for the add-in and look through the .rdf files to figure out which to edit.
There is also an add-in that can let you override version checking.
I found VSE's install.rdf in C:\Program Files\Common Files\McAfee\SystemCore (on an XP system). I disabled VSE Access Protection, changed the maxVersion from 9.9 to 10.9, and enabled VSE Access Protection. Then I updated Firefox to 10, and it didn't complain or disable the add-in. Thanks andyross for the info.