New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 627071 link

Starred by 5 users

Issue metadata

Status: Fixed
Owner:
Closed: Jun 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Chrome doesn't start properly in Citrix when started from Outlook linke (DDE request)

Project Member Reported by pastarmovj@chromium.org, Jul 11 2016

Issue description

This is still an issue in the current version of Chrome.

Our current Citrix environment is still Citrix 6.0 (Server 2008R2). We are in the process of migrating to Citrix 7.8, but this will take time.

In terms of Chrome, the published app we are using is the 32bit version of ChromeEnterprise. There is reported issues with using the 64bit version of ChromeEnterprise - where by the command line switches --alow-no-sandbox-job and -disable-gpu do not function. I have been able to confirm this when I had installed it on a server initially. Uninstalling it and downgrading it to the 32bit version was the solution. 

ChromeEnterprise is being managed by our GPO's.

We have the published app starting with the appropriate "C:\Program Files (x86)\Google\Chrome\Application\Chrome.exe" --allow-no-sandbox-job --disable-gpu settings. 

Everything is working fine as a standalone browser. Chrome is set as default.

HOWEVER - one MAJOR (for us) problem. Links from Outlook do not function.

When you click on a link within Outlook, Chrome launches, it has the link address in the address bar but fails to make a connection. It is like the --allow-no-sandbox-job setting gets disabled or turned off. It hangs. can't even get to the properties page of Chrome. 
This needs to function properly.
I'm going to test this in our Citrix 7.8 Environment (Server 2012R2) to see if this issue follows. 

 
Exactly as described this issue has been going on since we are using the combination Xenapp 6.5  / server 2008 r2 / Chrome / Outlook
Its frustrating that no absolute solution is available.
We are forcing to patch registry keys on outlook start regarding http association to point to internet explorer or firefox to work-a-round the issue, but this is not a stable solution. 
We tried to add the --allow-no-sandbox-job parameter to the default execution path of the http association registrykey.
Once chrome is started the patch has no effect anymore because chrome.exe overwrites the default association regkeys every start.
Result: Complaining users getting frustrated not being able to open links from Outlook.

Comment 2 by saswat@chromium.org, Nov 10 2016

Cc: -saswat@chromium.org
Cc: pastarmovj@chromium.org ligim...@chromium.org
 Issue 669084  has been merged into this issue.
Status: Started (was: Assigned)
This should be fixed in Chrome 58 which is beta now. This version does not require the flag and can automatically detect and react to remote desktop environment.

Can you please verify the fix in your test environment and tell us if it works for you.

Simply publish Chrome 58 with no extra flags and check that it works as expected.
Can anyone following this issue please confirm whether Chrome 58 and newer are working as expected when launched from Outlook in Citrix sessions?
Status: Fixed (was: Started)

Sign in to add a comment