MCTS Self-Paced Training Kit (Exam ): Configuring Windows Server 2008 Application Platform

Transcription

1 MCTS Self-Paced Training Kit (Exam ): Configuring Windows Server 2008 Application Platform J.C. Mackin and Anil Desai PREVIEW CONTENT This excerpt contains uncorrected manuscript from an upcoming Microsoft Press title, for early preview, and is subject to change prior to release. This excerpt is from MCTS Self-Paced Training Kit (Exam ): Configuring Windows Server 2008 Application Platform from Microsoft Press (ISBN , copyright 2008 Anil Desai, J.C. Mackin, all rights reserved), and is provided without any express, statutory, or implied warranties To learn more about this book, visit Microsoft Learning at Anil Desai and J.C. Mackin. All rights reserved.

2 Table of Contents Chapter 1: Configuring File and Print Services Lesson 1: Configuring and Managing a File Server Overview of the File Services Role Installing the File Services Role Managing a File Server Implementing Distributed File System Practice Lesson Summary Lesson Review Lesson 2: Configuring and Managing Print Services Overview of the Print Services Role Installing the Print Services Role Managing a Print Server Monitoring a Print Server Practice Lesson Summary Lesson Review Lesson 3: Backing up and Restoring Data Installing the Windows Server Backup Feature Scheduling Backups Restoring Data Troubleshooting Windows Server Backup Practice Lesson Summary Lesson Review iii

3 iv Table of Contents Chapter Review Chapter Summary Key Terms Case Scenarios Case Scenario 1 Case Scenario 2 Suggested Practices Take a Practice Test Chapter 2: Installing and Configuring Web Applications Lesson 1: Installing the Web Server (IIS) Role Understanding Web Server Security Understanding IIS Components and Options Understanding the Application Server Role Understanding IIS 7.0 Role Services Installing the Web Server (IIS) Role Practice: Installing and Verifying the Web Server (IIS) Role Lesson Summary Lesson Review Lesson 2: Configuring Internet Information Services Working with IIS Management Tools Creating and Configuring Web Sites Understanding Web Applications Working with Application Pools Working with Virtual Directories Using Command-Line Management Managing Web Server Configuration Files Migrating From IIS 6.0

4 Table of Contents v Practice: Configuring and Managing IIS Settings Chapter Review Chapter Summary Key Terms Case Scenarios Case Scenario 1: IIS Web Server Administration Case Scenario 2: Managing Multiple Web Sites Suggested Practices Managing Web Applications Take a Practice Test Chapter 3: Managing Web Services Security Lesson 1: Understanding IIS Security Understanding the IIS 7 Security Architecture Enabling and Disabling Request Handlers Managing IIS Permissions Managing File System Permissions Web Services Discovery through UDDI Practice Lesson Summary Lesson Review Lesson 2: Controlling Access to Web Services Managing IIS Authentication Options Understanding Authorization Approaches Configuring Web Services Rights and Permissions Securing Communications with Certificates Understanding.NET Trust Levels Practice

5 vi Table of Contents Lesson Summary Lesson Review Chapter Review Chapter Summary Key Terms Case Scenarios Case Scenario 1 Case Scenario 2 Suggested Practices Take a Practice Test Chapter 4: Configuring FTP and SMTP Services Lesson 1: Configuring FTP Understanding FTP Enabling the FTP Server Configuring FTP security Monitoring and Managing FTP Server Practice Lesson Summary Lesson Review Lesson 2: Configuring SMTP Understanding SMTP SMTP Scenarios Enabling the SMTP Server Understanding SMTP forwarding Securing SMTP Services Practice

6 Table of Contents vii Lesson Summary Lesson Review Chapter Review Chapter Summary Key Terms Case Scenarios Case Scenario 1 Case Scenario 2 Suggested Practices Take a Practice Test Chapter 5: Configuring Communication Services Lesson 1: Configuring Media Server Capabilities of Media Server Enabling Media Server Functionality Practice Lesson Summary Lesson Review Lesson 2: Configuring Fax Services Understanding Fax Services Enabling Fax Services Configuring Fax Sharing Options Practice Lesson Summary Lesson Review Chapter Review Chapter Summary Key Terms

7 viii Table of Contents Case Scenarios Case Scenario 1 Case Scenario 2 Suggested Practices Take a Practice Test Chapter 6: Configuring Windows SharePoint Services Lesson 1: Enabling Windows SharePoint Services Understanding Windows SharePoint Services Understanding Windows SharePoint Services Deployment Options Adding the Windows SharePoint Services Server Role Installing Windows SharePoint Using the Command Line Verifying the Windows SharePoint Installation Removing Windows SharePoint Services Practice: Installing Windows SharePoint Services Lesson Summary Lesson Review Lesson 2: Configuring and Managing Windows SharePoint Services Using the SharePoint Central Administration Web Site Managing SharePoint Operations Setting Understanding Backup and Recovery for WSS Deploying and Configuring SharePoint Sites Managing Web Applications Installing Application Templates Practice: Configuring and Managing Windows SharePoint Services Lesson Summary Lesson Review

