Microsoft Sharepoint Products and Technologies Resource Kit eBook

1102 Part XI: Upgrading and Migrating to SharePoint Products and Technologies
and you cannot compare or test the restored sites to the original sites to verify
that the migration was successful. Also, during the operating system upgrade,
the upgrade process will use the configuration and security settings of the previous
Windows 2000 install. This will not be same as if you had chosen a clean
installation of Windows Server 2003, which is a much more security-conscious
installation. If you do choose this option, ensure that you refer to Chapter 6,
“Security Architecture for SharePoint Products and Technologies,” and to the
Security Guidance Center for Windows Server 2003 at http://www.microsoft.com
/security/guidance/prodtech/WindowsServer2003.mspx.
■ Co-existence. Install the new software product version on the same computer
or on a different computer in such a way that the previous version of the product
and the newly installed version of the product can both be used. This requires
no additional hardware but is not recommended because there are coresidency
issues to address. For SharePoint Products and Technologies, certain combinations
of cross-version products and versions on the same computer are not supported.
(See Chapter 3, “Installing Microsoft Office SharePoint Portal Server
2003.”) Therefore, it is impossible to use the same machine co-existence strategy.
If you wish to use this strategy, you will need additional hardware, and in most
cases you will be using the following strategy, co-existence and migration.
■ Co-existence and Migration. Use a two-step process to support concurrent
operation of the previous software version until the organization is ready to
switch to the new software version and turn off the old version of the software
product. Install the new software version in parallel with the previous version of
the product, and run both solutions in parallel. During this time, migrate your
users and their data from the previous version of the software to the new version.
When the migration is complete, turn off and remove the previous version
of the software. This strategy is beneficial because it allows you to keep original
sites operational during the deployment of Windows SharePoint Services. It also
allows you to verify that the migration was successful. However, it requires a
greater number of servers to implement than the other two strategies.
When you migrate from SharePoint Portal Server 2001 to SharePoint Portal
Server 2003, you can use the in-place upgrade, co-existence (additional hardware),
and co-existence and migration strategies. Similarly, you can use all three strategies
for SharePoint Team Services, but in reality the in-place upgrade is implemented as
a migration progress, as is detailed in the next section of this chapter. Therefore,
your SharePoint Team Services sites are likely to always be upgraded using the
migration strategy, and I would recommend that you always migrate to a computer
that has a clean install of Windows Server 2003 whenever possible. This will reduce
the number of post-installation tasks concerning the configuration of the server,