.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
david stephan
Gaurav Pal
Post New Web Links

SharePoint 2007 to 2010 Upgrade AND Farm Merge

Posted By:      Posted Date: September 20, 2010    Points: 0   Category :SharePoint

Hello all,

I'm curious to see if anyone has done this.  Currently, my environment has 3 seperate SharePoint 2007 server farms.  I'm currently evaluating SharePoint 2010 and so far like what I see.  I'm wondering though what would be the steps I would need to go through to actually upgrade and then merge them all to one SharePoint 2010 farm?  The steps I can think of are the following:

1. Make sure all 2007 farms are on the lastest (or at least similar) version

2. Upgrade each farm to SharePoint 2010

3. Create new 2010 farm

4. Copy upgraded farms' site collections to NEW 2010 farm.

OR can I do this:

1. Make sure all 2007 farms are on the same version

2. Create a copy of each current SharePoint 2007 site collection that I want

3. Create NEW 2007 Farm

4. Copy content to new farm

5. Upgrade new farm to 2010


Any and all help would be greatly appreciated, thanks!


View Complete Post

More Related Resource Links

Cannot crawl sharepoint site and mysite after database attach upgrade form sharepoint 2007 to 2010.

After database attach upgrade site and mysite from sharepoint 2007 to 2010 , I have full crawl and get "The crawler could not communicate with the server. Check that the server is available and that the firewall access is configured correctly. If the repository was temporarily unavailable, an incremental crawl will fix this error. ( Error from SharePoint site: HttpStatusCode ServiceUnavailable The request failed with HTTP status 503: Service Unavailable. )" for mysite and get "Access is denied. Verify that either the Default Content Access Account has access to this repository, or add a crawl rule to crawl this repository. If the repository being crawled is a SharePoint repository, verify that the account you are using has "Full Read" permissions on the SharePoint Web Application being crawled." for sharepoint site. The content access account for search is "db_owner" of both of site and mysite. How do I solved this problem ?

MOSS 2007 upgrade to Sharepoint 2010 across domains

I recently did an upgrade at a customer site. I migrated their content successfully as well as their Mysites. Their MOSS farm was situated on a domain, let's say "domain 1". Due to a merger, their domain had to change to "Domain 2". The Sharepoint 2010  farm was set up on new domain. We now need to change the existing user logins from the upgraded content db to the new domain. domain1\user to Doamin2\user.  We considered a manual process, but it is simply not a viable option. Furthermore, the migrated mysites works fine, but the problem is, the users need to login with their old login details to view the content. Which is unacceptable. The mysite content now needs to be associated with the users on the new domain. Bear in mind that the users already have logins and permissions as per the previous configuration (domain1\user) I consideredd using the stsadm migrate user command, but that could also be laborious. The other concern is the SID associated to each login. I am not sure if the -ignoresidhistory switch will help, or if this command is even usable in SP 2010. I there possibly another, more effective method to accomplish these tasks, say a Powershell script or a magic wand?   Regards,   Warren  

Upgrade from MOSS 2007 Trial to Sharepoint Server 2010

I have a client who setup MOSS 2007 Trial and are coming up on the expiration.  Instead of buying a key for MOSS 2007 they purchased Sharepoint 2010.  I'm having some problems upgrading because its the trial.  What are my options for upgrading/migrating over to Sharepoitn 2010?

MOSS 2007 to SharePoint Server 2010 Hybrid Upgrade Approach on Windows Server 2003 x64

There's some guidance circulating about upgrading to 2010 with a mix of In-Place and Database Attach upgrade methods. My Central Admin and SharePoint Web App are on a 64 bit server, but it's running on Windows server 2003 x64 and not on Windows Server 2008 or 2008 R2. SharePoint Team Blog says Server 2008 or 2008 R2 is required for SP2010. If I want to do the hybrid upgrade approach, is it possible to first upgrade the OS to Server 2008 R2 on the server where my Central Admin and SP Web App runs?  Or will this break MOSS 2007?

SharePoint 2007 upgrade to 2010 without UI update masterpage issue