8 Table of Contents ix Chapter Review Chapter Summary Key Terms Case Scenarios Case Scenario 1: Deploying Windows SharePoint Services Case Scenario 2: Managing Windows SharePoint Services Suggested Practices Implementing and Managing Windows SharePoint Services Take a Practice Test Chapter 7: Installing and Configuring Terminal Services Lesson 1: Deploying a Terminal Server Terminal Services Basics Enabling Remote Desktop Installing Terminal Services Staging the Terminal Server Practice: Installing a Terminal Server Lesson Summary Lesson Review Lesson 2: Configuring Terminal Services Introducing the Terminal Services Configuration Console Configuring Terminal Services (RDP-TCP) Properties Configuring Terminal Services Server Properties Configuring Terminal Services Printer Redirection Practice: Installing and Configuring a License Server Lesson Summary Lesson Review

9 x Table of Contents Chapter Review Chapter Summary Key Terms Case Scenarios Case Scenario 1: Choosing a TS Licensing Strategy Case Scenario 2: Troubleshooting a Terminal Services Installation Suggested Practices Take a Practice Test Chapter 8: Configuring and Managing a Terminal Services Infrastructure Lesson 1: Configuring and Managing Terminal Services Clients Configuring Terminal Services Client Connections Managing Terminal Services User Connections Practice: Managing Client Connections Lesson Summary Lesson Review Lesson 2: Deploying a Terminal Services Gateway Overview of Terminal Services Gateway Installing the Configuring Terminal Services Gateway Practice: Installing and Configuring Terminal Services Gateway Lesson Summary Lesson Review

10 Table of Contents xi Lesson 3: Publishing Applications with Terminal Services RemoteApp Overview of Terminal Services RemoteApp Configuring a Server to Host RemoteApp Programs Adding Programs for Publication in Terminal Services RemoteApp Manager Deploying a RemoteApp Program through TS Web Access Creating an RDP File of a RemoteApp Program for Distribution Creating a Windows Installer Package of a RemoteApp Program for Distribution Practice: Publishing Applications with Terminal Services RemoteApp Manager Lesson Summary Lesson Review Chapter Review Chapter Summary Key Terms Case Scenarios Case Scenario 1: Managing Terminal Services Sessions Case Scenario 2: Publishing Applications Suggested Practices Deploy a Terminal Services Infrastructure Take a Practice Test Chapter 9: Monitoring and Maintaining Windows Server 2008 Lesson 1: Monitoring Server Performance Introducing the Reliability and Performance Console

11 xii Table of Contents Capturing Performance Data Monitoring Reliability Using Data Collector Sets Generating Performance Reports Practice Lesson Summary Lesson Review Lesson 2: Event Viewer Introduction to Event Viewer Reading Windows Logs Reading Application and Service Logs Creating Custom Views Creating Subscriptions Practice Lesson Summary Lesson Review Lesson 3: Scheduling Maintenance Tasks Creating Scheduled Tasks Using Predefined Tasks Practice Lesson Summary Lesson Review Chapter Review Chapter Summary Key Terms Case Scenarios Case Scenario 1 Case Scenario 2

12 Table of Contents xiii Suggested Practices Take a Practice Test Chapter 10: Monitoring Network Performance Lesson 1: Capturing Network Traffic with Network Monitor Introduction to Network Monitor 3.1 Capturing Network Data Practice Lesson Summary Lesson Review Lesson 2: Monitoring Networks Overview of SNMP Deploying SNMP Components Using SNMP Agents Practice Lesson Summary Lesson Review Chapter Review Chapter Summary Key Terms Case Scenarios Case Scenario 1 Case Scenario 2 Suggested Practices Take a Practice Test

13 Chapter 2 Installing and Configuring Web Applications Modern Web sites provide functionality that is on par with the experience found in many locally installed client applications. They provide access to databases in both public and intranet environments and enable users to customize their experience based on specific needs. These programs are known as Web applications or Web services, and they can rely upon a broad variety of different standards, protocols, and development technologies. The Windows Server 2008 operating system includes Internet Information Services (IIS) 7.0, a complete Web services platform that is capable of supporting a broad variety of different types of Web content and applications. IIS 7.0 provides significant enhancements in manageability, scalability, and reliability. It also provides backward compatibility to support the millions of Web sites that are already hosted on previous versions of IIS. In this chapter, you ll learn how to install and configure the Web Server (IIS) and Application Server roles in Windows Server There are numerous features and services that you can enable based on the needs of your environment. You ll also learn about how you can configure IIS to meet a wide variety of requirement types. This information will help you deploy and configure IIS and its related features in production environments. Exam objectives in this chapter: Configuring a Web Services Infrastructure Configuring backup. Configuring Web applications. Configuring Application Pools. Configuring IIS components. Publishing IIS Web sites. Migrating sites and Web applications. Lessons in this chapter: Lesson 1: Installing the Web Server (IIS) Role Lesson 2: Configuring Internet Information Services

14 2 Chapter 2 Installing and Configuring Web Applications Before You Begin The steps in the practice exercises assume that you will be using either server1.contoso.com or server2.contoso.com to perform all the necessary steps and that the Application Server role has not yet been installed. You can perform most of the steps on another computer running Windows Server 2008, but you might need to make some adjustments to the steps. Also, although there are some licensing differences between the different editions of Windows Server 2008, the basic architecture of the Web Server (IIS) role is consistent among them. Real World Anil Desai The success of a server installation is often based on how well its configuration matches the needs of users and developers. If some features are missing, applications will not run as expected. If too many features are enabled, there could be security, compatibility, or performance implications. The goal is to get it right. This is one area in which communications are important. In many IT departments, I ve seen a significant disconnect between development teams (such as groups of Web developers) and the systems administrators who are responsible for deploying and supporting the applications that the developers create. Often, the responsibilities blur between these two parts of the organizations, and it can become difficult to figure out who is ultimately responsible for the final configuration. Fortunately, these types of problems can be solved. On the systems administration side, IT staff should try to determine the specific business and technical needs of the Web applications that they support. Web developers can do their part by proactively communicating upcoming requirements and potential implications for the configuration of production servers. Documentation is helpful for thinking through and communicating the most important points. Finally, it s important not to forget about end users. Whether these are people who are part of your organization or the public at large, it s important to understand their specific reasons for visiting your Web sites. Marketing input can often help in this area.

15 Lesson 1: Installing the Web Server (IIS) Role 3 Lesson 1: Installing the Web Server (IIS) Role Although the basic steps and processes required for enabling IIS and its related components is usually a simple procedure; the primary challenge lies in understanding the architecture, components, and available features of the platform. In this lesson, you will learn about the modular architecture of IIS and how you can configure a computer running Windows Server 2008 as a Web server. After this lesson, you will be able to: Describe the architecture of IIS 7.0, including new features. Define the purpose of the Application Server role. Describe the purpose of role services related to the Web Server (IIS) role. Install the Web Server (IIS) role and add and remove role services. Perform command-line installations and automated installations of the Web Server (IIS) role. Estimated lesson time: 45 minutes Understanding Web Server Security IIS 7.0 represents the evolution of the Microsoft IIS platform over several years. It includes a broad array of features and options to support different types of Web services and applications. The process of installing IIS and its related features and options is simplified through using the Server Manager utility. As a systems administrator, you will be responsible for deploying IIS based on different needs and requirements. Therefore, it is important to understand the design of IIS before learning methods for installing the Web Server and Application Server roles. This section will provide details about deployment options for the IIS platform. MORE INFO Other features of IIS In addition to supporting Web applications, the IIS platform also provides server components for the File Transfer Protocol (FTP) and the Simple Mail Transfer Protocol (SMTP). This chapter focuses on Web-based applications. For more information about these other features, see Chapter 4, Configuring FTP and SMTP Services. Web Standards and Protocols To understand the purpose and function of the IIS platform, you must first understand (or review) basic information about how Web services operate. Hypertext Transfer Protocol (HTTP) is the primary protocol used to communicate with Web services. HTTP is designed to provide a request response model for communicating between different computers across a network. HTTP traffic is accessed by using Transmission Control Protocol/Internet

16 4 Chapter 2 Installing and Configuring Web Applications Protocol (TCP/IP) based network connections. Due to the importance of Web-based traffic, most organizations allow their users to access the Internet by using TCP port 80, the default HTTP port. The HTTP protocol is stateless; that is, it provides no built-in mechanism to keep track of conversations between clients and servers. Each request must include details that identify the requester and any other data that might be required to complete a transaction. By default, HTTP traffic is transmitted using a plaintext stream that can be decoded easily. Although this is acceptable when users are accessing public content, many Web sites and applications need to transmit information securely between clients and servers. The most common example is that of a payment-processing site that accepts credit card information over the Internet. The HTTP Secure (HTTPS) protocol is designed to provide support for encryption of HTTP-based traffic. By default, HTTPS connections use TCP port 443 for communications, although any other port can be used as well. The most commonly used encryption mechanisms are Secure Sockets Layer (SSL) and Transport Layer Security (TLS). Other encryption mechanisms can also be used, especially in intranet environments. Apart from using standards-based communications protocols, the popularity of Web-based content is based on a standard method of presenting information. The Hypertext Markup Language (HTML) is the primary specification for Web pages. The tag-based format of HTML pages enables developers to use a wide variety of technologies to create their own content in a way that is accessible to different Web browsers. The development tools can range from text editors such as Microsoft Windows Notepad to full-featured development environments such as the Microsoft Visual Studio platform. The HTTP and HTML specifications were designed to provide basic communication and presentation services. Modern Web applications include features that enable complex application functionality to be presented using these standards. Web developers can use development platforms such as ASP.NET (a component of the Microsoft.NET Framework) to build active Web sites. These sites can keep track of user sessions and can provide access to databases and other information that is stored within the environment. MORE INFO Further details about Internet standards For more information about specific Internet and Web-based standards, see the World Wide Web Consortium (W3C) Web site at and the Internet Engineering Task Force (IETF) Web site at Both sites include the official specifications and descriptions for basic Internet protocols. The IIS platform is designed to support standard Web services protocols and specifications as well as numerous additional features that can improve Web server performance and reliability. You ll learn more about these specific features later in this lesson.

