Today if one needs to run Chrome in Citrix or Terminal Services running on Windows Server 2008 R2 as a published app they need to run it with the --allow-no-sanbox-job flag.

This flag makes allows the sandbox to start without creating a Job around its children processes because the rdp host process creates one itself and Windows 2008 does not support nested jobs. 

Currently we check if the flag is set and we are on the affected Windows version and skip the job creation. Instead the proposal is to always attempt the job creation. If it fails we check if we are on Windows Server 2008 R2 and maybe whether we are running in a TS session (if feasible) and then ignore the error if the condition is met.

The reson behind this change is to simplify the deployment of Chrome for remote sessions and to fix issues where Chrome is invoked through file/protocol associations which don't set the required flags on the browser.