Delivering the Chrome browser as a GPU accelerated published application.

The default method for delivering Chrome as a published application via XenApp requires the application to be run with no GPU acceleration. Any customer delivering Chrome as a published application will have used the switches as below:

"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --allow-no-sandbox-job --disable-gpu

For a user to get a GPU accelerated experience in Chrome it should be published with with these switches:

"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --allow-no-sandbox-job --disable-gpu-sandbox

Small changes, but enough to switch from no GPU to a fully accelerated application.

Nice to know – thank you, Jason! Do similar settings hold true for Firefox?

To be honest I’ve not encountered anyone having challenges delivering Firefox, so maybe it just works!

Ressurecting this old thread!

Something we recently discovered with Firefox in a XenApp environment, which may be useful to Tobias and other members.

I did catch that earlier, Jason, and thank you though for cross-posting that information here. It never hurts to experiment and also to have a gut feeling when something just doesn’t look quite right that it needs further investigation. As it turns out, we only run very specific apps via XenApp and GPU passthrough the GRID engines, so we never would have seen this as in our case, no browsers were set to leverage any GPU resources.