
- #Mozilla firefox homepage registry how to
- #Mozilla firefox homepage registry install
- #Mozilla firefox homepage registry full
HKEY_LOCAL_MACHINE\Software\Wow6432Node\ Vendor\ Name\Extensions HKEY_LOCAL_MACHINE\Software\ Vendor\ Name\Extensions

This is because the application will read from a different registry key depending on the architecture of the application and the OS.

#Mozilla firefox homepage registry install
The location to use varies depending on whether you want to install the extension for all users of the computer or just the current user and.įor the current user use the following registry key: HKEY_CURRENT_USER\Software\ Vendor\ Name\Extensionsįor all users of the computer you should add to both of the following registry keys. This mechanism is designed to make it easier for third-party installers to register extensions with Firefox and Thunderbird.
#Mozilla firefox homepage registry how to
Firefox should pass your Windows credentials automatically and you should not see any browser popups asking for a username & password.This document explains how to "install" Firefox and Thunderbird extensions using the Windows Registry. Of course, as a final test, try accessing your Password Reset or uReset enrollment page, or try logging into Office 365 using Specops Authentication. The settings should be locked and the values should match what you set in your GPO. If you want to double-check the policy has applied within Firefox, open a new tab and go to about:config.

Next, close and re-open Firefox for the settings to take effect. You should see registry keys created under HKLM/Software/Policies/Mozilla Enable Authentication/NTLM and Authentication/SPNEGO (-uris) and add the following URLs to both settings:Īpply the GPO and run gpupdate. Specops Authentication leverages NTLM and Kerberos. Specops uResetĮnable Authentication/NTLM and add to the URL list. If you are using a certificate issued by an internal CA, you can also enable the Certificates/Import Enterprise Roots setting (security.enterprise_roots.enabled) so Firefox will automatically use the Trusted Root Certificates from Windows. Specops Password ResetĮnable /Authentication/NTLM and add the address used by your users to access your internal SPR server (this corresponds to the -uris setting in Firefox). Now you can add settings that will enable Windows integrated authentication. You should now have a Mozilla/Firefox folder in your group policy editor under Computer Configuration/Administrative templates: Unzip the policy-templates.zip file from GitHub and copy the ADMX and ADML files to the appropriate location: If you have a central store, then copy the files to \\domain\sysvol\\policies\policydefinitions, otherwise copy the %windir%\policydefinitions on the machine where you’ll be editing your Firefox GPOs.

The Group Policy ADMX templates are available to download from Mozilla’s GitHub page (get at least version 1.0):
#Mozilla firefox homepage registry full
You will need to install the ESR (Extended Support Release) version of Firefox 60 in order to get full support for GPO settings, as the main release channel of Firefox ignores many of the settings. For customers using Specops uReset, Specops Authentication, or Specops Password Reset, this means you can now set up your Firefox users to take full advantage of integrated Windows authentication in these solutions. Mozilla recently launched Firefox 60, which now includes official support for configuration via Active Directory Group Policies.
