The removal of NPAPI support will affect user experience for users who access Citrix Receiver for Web using the Chrome browser on Windows and Mac.
Users will be prompted to install Citrix Receiver every time they access the Receiver for web site.
An ICA file will be saved when users try to launch an application or desktop. They will have to click the ICA file at the bottom of the browser to activate the launch.
Workspace control will be disabled on Windows.
To improve Chrome’s security and stability, Google announced late 2014 that NPAPI plugin support, a capability we have depended on for years, will be disabled by default in Chrome by April 2015. NPAPI is a plugin that Receiver for Windows and Mac that enables Receiver for Web to detect if Receiver is installed. It also enables users to launch applications by simply clicking them.
While Citrix is actively working on new technology that will replace our dependency on NPAPI plugins, there are some workarounds that can be taken in the short term. Tru cool max silverado.
Use one of the following workarounds to fix the issue:
Use a different Citrix Receiver supported web browser such as Internet Explorer, Mozilla Firefox, or Apple Safari to connect.
Citrix Google Chrome Roaming Profile
Re-Enable NPAPI within the Chrome address bar
As stated here, NPAPI can still be enabled in Chrome by advanced users and enterprises after April 2015 when it is disabled by default. However, this will only work until September 2015 when Google Chrome will completely disable NPAPI.
Important Note - Consult the security specialist of your organization before change:
To re-enable the NPAPI plugin in Chrome:
- Type chrome://flags/#enable-npapi in your browser’s address bar.
- Click Enable.
- Quit Chrome (close all open windows) and restart the browser.
- Use Task Manager to verify there are no running Chrome.exe processes listed. If there are any still running end those tasks before logging on.
- Go back to your website and logon. The applications should now launch normally.
Customize Receiver for Web
If you do not want to or cannot disable Chrome auto update or re-enable NPAPI Plugin, you can do a number of customization to Receiver for Web to reduce the disruption.
Note: All the customization code in this article is applicable to StoreFront 2.6.
Disable client download prompt for Chrome
If you insert the following code into custom.script.js in the contrib folder under the Receiver for Web site, Chrome users will never be prompted to install Citrix Receiver:
Provide a permanent link for downloading Receiver in Chrome
The preceding code snippet helps you disable the Receiver install prompt for Chrome. However, you might still want your users to be able to download and install Receiver if needed. Apply the following code snippet in custom.script.js will add a link to the user menu to download Receiver for Chrome browser:
You have to also add the following strings to custom.wrstrings.en.js and a localized version for every language you need to support to custom.wrstrings.<language>.js:
The resultant UI looks similar to the following:
Enable Workspace Control For Chrome On WindowsWorkspace control is disabled on Windows if Receiver for Web cannot detect whether the browser is running in an ICA session (pass-through mode). This is to avoid disconnecting the session running the browser itself. If you can ensure that this never happens, that is, Chrome is never used in the double-hop deployment to access applications/desktops in the second-hop sharing the same XenApp/XenDesktop farms/sites, you can apply the following code snippet to custom.script.js in the contrib folder under the Receiver for Web site to enable workspace control for Chrome.
Enable Chrome To Open ICA file AutomaticallyAfter the ICA file is saved, users can open the action menu for the ICA file at the bottom of the browser and select Always open files of this type. After that, launch will be automatically activated when the user clicks an application/desktop icon to launch.
Google Chrome by default will install into a user profile which is problematic for mass deployment in a layer. However Google does provide an “offline” installer that installs Chrome into “Program Files” and this installer should be used with Unidesk if installing into a layer.
The basic installation steps are straight forward:
1.Create a Google Chrome application layer
a.Install Chrome using the offline installer or msi
b.Note on extensions
c.Disable Google Updates (optional)
2.Configure Chrome AD GPO’s
3.Apply the layer to desired desktops
Step 1 Create a Google Chrome Application Layer
The first step is to install Chrome itself.Download the offline installer from here:
Choose the Alternate installer for all user accounts.Then install Chrome.It will install into the “Program Files” directory.
To install extensions please use a GPO http://dev.chromium.org/administrators/policy-list-3#ExtensionInstallForcelist
There are two ways that can be used to disable Google Updates for Chrome.You can use the enterprise GPOs, see the next section or follow this link to disable via the registry
Citrix Google Chrome
or set the value of HKEY_LOCAL_MACHINESOFTWAREPoliciesGoogleUpdateAutoUpdateCheckPeriodMinutes to the REG_DWORD value of '0'.
Step 2 (Optional but recommended) Install and configure the Google Enterprise Active Directory Templates In Order To Manage These Settings
The Goggle Chromium project has created a set of GPO settings that can be used to manage Chrome in an Enterprise Environment.
Here is where you can download the ADM files and see the documentation:
Once you have the ADM files installed its very easy to configure Chrome settings.
Unidesk recommends including the OS Type and OS bit level in the name, for Example Google Chrome 31 Win7x32. For versions remember that when choosing a layer you can see the version name but not the version description. Use naming that will allow you to differentiate versions appropriately. For example “1.0 12-12-2013”.
If you are using a GPO to disable updates just add a version to your layer and open Chrome it will automatically update.If you have used the registry setting to disable updates modify the registry setting to a number other than 0 and open chrome, it will update then you can set the registry entry back to 0.Note: If this doesn’t work for you let me know I was not able to test this in the lab.
Google Chrome Citrix Workspace App
It is not possible to add custom extensions for a single user with a NP desktop.