Reading Time: 6 minutes

 

 

Features
removed from SharePoint Server 2010

 

 

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

 

    • 32-bit operating systems

 

    • Side-by-side installation

 

    • Gradual upgrade

 

    • Office Web Components

 

    • Web discussions

 

    • SQL Server 2000 data sources

 

    • ODBC data sources

 

    • Version 3 themes

 

    • Storage Management page

 

    • Web bot software agents

 

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

 

    • Permissions for sub-webs

 

    • Shared Services Provider (SSP)

 

    • Internationalized domain names

 

    • Site directory template

 

    • News portal template

 

  • Collaboration portal template

32-bit operating
systems

 

SharePoint Server 2010 requires a 64-bit operating system.
Running SharePoint Server 2010 on 32-bit operating systems is no longer
supported.
Reason for change: SharePoint Server 2010 has
numerous features that benefit from the performance provided by 64-bit operating
systems.
Migration path: Install SharePoint Server 2010 on
64-bit operating systems.

 

Side-by-side
installation

 

The ability to perform side-by-side installation of Office
SharePoint Server 2007 and SharePoint Server 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 Office SharePoint Server 2007 and
SharePoint Server 2010 versions of a farm must exist at the same time.

 

Gradual
upgrade

 

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 Office SharePoint Server 2007 with the database attach upgrade
capability of SharePoint Server 2010 to minimize downtime.

For long
upgrade periods where you must maintain both Office SharePoint Server 2007 and
SharePoint Server 2010 versions of a farm, you can use the alternate access
mapping (AAM) URL redirection capability provided in SharePoint Server 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).

Office
Web Components

 

SharePoint Server 2010 no longer supports Office Web
Components (OWC). The PivotChart, PivotTable, and Trend Chart report types are
no longer available as options in the SharePoint Dashboard
Designer.
Reason for change: This is a 2007 Microsoft Office
system feature that is now replaced by the features available in Excel Services
in Microsoft SharePoint Server 2010 in SharePoint Server
2010.
Migration path: In SharePoint Server 2010, use Excel
Services instead of Office Web Components.

 

Web
discussions

 

Web discussions enable users to add comments about documents
and pages without modifying their actual content. SharePoint Server 2010 does
not support Web discussions.
Reason for change: This feature
was deprecated in Office SharePoint Server 2007 because of its low adoption
rate. The feature has now been removed from the product.
Migration path: The
Note Board feature in SharePoint Server 2010 now provides this
functionality.

 

SQL Server 2000
data sources

 

SQL Server 2000 data sources are no longer supported in
SharePoint Server 2010.
Reason for change: SQL Server 2000
does not fully support many of the newer data features available in SharePoint
Server 2010.
Migration path: Use data sources that are on
Microsoft SQL Server 2005 or Microsoft SQL Server 2008.

 

ODBC data
sources

 

ODBC data sources are no longer supported in SharePoint
Server 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

 

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.

 

Storage
Management page

 

The Storage Management (storman.aspx) page is now removed
from the Central Administration Web site.
Reason for change:
This feature can cause dramatic performance issues in a SharePoint farm. Site
administrators who use this feature were often unaware of the performance
slowdown that it was imposing on users.
Migration path: Site
administrators can no longer use this feature.

 

Web bot
software agents

 

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 Server 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)

 

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 Server 2010. Use claims authentication
instead.

Permissions for
sub-webs

 

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
Office SharePoint Server 2007, 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 Office
SharePoint Server 2007, 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 Server 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 Office SharePoint Server 2007 and have these unique
permission level structures will continue to work. However, the user interface
in SharePoint Server 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 Office SharePoint Server 2007 process, use the SharePoint
Server 2010 object model.

 

Shared Services
Provider (SSP)

 

Shared Services Providers (SSPs) do not exist in SharePoint
Server 2010.
Reason for change: Service applications replace
this functionality.
Migration path: Use service applications
for many of the features that were supported and configured in SSPs.

 

Internationalized domain
names

 

Although Microsoft Office SharePoint Server 2007 supported
internationalized domain names (IDNs), SharePoint Server 2010 does
not.
Reason for change: Support of internationalized domain
names (IDNs) has been deprecated.
Migration path: If you currently use IDNs
with Office SharePoint Server 2007 and you plan to upgrade or migrate to
SharePoint Server 2010, you must stop using IDNs, delete all IDN settings, and
then set up an environment that does not use IDN before doing so.

 

Site
directory template

 

This site template is not available as an option in
SharePoint Server 2010.
Reason for change: The functionality
provided in this template is now replaced by Enterprise Content Management (ECM)
solutions.
Migration path: Use the social tagging features
in SharePoint Server 2010 to get much of the functionality provided by the site
directory template. For more information, see Social tagging overview
(SharePoint Server 2010) and Privacy and security implications of social tagging
(SharePoint Server 2010).

 

News portal
template

 

This site template is not available as an option in
SharePoint Server 2010.
Reason for change: The functionality
provided in this template is now replaced by Enterprise Content Management (ECM)
solutions.
Migration path: This template can still be
accessed and used programmatically by developers. It is also still available as
options in the UI if the SharePoint Server 2010 farm is upgraded from Microsoft
Office SharePoint Server 2007. Use the publishing sites template to replace this
template.

 

Collaboration portal template

 

This site template is not available as an option in
SharePoint Server 2010.
Reason for change: The functionality
provided in this template is now replaced by Enterprise Content Management (ECM)
solutions.
Migration path: This template can still be
accessed and used programmatically by developers. It is also still available in
the UI if the SharePoint Server 2010 farm is upgraded from Office SharePoint
Server 2007. Use the publishing sites template to replace this template.