17 Lesson 1: Installing the Web Server (IIS) Role 5 Web Server Usage Scenarios In modern IT environments, Web servers can be deployed to support a wide range of usage types. The primary advantage of using Web-based content and applications is accessibility from a broad range of client computers. Unlike standard applications, there is generally no need to install or configure any software on users computers. Because modern operating systems include or support standards-based Web browsers such as Microsoft Internet Explorer, most users already have the basic client tools they need to access content. IT staff and software developers can use a variety of different technologies to present content and deploy applications to both internal and external users. The IIS platform has been designed to support a wide variety of usage scenarios. Some examples include: Public Web sites Many businesses have relatively simple needs for communicating information on the Internet. For example, a small business might want to provide contact information and details about its services on a simple Web site. Online shopping The Internet has become a commercial marketplace that enables vendors to display and sell a wide variety of products. Online sites include shopping-cart functionality, order processing, and customer support features. Intranet scenarios The Web provides a simple method for all users within an organization to access and present content. Company tasks such as creating expense reports or verifying benefits can often be performed online without the need to contact internal staff. Enterprise applications A common challenge with enterprise line-of-business applications is the need to deploy and manage client-side installations. To alleviate some of these problems, many organizations have created internal applications that are designed to be accessed through a Web browser. The applications can range from basic singlefunction sites to distributed enterprise-wide systems. Internet applications Web-based solutions are available for performing a wide array of computing tasks by using standards such as HTML. Users can access their and create documents, for example, without installing applications on their computers. Distributed organizations and teams can also take advantage of secure access to corporate applications by using the Internet while traveling or working from remote locations. Extranet scenarios Businesses commonly partner with other organizations to obtain services. An extranet scenario is one in which users from outside the organization are able to access information. Security is an important concern, but Web-based applications are a good choice because they provide a standard method by which a broad range of users can access the information they need. Web hosting Many companies have focused on offering the service of hosting Web sites for their customers. These hosting companies tend to run large numbers of Web sites on a single physical server. Ensuring security, performance, and reliability are key concerns.

18 6 Chapter 2 Installing and Configuring Web Applications Most organizations will deploy IIS in several different roles within the organization. It is important to note that requirements related to features and options will vary based on the specific needs of each deployment. Exam Tip When learning about the many different features and options of the IIS platform, it often helps to think of scenarios in which those features can be helpful to meet technical or business requirements. When taking Exam , expect to see questions that require you to understand specific requirements and find the most appropriate option or feature to meet those requirements. You ll learn more about the specific features and services that the IIS platform supports later in this lesson. New Features in IIS The IIS platform is one of the most popular Web servers in use for both public and private Web sites. IIS 7.0 in Windows Server 2008 includes numerous new features that provide increased performance and functionality in a broad range of areas. The major areas of improvement include: Administration One of the primary challenges of working with previous versions of IIS was dealing with a large number of property pages and dialog boxes. IIS 7.0 includes new administration tools that are designed to manage the many available options and settings more effectively. The user interface has been designed to be both powerful and accessible for both Web developers and systems administrators. Security By default, the Web Server (IIS) server role is enabled with only a basic set of functionality. Even the binary files for unused features are not available for access in the standard operating system locations. Systems administrators must enable additional services and features explicitly. This helps reduce the attack surface of IIS while also simplifying manageability. In addition, functionality for automatically detecting common hacking attempts is included with the product itself. (This feature was commonly enabled in the past by installing the URLScan utility.) Diagnostics and troubleshooting Because organizations depend on Web services as a mission-critical component of their infrastructure, it s important to detect and resolve any Web-based errors quickly. IIS 7.0 includes new features that make it easier to pinpoint problems and obtain the details necessary to address them. Centralized configuration management Many organizations support dozens or even hundreds of IIS installations. To meet scalability and performance requirements, it is often necessary to deploy numerous Web servers that essentially have the same configuration settings. In previous versions of IIS, it was difficult to manage these configurations without connecting to each of the servers. IIS 7.0 provides a simplified method by which administrators can share configuration information across server farms. Further,

