- Chrome Os Citrix Workspace
- Citrix Cannot Start App Chrome
- Citrix App Layering Chrome Recipe
- Citrix Workspace Chrome App
- Chrome App Citrix Workspace
Citrix Receiver for Chrome product software. Important update about Citrix Receiver Beginning August 2018, Citrix Receiver will be replaced by Citrix Workspace app. One of the most popular browsers today, Google Chrome, is a must-have for many Citrix Virtual Apps and Desktops environments.
Objective
The default way Chrome will work is to then copy itself into the user profile when it runs.
Instructions
None.Citrix Cannot Start App Chrome
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”.The basic installation steps are straight forward:- Create a Google Chrome application layer
- Install Chrome using the offline installer or msi
- Note on extensions
- Disable Google Updates (optional)
- Configure Chrome AD GPO’s
- 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:https://support.google.com/chrome/answer/126299?hl=en
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
Disable Updates
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 registryhttp://www.chromium.org/administrators/turning-off-auto-updates
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:
https://support.google.com/installer/answer/146164?hl=en
Once you have the ADM files installed its very easy to configure Chrome settings.
Updates
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.
If you have enabled any updates through scheduled tasks, disable that as well.
Considerations for Non-Persistent Desktops
It is not possible to add custom extensions for a single user with a NP desktop.
Applicable Products:
Citrix Receiver for HTML5, Citrix Receiver for Chrome, Citrix Workspace app for Chrome, Citrix workspace app for HTML5
Citrix App Layering Chrome Recipe
Solution
Citrix Workspace Chrome App
Recommended solution: Update the certificates.
Alternatively, you can try this workaround:
Close the Citrix Workspace app for Chrome / Citrix Receiver for Chrome.
Open Chrome browser in your Chromebook.
Visit your site.
It will show some error as below.
Now, open the Citrix Workspace app for Chrome or Citrix Receiver for Chrome and it might allow you to access your StoreFront/VDA.
Other possible workaround for specific certificate error:
NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM error
Latest Firefox and Chrome browsers do not support SHA-1 certificate and StoreFront connection fails with error: NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM
Citrix Receiver for Chrome/HTML5 or Citrix Workspace app for Chrome/HTML5 cannot establish secure connection and session launch will failNET::ERR_CERT_COMMON_NAME_INVALID error
Chrome requires Subject Alternative Name for SHA-2 certificate, without SAN (Subject Alternative Name) in the SHA-2 certificate, the connection will fail with error NET::ERR_CERT_COMMON_NAME_INVALID
Session launch fails with CERT_COMMON_NAME_INVALID(-200) error dialog
Workaround for NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM and
NET::ERR_CERT_COMMON_NAME_INVALID:Mozilla:
Enable network.websocket.allowInsecureFormHTTPS from about:config
Chrome:
Chrome by default requires SHA2 Certificate with Subject Alternative Names (SAN)
Add the following registry keys at : SoftwarePoliciesGoogleChromeEnableCommonNameFallbackForLocalAnchors – true
(Note: Chrome need SAN by default)EnableSha1ForLocalAnchors – true
(Note: SHA1 is not supported)
Recommended Solution: Use SHA2 certificates with Subject Alternative Names (SAN).Problem Cause:
CTX134123 - Receiver for HTML5 - Unable to Launch Apps Using HTTPS URL
CTX217352 - How to Collect Logs in Receiver for Chrome and Receiver for HTML5
NET::ERR_CERT_SYMANTEC_LEGACY
From Chrome OS version 66 onwards the SSL certificate from Symantec is distrusted. You can go through https://security.googleblog.com/2018/03/distrust-of-symantec-pki-immediate.html to know more about it.
Workaround: Try general workaround mention above.
Recommended Solution: Update SSL certificates.
Problem Cause
Chrome App Citrix Workspace
CTX134123 - Receiver for HTML5 - Unable to Launch Apps Using HTTPS URL
CTX217352 - How to Collect Logs in Receiver for Chrome and Receiver for HTML5