I have a public facing site on a SharePoint 2007 farm that will be upgraded to 2010.  This site has a very customized look and feel that will not initially be updated to the 2010 UI.    I have run into one small issue with 2010's handling of legacy 2007 UIs.In SharePoint 2007,  to have a different master page for the application pages and dialog boxes we utilized an HTTP Module to switch the master page on the fly.    After migrating the SP2007 into our 2010 beta test environment the HTTP Module no longer worked properly.   I did some debugging and found out that SharePoint 2010 is returning a NULL value for MasterPageFile property on the pages in the _layouts folder.   I would have expected to see the URL pointing to the application.master page (or dialog.master).   Any ideas if this is a bug in SP2010 beta and will be fixed in RTM or is this the intended behavior.If it is the intended behavior in SP2010 how could I update my HTTP Module to allow the site to continue functioning as it did on 2007?   

How to upgrade MOSS 2007 custom site definitions to SharePoint 2010?

I would like to know how to upgrade custom site definitions of MOSS 2007 to SharePoint 2010 in detail?

Looking for guidance: Integrated SharePoint SSRS migration and upgrade from 2007 to 2010


Our existing prod farm is MOSS 07 with an integrated SSRS instance using SQL Server 2008, both on Windows Server 2003 64bit boxes. SharePoint databases are on a different SQL Server 2008 server.

I have built a new SharePoint 2010 farm on Windows Server 2008 R2 boxes, using a single SQL Server 2008 R2 Enterprise server as the backend for both SharePoint databases and Reporting Services (installed in Integrated mode). We are going to be using the database-attach method of upgrading our SharePoint farm.

Is there any specific guidance out there on exactly how to migrate/upgrade Reporting Services in this scenario? I've read through some of the MSDN content (How To: Migrate a Reporting Services Installation) but nothing seems to deal specifically with doing this when in Integrated mode with SharePoint. Our business heavily relies on SSRS reports in SharePoint and also shared and custom report subscriptions via email.

We do have a dev SharePoint 2010 farm in a similar configuration that I can test migration/upgrade steps. Thanks.

MOSS 2007 to SharePoint 2010 Upgrade Fails - Object with Id 57bdacb5-31fe-4f4c-bdb3-3caf048474bd and


Ok apart from deleting these Classes and Objects what else can be done. Any one know a way around. Just to help you find them if you have a similar error look in the Classes and Objects Tables in the Offending database listed in the error message. In this error message below it is SharePoint_Config. How I found them,  yes its like looking for a needle in a hey stack see this post, very handly sql query.

I have a copy of a VM I can create again so I am going to try deleting these and if this works I will Answer my own post. This of course is unsupported and purely a hack hence why I am posting searching for enlightenment. Of course I have other errors so this may merely negate the first one.