19 Lesson 1: Installing the Web Server (IIS) Role 7 a consistent set of user accounts (including globally unique identifiers [GUIDs] and permissions) are used for IIS security accounts. This means administrators can depend on specific account names and settings when scripting and automating common processes. IIS 7.0 also includes greatly improved command-line support. Support for delegation It is often necessary to divide Web server administration tasks for security or management reasons. IIS 7.0 provides the ability to implement granular security configuration permissions to support Web-hosting environments and enterprise-level configurations. Backward compatibility The vast majority of Web sites and applications that were created for previous versions of IIS will remain compatible with IIS 7.0. In addition, IIS 6.0 management tools are provided for those applications that depend on them. Overall, IIS 7.0 has been designed to address the most common issues encountered with previous versions of IIS. There are also numerous additional improvements in IIS that you ll learn about as this chapter discusses the various features in depth. MORE INFO IIS in Windows Vista Microsoft first made the IIS 7.0 platform available in the Windows Vista operating system. Because the core architecture of IIS in Windows Vista is similar to that in Windows Server 2008, Web developers can use similar environments on both their development workstations and their production servers. It is important to note that there are some feature and licensing differences between the two platforms. For more information, see the Microsoft Internet Information Services Web site at MORE INFO Information from the IIS team The IIS team at Microsoft has created a Web site that includes tutorials, technical articles, and other details about working with the IIS platform. This is a great resource for in-depth information on the many different features and components that are available. The site includes links to downloads and information about products that work with (or on) the IIS platform. Team members have their own blogs, too, which focus on their specific areas of expertise. The main page is located at Understanding IIS Components and Options The IIS platform has been designed with a modular, component-based architecture. In its simplest configuration, the Web server component provides basic HTTP functionality. IIS includes many components and features that can be used to support different types of content and applications. Most deployments will need only a subset of these features. Therefore, administrators can choose to enable only those components that their Web applications require.

20 8 Chapter 2 Installing and Configuring Web Applications Although the modular approach requires systems administrators to enable explicitly the features that they require, this architecture provides numerous advantages: Enhanced security Each enabled service or feature potentially can increase the security attack surface on an IIS server. This is a significant concern for publicly accessible servers that might be the targets of malicious attacks of unauthorized access attempts. For example, a defect or vulnerability in a specific type of IIS extension might be used to perform unauthorized actions on the server. Administrators can reduce these risks greatly by enabling only those features and services that are required by their content and applications. Improving performance Installing and enabling unnecessary components can use up system resources on the server that is running IIS. By enabling only those features that are required specifically, server resources can be retained for use by other applications. The end result is better performance and scalability. Customizing server configurations As mentioned earlier in this lesson, organizations tend to use IIS in a wide variety of deployment scenarios. The security and functionality requirements can vary significantly, and a modular architecture allows systems administrators to customize each deployment based on its specific needs. For example, the authentication and security requirements of internal Web servers and Internet accessible servers often differ. Administrators can enable the required features for each type of server independently. In this section, you ll learn about components and options that are related to the IIS platform. Understanding the Application Server Role One of the primary strengths of the Windows platform is its ability to support a wide range of different application development technologies. Modern applications often rely on extensive communications features. For example, a distributed application might need to create and manage transactions across several different sites and services using a distributed network. Building this type of functionality can be difficult and complicated. Applications developers can save significant time and effort by taking advantage of the features that are already available on their operating system platform. Windows Server 2008 includes the Application Server role to provide support for a variety of different application development technologies. The Application Server role is based on.net Framework 3.0 technology and includes support for other communications and presentation features. Although the Application Server role is not specifically dependent on the Web Server (IIS) role, distributed applications that are built using ASP.NET or Windows Communication Foundation (WCF) will require both roles.

21 Lesson 1: Installing the Web Server (IIS) Role 9 Exam Tip The Application Server role provides additional functionality on top of ASP.NET support and other services that are available for the Web Server (IIS) role. In general, you should not need to install the Application Server role unless a specific Web application or Web service requires it. Basic ASP.NET applications, for example, will run without the Application Server role enabled on the server. You can install the Application Server role by using the Add Roles Wizard in Server Manager. When you add the role, you will be given the option of determining which additional role services you plan to enable. (See Figure 2-1.) The specific features include: Figure 2-1 Viewing a list of available role services for the Application Server role Application Server Foundation This is a required feature of the Application Server role. It includes support for technology in the.net Framework 3.0 platform. The primary technology components are the Windows Communication Foundation (WCF), Windows Presentation Foundation (WPF), and Windows Workflow Foundation (WF). Web Server (IIS) Support The Application Server role can be integrated with the Web Server (IIS) role to enable Web applications to access advanced features. When you select this option, the Add Roles Wizard will prompt you to install IIS automatically if it is not already installed. COM+ Network Access The Component Object Model (COM) standard provides applications developers with a method for accessing different pieces of application code. COM+ provides the ability to invoke (or access) application code remotely

