Follow

KLC browser plug-in support with Google Chrome (VSA 6.2 and earlier)

KB #: KKB000911

SYMPTOM

In Google Chrome, these errors are related to recent updates of Google Chrome and occur when logging into a v6.2 VSA on a machine with the KLC Plug-in Manager installed (choose one):

Chrome on Windows displays "Extensions, apps, and user scripts can only be added from the Chrome Web Store"

chome-1.png


Chrome on Mac OS displays "Could not load Plug-in Manager"

chome-2.png

 

-------------

Chrome on Windows displays "Extensions, apps, and user scripts can only be only be added from the Chrome Web Store"

CAUSE

With Chrome v21 and later, the default security configuration prohibits automated installation of extensions from sources other than the Chrome Web Store. This means that KLC plug-ins will no longer be automatically installed when needed.

This affects installation of KLC browser plug-ins on Windows only (plug-ins on Mac OS are installed using a downloaded image file).

 

SOLUTION

Chrome allows the policy to be bypassed for specific URL's., however installation of KLC plug-ins uses a file which is downloaded to the local drive, so installation requires temporarily disabling the policy:

 

1) Close and exit all Chrome windows.

2) Create the following key in the registry location:

HKEY_CURRENT_USER\Software\Policies\Google\Chrome\ExtensionInstallSources

3) Under this key, create a string value like this:

Name: 1
Type: REG_SZ
Data: <all_urls>

NB - the name "1" may already be taken by another policy. If so, use the next available numeric value.

chome-3.png


4) Start Chrome again, log onto the VSA and install KLC plug-ins (you may be prompted on login or when trying to start a KLC connection).

5) If necessary, remove the string value created in step 3 (to reapply the default Chrome 21 security policy). 

NB - The next release of Kaseya (v6.3) will have a downloadable installer for browser plug-ins, so will not be affected by this problem.

--- 

Chrome on Mac OS displays "Could not load Plug-in Manager"

CAUSE

Chrome 22 and later on Mac require plug-ins to specify an event model.

 

SOLUTION

This is addressed in the next release of Kaseya (v6.3).

---------

APPLIES TO

Kaseya VSA 6.2 and earlier
Google Chrome

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.