UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36

Example URL:

Steps to reproduce the problem:
1. Log into Citrix (6.0) environment environment (Server 2008R2) with published Outlook application. 
2. Open Outlook App, and click on link in an email
3. Watch as Chrome opens to a grey screen and fails. 

I still need to test on our Citrix 7.8 environment that we are migrating to, which is running Server 2012R2 to see if the issues occur there. 

What is the expected behavior?
When a weblink is clicked on from Outlook, the expected behavior is that it would open in the browser. 

What went wrong?
The --allow-no-sandbox option is not being passed to Chrome, because Chrome is not the published application - Outlook is. There needs to be a way to disable the sandbox server side either via registry manipulation or group policy (preferred). 

Please note, if Chrome was previously opened either by Published App or a shortcut with the --allow-no-sandbox option enabled, then clicking on the link in Outlook will function properly. If however the browser is closed, then the browser just hangs as the sandbox is on and can't function properly.  A sandbox in Citrix is basically like a sandbox inside a sandbox behind a firewall, which could explain why this is such a big issue for Citrix Administrators. The new Citrix 7.x environment is even more so as there are even more segregation layers. 

Does it occur on multiple sites: Yes

Is it a problem with a plugin? No 

Did this work before? N/A 

Does this work in other browsers? Yes 

Chrome version: 51.0.2704.103  Channel: stable
OS Version: Server 2008R2
Flash Version: Shockwave Flash 22.0 r0

This is a huge deal to us and has a high impact. We have been struggling to get this working and its really frustrating.  I'm willing to work with your engineers and perform testing if required. Don't hesitate to contact me.
 

Deleted: Chrome Fail.JPG 31.0 KB

	Chrome Fail.JPG 31.0 KB View Download