22 10 Chapter 2 Installing and Configuring Web Applications across a network. Distributed applications, such as those that require multiple tiers of functionality, might require this feature. TCP Port Sharing A potential management challenge of working in distributed environments is that of supporting many different server applications on a single computer. Generally, each application requires its own TCP port for responding to inbound requests. The TCP Port Sharing feature enables multiple applications to share the same port to simplify server and firewall configuration. Windows Process Activation Service Support The Windows Process Activation Service (WAS) provides the ability to access application services over the network by using different types of protocols and services. This feature can be used by IIS itself to support additional protocols and communications methods. Distributed Transactions Applications that involve distributed transactions require multiple servers and applications to coordinate their activities before changes are made permanent. By using this section, you enable incoming and outgoing remote transactions and support the WS-Atomic Transactions standard for Web Services. Generally, you should verify requirements with Web application developers to determine which Application Server components (if any) are required. When done correctly, collecting and communicating Web server requirements can help ensure that systems administrators are aligned with the developers and users that they support. From an IT standpoint, IIS is one of those technology areas that can benefit from input and expertise from all areas of your organization. Be sure to do your homework before diving into the configuration process and you re much more likely to end up with the right IIS configuration. Using Windows System Resource Manager An important consideration for any server is to ensure that critical services are not interrupted when the system is under load. By default, most services in Windows Server 2008 run at an equal priority level. Windows System Resource Manager (WSRM) helps administrators assign priorities to various system processes such as IIS. Although WSRM is not a requirement for running IIS, on busy Web servers or servers that are providing many important services, enabling this feature can be helpful. For example, administrators can create Resource Allocation policies to define CPU and memory limitations to ensure that the system continues to respond well even when under heavy load. (See Figure 2-2.)

23 Lesson 1: Installing the Web Server (IIS) Role 11 Figure 2-2 The Windows System Resource Manager console You can add WSRM to a computer running Windows Server 2008 by using Server Manager. Right-click the Server Manager item and select Add Features to start the process. The Add Features Wizard includes an option to add WSRM. For more information about WSRM, In the Start menu Start Search box type system resource and then press Enter. The help file includes details on creating and managing resource settings. Understanding IIS 7.0 Role Services Role services define which specific features and options of the IIS platform are available for use on the local Web server. Once you have installed IIS 7.0 on a computer running Windows Server 2008, you can add additional components by using Server Manager. To do this, expand Roles, right-click Web Server (IIS), and select Add Role Services. You will see a dialog box like the one shown in Figure 2-3.

24 12 Chapter 2 Installing and Configuring Web Applications Figure 2-3 Managing Web Server role services in Server Manager IIS role services are organized into several major areas: Common HTTP Features Application Development Health and Diagnostics Security Performance Management Tools FTP Publishing Service The top level of the hierarchy is the Web Server itself. This item represents the core IIS services that are required by the below optional components that are listed below. Two other items, Management Tools and the FTP Publishing Service, can be installed independently of the Web Server. Each area contains features and options that are related. Several of the items depend on other role services. If you select an item without first selecting its dependencies, you will be given the option to add the required role services automatically. (See Figure 2-4.)

25 Lesson 1: Installing the Web Server (IIS) Role 13 Figure 2-4 Including role dependencies when adding a role service Exam Tip Note that adding a role service makes it available for use by your Web sites and applications. Additional configuration is sometimes required to take advantage of the service. For example, enabling certain authentication options will not make them automatically apply to all your Web sites. When taking Exam , keep in mind that adding a Web Server role service might be only one step in meeting the complete solution requirements. Default IIS Role Services As mentioned earlier, the default configuration includes a limited set of functionality. It is appropriate for installations that want to serve only limited static content and do not need advanced security or development features. In many cases, you will want to enable additional options. Table 2-1 lists the role services that are included when you add the Web Server (IIS) server role to the computer. Table 2-1 Default Role Services Included in the Web Server (IIS) Server Role Group/Category Feature(s) Common HTTP Features Static Content Default Document Directory Browsing HTTP Errors HTTP Redirection Application Development Features.NET Extensibility

26 14 Chapter 2 Installing and Configuring Web Applications Table 2-1 Default Role Services Included in the Web Server (IIS) Server Role Group/Category Feature(s) Health and Diagnostics Features HTTP Logging Logging Tools Request Monitor Tracing Security Request Filtering Performance Features Static Content Compression Management Tools IIS Management Console Windows Process Activation Service Features Process Model In the following sections, you ll learn more about the purpose of these and the many optional role services. Common HTTP Features The most important capability of the Web Server (IIS) role is to provide support for serving HTML Web pages using the HTTP protocol. All the components of the Common HTTP Features group are included in the default installation. They are: Static Content This functionality allows for serving static Web pages to clients, using HTTP. The most common content types are static HTML pages and images. Static content files are usually sent directly to users without any server-side processing. Default Document This feature allows IIS to return a specific file automatically for a Web site when one is not explicitly requested in the URL. For example, if a user attempts to connect to the Web server can be configured to return the default.htm file as a response. Directory Browsing IIS includes built-in functionality for providing basic directory listings to users. When enabled, directory browsing sends information about the files and folders on a Web site to the client s Web browser. (See Figure 2-5.). Because users will have the ability to access and download any files to which they have the appropriate permissions, this feature is usually disabled for public Web sites. If the default document feature is enabled and a default document is found, users will not see the directory browsing screen.