[psconfigui] [SPConfigurationDatabaseSequence2] [INFO] [9/30/2010 3:44:42 PM]: SPConfigurationDatabase Name=SharePoint_Config
[psconfigui] [SPConfigurationDatabaseSequence2] [WARNING] [9/30/2010 3:44:42 PM]: Object with Id 57bdacb5-31fe-4f4c-bdb3-3caf048474bd and class id 92e1ba91-03dc-4d85-8978-8c6224d84d5e could not be deserialized. Most likely its type is no longer a sub class of SPPersistedObject.
[OWSTIMER] [UserProfileApplicationSequence] [INFO] [9/30/20

MOSS 2007 to SharePoint 2010 Upgrade Fails - Exception: The user or group 'wsaarole:wsaa administra


Ok the top part of the error I have tracked down to some entries in the SharePoint_Config database (Classes, Objects, TimerRunningJobs) and since I have a VM I am going to study them and try deleting them probably, if it dies I will delete this VM and roll up another VM in my case its a timer job that I am guessing the farm can live without.

The other error further down is more of a concern to me which is the one I listed above. The Group exists and it is in the farm and appears to be healthy no errors in preugrade check or the like or in the Farm. When upgrading the show stopper for me is that the content databases will not upgrade (assuming they upgrade FBA I can configure) the chicken and egg issue for me is this is an FBA farm, so is it the case that b/c FBA is missing not configured yet on the other side of the upgrade in 2010 that these content dbs connected to FBA (by FBA users in the content dbs) will upgrade affter FBA is configured ( I haven't tried this yet sorting my error log one error at a time). The Particular content dbs with an issue are shared services and the main site collection db which includes my sites site collections also.

[psconfigui] [SPConfigurationDatabaseSequence2] [INFO] [9/30/2010 3:44:42 PM]: SPConfigurationDatabase Name=SharePoint_Config
[psconfigui] [SPConfigurationDatabaseSequence2] [WARNING] [9/

After SharePoint 2007 upgrade to SharePoint 2010 issue with custom site(s)


With our 2007 site(s) we had a custom module (we developed) to swap out the application.master with our own master page which resembled the site default.master.  This worked great.

After the upgrade, out site's main pages looked fine however when navigating to the admin type pages (settings/viewlists etc.) pages the module stopped working.

1.) I have figured out something things with respect to what is going on but am still at a loss to how best resolve.  We want the layouts/admin pages to have the same master page as the main user pages.   I have read in 2010 this is now possible.  How can I achieve this?


2.) Currently, when navigating to the sites/settings page the site is using template/layouts/layoutsv3.master as the master page.  The settings.aspx page has DynamicMasterPageFile="~masterurl/default.master" .  It was my understanding that when DynamicMasterPageFile was set to default.master it would use the master page from the site.  So, with that said I am confused why it is using layoutsv3.master

any help would be appreciated



Upgrade from MOSS 2007 to SharePoint Server 2010 but with a catch...


... and the catch is that the MOSS 2007 Site Collection is contained in the SharePoint Central Administration v3 Web Application and therefore the SharePoint_AdminContent_... database which is used by Central Administration (not my doing btw).  Please let me know how to copy it to a new 2010 server farm and then upgrade just our sites and content while removing all of the 2007 Central Administration stuff.



Upgrade/Migrate MOSS 2007 Wiki to SharePoint 2010 Enterprise Wiki


We've been running MOSS 2007 for a few years now and have built up a Wiki.


I am now investigating the migration to SharePoint 2010, I've used the database attach method to copy across our Intranet site collection to a development SharePoint 2010 install (this includes our Wiki).


This works except for an error under the "Recent Changes" heading and the new 2010 Enterprise Wiki features are not available.


What I'm trying to find out is if there is a way to either upgrade the Wiki sub-site or migrate the Wiki data into a new 2010 Wiki sub-site that I can swap for the live one.


I've tried to just copy the items from the "Wiki Pages" list of the imported sub-site to the "Pages" list of a new 2010 Wiki sub-site, but they then just appear as "ASP.Net pages" and don't display the Wiki content.

I've also tried a couple of the commercial migration tools but these also just seem to copy the aspx files and leave them not viewable.


Thanks in advance


In Place Upgrade from SharePoint 2007 to SharePoint 2010


I have a client that is trying to do an In place upgrade 2007 to 2010 and has received a failed report. Any suggestions?

[psconfigui] [SPConfigurationDatabaseSequence2] [INFO] [7/12/2010 1:27:17 PM]: SPConfigurationDatabase Name=SharePoint_Config
[psconfigui] [SPConfigurationDatabaseSequence2] [WARNING] [7/12/2010 1:27:17 PM]: Object with Id 72e2b269-2d72-4c93-bfc2-93682d55c361 and class id 92e1ba91-03dc-4d85-8978-8c6224d84d5e could not be deserialized. Most likely its type is no longer a sub class of SPPersistedObject.
[psconfigui] [SPConfigurationDatabaseSequence2] [INFO] [7/12/2010 1:27:23 PM]: SPConfigurationDatabase Name=SharePoint_Config
[psconfigui] [SPConfigurationDatabaseSequence2] [WARNING] [7/12/2010 1:27:23 PM]: Object with Id 7632ab71-7414-4b79-a305-2ad5cd3496d1 and class id 92e1ba91-03dc-4d85-8978-8c6224d84d5e could not be deserialized. Most likely its type is no longer a sub class of SPPersistedObject.
[psconfigui] [SPConfigurationDatabaseSequence2] [INFO] [7/12/2010 1:27:26 PM]: SPConfigurationDatabase Name=SharePoint_Config
[psconfigui] [SPConfigurationDatabaseSequence2] [WARNING] [7/12/2010 1:27:26 PM]: Object with Id 81793d13-fa7a-4d48-bf43-0457a79cd714 and class id 92e1ba91-03dc-4d85-8978-8c6224d84d5e could not be deserialized. Most likely its type is no longer a sub class of SPPersistedObject.
[psconfigui] [SPConfi

In place upgrade from Moss 2007 to SharePoint 2010


Having successfully run through stsadm -o preupgradecheck without having any issues highlighted to me, I believed I was now in a position to upgrade my Development Farm (single server Farm)......WRONG! From blogging, I have seen others suffer the same fate as me, has anyone got any advice/fixes for the following error log:


[psconfigui] [SPConfigurationDatabaseSequence2] [INFO] [8/4/2010 12:29:23 PM]: SPConfigurationDatabase Name=SP2010_SharePoint_Config
[psconfigui] [SPConfigurationDatabaseSequence2] [WARNING] [8/4/2010 12:29:23 PM]: Object with Id 873adcc7-97b6-4f40-a2d6-25e7ab360a53 and class id 92e1ba91-03dc-4d85-8978-8c6224d84d5e could not be deserialized. Most likely its type is no longer a sub class of SPPersistedObject.
[psconfigui] [SPConfigurationDatabaseSequence2] [INFO] [8/4/2010 12:29:26 PM]: SPConfigurationDatabase Name=SP2010_SharePoint_Config
[psconfigui] [SPConfigurationDatabaseSequence2] [WARNING] [8/4/2010 12:29:26 PM]: Object with Id 524b79a8-8e70-4066-9975-2a94617dda64 and class id 92e1ba91-03dc-4d85-8978-8c6224d84d5e could not be deserialized. Most likely its type is no longer a sub class of SPPersistedObject.
[psconfigui] [SPConfigurationDatabaseSequence2] [INFO] [8/4/2010 12:29:51 PM]: SPConfigurationDatabase Name=SP2010_SharePoint_Config
[psconfigui] [SPConfigurationDatabaseSequence2] [WARNING] [8/4/201

How to upgrade MOSS 2007 custom site definitions to SharePoint 2010?

I would like to know how to upgrade custom site definitions of MOSS 2007 to SharePoint 2010 in detail?

SharePoint Designer 2007 upgrade to 2010

I currently use SPD 2007 for my website editing and uploading, looking to upgrade to 2010 and I'm fearful that you cant really use the new product for uploading a website and editing it.  Any suggestions on what product I would be using now?

SharePoint 2007-2010 content upgrade, Summary Links web part closed after upgrade.


Has anyone seen this before?

Did a DB content upgrade from SharePoint 2007 to 2010.  After the content upgrade (with only a warning saying that an unknown 3rd party web part was missing), we reviewed the new site, and found MANY pages which contained Summary Links web parts suddenly had many (but not ALL) of the Summary Links web parts now marked as closed.  At first we thought the parts were missing from the page, but when we edit the page we see the parts are in the Closed gallery.  We can add the part back in from the Closed gallery and all it's originally set properties are there.  Why are they coming up as Closed after the upgrade when they weren't Closed BEFORE the upgrade?

More details:

We have quite a few pages that contain one or more Summary Links web parts.  On SOME of the pages, one or more of these web parts are now Closed.  However, not ALL of the pages that contain these parts have the parts closed, and on the pages that now have these closed parts, not ALL of the Summary Links parts on that page are Closed, so it is not a problem with an unregistered Summary Links web part as the part is working on the same and other pages (I found other people on the web mentioning issues where NONE of their Summary Links parts are working after an upgrade.)  So, it seems to be somewhat random as to which instance

ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend