<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Migrating Sharepoint site from Windows 2003 server to Windows 2008 server</title>
	<atom:link href="http://blogs.circlesource.com/2009/01/07/migrating-sharepoint-site-from-windows-2003-server-to-windows-2008-server/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.circlesource.com/2009/01/07/migrating-sharepoint-site-from-windows-2003-server-to-windows-2008-server/</link>
	<description>CircleSource Technical Talent ShowCase</description>
	<lastBuildDate>Thu, 25 Feb 2010 15:22:13 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Steve</title>
		<link>http://blogs.circlesource.com/2009/01/07/migrating-sharepoint-site-from-windows-2003-server-to-windows-2008-server/comment-page-1/#comment-72</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Wed, 07 Jan 2009 13:43:27 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.circlesource.com/?p=60#comment-72</guid>
		<description>Your points are basically correct.  However, regarding the movement of content between servers: we always go the &quot;copy-contentdb-path&quot; which essentially means we detach the content db from the old site on the old server and attach it to the new site on the new server (stsadm -o addContentDb).  That saved us lots of trouble in the past.  Yet, your WP issues (domain name stuff) may still be relevant with this approach.

Additionally, you may want to add that in order to install MOSS on a Windows Server 2008 you will have to add IIS6 metabase compatibility before installation.</description>
		<content:encoded><![CDATA[<p>Your points are basically correct.  However, regarding the movement of content between servers: we always go the &#8220;copy-contentdb-path&#8221; which essentially means we detach the content db from the old site on the old server and attach it to the new site on the new server (stsadm -o addContentDb).  That saved us lots of trouble in the past.  Yet, your WP issues (domain name stuff) may still be relevant with this approach.</p>
<p>Additionally, you may want to add that in order to install MOSS on a Windows Server 2008 you will have to add IIS6 metabase compatibility before installation.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
