Skip to main content

Marwan Tarek's Blog [MVP]

Go Search
Ayman El-Hattab's Blog
Marwan Tarek's Blog
Mohamed Yehia's Blog

SharePoint 4 Arabs - Online SharePoint Training, Video Tutorials and Webcasts in Arabic > Marwan Tarek's Blog [MVP] > Categories
Key Changes between SharePoint 2010 and 2007

SharePoint 2010 Upgrade page highlights key changes in SharePoint 2010 from SharePoint 2007


Concept, term, or feature

New or changed


Pre-upgrade checker


The pre-upgrade checker is an Stsadm command-line operation that you run in an Office SharePoint Server 2007 environment to find any potential issues for upgrade and to review recommendations and best practices.

Unlike the pre-upgrade scan tool (Prescan.exe) that was used when upgrading to Office SharePoint Server 2007, the pre-upgrade checker does not make any changes to your environment. For more information, see Run the pre-upgrade checker (SharePoint Server 2010).

SharePoint Central Administration Web site


The Central Administration Web site has been redesigned with such new available options and functionality as the following:

· The ribbon makes it easier for you to view or change details about a Web application by supplying all the options on the same page. For more information about Web applications, see Web applications management (SharePoint Server 2010).

· Configuration Wizards have been added to make the configuration process easier by guiding you through the steps to configure the server farm. For more information, see Deploy a single server with SQL Server (SharePoint Server 2010).

· You can now perform a backup from the Backup and Restore page. For more information, see Backup (SharePoint Server 2010).

You now use the Central Administration Web site to manage services, instead using a separate administration site.



The ribbon user interface has been introduced to ensure a consistent user experience and to make it easier for you to work with SharePoint sites. The ribbon is contextual so that you only see the options that are relevant to the tasks that you want to perform. The ribbon is also customizable.

Service applications


New services architecture allows you to effectively manage and centralize services. Individual services can be configured independently and third-party companies can add services to the platform. For more information, see Configure services (SharePoint Server 2010).

Master pages


A site owner can now apply branding to their site, independent of other sites, and administrators can specify whether the system pages in the _Layouts folder are rendered by using the site master pages provided by site owners or by default master pages available across the system. Also, it is possible to use Windows PowerShell to specify a customer master page to system error pages, login pages, confirmation pages, and other non-site-specific pages.



SharePoint Server 2010 has changed the way themes work, making them easier to customize. You can import Microsoft PowerPoint 2010 themes directly into SharePoint Server 2010. Additionally, themes can now be applied to all subsites from this interface. For more information, see Plan for using themes (SharePoint Server 2010).

Business Connectivity Services (BCS)


Business Connectivity Services (BCS) builds on the Business Data Catalog functionality available in the previous product version to provide access to external systems from SharePoint-based solutions. BCS supports interacting with external systems using SharePoint lists and Web Parts, and also supports interacting with data from rich Office clients. For more information, see Business Connectivity Services overview (SharePoint Server 2010).

Claims-based authentication


Claims-based authentication is a new, more powerful and flexible authentication model that works with any corporate identity system, including Active Directory Domain Services (AD DS), LDAP-based directories, application-specific databases, and new user-centric identity models such as LiveID. For more information, see Configure forms-based authentication for a claims-based Web application (SharePoint Server 2010).

Throttling and list controls


Throttling and list controls are two new performance controls. Throttling provides a way to control server resources and is designed so that the server can be protected from overload during peak business hours. SharePoint Server 2010 also provides several different settings that will restrict the queries that can be run against a large list. These settings can be configured for each Web application.

SharePoint Designer


SharePoint Server 2010 gives administrators added control over how SharePoint Designer is used in each Web application; for example, administrators control whether site administrators are allowed to customize master pages and layout pages, and whether site administrators can manage the URL structure of their site.

Developer dashboard


This is a new addition to server diagnostics and displays detailed information for each page load and therefore helps troubleshoot performance issues.

Sandboxed solutions


You can now enable site administrators to upload custom user code by using sandboxed solutions. For more information, see Plan for sandboxed solutions (SharePoint Server 2010).


Technorati Tags: ,
How to treat customizations in your environment during upgrade

If you are planning for SharePoint upgrade (2007 –> 2010), you need to identify the customizations deployed on your current SharePoint environment and start planning for the required actions.

Technet article Determine how to handle customizations (SharePoint Foundation 2010) explains types of different customizations and how to handle them during upgrade process.

Customization type


Site templates (.stp files)

Site templates (.stp files) are a deprecated feature in SharePoint Foundation 2010. New site templates in SharePoint Foundation 2010 are saved as .wsp files (solution packages).

A site that was provisioned by using a site template will be upgraded, but you will be unable to create new sites that are based on that template. If you want to be able to create new sites, you can create and deploy a solution package instead. For more information, see Troubleshoot upgrade issues (SharePoint Foundation 2010).

Site definition

Migrate sites to a supported, predefined site definition, then apply custom features by using solution deployment.

You can also continue to use a custom site definition. You do not have to create a new site definition that is based on SharePoint Foundation 2010.

However, if you must perform custom upgrade actions for the definition, you might have to create an upgrade definition file for that site definition. For more information, see Upgrade Definition Files ( on MSDN.

"Fabulous 40" application templates

Microsoft is not creating new versions of these templates. Sites that are based on these templates can be upgraded, but make sure that you test each site before you upgrade the production environment. For more information, see Troubleshoot upgrade issues (SharePoint Foundation 2010).


Evaluate, then redesign or redeploy if necessary.

Workflows and server controls

Depends on the solution. Contact the vendor to find out whether there is an updated solution. If a workflow is compatible with the new version, redeploy.

Event handler

Rewrite and redeploy as a feature.

Managed paths (inclusions/exclusions)

Re-create inclusions for a database attach upgrade. Exclusions are assumed and do not have to be re-created.


Because of the extensive changes to the UI, custom themes that are based on Windows SharePoint Services 3.0 will not work in SharePoint Foundation 2010. Use Visual Upgrade to continue to use the sites in the old user experience until you can create and apply a new theme that is based on SharePoint Foundation 2010.

Toolbar actions

Move to the ribbon (Fluent UI).

Master pages and CSS files

Rework to accommodate the new user experience.


Test to determine whether any actions are required. In some cases, you might have to adjust the scripts to work with the new page model. Verify that it works on an upgraded site, and in both Visual Upgrade modes.

Search provider or security trimmer

Test to determine whether any actions are required.

Web Parts

Test to determine whether any actions are required. You might have to adjust the Web Parts to work with strict XHMTL mode.

If a Web Part is located on a page but not in a Web Part Zone (so that it is, basically, HTML code embedded directly in a page), it will not work if you revert the page to the default template.


Test to determine whether any actions are required. Redesign or adjust code, as needed.

Authentication providers

Test to determine whether any actions are required. Redeploy the provider on a test farm and ensure that it works correctly with claims authentication.