Step 1: Installing the extension via UEM solutions [Generic]
This page includes:
About installing the extension via UEM solutions
Important: Before implementing the procedures described on this page, make sure to see Deploying the extension [Managed deployment]. |
This page describes Step 1 of the extension deployment process - Installing the extension using a UEM.
-
After initial deployment of the extension, the extension is periodically updated - automatically - as required.
-
For information about using GPOs in Active Directory to deploy the browser extension, see Deployment via GPOs in Active Directory.
Force-install the extension
When you use a managed installation option, it is recommended that you implement a procedure that will force-install the extension on all target devices so that users won't be able to remove or disable the extension. This will help to make sure that their browsers are always protected by the extension. For details, and additional recommendations, see Strict enforcement of the browser extension.
Multiple browser profiles
It is recommended that you install the extension and the associated organization token on the device level. This will enable the extension to be automatically added to all browser profiles of all users on each target device. This includes both corporate profiles and personal profiles. It also includes profiles that are added in the future.
If you don't install the extension and the organization token on the device level, but rather on the user level or on a profile level, then the extension will be installed on the specified browser profiles only. The extension will not be added to other browser profiles on a target device - which then won' be fully protected by the extension. However, installing on the user level or on a profile level gives you additional flexibility. For example, you could choose to add the extension to corporate browser profiles, but not to personal browser profiles.
Installing the extension - options
There are two procedures available to install the extension. One procedure installs the extension on all supported browsers other than Safari. The other procedure installs the extension on Safari browsers only.
Installing the extension - excluding Safari
[For details on how to install the extension on Safari, see Installing the extension - Safari only below.]
The available options for installing the extension vary, depending on:
-
whether you are currently using your UEM to manage extensions.
-
the functionality that is available in your UEM solution.
-
the browsers on which the extension will be installed. [For example, Google Chrome and Microsoft Edge]
-
the operating systems on the target devices. [For example, Windows and MacOS]
You may need to implement multiple procedures, where different procedures are applicable to different browser/operating system combinations. For example, you may need to implement one solution for installing the extension on Google Chrome and Microsoft Edge browsers on Windows, another solution for Firefox on Windows, and another solution for Google Chrome and Microsoft Edge browsers on MacOS.
The options for installing the extension are summarized in the table below.
Option 1 - You already use your UEM to manage extensions If you already use a UEM to manage other extensions [for the required browser/OS combination], then use the same UEM capabilities to install the ABS extension.
|
|
Option 2 - You currently don't use a UEM to manage extensions If you currently don't use a UEM to manage extensions [for the required browser/OS combination], then you'll need to choose a UEM to install the extension. Based on the installation capabilities of the UEM that you choose, there are two options available: |
|
|
Option 2A - You can choose a UEM that has native extension management capabilities If you choose a UEM that has native extension management capabilities [for the required browser/OS combination], then use the UEM's native extension management capabilities to install the extension.
Option 2B - You can choose a UEM that doesn't have native extension management capabilities If you choose a UEM that doesn't have native extension management capabilities [for the required browser/OS combination], then installing the extension is performed by the UEM to run an extension installation script that can be downloaded from the Advanced Browser Security console.
|
Important: After installing the extension, any browsers that were open during the installation should be restarted. This will enable all open tabs in the browser to be protected by Advanced Browser Security. |
Installing the extension - Safari only
[For details on how to install the extension on all browsers other than Safari, see Installing the extension - excluding Safari above.]
To install the ABS extension on Safari browsers:
-
In the Advanced Browser Security console, click Settings > Deployment options.
-
Under "Installing the extension to endpoints", open the "Deploying on Safari" dropdown.
-
Click the copy icon to copy the App ID to the clipboard.
-
Use your MacOS UEM solution to push the MacOS App Store application to end-users.
-
End-users must manually grant permissions to the extension (via Safari settings) and authenticate by clicking the extension icon.
Important: After installing the extension, any browsers that were open during the installation should be restarted. This will enable all open tabs in the browser to be protected by Advanced Browser Security. |
What's next
![]() |
Now that the extension is installed on the endpoints, you must now connect the extensions to the ABS organization. For details, see Step 2: Connecting the extension via UEM solutions [Generic]. |
See also: