How to configure Chrome on a Terminal Server

This has been included in the stable release of Chrome 5.x as of May 2010. It works similar to Internet Explorer in that "Intranet" URLs (without dots in the address) will attempt single sign-on if requested by the server.

To enable passthrough for other domains, you need to run Chrome with an extra command line parameter:

chrome.exe --auth-server-whitelist="*example.com,*foobar.com,*baz"

Background

According to the Google Issues list for Chromium, this issue was reported in Sep 2008. The NTLM passthrough feature was apparently given to the Google Summer of Code team. It sounds like it will be worked on in Summer 2009 at the Google Summer of Code.

This is good news, and will hopefully bring some stature to Chrome's image in the enterprise. The intranet is so prevalent, and to adopt a browser is difficult without having this feature.

Sure.

Open notepad, and copy/paste the following into the file:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings]
"IEHardenIENoWarn"=dword:00000000

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings\ZoneMap]
"IEHarden"=dword:00000000

Save the file as "IEHardenFix.reg" in a directory that all users have access to. In my case, I used my "Scripts" directory, but the %systemroot%\system32 works too.

Then, modify %systemroot%\system32\usrlogon.cmd. At the end, after the line that contains ":DONE" add a new line that looks like this:

regedit /s "%systemroot%\system32\IEHardenFix.reg"

Save and close the usrlogon.cmd file.

Now, when the users log on, this reg file will be silently imported into their registry, disabling the Enhanced Security Configuration for that user.

Hope this helps,

Glenn