Loading...Web Control browser extension must be enabled by the user
Technical Articles ID:
KB87568
Last Modified: 11/10/2020 EnvironmentMcAfee Endpoint Security (ENS) Web Control 10.x
Google Chrome Microsoft Edge Microsoft Edge Chromium Microsoft Internet Explorer Mozilla Firefox SummaryENS Web Control works with Chrome, Edge, Edge Chromium, Firefox, and Internet Explorer as a browser extension or add-on. These browsers require you to manually activate the ENS Web Control extension before you can use Web Control.
Each browser has different behaviors and steps associated with activating the ENS Web Control extension after ENS Web Control is installed on the local system. IMPORTANT: If enabled, the ENS option to Prevent users from uninstalling or disabling browser plugins prevents users from disabling the ENS Web Control extension only in Internet Explorer. The hardening policy does not prevent users from disabling ENS Web Control in Chrome, Edge, Edge Chromium, or Firefox. Contents Click to expand the section you want to view: NOTE: The version of ENS Web Control reported in the browser is 10.7.0.x when ENS Web Control 10.6.1 is installed. Edge Chromium also allows for the ENS Web Control extension to be force-enabled through Active Directory. For details see https://docs.microsoft.com/en-us/deployedge/configure-microsoft-edge. The The extensionID for ENS Web Control is NOTE: The version of ENS Web Control reported in the browser is 10.7.1 when ENS Web Control 10.6.1 is installed. If a user disables the ENS Web Control extension in Edge, you can't re-enable the extension through ePolicy Orchestrator (ePO) and the McAfee Agent. The user must re-enable the extension locally. Windows provides a group policy, Prevent turning off required extensions, to harden the Edge extension. To make sure that users can't disable the ENS Web Control extension, add the ENS Web Control extension PFN to the group policy Prevent turning off required extensions. The ENS Web Control extension PFN is the following and can be fetched from the Dev Center portal: For detailed instructions to enable this group policy, see https://docs.microsoft.com/en-us/microsoft-edge/deploy/new-policies#prevent-turning-off-required-extensions. Currently, Microsoft does not provide a way to manage Edge through Active Directory to force-enable the ENS Web Control extension. If a user disables the ENS Web Control add-ons in Internet Explorer, the add-ons can't be re-enabled with ePO and the McAfee Agent. The user must re-enable them locally. If enabled, the ENS self-protection policy keeps users from disabling the add-ons. Internet Explorer also allows for the ENS Web Control extension to be force-enabled through Active Directory. For details, see https://technet.microsoft.com/en-us/library/cc985341.aspx and https://technet.microsoft.com/en-us/itpro/internet-explorer/ie11-deploy-guide/enable-and-disable-add-ons-using-administrative-templates-and-group-policy. The CLSID for the ENS Web Control BHO is If a user deletes the ENS Web Control extension in Chrome, you can't restore the extension through ePO. An uninstall and reinstall of ENS Web Control does not add the ENS Web Control extension back in Chrome. To make the ENS Web Control extension available in Chrome again, you must do either of two things. Either delete the Chrome user profile that deleted the ENS Web Control extension, or reinstall Chrome on the system. When you add the ENS Web Control extension to force install in group policy, you must remove the SiteAdvisor Enterprise extension from being force installed. Otherwise, there will be two icons in Chrome. The SiteAdvisor Enterprise icon does not function because the SiteAdvisor Enterprise service is not running. The SiteAdvisor Enterprise extension interferes with the ENS Web Control extension, and it causes navigation issues from ENS Web Control enforcement messages. Firefox also allows for the ENS Web Control extension to be force-enabled through Active Directory. Firefox provides ADMX templates to configure policies using Active Directory. The templates are available at: https://github.com/mozilla/policy-templates/releases. The policies work with Firefox 60 and later, and Firefox ESR 60 and later. Use the policy template Extensions to Install to apply a policy to install the ENS Web Control extension. The policy requires the file path of the ENS Web Control extension file on the system. To install the extension on both x86 and x64 systems, add two entries to the policy with the respective paths: NOTE: These paths are the default installation paths for the extension. For custom installation paths, specify the custom installation directory.
There is also a policy to prevent users from removing the ENS Web Control extension. Use the policy template Prevent extensions from being disabled or removed. The extension ID for the ENS Web Control extension is If you installed the ENS Web Control extension using group policy, it must be uninstalled using group policy. ENS product uninstallation does not remove the extension. To uninstall the ENS Web Control extension, edit the Extensions to Uninstall policy and add an entry for the ENS Web Control extension ID. When you upgrade ENS, the ENS Web Control extension does not upgrade. The upgrade does not occur because the Extensions to Install policy does not watch for file changes. Extensions can be updated via policy by uninstalling and reinstalling them. For more details and workarounds, see https://bugzilla.mozilla.org/show_bug.cgi?id=1510993#c3. There are known issues when sometimes the Extensions to Uninstall policy fails to remove the extension. In these cases, Mozilla recommends using the ExtensionSettings with the blocked configuration. The blocked configuration prevents installation of the extension and removes it if the extension is installed. Using the ENS Web Control extension ID, you can enable the blocked configuration to remove the extension from the endpoint in the case that the Extensions to Uninstall policy fails. For detailed documentation on the ExtensionSettings policy, see https://github.com/mozilla/policy-templates#extensionsettings. Affected ProductsLanguages:This article is available in the following languages: English United StatesSpanish Spain French Italian Japanese Portuguese Brasileiro Glossary of Technical Terms |
|
Question?
