I noticed you can easily uninstall the SAE 3.5 addon on Google Chrome latest version by going to tools, extensions, and choosing to remove the addon. Isn't it supposed to be protected from being uninstalled? Using EPO 4.6 in our environment.Message was edited by: fleiva79 on 12/8/11 11:22:04 AM CST
When you uncheck the Addons, you are not uninstalling the product. It's kind of the disabling it for that brower.
I will suggest you to have the user policy not to modify any browser settings except Admins.
I am not sure if this will be possible only for SAE.
I will suggest you to submit PER #: https://secure.mcafee.com/apps/downloads/products/products-enhancement-request.aspx?region=us
My company uses SiteAdvisor 3.5 Enterprise, I see a setting called Hardening within that setting you'll see a check box you can check that says:
I NEED a way to make it where you can't disable the Chrome version of Site Advisor. Does anyone have any suggestions?
There's a way to manually protect SAE to be disabled from Firefox through VirusScan policies, perhaps you can apply it to chrome? (changing affected foders, of course)
I've got same problems, KB article mentioned above is not a solution for me. I guess McAfee needs to provide a way how to prevent this via EPO Server or how to deal with autoupdateurls for chrome extensions.
Because there are chrome GPO's available where I can put extensionsids for autoinstall and autoupdate of extensions provided from webstore in. those extensions cannot be disabled or deinstalled within chrome by users. However this is currently not working even if i put the extensionid in cause siteavisor is not available in chrome webstore respectively not providing an updateurl pointing to the EPO server either. Realy annoying thing.
I currently have an open SR with McAfee on this. I'm using a RTS version of SAE 3.5 (188.8.131.524) and while I can lock down SAE in IE and FF with the SAE policy, Google Chrome and SAE 3.5 aren't playing ball with each other. I might just block execution of Chroms via SAE policy since Chrome is not a supported browser at my company.