لطفا منتظر باشید ...
Overview of Upgrading an IIS Server to IIS 6.0
The advantages of upgrading the server that hosts your existing IIS Web sites and applications to IIS 6.0 include the following:
Reduces the time required to deploy IIS 6.0. Upgrading requires minimal user interaction.
Reduces possible configuration errors. Because the majority of the current operating system, IIS, and Web site configuration settings are retained during upgrade, fewer configuration errors result.
The disadvantages of upgrading the server that hosts your existing IIS Web sites and applications to IIS 6.0 include the following:
Retains previous versions of software. The upgrade process upgrades only software components identified by Microsoft Windows Server 2003, Standard Edition; Windows Server 2003, Enterprise Edition; and Windows Server 2003, Web Edition. Any other installed software components, such as applications or application dynamic-link libraries (DLLs), remain unchanged.During the IT lifecycle of the server, you can install and subsequently remove many of these additional software components. The software removal process often leaves DLLs, other files, and folders on the system. Over time, these unused components can accumulate, consume available disk space, and potentially cause instability with existing applications.
Retains the previous registry configuration. The upgrade process makes the appropriate modifications to the registry entries identified by Windows Server 2003. Registry entries are created by an application as it is installed, but are not removed when the application is removed. Cumulatively, these registry entries consume disk storage and can make troubleshooting registry-related problems more difficult because the unused registry entries can have similar naming conventions to active registry entries.
After upgrading a server to Windows Server 2003 and IIS 6.0, the server runs in IIS 5.0 isolation mode, which allows IIS 6.0 to emulate the memory and request processing model in IIS 5.0. However, to take advantage of the security and performance benefits of IIS 6.0, you need to configure the server to run in worker process isolation mode, which is the new IIS 6.0 memory and request processing model.When upgrading existing IIS Web sites is not the best solution for your existing server, consider migrating your IIS Web sites to a newly installed server running IIS 6.0. For information about migrating your existing IIS Web sites to IIS 6.0, see "Migrating IIS Web Sites to IIS 6.0" in this book.
Process for Upgrading an IIS Server to IIS 6.0
The process for upgrading an existing IIS server hosting IIS Web sites and applications includes preparing for the upgrade, as well as performing the upgrade. Upon completing the upgrade process outlined in this chapter, you can then configure IIS 6.0 to run your applications in worker process isolation mode. Lastly, if the newly upgraded IIS 6.0 server hosts existing ASP.NET applications, you must configure IIS to use the proper version of the Microsoft .NET Framework for these applications.Figure 5.1 illustrates the process for upgrading an existing IIS server hosting Web sites and applications to IIS 6.0.
Figure 5.1: Upgrading an Existing IIS Server to IIS 6.0
In addition to upgrading the existing operating system and IIS, the upgrade process automatically upgrades any components that are a part Windows Server 2003, such as FrontPage Server Extensions from Microsoft. As a part of the upgrade process, you need to evaluate the compatibility of the software that is installed on your existing server, including device drivers, other Windows components, and software, before performing the upgrade of the server.
| Tip | To upgrade a Web farm, use the process described in this chapter to upgrade each server in the Web farm. |
Depending on your familiarity with IIS and its upgrade process, you might require less information to complete the upgrade process. To facilitate the fastest possible upgrade, the following quick-start guide is provided. You can use this guide to help identify the steps of the upgrade process that you need additional information to complete, and then you can skip the information with which you are already familiar. In addition, all of the procedures that are required to complete the upgrade process are documented in "IIS Deployment Procedures" in this book.
Prepare to Upgrade
Determine compatibility with Windows Server 2003.
Identify and compensate for changes to IIS 6.0:
Ensure that the World Wide Web Publishing Service (WWW service) is enabled after upgrade.
Compensate for changes to IIS components.
Determine application compatibility with worker process isolation mode by completing the following steps:
Evaluate the benefits of worker process isolation mode.
Evaluate application changes required for worker process isolation mode.
Evaluate management and provisioning script changes required for worker process isolation mode.
Verify application compatibility with worker process isolation mode in a lab.
Determine application compatibility with the .NET Framework.
Perform the Upgrade
Back up the Web server before upgrade.
Verify that clients are not accessing Web sites.
Prevent the WWW service from being disabled.
Upgrade the Web server to IIS 6.0.
Verify that the operating system upgrade was successful.
Back up the IIS 6.0 metabase after upgrade.
Convert to Worker Process Isolation Mode
Document the current application isolation settings.
Configure IIS to run in worker process isolation mode.
Configure application isolation settings in IIS 6.0.
Configure IIS 6.0 Properties
Enable the WWW service.
Configure Web service extensions.
Configure Multipurpose Internet Mail Extensions (MIME) types.
Modify references to IIS 6.0 metabase properties that have changed or are no longer supported.
Upgrade FrontPage extended Web sites.
Determine whether to run the IIS Lockdown Tool and UrlScan.
Make the following security-related configuration changes:
Enable essential IIS components and services.
Remove any unnecessary IIS virtual directories.
Configure the anonymous user identity.
Configure IIS to Host ASP.NET Applications
Configure IIS to use the correct version of the .NET Framework.
Configure the .NET Framework.
Review how ASP.NET applications run in each application isolation mode.
Migrate Machine.config attributes to IIS 6.0 metabase property settings by completing the following steps:
Migrate recycling-related attributes.
Migrate performance-related attributes.
Migrate health-related attributes.
Migrate identity-related attributes.
Complete the Upgrade
Verify that the Web sites and applications run properly.
Back up the Web server.
Enable client access after upgrade is complete.
