Microsoft Windows Server 2003 Deployment Kit—Deploying Microsoft Internet Information Services (IIS) 6.0 [Electronic resources] نسخه متنی

اینجــــا یک کتابخانه دیجیتالی است

با بیش از 100000 منبع الکترونیکی رایگان به زبان فارسی ، عربی و انگلیسی

Microsoft Windows Server 2003 Deployment Kit—Deploying Microsoft Internet Information Services (IIS) 6.0 [Electronic resources] - نسخه متنی

Microsoft Corporation

| نمايش فراداده ، افزودن یک نقد و بررسی
افزودن به کتابخانه شخصی
ارسال به دوستان
جستجو در متن کتاب
بیشتر
تنظیمات قلم

فونت

اندازه قلم

+ - پیش فرض

حالت نمایش

روز نیمروز شب
جستجو در لغت نامه
بیشتر
توضیحات
افزودن یادداشت جدید












Deploying the Target Server

You must install Windows Server 2003 on the target Web server before you can migrate the Web sites and applications. In addition to installing Windows Server 2003, you must install and configure IIS 6.0 on the target server. To follow the process described in this chapter, install Windows Server 2003 and IIS 6.0 with the default options.

You must also configure the target server to run in worker process isolation mode or in IIS 5.0 isolation mode. Run IIS in IIS 5.0 isolation mode only when a Web site or application cannot run in worker process isolation mode. If there are no incompatibilities, configure IIS to run in worker process isolation mode to utilize the benefits of IIS 6.0 features.


Figure 6.3 illustrates the process for deploying the target server.


Figure 6.4: Deploying the Target Server

If you have already installed Windows Server 2003 on the target server, and you have already installed and configured IIS 6.0 on the target server, you can proceed to "Migrating Web Sites with the IIS 6.0 Migration Tool" or Migrating Web Sites Manually later in this chapter.



Installing Windows Server 2003


The primary concern when installing Windows Server 2003 is to ensure that the security of the target server is maintained. When you install Windows Server 2003 as a dedicated Web server, the default components and services are configured to provide the lowest possible attack surface. You can further reduce the attack surface of the target server by enabling only the essential Windows Server 2003 components and services.

The migration process presented in this chapter assumes that you install Windows Server 2003 with the default options. If you use other methods for installing and configuring Windows Server 2003, such as unattended setup, your configuration settings might be different.





Note

When you complete the installation of Windows Server 2003, Manage Your Server automatically starts. The migration process assumes that you quit Manage Your Server and then further configure the Web server in Add or Remove Programs in Control Panel.


For more information about enabling the essential Windows Server 2003 components and services required by your server, see "Enabling Only Essential Windows Server 2003 Components and Services" in "Securing Web Sites and Applications" in this book.


Installing and Configuring IIS 6.0


Because IIS 6.0 is not installed during the default installation of Windows Server 2003, the next step in deploying the target server is to install and configure IIS 6.0. The migration process presented here assumes that you install IIS 6.0 with the default options in Add or Remove Programs in Control Panel. If you use other methods for installing and configuring Windows Server 2003, such as Manage Your Server, the default configuration settings might be different.

Install and configure IIS 6.0 by completing the following steps:



Install IIS 6.0 with only the essential components and services.

As with installing Windows Server 2003, the primary concern when installing and configuring IIS 6.0 is to ensure that the security of the target server is maintained. Enabling unnecessary components and services increases the attack surface of the target server. You can help ensure the target server is secure by enabling only the essential components and services in IIS 6.0.

For more information about how to install IIS 6.0, see "Install IIS 6.0" in "IIS Deployment Procedures" in this book. For more information about the IIS 6.0 protocols and services, see "Enabling Only Essential IIS 6.0 Components and Services" in "Securing Web Sites and Applications" in this book.




If the source server has Web sites with FrontPage Server Extensions, install FrontPage 2002 Server Extensions from Microsoft on the target server.

For more information about how to enable FrontPage Server Extensions, see "Configure Web Service Extensions" in "IIS Deployment Procedures" in this book.



Configure IIS 6.0 to run in IIS 5.0 isolation mode.

If you determined that one or more of your Web sites or applications are incompatible with worker process isolation mode (the target server is currently configured to run in worker process isolation mode), configure IIS 6.0 to run in IIS 5.0 isolation mode in IIS Manager, or by setting the IIS metabase property IIs5IsolationModeEnabled to a value of True.





Note

If you configure IIS 6.0 to run in IIS 5.0 isolation mode and then decide to change the configuration back to worker process isolation mode, the original worker process isolation mode settings are retained. Similarly, if you configure IIS 6.0 to run in IIS 5.0 isolation mode, change to worker process isolation mode, and then change back to IIS 5.0 isolation mode, the IIS 5.0 isolation mode settings are retained.


For more information about how to configure IIS 6.0 to run in worker process isolation mode or in IIS 5.0 isolation mode, see "Configure Application Isolation Modes" in "IIS Deployment Procedures" in this book. For more information about determining compatibility with worker process isolation mode, see "Evaluating Application Changes Required for Worker Process Isolation Mode" earlier in this chapter.



/ 174