Friday, June 24, 2011

Upgrade to SharePoint Server 2010 from SharePoint Server 2007


Microsoft claims that migrating from SharePoint 2007 to 2010 is a easy and straightforward, however, I remember when migrating from SharePoint 2003 to 2007 the process was painful and difficult and there were several  incompatible elements that had to be dealt with. You can upgrade your servers or server farm from a previous version of the SharePoint Products to a new version, or you can migrate content into a new SharePoint environment. This page helps you in steps for upgrade as well as perform the upgrade process.

The sample intranet site presented in this article is hosted on Windows Server 2008 R2 64-bit (which is required for SharePoint 2010) with SQL 2008R2 Express 64-bit.

First, let’s look at the SharePoint 2007 site we migrate. For this demonstration I created a simple MOSS 2007 Enterprise environment based on the Collaboration template, which contains some generic web parts we’ll test on SharePoint 2010, Document Center and Search Center. I setup and double checked the search, because I wonder if the migrated SharePoint would be able to use the search database crawled in the previous, 2007 version of SharePoint. Search is an important issue for migrating Sharepoint installations with large amount of data where a full crawl of the content may take weeks.

My Intranet Site in MOSS 2007

Now, install SharePoint Server 2010 right on the existing installation. In the Setup window, we can view the server requirements, installation guide etc. We will skip this part and proceed straight to the Installation.
SharePoint Server 2010 installation screen

First we need to install software prerequisites. We may already have all required components since we are already running MOSS 2007, but to be sure, we’ll go select this option.

The preparation tool window that launches checks our server for the required components, and installs them if needed. The components that will be updated are:
  • Application Server Role and IIS Role
  • SQL Server 2008 Native Client
  • Microsoft “Geneva” Framework Runtime
  • Microsoft Sync Framework Runtime v1.0
  • Microsoft Chart Controls for Microsoft .NET Framework 3.5
  • Microsoft Filter Pack 2.0
  • Microsoft SQL Server 2008 Analysis Services ADOMD.NET
Let’s open the preparation tool. After reading the short tool description and accepting the terms, the preparation tool will start updating the server immediately.
SharePoint Server 2010 Preparation Tool

After succesfull configuration, the summary screen will be displayed and the tool will likely request a  reboot of the system.
Preparation Tool Summary Screen

When Finish button is clicked the system will reboot automatically. After the reboot, the Preparation Tool launches again and finishes the rest of the steps. Now our system is ready to install SharePoint Server 2010, so select that option from the setup pane.

We will be prompted to enter the license key (which is necessary even when Sharepoint 2010 is in Beta):
Product Key window in SharePoint Server 2010 Setup

After the key we have to read and accept licence terms. Next screen advise that MOSS 2007 was detected.
SharePoint Server 2010 Setup Screen – Upgrade Window

As advised in the above screen we need to run the stsadm command now to ensure our intranet can be successfully migrated. Open cmd.exe console in administrator mode.

Start – Cmd.exe in Administrator mode.

Navigate to the MOSS 2007 Bin Directory, which is located by default at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\bin directory.

Cmd Window in the MOSS 2007 bin folder.

Enter stsadm -o preupgradecheck. This command does  not perform any repairs, but \only checks for and reports issues with possible solutions to apply before the migration. As the command executes we will see the output continuously displayed on the screen with different status notifications. In this check, some notifications were “Aborted due to internal error”. We will ignore this for now as the overall check was succesfull.

stsadm preupgradecheck output.

The browser will then open  to display the  html document with the summary of the output and details of every issue. As all components passed the test  we are ready for the migration.

Go back to our SharePoint Server 2010 Setup window and click the Install Now button.
After the installation, we’ll see the final screen where we are informed that we must launch the SharePoint configuration wizard in order to update our content to latest SharePoint version.
SharePoint Server 2010 Installation Summary screen

Click Close to run SharePoint Configuration wizard. If you were expecting a wizard similar to the SharePoint 2007 wizard, you will be disappointed . We have now entirely new environment for Sharepoint 2010 version and hence a new Configuration Wizard.
SharePoint 2010 Configuration Wizard

Click Next, and the below warning will be shown

Warning Window in SharePoint 2010 Configuration Wizard

Click Yes and we will see a new feature of Sharepoint 2010  -  Farm Passphrase.
Farm Security Settings Window

