Export (0) Print
Expand All
ABS
AND
ASC
COS
DAY
DDB
EXP
FV
IF
INT
LEN
LN
LOG
MAX
Me
MID
MIN
MOD
NOT
IS
NPV
ODD
OR
PI
PMT
PV
SIN
SLN
SUM
SYD
T
TAN
VAR
Expand Minimize
This topic has not yet been rated - Rate this topic

Upgrade Considerations

Archived content. No warranty is made as to technical accuracy. Content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

There are two stages in upgrading from from Microsoft orFrontPage 2002 Server Extensions from Microsoft to Microsoft :

  • First, you back up your existing Web sites using the Microsoft SharePoint Migration Tool and remove or FrontPage 2002 Server Extensions from the virtual servers.

  • Second, you install on your server computer or to a new server, and restore your Web sites to new locations on the existing server, or to the same locations on a new server.

There is no "upgrade in place" method for upgrading your server or your sites. Because requires Internet Information Services (IIS) to be in IIS 6.0 worker process isolation mode and and FrontPage 2002 Server Extensions work in IIS 5.0 isolation mode, you cannot run both the old applications and at the same time. Your sites are likewise always upgraded by way of migration.

You can also choose to upgrade your database from Microsoft SQL Server 2000 Desktop Engine (Windows) (WMSDE) to Microsoft SQL Server, if you find you need more database features or more storage capacity than are provided with WMSDE.

Considerations for Upgrading a Server from to

If you want to upgrade a server from or FrontPage 2002 Server Extensions to , consider the following changes:

  • The architecture has changed considerably. For example, you can now use in a server farm configuration. Also, all site content is now stored in the content databases instead of on the file system, and configuration data for a server or server farm is stored in the configuration database. For more information about the new architecture, see Windows SharePoint Services Architecture .

  • The security model has changed. For example, you can now grant administration rights to a specific domain group, in addition to the server's local administrators group. For more information about the new security model, see Windows SharePoint Services Architecture .

  • There are many new features, some changed features, and some features that no longer exist.

    t in the new version. For more information about features included in , see Introducing Windows SharePoint Services .

In addition to these general changes, several specific issues should be considered when you upgrade your server to . The following sections describe these areas and help you manage the upgrade process.

Upgrading from on Windows 2000 Server to on

requires that you be running Microsoft . If you are running on Windows 2000 Server, you must upgrade your server to and then upgrade to . To upgrade successfully, you must perform the following steps:

  1. Use the SharePoint Migration Tool (smigrate.exe) to back up the Web sites. For more information about backing up Web sites, see Migrating and Upgrading Web Sites .

    Note: Before you can use the SharePoint Migration Tool to migrate sites from to , you must verify that you are running the update to that updates it to function better with the SharePoint Migration Tool. To download this update, go to Office XP Web Services Security Patch: KB812708 .

  2. Remove . For more information about removing , see the SharePoint Team Services Administrator's Guide on the Microsoft TechNet Web site.

    Note: When you uninstall , some content may be left on the file system in the virtual server directory. In , all content is stored in the content databases, rather than on the file system, and so you no longer need this content. Because you have already backed up the Web sites, you can delete this content from the file system after you uninstall , and before you install . After you install you can restore the Web sites, and the content will be added to the content database.

  3. Upgrade your server computer to , Standard, Enterprise, Datacenter, or Web Edition. For more information about upgrading to , see the documentation.

    Note: When you upgrade from Windows 2000 Server to , the FrontPage 2002 Server Extensions are automatically installed. If you do not need FrontPage 2002 Server Extensions, it is recommended that you remove them (from the virtual server, and from your computer) before you install . If you want to run both FrontPage 2002 Server Extensions and , you must first remove in FrontPage 2002 Server Extensions from the default Web site before installing . If the default site contains information that you wish to preserve, use the SharePoint Migration Tool to back up the data before removing FrontPage 2002 Server Extensions. See Migrating and Upgrading Web Sites for more information.

  4. Install and enable ASP.NET. For more information about installing ASP.NET, see the documentation.

  5. Enable IIS and set it to run in IIS 6.0 worker process isolation mode, and then install . For more information, see Installation Considerations for Windows SharePoint Services , or one of the following deployment scenarios:

  6. Use the SharePoint Migration Tool to restore the backed up Web sites.

FrontPage 2002 Server Extensions Considerations

You cannot upgrade in place from FrontPage 2002 Server Extensions to . To upgrade successfully, you must perform the following steps:

  1. Use the SharePoint Migration Tool to back up the Web sites based on FrontPage 2002 Server Extensions. For more information about backing up Web sites, see Migrating and Upgrading Web Sites .

  2. Remove FrontPage 2002 Server Extensions. For more information, see the SharePoint Team Services Administrator's Guide on the Microsoft TechNet Web site.

  3. Install and enable ASP.NET. For more information about installing ASP.NET, see the documentation.

  4. Enable IIS and set it to run in IIS 6.0 worker process isolation mode, and then install . For more information, see Installation Considerations for Windows SharePoint Services , or one of the following deployment scenarios:

  5. Use the SharePoint Migration Tool to restore the backed up Web sites.