27 Lesson 1: Installing the Web Server (IIS) Role 15 Figure 2-5 Using directory browsing to view the contents of a Web site HTTP Errors By default, most Web browsers are designed to present an error message automatically to users whenever a problem occurs. For example, if a page cannot be found or if the server is too busy, the Web browser will display this information to the user. To enhance the user experience, IIS can be configured to return custom error pages automatically when these problems occur. The content of the error pages can include contact information for the Web site s administrator or other details about resolving the problem. HTTP Redirection The HTTP protocol supports a method of redirecting a request from one site to another. The Web server can be configured to send an HTTP redirect request automatically to a Web user when a specific site is accessed. Site redirection is useful for situations in which a Web site has been relocated to a different URL or when multiple URLs are designed to access the same content. Although all the Common HTTP Features are enabled by default, the specific behavior of each IIS Web site will be based on its content and configuration settings.

28 16 Chapter 2 Installing and Configuring Web Applications Application Development Features Although some basic Web sites can meet their requirements by using only static content, it s far more common for production sites to require dynamic Web services and Web application support. IIS has been designed to support a broad array of different features and technologies to support these requirements. The list of Application Development role services includes: ASP.NET ASP.NET is the primary Microsoft Web server development platform. It is based on the.net Framework and provides a powerful and flexible development framework for handling common Web site design tasks. Features include built-in support for managing access to databases, security and authorization methods, and reliability and scalability features..net Extensibility The Microsoft.NET Framework programming platform can be used to make modifications to IIS Web server functionality. This role service enables developers to access the IIS management namespaces and objects for building logic that interacts with Web server requests. ASP Active Server Pages (ASP) technology is the predecessor to the ASP.NET platform. ASP provided a simplified, script-based method of developing Web-based applications. ASP scripts run on the Web server and generate HTML content that is passed back to the user through IIS. Support for ASP is provided primarily for backward compatibility with applications that have not yet been moved to the ASP.NET platform. CGI The Common Gateway Interface (CGI) is a standard that defines how Web servers can pass information to programmatic scripts. It is required by some server-side components, especially those that have been written to run on multiple Web server platforms. Web development languages such as PHP: Hypertext Preprocessor (PHP) rely on CGI support within the Web server. IIS 7.0 includes features that can improve the performance of CGI processing significantly. ISAPI extensions IIS supports an extensibility standard known as the Internet Server Application Programming Interface (ISAPI). By building ISAPI extensions, Web developers can create their own content handlers that can interact with every aspect of the Web request pipeline. The ISAPI standard is designed to provide scalability for supporting many simultaneous requests. ISAPI filters ISAPI filters are custom code that developers can create to process specific Web server requests. The logic can receive Web request details and return the appropriate content based on server-side logic. IIS attempts to match Web requests with the most appropriate ISAPI filter for handling that type of content. Enabling this role service allows developers to add custom ISAPI filters to IIS.

29 Lesson 1: Installing the Web Server (IIS) Role 17 Server-Side Includes Web designers can often benefit from having the ability to embed certain common content on all their Web pages. Examples include a site header, navigation elements, and site footers. The Server Side Includes role service enables the Web server to include other pieces of content when generating a Web server request. For security reasons, this feature is disabled by default. However, sites that do not rely on other Web development technologies (such as ASP.NET) might require this capability. Of these role services, only the.net Extensibility item is installed by default. When planning to deploy production Web sites, determine which additional features should be enabled. This information is usually available from the Web application development team or organization. Health and Diagnostics Features Although basic Web server functionality can appear simple, there are numerous steps that must be performed during the processing of a typical Web request. Organizations that depend on their Web servers for access to critical information and systems need a method of isolating and troubleshooting any problems that might occur. Role services that are included in the Health and Diagnostics features section are designed to help administrators and developers collect and analyze information about Web requests. A common challenge with monitoring Web sites is managing the volume of information that is generated. The process of recording in-depth details about all requests can add a significant level of performance overhead to production systems. To help address this issue, IIS 7.0 includes enhanced features for collecting details on specific requests and for configuring which information should be collected. The specific role services are: HTTP logging The most basic form of logging in IIS is to store HTTP request information within text files on the server s file system. HTTP logging enables this functionality, along with a set of default settings for logging requests. Details can be customized by accessing the properties of each Web site. The default location for log files is %SystemDrive%\Inetpub\Logs\LogFiles. Figure 2-6 shows a list of fields that can be included in the log files.

