Extensi

Google Chrome
The following steps are to be followed if the default browser on end user side is
Google Chrome.
- Login to the domain controller and download the AD templates provided by Google to
manage Chrome using the below link.

http://dl.google.com/dl/edgedl/chrome/policy/policy_templates.zip

- Extract the downloaded zip file in a directory.

- Identify your SYSVOL directory and navigate to the Policies directory inside it. The
default SYSVOL directory location is as below.

C:\Windows\SYSVOL\sysvol\<domain-name>\Policies

- Create a directory called “PolicyDefinitions” under Policies directory.

- Navigate inside the PolicyDefinitions directory.
- Copy the chrome.admx from the extracted folder to this directory.
- Create another directory called en-US and copy the chrome.adml file from the en-US folder
in the extracted directory to the current directory. If you are using any other language,
please choose the appropriate file from respective language folder.
- Choose the files from the adm folder if you are on Windows XP and Windows 2003 Server.
- Choose the files from the admx folder if you are using Windows Vista or later versions.
- In Server Manager, under Tools, select Group Policy Management.
- This will open the Group Policy Management window.
- If you want to create a new GPO, right click on your domain name and select ‘Create a GPO
in this domain and Link it here’ option. Give a name to the new GPO and select “Group Policy
Remote Update Firewall Ports” and click on OK.

- If you have an existing policy, you can skip this step.

- Right click on the newly created policy or existing policy and select Edit.
- In the GPME window, navigate to Computer Configuration → Policies → Administrative
Templates → Google Chrome → Extensions, right click on “Configure the list of force-
installed apps and extensions” and select Edit.

- Click on the Enable radio button and under options, click Show. Double Click on the value
text box for * and enter the following value.
<extension_id>;https://clients2.google.com/service/update2/crx

Note:

- Once the extension has been uploaded to chrome store, you will be provided with a link to
download and install. For instance, if the link you received is “https://chrome.google.com/web-
store/detail/whatfix-editor/ohkeehjepccedbdpohnbapepongppfcj”, then the exentsion ID will be
“ohkeehjepccedbdpohnbapepongppfcj”.

- Replace the <extension_id> placeholder with the actual value before entering it in GPO.
- Now, click OK to close the “Show Contents” window. Click on Apply and OK to close the
main window.
- From the command line, run “gpupdate /force” to force group policy update or wait for
update to kick in by itself.
- Once the group policy update is run, you can notice the Whatfix browser extension installed
on Google Chrome.
- Future updates will be installed automatically by Google Chrome as and when available.
Mozilla Firefox
The following steps are to be followed if the default browser on end user side is Mozilla Firefox.

- Firefox extension can be installed by placing the extension in the appropriate folder with
the name <extension_id>.xpi
- In order to do that, create a folder under C:\ and name it whatfix_extensions.
- Share the folder and give permissions to Authenticated Users to read the contents.

- Download the firefox extension using the below link and place it under the
whatfix_extenstions folder.

http://dl.google.com/dl/edgedl/chrome/policy/policy_templates.zip

- Open Group Policy Management Editor → Computer Configuration → Preferences →

Windows Settings → Files, right click on it and select New → File.
- Fill in the source file(s) text box with the network location of the whatfix firefox extension.
- Fill in the destination file text box with the below mentioned value.

C:\Program Files\Mozilla Firefox\browser\extensions\<extension_id>.xpi

Note:
- If you are installing a developer extension, replace the <extension_id> placeholder
with <customer_ent_id>-dev@whatfix.com
- If you are installing a production extension, replace the <extension_id> placeholder
with <customer_ent_id>-prod@whatfix.com
- <customer_ent_id> will be unique ID generated specific to each customer by Whatfix. ENT
ID will look like “4524f390-de7c-11e7-ae74-04013d24cd02”.
- For developer extension, the extension ID will look like
4524f390-de7c-11e7-ae74-04013d24cd02-dev@whatfix.com
- For production extension, the extension ID will look like
4524f390-de7c-11e7-ae74-04013d24cd02-prod@whatfix.com

- Click on Apply and OK.

- Run “gpupdate /force” from command line to force group policy update or wait for update
to kick in by itself.
- Once the group policy update is run, you can notice that the Whatfix browser extension got
installed in Mozilla Firefox. However, user have to manually enable the extension to use it.
- Due to security reasons, Mozilla has restricted the extension to be in disable state
for unattended installations.
- Once the Group Policy update is run, user will notice a yellow exclamation in the “Open
Menu” option in Mozilla Firefox in the right hand side corner.
- Future extension updates will be taken care by Firefox itself. It will detect if any new update
is available and will install it automatically.

- Clicking on the exclamation mark will open the menu and convey the message that Whatfix
extension has been installed. Clicking on that message will take the user to extension window.
- Once in the extension window, a pop up will appear asking user to enable or cancel the
extension installation. When the user clicks on Enable, the extension will get enabled in
Firefox and the icon can been seen near the address bar.
Internet Explorer
The following steps are to be followed if the default browser on end user side is
Internet Explorer:

- Unlike Chrome and Firefox, IE Add-on comes as a msi package which can be installed with
the help of Windows installer.
- In order to do that, download and place the IE extension in the same shared folder where
you have placed the Firefox extension.
- Open Group Policy Management Editor → Computer Configuration → Policies →
Software Settings → Software Installation, right click on it and select New → Package.
- Select the msi installer from the network share path. In the Deploy Software dialog, select
the “Assigned” radio button and click on OK.

- Run “gpupdate /force” from command line to force group policy update or wait for update to
kick in by itself.
- Group policy update might require a system restart. If prompted for restart, please restart
the machine.
- Once the group policy update is run, you can notice that the Whatfix browser extension
got installed in Internet Explorer.
- However, for security reasons the extension will be in disable state.
- Post Group Policy update, when the user opens IE, they will be prompted with a dialog box
at the bottom of IE mentioning that Whatfix addon has been installed and gives user option to
enable it.

- Once the user clicks on Enable, the extension gets enabled in IE.
- With respect to future updates, the new MSI package has to be pushed as part of group
policy again to update the extension to new version. Unlike Chrome and Firefox, IE does not
support auto update of browser addons.