<?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: Clone SharePoint (MOSS / WSS) stand-alone developer virtual machine (Rename SharePoint Server)</title>
	<atom:link href="http://code-journey.com/2009/09/15/clone-sharepoint-moss-wss-stand-alone-developer-virtual-machine-rename-sharepoint-server/feed/" rel="self" type="application/rss+xml" />
	<link>http://code-journey.com/2009/09/15/clone-sharepoint-moss-wss-stand-alone-developer-virtual-machine-rename-sharepoint-server/</link>
	<description>Mostly SharePoint</description>
	<lastBuildDate>Thu, 05 Aug 2010 21:12:56 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Code-Journey</title>
		<link>http://code-journey.com/2009/09/15/clone-sharepoint-moss-wss-stand-alone-developer-virtual-machine-rename-sharepoint-server/comment-page-1/#comment-155</link>
		<dc:creator>Code-Journey</dc:creator>
		<pubDate>Thu, 17 Sep 2009 21:03:58 +0000</pubDate>
		<guid isPermaLink="false">http://code-journey.com/?p=453#comment-155</guid>
		<description>Hi there

Yeah sysprepping is definitely also an option. I only ever did a couple of syspreps years ago, so this route seemed more natural for me.

About the SQL server. In my situation I used the build-in database, and nothing had to be done and I never had to the other times around either. Not sure if I ever renamed a VM with fullblown SQL server, but I don&#039;t think it&#039;s supposed to be any different that using the build-in actually.
 If I used a separate SQL database (on another server, and shared between copy server and original server), it would be a different matter. I did that when I &quot;cloned&quot; our production server to make a staging server.

My first attempt was to use same database server, to save the extra SQL license.
The steps for this was:
- Clone machine
- Rename, new sid
- Copy databases
- Offline production databases
- Start up stage server
- Detach production databases using STSADM
- Add stage databases

This did not work. I should have done this:
Clone machine
Rename, new sid
Copy databases
Offline production databases
Start up stage server
Run SharePoint Wizard and create new farm
Create new SSP
Create new web applications with content databases named something like DeleteMe and then go remove them and add the old ones.
Something like that at least.

Or even better
Install a new machine from scratch.
Install SharePoint
Add all solutions
Copy databases
Offline production databases
Start up stage server
Run SharePoint Wizard and create new farm
Create new SSP
Create new web applications with content databases named something like DeleteMe and then go remove them and add the old ones.

I also had major problems with the SharePoint WSS templates for IT manager, Financial Controller etc. that was used, and I did not want to reinstall those. They each use their own database, and it&#039;s hardcoded. I didn&#039;t feel like redoing that and installing them again.
Oh and out backup had not used VSS so all the DLL files were not copied since they were in use when the backup started. How sad. But it made me figure out how to get files out of GAC which inspired a post or 2 :-)</description>
		<content:encoded><![CDATA[<p>Hi there</p>
<p>Yeah sysprepping is definitely also an option. I only ever did a couple of syspreps years ago, so this route seemed more natural for me.</p>
<p>About the SQL server. In my situation I used the build-in database, and nothing had to be done and I never had to the other times around either. Not sure if I ever renamed a VM with fullblown SQL server, but I don&#8217;t think it&#8217;s supposed to be any different that using the build-in actually.<br />
 If I used a separate SQL database (on another server, and shared between copy server and original server), it would be a different matter. I did that when I &#8220;cloned&#8221; our production server to make a staging server.</p>
<p>My first attempt was to use same database server, to save the extra SQL license.<br />
The steps for this was:<br />
- Clone machine<br />
- Rename, new sid<br />
- Copy databases<br />
- Offline production databases<br />
- Start up stage server<br />
- Detach production databases using STSADM<br />
- Add stage databases</p>
<p>This did not work. I should have done this:<br />
Clone machine<br />
Rename, new sid<br />
Copy databases<br />
Offline production databases<br />
Start up stage server<br />
Run SharePoint Wizard and create new farm<br />
Create new SSP<br />
Create new web applications with content databases named something like DeleteMe and then go remove them and add the old ones.<br />
Something like that at least.</p>
<p>Or even better<br />
Install a new machine from scratch.<br />
Install SharePoint<br />
Add all solutions<br />
Copy databases<br />
Offline production databases<br />
Start up stage server<br />
Run SharePoint Wizard and create new farm<br />
Create new SSP<br />
Create new web applications with content databases named something like DeleteMe and then go remove them and add the old ones.</p>
<p>I also had major problems with the SharePoint WSS templates for IT manager, Financial Controller etc. that was used, and I did not want to reinstall those. They each use their own database, and it&#8217;s hardcoded. I didn&#8217;t feel like redoing that and installing them again.<br />
Oh and out backup had not used VSS so all the DLL files were not copied since they were in use when the backup started. How sad. But it made me figure out how to get files out of GAC which inspired a post or 2 <img src='http://code-journey.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Seth</title>
		<link>http://code-journey.com/2009/09/15/clone-sharepoint-moss-wss-stand-alone-developer-virtual-machine-rename-sharepoint-server/comment-page-1/#comment-152</link>
		<dc:creator>Seth</dc:creator>
		<pubDate>Thu, 17 Sep 2009 19:43:21 +0000</pubDate>
		<guid isPermaLink="false">http://code-journey.com/?p=453#comment-152</guid>
		<description>Good post.  Definitely something I have been trying to accomplish.  The only way I knew how to do it in the past was to create a VM, setup batch scripts to finish configuring SharePoint, then sysprep it.  It&#039;s a tedious process, and this gives another option for accomplishing the same thing if you didn&#039;t build the VM yourself.

I have one question.  What about SQL Server?  Don&#039;t you have to drop the database scheme and re-add it once the server has been renamed?  That was something I had to do on my sysprepped machine once the machine name was changed.  Otherwise SQL would throw fits.</description>
		<content:encoded><![CDATA[<p>Good post.  Definitely something I have been trying to accomplish.  The only way I knew how to do it in the past was to create a VM, setup batch scripts to finish configuring SharePoint, then sysprep it.  It&#8217;s a tedious process, and this gives another option for accomplishing the same thing if you didn&#8217;t build the VM yourself.</p>
<p>I have one question.  What about SQL Server?  Don&#8217;t you have to drop the database scheme and re-add it once the server has been renamed?  That was something I had to do on my sysprepped machine once the machine name was changed.  Otherwise SQL would throw fits.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
