SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am having a helluva time with this one.

I am attempting to migrate a 5 year old VM running Windows 2003 Windows Sharepoint Services 3.0 that was deployed as a standalone (thus to MSEE) to a Windows 2008 R2 x64 WSS3 implementation with SQL Server Standard 2008R2.

I was successful in getting the 14GB content DB moved over so now the standalone Win2k3 farm has its content DB on the 2008 machine (yay!).

However trying to get the config db & admincontent DB over has been troublesome. I have looked and followed the technet articles but seem to have no luck in resolving issues.

Is it best just to roll out a new farm and hook the new configuration into the old content DB or do I continue to try to preserve the configuration in the config DB & admin content DB (there aren't many customizations in my opinion).

share|improve this question

I'd just build a new farm on the new machine, add solutions and then add the content database.

You might need SPSolutionExtractor

share|improve this answer

I would strongly recomand you build your own MOSS 2007 server farm and go through a series of database attach/upgrade (i mean SharePoint 2007 attach to an existing farm, and it will force an upgrade).

Before that, make sure you identified all customizations, 3rd party developments, etc.

share|improve this answer
Missed the WSS 3.0 - updated. – Marius Constantinescu - MVP May 17 '12 at 8:09

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.