Note that certain features from FrontPage 2002 Server Extensions, such as using ASP pages in a Web site and linking to a database file (such as an .MDB file) to display dynamic database content on a Web page, are not supported in and do not work in any Web sites you migrate to the new technology.

Role and Right Considerations

Note: RolesToGroupsNote

Because the site group names and definitions changed between and , the default site groups for your user accounts change when you upgrade. The new site group assignments attempt to preserve the meaning of the previous roles. The following table lists the roles in and the new site group assignments that take effect when you upgrade to.

role name

site group membership after upgrade

Administrator

Administrator

Advanced Author

Web Designer

Author

Contributor

Contributor

Reader

Browser

Reader

If you have a custom role that you created in , a site group with the same name is created, and the rights that correspond to the rights are assigned to the site group when you upgrade. In some cases, because of changes to how works, there is no corresponding right. The following table lists the rights mapping between and .

right name

right

Author Lists

Add Items, Edit Items, and Delete Items

Author Pages

View Items, Add Items

Author Web Document Discussions

View Pages

Border Web

Apply Themes and Borders

Browse

View Pages

Close Web Document Discussions

View Pages

Configure Access

Manage Site Groups

Create Accounts

N/A

Design Lists

Manage Lists

Link Style Sheets

Apply Style Sheets

Manage Lists

Manage Lists

Manage Server Health

N/A

Manage Subweb

Create Subsites

Manage Usage Analysis

View Usage Data

Manage Web Document Discussions

N/A

Manage Web Subscriptions

N/A

Recalc Web

N/A

Set Source Control

N/A

Subscribe To Document

View Items

Theme Web

Apply Themes and Borders

View Lists

View Items

View Web Document Discussions

View Pages

For a complete list of the rights and site groups available in , see User Rights and Site Groups .

Considerations for Migrating Sites from to

You use the SharePoint Migration Tool to migrate sites from to . The site migration process is optimized for use with standard team Web sites. This means that many types of customizations do not migrate properly or do not work in a migrated site. Also, because the feature set and architecture have changed significantly between or FrontPage 2002 Server Extensions and , several features that you could use in these environments do not work in .

Note: Before you can use the SharePoint Migration Tool to migrate sites from to , you must verify that you are running the update to that updates to function better with the SharePoint Migration Tool. To download this update, go to Office XP Web Services Security Patch: KB812708 .

The customizations and features that do not migrate include, but are not limited to, the following items:

Type of customization or feature

Explanation of migration issues

Customized home pages

Home pages customized by using a -compatible Web page editor such as Microsoft revert to the standard team Web site home page. Home pages customized in the browser retain their customizations, including views that were added and changes that were made to the Quick Launch bar.

Note: When you migrate a site, the default.htm home page is replaced with a new page. The original default.htm page is renamed as default_old.htm.

Customized view and form pages

Most view and form pages customized by using a -compatible Web page editor such as Microsoft revert to standard view and form pages. However, views created with other applications or that include settings not available in the browser interface will not migrate.

Customized link bars

Link bars, such as the top link bar, that were customized using a -compatible Web page editor such as revert to the standard link bars.

Custom script files executed on the server

By default, the ISAPI filter for blocks the use of any script files (such as ASP pages) that are executed on the server and are not part of the installation. If you want to use custom script files with your SharePoint sites, you must put the script files in a separate virtual directory, and create an excluded path for the directory in . This allows IIS to control the directory, rather than , and allows the ASP pages to run. Note that script files running on the client are not blocked. For more information about creating an excluded path, see Managing Paths . For more information about ASP pages in , see Windows SharePoint Services Architecture . To prevent script files from being included during migration, either add those file extensions to the blocked files list in the destination Windows SharePoint Services site, or remove those files from your SharePoint Team Services site before migrating. See Migrating and Upgrading Web Sites .

Caution: Custom script files that are not being executed on the server can be browsed by users with read access to the folder where they are stored on the server. Browsing the files can allow users to discover information such as user names and passwords contained in the script files, as well as network paths.

Custom pages that link to SharePoint lists

The SharePoint Migration Tool does not include an automatic link fixup tool. After migration, any links that you have created to point to specific lists are broken. You can update the links to refer to the current list location after migration.

Note: If you have a link to a subsite, that link remains, but any links to parent Web sites or other Web sites at the same level do not work.

Customizations based on CAML

Customizations made to your site by using the Collaborative Application Markup Language (CAML) are not migrated. You must re-create these customizations. For more information about customizing SharePoint sites programmatically, see the .

Files or folders with trailing spaces

Trailing spaces at the very end of a filename ("filename.doc ") are not supported in . You must change the file name and then add the file manually to your site.

Unsupported characters

The following characters are not supported in :

/\:*?"<>|#{}%&~ or tab characters and multiple periods.

