Export (0) Print
Expand All
4 out of 5 rated this helpful - Rate this topic

Changes from Windows SharePoint Services 3.0 to SharePoint Foundation 2010

SharePoint 2010

Published: May 12, 2010

This article describes the features that have been deprecated or removed from Windows SharePoint Services 3.0 to Microsoft SharePoint Foundation 2010. Deprecated features are provided in SharePoint Foundation 2010 for compatibility with previous product versions. These features will be removed in subsequent versions.

In this article:

  • Deprecated features

  • Features removed from SharePoint Foundation 2010

Deprecated features

The following feature is shipped with SharePoint Foundation 2010 but will be removed from subsequent versions.

Stsadm command-line tool

Description: The Stsadm command-line tool has been deprecated.

Reason for change: The Stsadm command-line tool will be superseded by Windows PowerShell 2.0.

Migration path: The Stsadm command-line tool is included to support compatibility with previous product versions. You should use Windows PowerShell 2.0 when performing command-line administrative tasks.

Features removed from SharePoint Foundation 2010

The following features and functionality are no longer available in SharePoint Foundation 2010.

32-bit operating systems

Description: SharePoint Foundation 2010 requires a 64-bit operating system. Running SharePoint Foundation 2010 on 32-bit operating systems is no longer supported.

Reason for change: SharePoint Foundation 2010 has numerous features that benefit from the performance provided by 64-bit operating systems.

Migration path: Install SharePoint Foundation 2010 on 64-bit operating systems.

Side-by-side installation

Description: The ability to perform side-by-side installation of Windows SharePoint Services 3.0 and SharePoint Foundation 2010 on the same server is being removed. This change is related to the removal of support for Gradual upgrade.

Reason for change: Compatibility and performance issues prevent side-by-side installation.

Migration path: Perform upgrade-in-place installation on the same hardware, or perform database attach to a new farm. Use new hardware if both Windows SharePoint Services 3.0 and SharePoint Foundation 2010 versions of a farm must exist at the same time.

For more information, see Perform a database attach upgrade to SharePoint Foundation 2010.

Gradual upgrade

Description: Support for the gradual upgrade feature is being removed as part of the removal of Side-by-side installation.

Reason for change: Compatibility and performance issues prevent side-by-side installation.

Migration path: Use the read-only database capability of Windows SharePoint Services 3.0 with the database attach upgrade capability of SharePoint Foundation 2010 to minimize downtime.

For more information, see Perform a database attach upgrade to SharePoint Foundation 2010.

For long upgrade periods where you must maintain both Windows SharePoint Services 3.0 and SharePoint Foundation 2010 versions of a farm, you can use the alternate access mapping (AAM) URL redirection capability provided in SharePoint Foundation 2010. Upgrades that use AAM URL redirection are performed by using database attach upgrade command-line operations instead of timer job-based events that are scheduled from the user interface (UI).

For more information, see Using AAM URL redirection as part of the upgrade process (SharePoint Foundation 2010) (white paper).

Web discussions

Description: Web discussions enable users to add comments about documents and pages without modifying their actual content. SharePoint Foundation 2010 does not support Web discussions.

Reason for change: This feature was deprecated in Windows SharePoint Services 3.0 because of its low adoption rate. The feature has now been removed from the product.

Migration path: This functionality is no longer available.

SQL Server 2000 data sources

Description: SQL Server 2000 data sources are no longer supported in SharePoint Foundation 2010.

Reason for change: SQL Server 2000 does not fully support many of the newer data features available in SharePoint Foundation 2010.

Migration path: Use data sources that are on Microsoft SQL Server 2005 or Microsoft SQL Server 2008.

ODBC data sources

Description: ODBC data sources are no longer supported in SharePoint Foundation 2010.

Reason for change: Newer and more versatile database connection options have replaced the functionality of ODBC.

Migration path: ODBC is no longer listed as an option for connecting to a data source. Use another data connection type.

Version 3 themes

Description: A theme is a set of colors, fonts, and decorative elements that enable you to quickly change the appearance of a site. The functionality provided in the version 3 themes is not available in the newly designed version 4 themes.

Reason for change: Version 4 themes are redesigned to simplify the process of generating themes. The new architecture is not compatible with the architecture of version 3 themes.

Migration path: Version 3 themes are still supported if the UI mode is kept at version 3. Version 3 themes are not supported in version 4 UI mode.

Web bot software agents

Description: A Web bot software agent is a dynamic object on a Web page that is evaluated when the page is saved or, in some cases, when the page is opened in a Web browser. Search crawlers and indexers are examples of Web bots. Developers can no longer use Web bot entry points and users cannot add Web bots to SharePoint Foundation 2010 sites.

Reason for change: This functionality is replaced by Web Parts.

Migration path: Use Web Parts instead of Web bots.

E-mail enabled groups and Microsoft SharePoint Directory Management service (DMS)

Description: The Microsoft SharePoint Directory Management service (DMS) connects SharePoint sites to an organization's user directory to provide enhanced e-mail features. If a SharePoint farm is using DMS, users cannot enable SharePoint groups to use e-mail.

Reason for change: The type of authentication used in DMS is being replaced with claims authentication.

Migration path: This feature is not available in SharePoint Foundation 2010. Use claims authentication instead.

For more information, see Plan authentication methods (SharePoint Foundation 2010).

Permissions for sub-webs

Description: When you assign a permission level to a parent site, that permission level is inherited by all sub-webs of the parent site by default. In Windows SharePoint Services 3.0, if you wanted a sub-web to have different permissions from its parent, you could edit the inherited permission level definition at the sub-web scope. The result was that you would have two permission levels with the same name but different permissions, depending on their scope. For example, suppose you assigned the Design permission level to a parent site, but you want to change the permissions on a sub-web so that users will not be able to apply style sheets to pages in that sub-web. In Windows SharePoint Services 3.0, you could edit the Design permission level on the sub-web itself, remove the Apply Style Sheets permission, and save the permission level as Design. It would not be possible, just by looking at permission levels, to determine that the sub-web actually had a different set of permissions than its parent site.

Migration path: In SharePoint Foundation 2010, if you want to give different permissions to a sub-web, you must assign a separate permission level to the sub-web. Site collections that are upgraded from Windows SharePoint Services 3.0 and have these unique permission level structures will continue to work. However, the user interface in SharePoint Foundation 2010 does not have a way to edit an inherited permission level at the sub-web scope, so you cannot change them or create new permission level definitions of this type. If you have a specific business need for continuing to use the Windows SharePoint Services 3.0 process, use the SharePoint Foundation 2010 object model.

Internationalized domain names

Description: Although Windows SharePoint Services 3.0 supported internationalized domain names (IDNs), SharePoint Foundation 2010 does not.

Reason for change: Support of internationalized domain names (IDNs) has been deprecated.

Migration path: If you currently use IDNs with Windows SharePoint Services 3.0 and you plan to upgrade or migrate to SharePoint Foundation 2010, you must stop using IDNs, delete all IDN settings, and then set up an environment that does not use IDN before doing so.

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.