<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Tristan Watkins on IT Infrastructure &#187; 401.1 Archive</title>
	<atom:link href="http://tristanwatkins.com/index.php/tag/401-1/feed/" rel="self" type="application/rss+xml" />
	<link>http://tristanwatkins.com</link>
	<description>Technical guidance for SharePoint, Cloud Services, Windows and more</description>
	<lastBuildDate>Fri, 21 Oct 2011 23:33:55 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.4</generator>
		<item>
		<title>Custom STSADM command for BackConnectionHostNames</title>
		<link>http://tristanwatkins.com/index.php/custom-stsadm-command-for-backconnectionhostnames/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=custom-stsadm-command-for-backconnectionhostnames</link>
		<comments>http://tristanwatkins.com/index.php/custom-stsadm-command-for-backconnectionhostnames/#comments</comments>
		<pubDate>Tue, 29 Sep 2009 23:18:57 +0000</pubDate>
		<dc:creator>Tristan Watkins</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[SharePoint]]></category>
		<category><![CDATA[Windows]]></category>
		<category><![CDATA[401.1]]></category>
		<category><![CDATA[BackConnectionHostNames]]></category>
		<category><![CDATA[DisableLoopbackCheck]]></category>
		<category><![CDATA[SharePoint 2007]]></category>
		<category><![CDATA[STSADM]]></category>

		<guid isPermaLink="false">http://tristanwatkins.com/?p=293</guid>
		<description><![CDATA[Gary Lapointe recently released a custom STSADM command for setting the BackConnectionHostNames registry key. The relevant Microsoft KB article recommends specifying each host header with the  BackConnectionHostNames key rather than disabling the loopback check, as this check is a valuable security fix. As Gary Lapointe mentions, Spencer Harbar put together some thorough background information on [...]]]></description>
			<content:encoded><![CDATA[<p>Gary Lapointe recently released <a title="SharePoint Automation" href="http://stsadm.blogspot.com/2009/09/setting-back-connection-host-names-for.html" target="_blank">a custom STSADM command for setting the <em>BackConnectionHostNames</em> registry key</a>. The relevant <a title="KB896861" href="http://support.microsoft.com/kb/896861" target="_blank">Microsoft KB</a> article recommends specifying each host header with the  <em>BackConnectionHostNames</em> key rather than disabling the loopback check, as this check is a valuable security fix. As Gary Lapointe mentions, Spencer Harbar put together some <a title="Harbar.net" href="http://www.harbar.net/archive/2009/07/02/disableloopbackcheck-amp-sharepoint-what-every-admin-and-developer-should-know.aspx" target="_blank">thorough background information</a> on the roots of the fix. Without this command, setup and maintenance can be a bit of a hassle if you have lots of SharePoint applications or lots of Alternate Access Mappings (or if any of this information changes with any regularity). These registry changes need to be made on each web server for any sites with host headers. This includes Central Administration if it&#8217;s not configured on &lt;servername:port&gt;. So this could get quite laborious if the farm is fairly large. The UpdateFarm parameter may be particularly helpful in this regard.</p>
]]></content:encoded>
			<wfw:commentRss>http://tristanwatkins.com/index.php/custom-stsadm-command-for-backconnectionhostnames/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