If a file, folder, or URL name in your original site contains one of these characters, it is replaced with an underscore (_). Multiple periods are replaced with a single period. Additional digits may be appended to the file or folder name if there are conflicting renaming changes.

Files with file extensions that are blocked in

A new feature allows server administrators to control whether specific file types can be uploaded or downloaded to the server. If a file in your site uses one of these file extensions (for example, .exe), the file are not migrated to the new site. If you know that certain file extensions are in a site you want to migrate, you can temporarily remove those file extensions from the list of blocked file extensions while you migrate the site. For more information about blocked file extensions, see Configuring Blocked File Extensions .

Long file and folder names (more than 255 characters)

File and folder names longer than 255 characters are not supported in . You can rename files or folders that have long names before migrating a site, or rename them after migration and add them manually to the new site.

Lists with too many fields or columns

Lists in can only contain a certain number of fields or columns. If a list in your site contains too many fields or columns, it are not migrated. You must manually re-create the list. Note that this includes surveys. The maximum numbers for fields and columns are:

  • 64 text fields, including the following field types: Single line of text, Choice, Hyperlink, or Picture.

  • 16 Lookup fields

  • 16 Date and Time fields

  • 16 Yes/No fields

  • 32 Number and Currency fields

  • 32 Multiple lines of text fields

Links with long URLs (more than 255 characters)

URLs longer than 255 characters are not supported in . Note that this character limit is for the URL and description.

User account limits

User account limits are not supported in . If you are using Active Directory account creation mode for user accounts, you can limit the number of users per site by using quotas. For more information, see Configuring Site Quotas and Locks .

Local user accounts

Local user accounts are only supported if you are using Active Directory account creation mode with , and local user accounts from your original site are not automatically created during migration. If you are using local accounts, first be sure that the server you are migrating to is using Active Directory account creation mode, and then add the users to the site manually after migration. For more information, see Installation Considerations for Windows SharePoint Services and Managing Users and Cross-Site Groups .

Subscriptions

The subscriptions feature in changed to the Alerts feature for . Users can create alerts in the new site to notify them about changes. To restore subscriptions as alerts, you must be sure that alerts are enabled for the virtual server you are restoring to. Set the number of alerts to unlimited so that the restore does not stop when it reaches a limit. Also note that if a user only set up subscriptions on the original site and hasn't added information to lists or libraries, his or her subscriptions won't get migrated. To resolve this problem, the user should create a new item in a list and then delete it. For more information about alerts, see Managing Alerts .

Remote Web discussions and subscriptions

does not support using a server running in an intranet to discuss content on the Internet, nor does it support creating alerts for content on the Internet. For example, you cannot use http://server1 to create discussion items or alerts for http://www.example.com.

Web discussions and subscriptions from unavailable user accounts

If the user account for a Web discussion or subscription cannot be determined at restore time, the Web discussion or alert are restored with the user name of the administrator restoring the site.

Security from a site based on FrontPage 2002 Server Extensions

If the original server is running FrontPage 2002 Server Extensions, the security information (such as user roles) cannot be migrated.

Created By/Modified By fields

If the original user account is not available on the new server when the site is restored, the Created By and Modified By fields are set to the account that performed the restore.

Subsites that have the same name as a wildcard inclusion or exclusion

If you have set up included and excluded paths for the server that hosts the migrated sites, ensure that the names of those paths do not conflict with the names of the sites to be migrated. For example, if you had a subsite named http://server1/sites, and the /sites path on the new server is a wildcard inclusion, the http://server1/sites subsite are not migrated. For more information about included and excluded paths, see Managing Paths .

Theme applied to site

If the original site was based on and had a theme applied, when you restore the site, you may notice formatting issues such as the Search box being sized differently than it was. To fix these issues, apply a new theme in .

Specific file permissions on the file system

If you set access control lists (ACLs) on specific files or folders in your Web site, those ACLs are not restored, and the files and folders are accessible to any user with access to your restored site.

Currencies

When migrating a site from to , converts some obsolete currencies to their modern equivalents. For example, German Deutschmarks are converted to Euros. However, only the format of the currency field is changed. The value for each entry is not altered and must be manually converted using the desired conversion rate.

sites based on customized schemas

sites that are based on customized schema files may not migrate properly to . Even though the Software Development Kit (SDK) documented how to customize schema files for , the Smigrate.exe utility does not support migrating sites based on customized schema files.

For more information about how to migrate Web sites, see Migrating and Upgrading Web Sites .

Considerations for Upgrading from WMSDE to SQL Server

WMSDE has only a small subset of the capabilities available with SQL Server. For example, WMSDE does not include tools for backing up and restoring the database, and WMSDE doesn't provide full-text searching of site content as SQL Server does. Also, you cannot create a server farm with multiple back-end database servers if you are using WMSDE. If you are running , and you originally installed with WMSDE but now want to take advantage of these capabilities with SQL Server, you can upgrade your databases from WMSDE to SQL Server. For more information about switching to SQL Server, see Migrating from WMSDE to SQL Server .

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