The Farm Passphrase will prevent server administrators from changing any data in  our SharePoint 2010 installation when no password is provided. Administrations won’t be able to use content or configuration databases even if  full database backups are obtained. Enter a password and continue with the configuration.
The next step is the Visual Upgrade.
Visual Upgrade Window

Here we decide the look and feel of the SharePoint site. You can upgrade all your farm to the SharePoint 2010 design right now. However we will not do this in this demonstration in order to be sure that everything will run fine in 2010 before modifying the design. SharePoint Server 2010 allow me to preview the look and feel of sites before switching to the new SharePoint design, so  select “Preserve the look and feel of existing SharePoint sites” option, which will maintain the original SharePoint Server 2007 design.

Next we’ll be presented with a summary screen where we can review our settings and then click Next to start the farm configuration.

SharePoint 2010 Configuration Wizard Summary Window

If everything went fine and without any errors, we’ll see the final screen.

Configuration Wizard Setup Finished Screen

Click finish and review the migrated site:
Our Intranet site on SharePoint 2010

Since we elected to preserve the original SharePoint 2007  design the site looks identical to the site prior to migration (except for the large Give Feedback button)..

We can now preview the new layout. From the Site Actions Menu, select Visual Upgrade.
Site Actions Menu

The configuration window will open, where we can select generic options about the site, such as the title, description, logo and the template.
Site Settings Window

Under the Visual Upgrade option, select “Preview the new SharePoint user interface” which will allow us to view the site in new 2010 design but we still have the ability to revert to the SharePoint 2007 layout if any errors are encountered. Click OK and view the results.

Site Preview of the SharePoint 2010 Design

We can view the new layout and it seems to work as expected. So go back to Visual Upgrade option and finish the migration completely.

Site settings screen – we’ve selected Use the New SharePoint User Interface option.

We are done! As you’ve seen, it is quite simple to migrate a SharePoint 2007 environment to SharePoint 2010. :)

Happy and successful migrations!


Thursday, June 16, 2011

Difference between SharePoint 2010 and MOSS 2007

SP 2010 Vs. MOSS 2007

Look and feel

In SP 2010 look and feel perspective there will be a ribbon where we can have a look and feel like Office 2010 In MOSS 2007 there is no ribbon

Deployment of Web parts

In SharePoint 2010 deploying custom web part is pretty simple i.e. just right click on the solution and click Deploy In MOSS 2007 you need to drag the dll either to bin or GAC

Silverlight Application

In SP 2010 we can create a Silverlight application directly from Visual Studio 2010 In MOSS 2007 we have to create a web part to host Silverlight application

Shared Database & Service Application

In SP 2010 there is no SSP but there is a concept of Service Application like BCS as one service application, Excel Services as another service application, User Profile as separate service application
General idea is that you have an application for each service, rather than one application with lots of service crammed into it
Own database rather than shared database in SP 2010 In MOSS 2007 we have SSP where we can work around with BI,Search Settings, User Profile Import, Excel Services, Info path
In Database also we use to have separate area for SSP stuff

Easy exports/imports between the forms

In SP 2010 we can update existing information In MOSS 2007 through we can just read the information and we can't update the existing services

Improvement in Deployment

In SP 2010 we can Deploy through Farm based and solution based solution in SP 2010 In MOSS 2007 there is no such option

Alerts

In SP 2010 it has been improved in validation and unique values. While creating column itself we have an option "Allow Duplicate values" to Yes or No In MOSS 2007 alerts were sent only through emails but in SP 2010 users can also send alerts to mobile device as SMS message. A New property delivery channel is introduced to indicate, whether the alerts is delivered as Email or an SMS message

Improvements of events

New events for list creation and web creation No List and web events in MOSS 207

Getting Items from the list

In SP 2010 through object model we can fetch multiple list data by LINQ query and object model In MOSS 2007 we can fetch only through object model

Rating

In SP 2010 we can have rating column by default In MOSS 2007 we should install the feature that is available in codeplex to have rating

Key Word Suggestions

In SP 2010 we can have keyword suggestions In MOSS 2007 we don’t have any keyword suggestions

Taxonomy

In SP 2010 we can create Taxonomy by using Managed Metadata service In MOSS 2007 we don’t have taxonomy

Other Features

In SP 2010 we have Power Shell Scripting, JavaScript object model, Chart Web Parts In MOSS 2007 we don’t have Power Shell Scripting, JavaScript object model, Chart Web Parts

Running stsadm command

In SP 2010 we have to go 14 hive path to run stsadm command In MOSS 2007 we have to go 12 hive path to run stsadm command