30 18 Chapter 2 Installing and Configuring Web Applications Figure 2-6 Configuring logging options Logging Tools Raw HTTP request logs are difficult to view and analyze manually. On busy Web servers, the files can get extremely large quickly. Because the content typically is organized with a single row per request, administrators might need to search through thousands of rows to get the information they need. The Logging Tools role service provides simple utilities for accessing and analyzing log files. Request Monitor A common difficulty with diagnosing performance-related issues on a Web server is that of trying to determine which activity is occurring currently. The Request Monitor feature enables administrators to see which requests are executing within the Web server process currently. This can help isolate the potential source of slowdowns or loss of service due to long-running requests or other issues. Tracing When an error or performance-related issue occurs on a Web server, it is useful to collect as much information as possible about the problem. Unfortunately, due to performance requirements, it s usually impractical to store details about all requests. Tracing functionality enables IIS to store detailed information for any failed requests. This feature works by keeping information about executing requests in memory just long enough to determine whether it was successful. If it was not, the results can be stored on the Web server for later analysis. Custom Logging The HTTP Logging feature provides a default text-based format for storing Web request information. Although this can meet the basic needs for most Web sites and services, organizations can also create their own COM-based modules, using the Custom Logging option. Developers will need to build the logging module and then register it with IIS for it to store data. This approach provides the greatest flexibility in determining which details are important to record. ODBC Logging Although storing data in a text file is an efficient method of logging requests, it makes the process of analyzing and reporting on Web server performance

31 Lesson 1: Installing the Web Server (IIS) Role 19 difficult. The ODBC Logging role service enables applications to store Web request data in any format that is supported by an Open Database Connectivity (ODBC) connection. Examples include relational database servers such as Microsoft SQL Server and filebased formats such as Microsoft Excel. It is important to note, however, that logging to ODBC-based sources can cause significant processing and storage overhead, especially on busy Web servers. By default, all these features are enabled except for Custom Logging and ODBC Logging. Web administrators often use log analyzer applications to process the text-based log files that store request information. Details can be used to isolate problems (such as erroneous links or missing content) as well as to analyze traffic and the popularity of specific Web pages. Security Features Maintaining security for Web sites, Web applications, and Web services is an important concern with all Web servers. Depending on the specific deployment and usage configuration, organizations can enable a wide variety of security mechanisms. The Security role services that are available for IIS include: Basic Authentication Windows Authentication Digest Authentication Client Certificate Mapping Authentication IIS Client Certificate Mapping Authentication URL Authorization Request Filtering IP and Domain Restrictions Selecting and implementing these security mechanisms is covered in Chapter 3, Managing Web Services Security. Performance Features Organizations often find that they receive a large volume of activity on their production Web servers, so it is fundamental for all types of Web servers to be able to service a large number of requests in a given amount of time. IIS includes numerous architectural features that help make the servicing of Web requests as efficient as possible. In addition, the Performance role services section includes two additional options: Static Content Compression The HTTP protocol provides a method by which unchanging Web pages can be compressed before they are sent to clients Web browsers. The Web browser expands the information and renders the Web page. This method can save significant bandwidth with a minimal cost to CPU performance on the client and the

32 20 Chapter 2 Installing and Configuring Web Applications server. In addition, IIS has the ability to store frequently accessed static content in memory, further increasing performance and scalability. This feature is enabled by default and will work automatically as long as users Web browsers support HTTP compression. Dynamic Content Compression Dynamic content usually results in different information being sent to different users. Because dynamic content often changes for each request that is made to the Web server, the amount of processing overhead for compressing the data can be significant. Dynamic content compression is disabled by default, but it can be added to help reduce bandwidth consumption for Web applications. In general, bandwidth is more limited than is processing power on modern servers. Therefore, unless an organization has a specific reason to disable it, it is recommended that static content compression remain enabled. Management Tools The Management Tools section provides administrators with the ability to determine which programs will be available for working with IIS. By default, only the primary administration tool, the IIS Management Console, is installed along with the Web Server (IIS) role. This tool provides a graphical method of configuring and managing IIS Web services. You can choose to remove the IIS Management Console if you will be managing the server remotely or if your corporate security policy requires it. The other available Management Tools options include IIS Management Scripts and Tools, which allows for command-line administration of IIS, and the Management Service, which enables you to administer IIS remotely using the IIS Management Console. An important design goal for IIS 7.0 was to provide support for IIS 6.0 based Web applications. Although many applications can be moved directly to IIS 7.0, there are several backwardcompatibility features that are included as role services: IIS 6 Management Compatibility IIS 6 Metabase Compatibility IIS 6 WMI Compatibility IIS 6 Scripting Tools IIS 6 Management Console You ll learn more about these features and how you can use them in Lesson 2, Configuring Internet Information Services.