This step-by-step guide illustrates how to deploy Active Directory® Group Policy objects (GPOs) to configure Windows Firewall with Advanced Security in Windows Vista® and Windows Server® 2008. Although you can configure a single server locally by using Group Policy Management tools directly on the server, that method is not consistent or efficient when you have many computers to configure. When you have multiple computers to manage, create and edit GPOs, and then apply those GPOs to the computers in your organization. The goal of a Windows Firewall with Advanced Security configuration in your organization is to improve the security of each computer by blocking unwanted network traffic from entering the computer. Network traffic that does not match the rule set of Windows Firewall with Advanced Security is dropped. You can also require that the network traffic which is allowed must be protected by using authentication or encryption. The ability to manage Windows Firewall with Advanced Security by using Group Policy allows an administrator to apply consistent settings across the organization in a way that is not easily circumvented by the user. In this guide, you get hands-on experience in a lab environment using Group Policy management tools to create and edit GPOs to implement typical firewall settings. You also configure GPOs to implement common server and domain isolation scenarios and see the effects of those settings.

Storage Manager for SANs is a Microsoft Management Console (MMC) snap-in that helps you create and manage logical unit numbers (LUNs) on Fibre Channel and Internet SCSI (iSCSI) disk drive subsystems that support Virtual Disk Service (VDS) in your storage area network (SAN). Before you deploy Storage Manager for SANs on a production server, we recommend that you use this guide to first familiarize yourself with the different LUN management options in Storage Manager for SANs by installing and running it on a test server.

With the increasing demand on storage resources, as organizations rely more heavily on data than ever before, IT administrators face the challenge of overseeing a larger and more complex storage infrastructure, while at the same time, tracking the kind of information available in it. Today, managing storage resources not only includes data size and availability but also the enforcement of company policies and a very good understanding of how existing storage is being used, allowing for sound strategic planning and proper response to organizational changes. File Server Resource Manager is a suite of tools that allows administrators to understand, control, and manage the quantity and type of data stored on their servers. By using File Server Resource Manager, administrators can place quotas on volumes, actively screen files and folders, and generate comprehensive storage reports. This set of advanced instruments not only helps the administrator to efficiently monitor existing storage resources, but it also aids in the planning and implementation of future policy changes.

Terminal Services Web Access (TS Web Access) is a role service in the Windows Server® 2008 operating system that enables users to access RemoteApp™ programs or the full terminal server desktop from a Web site. By default, the TS Web Access Web site enables you to point to a single terminal server or to a single terminal server farm to populate the list of RemoteApp programs that appear on the site. If you have multiple terminal servers or multiple terminal server farms, you can use Windows® SharePoint® Services to create a single Web access point for RemoteApp programs and full terminal server desktop connections that are available on different terminal servers. You can customize a Windows SharePoint Services site by adding multiple TS Web Access Web Parts, each pointing to a different terminal server or terminal server farm.

This step-by-step guide provides instructions for building a server in your test lab that is based on the Server Core installation option of the Windows Server® 2008 operating system. It includes information about installation, initial configuration, and managing a server that is running a Server Core installation.

Server Manager is a new tool available with Windows Server® 2008 that guides information technology administrators through the process of installing, configuring, and managing server roles and features that are part of Windows Server 2008. This step-by-step guide provides an overview of Server Manager and walkthroughs of several common scenarios for using Server Manager in your enterprise, focusing on new and enhanced features of Server Manager. This guide helps you learn about how Server Manager functions as a server role deployment, decommissioning, and management tool. The guide also describes how Server Manager helps improve productivity, so IT pros can spend less time deploying, managing, and maintaining their infrastructures, and spend more time using Windows Server 2008 software packages to add business value. The scenarios described in this step-by-step guide include initial server configuration tasks as well as deployment, management, and removal of server roles and features.

This step-by-step walks you through the process of decommissioning Active Directory Rights Management Services (AD RMS) in your organization. Removing AD RMS requires that all rights-protected content that you want to be able to use be decrypted before all servers are removed from the AD RMS cluster. Once complete, you can use the test lab environment to learn about AD RMS decommissioning on Windows Server® 2008 and assess how it might be deployed in your organization. As you complete the steps in this guide, you will: · Decommission an AD RMS cluster. · Verify the removal of AD RMS functionality after you complete the configuration. This guide assumes that you previously completed the steps in the Windows Server Active Directory Rights Management Services Step-by-Step Guide (http://go.microsoft.com/fwlink/?LinkId=72134), and that you have already deployed the following components: · An AD RMS server · An AD RMS database server · One AD RMS-enabled client · One Active Directory domain controller