Citrix WebHelper for Google chrome can work as invoked mode or Non-invoked mode to access XenApp/XenDesktop resource.
The article describes configuration steps for Citrix WebHelper invoked mode. It is essential to have access to back-end application via NetScaler Gateway when Receiver Client Selective Trust (CST) feature is enabled.
Instructions
1. For an already installed Chrome,
Chrome > Settings > Show advanced settings > Privacy > clearing Browsing data: the beginning of time, then exit Chrome and re-run it.
2. Access Netscaler Access Gateway URL in Chrome and login with user credential, You should get below “Detect Receiver” page.

3. Click “Detect Receiver” button and wait, you should see Chrome “External Protocol Request” dialog window pop up.
Note: Verify url receiver://<AG FQDN>/Citrix/…, Verify the client machine can resolve the AG FQDN to correct IP address.
4. Click “Launch Application” button, the expected output is, “Just a moment, we’re detecting if…” and then automatically redirects to Storefront resource enumeration page with resources listed, or Storefront login page (you might need to re-enter user credential and click “Logon” button).
Important Note:
- If “Just a moment, we’re detecting if…” webpage doesn’t auto redirects to enumeration/login page of storefront, please click “Detect again” button to try again.
- If “Just a moment, we’re detecting if…” webpage doesn't redirect to storefront web page, it means the configuration for Citrix WebHelper invoked mode failed. In this situation, user can click “Already installed” to continue, Chrome will work in Citrix WebHelper NOT invoked mode.
5. In Storefront resource enumeration page, click an application icon. If “External Protocol Request” dialog window pops up.
It indicates Chrome is working at WebHelper.exe invoked mode.Otherwise, It will work in non-invoked mode. Where it will download ICA file for the resource.
6. Check "Remember my choice" to avoid repeated
External protocol request popup and Click “Launch Application” button, the application should be launched by Receiver successfully even with CST enabled.