Chrome Terminal Server no sandbox switch

[Wil Martin]

Hello all,

I'm looking for a solution for getting chrome to work as the default browser for all HTM/L applications on a windows 2008 r2 remote desktop environment. Chrome has proven to be unstable installed in it's native form using the offline installer for all users but using the --allow-no-sandbox-switch has proven to drastically improve performance and stability. 

I would like to replace IE completely on the terminal server with chrome for security and performance reasons and have already directed users to launch new web browser instances from chrome shortcuts in the start menu, on the desktop, and on the quicklaunch bar. Unfortunately when clicking links (in email, for example) will launch chrome using the .html default file association which points directly to the chrome executable, which prevents it from launching with the required no sandboxing switch. Is there somewhere I can set the chrome exe to launch with this switch always enabled for all users? Or is there perhaps another method of forcing windows to imply a launch switch on default applications?

Thanks in advance for any advice.

[Isiah Meadows]

Have you tried adding that flag to file associations in the registry? The following hives to check are:

HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\ <-- This is for Explorer associations only
HKCU\SOFTWARE\Classes <-- This is for the current user
HKLM\SOFTWARE\Classes
HKCR

You may have to poke around a little in regedit to find the exact keys you're looking to change, but that should be a little easier once you're actually there looking.

And one thing that is always worth stressing, always back up your registry before you make any changes to it.