Tuesday, October 4, 2011

Migration from MOSS 2007 to SharePoint 2010


System Requirements

è For migration from MOSS 2007 to SharePoint 2010 the minimum requirement is WSS SP2 and Office Server SP2 must be installed in the MOSS 2007 server. So before upgrade the content database make sure both the things are installed in the source server

Preupgrade check

è Preupgradecheck command will let us know about the things that may restrict us to upgrade the database in SharePoint 2010 server. Before upgradation we need to fixed up all the steps which are failed in the preupgradecheck.


Backup Content Database of MOSS 2007 site

è Before start taking backup of the database first go to the Manage Content Databases section in the Central Administration site and check the name of the database attach to your site.

Central AdministrationàApplication Management->Manage Content databases


è Open SQL Server right click on the databaseàTasksàBack Up

è Click on Add button and browse to the path where you want to copy the backup file





Move the database to destination server

è Move the backed up database to your destination database server and restore it SQL server

Restoring Content Database

è Open SQL Server right click on Database à Restore database

è Specify a database name for restoring the database. If the specified database name is exist in the list of databases then your backed up database will overwrite it else it will create a new database and restore over it.





è Go to the Options page and check the Overwrite the existing database checkbox



Create a blank site in destination server

è For creating blank site in SharePoint 2010, open the Central Administration site and click on Manage web application link in the Application Management group.

Central AdministrationàApplication ManagementàManage web applications


è Click on New link from the top left corner of the page

è Enter the details of the site



è Make the site Configurable and give the Service Account for it

è After the Web Application is created click on Create Site Collection link for creating a blank site collection for the Web Application


è Give service account for Primary Site Collection Administrator


Detaching Content Database

è After the site get created go to Manage Content Database section and detach the database attached with the blank site

è Central AdministrationàApplication ManagementàManage content databases

è


Click on the database


è Check the Remove content database check box and click OK for the warning message


è Click OK button and remove it

Upgrading and Attaching Content Database

è After detaching the database attached with the blank site, our next step is to upgrade the MOSS 2007 site content Database restored in SQL Server and attach it to our blank site using PowerShell command prompt

è Run PowerShell with Administrator privilege


è Test –SPContentDatabase –Name [Database Name] –WebApplication [Web Application Name]

è The above command will check the database for any references are missing in the destination server [i.e Custom Feature, Custom Webpart, Custom Site Definition etc].If any of the components are missing then deploy those to the destination server .Basically the custom components do not restrict the upgradation of the database, you can deploy this after upgradation too but it’s a good practice to deploy it before upgradation of the database.


è Mount –SPContentDatabase –Name [Database Name] –WebApplication [Web Application name]

è The above command will upgrade the database and attach with the site collection of the specified web application


Deploying EasyTabParts webpart

Add solution Farm Solutions

Open command prompt and go to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN folder and run the command stsadm –o addsolution –filename C:\EasyTabParts.wsp

[I have store the EastTabParts.wsp file in C drive, if you have stored it in other location then specify the path instead of C:\EasyTabParts.wsp]


Deploy Solution

Open Central Administration site and go to Manage Farm Solutions page

Central AdministrationàSystem SettingsàManage Farm Solutions


Click on Deploy Solutions link and deploy the solution to your site


Search Configuration



Give a name for the Search Application

Search service account should be your service account

Give an Application pool name for Search Admin Web Service


The Application pool for Search Admin Web Service should be configurable with service account

Give an Application pool name for Search Query and Site Settings web Service

The application pool for Search Query and Site settings web Service should be configurable with service account


àClick OK to create the search Service


Click on Search Service Application MC and then click on Content Source from the left navigation bar


Edit the Content Source and map your site


Make sure the URL is your site collection URL

àSchedule your content source both for Full Crawl and Incremental Crawl as per requirement and check the start full crawl of the content source check box for crawl the content source

Check the crawl log once full crawl is completed

è Click on Central AdministrationàApplication ManagementàConfigure Service Application Associations


àClick on your site


è Change the Edit the Following group of connections to custom


è Choose the proper search service application and click ok


IIS Settings for running .exe files

Open Internet Information Service(IIS)

Click on your site from the list of sites

Double click on Handler Mapping

Click on Edit Feature Permissions, uncheck Execute checkbox and click OK to save the change