Microsoft Windows Server 2008 R2 Administration Instant Reference E-Book

Matthew Hester

• Herausgeber: John Wiley & Sons
• Kategorie: Wissenschaft und neue Technologien
• Sprache: Englisch

Seitenzahl: 638

Veröffentlichungsjahr: 2010

Beschreibung

All your Windows Server 2008 R2 questions answered--on the spot! Get up to speed on the new features of Windows Server 2008 R2 with this indispensableguide. Designed for busy IT professionals, it's the perfect go-to resource for quick answers and real-world solutions as you administer the new server OS. You'll find easy-to-read lists, quick-reference tables, helpful thumb tabs, and much more in a handy, compact format that puts the information you need at your fingertips. Topics include: * Getting started and adding roles and functionality * Automating tasks * Managing users, groups, directories, and the centralized desktop * Handling folder security, disk management, storage, backup, and recovery * Monitoring and maintaining web servers * Troubleshooting IP and managing remote access * Doing performance tuning and maintaining virtual servers

Leseprobe

Table of Contents

Cover

Title Page

Credits

Copyright

Publisher's Note

Dedication

Acknowledgments

About the Authors

Introduction

Who Should Read This Book

How to Contact the Authors

Part I: Getting Started

Chapter 1: Getting Started with Windows Server 2008 R2

Plan for Windows Server 2008 R2

Install Windows Server 2008 R2

Migrate to Windows Server 2008 R2

Chapter 2: Adding Server Roles and Functionality

Plan for Windows Server 2008 R2 Roles

Install Windows Server 2008 R2 Roles

Migrate Roles to Windows Server 2008 R2

Chapter 3: Automating Administrative Tasks with Windows Server 2008 R2

Learn the Basics of Windows PowerShell v2

Use PowerShell Remoting

Learn PowerShell Integrated Scripting Environment (ISE)

Part II: Manage Active Directory and Local Users

Chapter 4: User and Group Maintenance

Understand Local Users and Groups

Understand Active Directory Users and Groups

Automate User and Group Management

Chapter 5: Managing and Replicating Active Directory

Manage the Active Directory Database

Understand Active Directory Replication

Chapter 6: Maintaining and Controlling the Centralized Desktop

Understand Group Policy

Administer Group Policy

Troubleshoot Group Policy

Part III: Data Access and Management

Chapter 7: Configuring Folder Security, Access, and Replication

Implement Permissions

Share Folders

Configure Offline File Caching

Secure Folders and Files

Implement the Distributed File System

Chapter 8: Backing Up and Recovering Your Server

Understand Backup and Recovery

Manage Backup and Recovery

Perform Backup and Recovery with Command Tools

Chapter 9: Managing Disks and Disk Storage

Understand the Basics

Work with RAID Volumes

Manage Disk Storage

Part IV: Network Configuration and Communication

Chapter 10: Maintaining Your Web Server

Install Internet Information Services

Manage Internet Information Services

Work with Websites

Chapter 11: Administering DNS

Add and Remove DNS Servers

Manage a DNS Server

Troubleshoot DNS

Chapter 12: Troubleshooting TCP/IP

Understand TCP/IP Basics

Troubleshoot TCP/IP

Troubleshoot IPV6

Troubleshoot IPV4

Part V: Manage Desktop and Server Virtualization

Chapter 13: Managing Remote Access to Your Server

Understand Remote Desktop Services

Manage Remote Desktop Services

Work with Remote Clients

Chapter 14: Maintaining Virtual Machines

Understand Virtualization with Hyper-V

Build Virtual Machines

Part VI: Server Tuning and Maintenance

Chapter 15: Tuning and Monitoring Performance

Analyze Server Roles

View Server Performance Data

View Server Events

Chapter 16: Keeping Your Servers Up-to-Date

Work with Windows Updates

Work with Windows Server Update Services

Index

Acquisitions Editor: Agatha Kim

Development Editor: Kim Beaudet

Technical Editor: Harold Wong

Production Editor: Dassi Zeidel

Copy Editor: Kim Wimpsett

Editorial Manager: Pete Gaughan

Production Manager: Tim Tate

Vice President and Executive Group Publisher: Richard Swadley

Vice President and Publisher: Neil Edde

Book Designer: Maureen Forys, Happenstance Type-O-Rama

Compositor: Craig Johnson, Happenstance Type-O-Rama

Proofreader: Josh Chase, Word One New York

Indexer: Jack Lewis

Project Coordinator, Cover: Lynsey Stanford

Cover Designer: Ryan Sneed

Cover Image: iStockphoto

Copyright © 2010 by Wiley Publishing, Inc., Indianapolis, Indiana

Published simultaneously in Canada

ISBN: 978-0-470-52539-5

No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning or otherwise, except as permitted under Sections 107 or 108 of the 1976 United States Copyright Act, without either the prior written permission of the Publisher, or authorization through payment of the appropriate per-copy fee to the Copyright Clearance Center, 222 Rosewood Drive, Danvers, MA 01923, [phone], fax [phone]. Requests to the Publisher for permission should be addressed to the Permissions Department, John Wiley & Sons, Inc., 111 River Street, Hoboken, NJ 07030, [phone], fax [phone], or online at http://www.wiley.com/go/permissions.

Limit of Liability/Disclaimer of Warranty: The publisher and the author make no representations or warranties with respect to the accuracy or completeness of the contents of this work and specifically disclaim all warranties, including without limitation warranties of fitness for a particular purpose. No warranty may be created or extended by sales or promotional materials. The advice and strategies contained herein may not be suitable for every situation. This work is sold with the understanding that the publisher is not engaged in rendering legal, accounting, or other professional services. If professional assistance is required, the services of a competent professional person should be sought. Neither the publisher nor the author shall be liable for damages arising herefrom. The fact that an organization or Web site is referred to in this work as a citation and/or a potential source of further information does not mean that the author or the publisher endorses the information the organization or Web site may provide or recommendations it may make. Further, readers should be aware that Internet Web sites listed in this work may have changed or disappeared between when this work was written and when it is read.

For general information on our other products and services or to obtain technical support, please contact our Customer Care Department within the U.S. at [phone], outside the U.S. at [phone] or fax [phone].

Wiley also publishes its books in a variety of electronic formats. Some content that appears in print may not be available in electronic books.

Library of Congress Cataloging-in-Publication DataHester, Matthew, 1971- Windows server 2008 R2 administration instant reference / Matthew Hester, Chris Henley. — 1st ed. p. cm. ISBN 978-0-470-52539-5 (pbk.) 1. Microsoft Windows server. 2. Operating systems (Computers) I. Henley, Chris. II. Title. QA76.76.O63H496 2010 005.4’476—dc22 2009043725

TRADEMARKS: Wiley, the Wiley logo, and the Sybex logo are trademarks or registered trademarks of John Wiley & Sons, Inc. and/or its affiliates, in the United States and other countries, and may not be used without written permission. Windows Server is a registered trademark of Microsoft Corporation in the United States and/or other countries. All other trademarks are the property of their respective owners. Wiley Publishing, Inc., is not associated with any product or vendor mentioned in this book.

10 9 8 7 6 5 4 3 2 1

Dear Reader,

Thank you for choosing Windows Server 2008 R2 Administration Instant Reference. This book is part of a family of premium-quality Sybex books, all of which are written by outstanding authors who combine practical experience with a gift for teaching.

Sybex was founded in 1976. More than 30 years later, we’re still committed to producing consistently exceptional books. With each of our titles, we’re working hard to set a new standard for the industry. From the paper we print on to the authors we work with, our goal is to bring you the best books available.

I hope you see all that reflected in these pages. I’d be very interested to hear your comments and get your feedback on how we’re doing. Feel free to let me know what you think about this or any other Sybex book by sending me an email at [email protected]. If you think you’ve found a technical error in this book, please visit http://sybex.custhelp.com. Customer feedback is critical to our efforts at Sybex.

Best regards,

Neil EddeVice President and PublisherSybex, an Imprint of Wiley

To Deb, for all of your love and support. I could not have done it without you. It means so much to me that you are on this journey with me. I love you!To Nicole, Mitchell, and Caitlin for all your patience when I was in my office writing. You are the best children a dad could wish for, thank you and I love you guys.

—Matthew Hester

To Julie, my best friend, thanks for seeing my potential and helping me realize it! All that I am I owe to you!

To Megan, Nicholas, and Lauren for helping me remember that all things have been done in the wisdom of him who knoweth all things. It is my pleasure to be your father!

—Chris Henley

Acknowledgments

I  would like to thank my friend and mentor Kerrie Meyler for guiding me through the process of writing and providing much needed happy hours and awesome advice. Thanks, Kerrie, for everything. I would also like to acknowledge Harold Wong for making sure Chris and I wrote the best book possible and for keeping us on the straight and narrow. I would also like to thank all the wonderful editors and staff at Sybex, thank you for giving Chris and I the chance. Lastly, and most important, I want to acknowledge one of the best coauthors I could ask for, Chris Henley. Thanks for doing this project with me, and I look forward to more from H&H productions.

—Matthew Hester

I  would also like to acknowledge the efforts of Harold Wong for his technical suggestions and experience, which have been significant contributions to this work. The production team at Sybex deserves a huge thank you for taking a chance on me and bringing me patiently through the process of getting this book to the presses. Thank you! I also would like to acknowledge the efforts of Matt Hester—a great coauthor, mentor, peer, and friend. Thanks for a great opportunity to work together! I look forward to many more successful projects together!

—Chris Henley

About the Authors

Matt Hester is a seasoned Information Technology Professional Evangelist for Microsoft and has been involved in the IT Pro community for more than 15 years. In his role at Microsoft, Matt has presented to audiences nationally and internationally as large as 5,000 people and as small as 10. Prior to joining Microsoft, Matt was a highly successful Microsoft Certified Trainer for more than eight years. Matt has also published several articles for TechNet magazine and runs a successful blog with about 350,000 touches a month. In his spare time, Matt is a movie buff with a massive DVD collection. He also runs marathons and dreams of joining the PGA tour. Matt cites his father as his role model: “The older I get, the smarter he gets.” Funny how that works.

Chris Henley is an entertaining and energetic proponent of technology who has worked in IT for more than 15 years. Chris loves to talk about how technology changes people’s lives for the better. He believes that with the right vision and the right technology, anything is possible. In addition, Chris has spent the last five years acting as an Information Technology Professional Evangelist for Microsoft specializing in client and server technologies. He loves speaking to audiences of all sizes and says, “There is no other experience that can compare with speaking to a large audience and helping them understand the possibilities that a new piece of technology can avail them.” Chris loves to spend time in the outdoors with his wife and three children. Camping, fishing, hiking, skiing, biking, and chocolate are his favorite pastimes.

Introduction

Administering and maintaining servers can sometimes appear daunting. In fact, a lot of industry studies say a majority of IT resources (such as budget, personnel, and time) are spent just maintaining existing servers and infrastructure. As administrators, we also do not always have the time to learn how new technologies can improve our day-to-day tasks, and we often rely on the status quo the server can provide.

Although this book is not designed to dig deep into the details behind Windows Server and server technologies, it will provide you with a quick and easy reference to many of the tasks you perform daily. This book will also get you quickly up to speed with many of the new features in Windows Server 2008 R2 as well as show you how Windows Server 2008 R2 can improve your daily administrative tasks.

You will notice that the book is organized specifically to help you find information quickly. It is organized into parts that categorize chapters into major topics. Then each chapter deals with a specific subject. At the beginning of each chapter, you will see what the chapter will cover and where you will find it in the pages. This method of organization is designed to assist you in finding the information that you need to solve immediate problems or begin a process as painlessly as possible. Ideally, this book will become part of your everyday tool belt, something that you can pick up whenever you need a quick reference or a reminder.

We hope you enjoy this book.

Who Should Read This Book

This book is designed for anyone who administers a Windows server environment. It is for experienced and new administrators alike. This book is also for administrators looking to learn how to use many of the new enhancements Windows Server 2008 R2 can bring to their existing networks. This book will show administrators how to improve many of the day-to-day tasks of server administration.

This book will provide guidance for many common server tasks, such as setting up Group Policy and backing up and recovering your server. This book will also show you many of the new and improved features built in to Windows Server 2008 R2 to help you improve server administration and management.

How to Contact the Authors

We welcome feedback from you about this book or about books you’d like to see from us in the future. You can reach us by writing to Matt at [email protected] or to Chris at [email protected]. You can also contact us via our blogs at http://blogs.technet.com/matthewms/ or http://blogs.technet.com/chenley/.

For more information about our work, please visit our websites:

http://blogs.technet.com/matthewms/

http://blogs.techent.com/chenley/

Sybex strives to keep you supplied with the latest tools and information you need for your work. Please check its website at www.sybex.com, where we’ll post additional content and updates that supplement this book if the need arises. Enter Microsoft Windows Server 2008 R2 Administration Instant Reference in the search box (or type the book’s ISBN, 978-0-470-52539-5), and click Go to get to the book’s update page.

Part I

Getting Started

In This Part

Chapter 1: Getting Started with Windows Server 2008 R2

Chapter 2: Add Server Roles and Functionality

Chapter 3: Automating Administrative Tasks with Windows Server 2008 R2

Chapter 1

Getting Started with Windows Server 2008 R2

In this chapter, you will learn to:

Plan for Windows Server 2008 R2 Understand Hardware Requirements Understand Windows Server 2008 R2 Editions and Roles Consider Your Licensing Options Install Windows Server 2008 R2 Perform a Windows Server 2008 R2 Full Installation Perform a Windows Server 2008 R2 Server Core Installation Upgrade to Windows Server 2008 R2 Install Windows Server 2008 R2 Server Unattended Migrate to Windows Server 2008 R2 Install Windows Server 2008 R2 Migration Tools Migrate to Windows Server 2008 R2

Every release of Windows Server has offered numerous features and functionality to assist administrators and companies with their day-to-day tasks. Each new release has offered plenty of new functionality but has also increased the administrative burden for the servers. Windows 2000 Server laid the foundation for Active Directory. Windows Server 2003 became the first dedicated server platform from Microsoft. Windows Server 2008 sought to offer flexibility for our servers by providing role-based deployment included streamlined new roles like Server Core.

Windows Server 2008 R2, an incremental release of the operating system, continues to build upon prior releases of the server platform. Windows Server 2008 R2 provides many new and increased capabilities for a powerful server environment. From improvements in Hyper-V with the addition of live migration to better power management capabilities to improvements in IIS to features such as DirectAccess designed to work specifically with Windows 7, Windows Server 2008 R2 has a lot to offer you.

However, even with the addition of all these capabilities, Windows Server 2008 R2’s true benefits are for administrators and to improve the day-to-day tasks of administrators.

Before you begin to dig into the day-to-day improvements of administrative tasks, it is important to understand how the server was built so you can properly administer it. Do you need to install a new server? Do you perform an in-place upgrade? Do you migrate existing services like DNS, Active Directory, or printers? These are all vital questions that need to be answered so you can start to take advantage of the administrative improvements in Windows Server 2008 R2. This chapter will take a brief look at planning, installing, and upgrading to Windows Server 2008 R2. You will also learn about installing the migration tools.

Plan for Windows Server 2008 R2

You have probably heard this phrase 1,000 times (well, make this a 1,001): “If you fail to plan, you plan to fail.” Having a solid idea what role the server will play is important to the health of IT as well as your sanity. Some of the decisions you make during the planning process can impact the installation phase. If your planning is off, then your installation will be off. Although fixing most installation problems can be straightforward, some can become quite complex to fix, if not completely irreversible. Everyone has done the “FDISK, format, reboot” dance of destruction at least once to fix the wrong decisions.

In this section, you will look at the hardware requirements and recommendations for a Windows Server 2008 R2 server installation. You will also learn about the roles and features that a Windows Server 2008 R2 server can perform. In addition to the resources mentioned in this chapter, Microsoft offers several free tools to assist you in your planning process. These assessment tools are included in the Microsoft Assessment and Planning (MAP) Toolkit:

http://technet.microsoft.com/en-us/solutionaccelerators/dd537566.aspx?SA_CE=NOT-MAPBETA-SITE-TNETWINSVR-20090615

Understand Hardware Requirements

Like its predecessors, Windows Server 2008 R2 offers numerous roles and editions of the server operating system. There is one important distinction in this version; it will be released only in 64-bit versions. This means before you even start, you need to have the proper hardware to support the operating system. This requirement will also dictate upgrade and migration paths. Table 1-1 shows the base hardware requirements for Windows Server 2008 R2.

Table 1-1: Windows Server 2008 R2 Minimum Hardware Requirements

ResourceRequirement Processor 1.4GHz x64 processor Memory 512MB RAM Drive space 10GB Drive DVD-ROM Display and others Super VGA 800×600 or higherKeyboard and mouse

These are just the bare minimum to get the server up and running. I highly recommend you take a look at Table 1-2 for additional recommendations for processor memory and hard drive space. These will offer a base system with solid performance and flexibility for additional functions.

Table 1-2: Additional Hardware Recommendations

ResourceRecommendation Processor 2GHz x64 dual-core processor Memory 4GB RAM Drive space 100GB

You need to be aware of a few important facts about the requirements. The amount of memory you can put into the server depends on the chosen operating system. If you have chosen Windows Server 2008 R2 Datacenter or Enterprise edition, you can install up to 2TB of RAM. Other versions are limited to 32GB RAM. Additionally, if you have more than 16GB RAM, you will need more hard drive space to support various system functions such as paging. Also, the edition controls the maximum number of processor cores the system can have. The Web and Standard editions are limited to 4, Enterprise edition can have up to 8, and Datacenter edition can have up to 64, and Itanium-based systems can have up to 64 IA64 sockets.

You should always look at the base requirements as the bare minimum to get the server operating system up and running. Generally speaking, these minimum requirements do not take into the account the workload you will be placing on the server. You should always consider the roles and applications that will be loaded on the server. You should consider the recommendations and requirements for those applications as additional resources to those listed in Table 1-1. This will allow you to have servers that will perform satisfactorily and meet your needs, while having a little room to grow.

If the server role you have selected is going to be used for virtualization workloads, ensure you have enough RAM and processor cores to support the Windows Server 2008 R2 operating system as well as the virtual servers running on the server. How many servers, what types of servers, and what types of applications are all factors you need to look carefully at when planning a virtualization server. One last note of concern for a virtualization server: whether you have chosen to use VMware or Hyper-V virtualization technologies, make sure your processor hardware supports hardware-assisted virtualization. Either AMD Virtualization (AMD-V) or Intel Virtualization Technology (Intel VT) will work. These technologies typically also have to be enabled in the BIOS because they are generally not enabled by default. Enabling the virtualization will normally require a full hard reboot to take effect. Make sure you have enabled these technologies before installing your virtualization technology.

Understand Windows Server 2008 R2 Editions and Roles

Windows Server 2008 R2 is offered in the same editions as in Windows Server 2008, namely, Datacenter, Enterprise, Standard, Itanium-based systems, and Web. One notable difference is that Windows Server 2008 R2 has the next version of Microsoft’s Hyper-V technologies included in Windows Server 2008 R2 Standard, Enterprise and Datacenter editions, and does not offer separate editions without Hyper-V. Table 1-3 gives an overview of the Windows Server 2008 R2 editions available.

Table 1-3: Windows Server 2008 R2 Editions

EditionOverview Datacenter Designed for large-scale enterprise applications or virtualization workloads, this edition is really for large scale-up operations. Enterprise This edition supports mission-critical applications as well as providing clustering capabilities. This server will fit most of your infrastructure needs. Standard This edition supports mission-critical applications and will fit most of your infrastructure needs. Itanium-based systems This edition is designed and optimized for large databases and critical line-of-business applications. Web This edition is a specifically designed server for website services.

This is just a brief rundown of the systems. For a full comparison, see http://www.microsoft.com/windowsserver2008/en/us/compare-features.aspx.

Once you have chosen the right edition for your needs, then you need to look at the services the server will provide for your infrastructure. These services come in the form of roles. Windows Server 2008 R2, like Windows Server 2008, provides several server roles that can be installed on the server. A role is a set of software features and functions that provides services for your server and infrastructure. Some of these roles also require some additional planning to have a stable and reliable environment.

Table 1-4 describes the server roles.

Table 1-4: Windows Server 2008 R2 Server Roles

RoleFunction Active Directory Certificate Services (AD CS) Allows for the creation of certificate authorities. This role allows you to host your own Public Key Infrastructure (PKI) on the server. Active Directory Domain Services (AD DS) Provides single sign-on (SSO) capabilities for your network and network services. This allows for the creation of objects (users, groups, computers, and so on) for use with network authentication and authorization. Active Directory Federation Services (AD FS) Provides single sign-on capabilities across multiple forests and domains. Additionally, this role provides web single sign-on. Active Directory Lightweight Directory Services (AD LDS) Commonly referred to as ADAM, is a lightweight version of AD DS. This role allows for the storage of a base directory used for specific applications. Active Directory Rights Management Services (AD RMS) Allows you to provide authorization and verification services to users to access protected content. Application Server Provides the ability to have high-performance distributed applications (mainly applications that use the .NET Framework). DHCP Server Provides automatic TCP/IP address services for your network. DNS Server Provides name and service resolution services for TCP/IP networks. This is a core component for AD DS, and it is highly recommended you use this built-in service for your domain controllers. Fax Server Allows for basic fax functions to be hosted on the server, such as sending, receiving, and reporting. File Services Provides many services for the file system, including replication, managing shares, and faster file searches. This role also provides services for UNIX clients to access files on the server. Hyper-V Provides the ability to create, manage, and perform live migration of virtual machines. Virtual machines operate on the host machine and are servers without the hardware. Network Policy and Access Services Provides resources for routing and remote access. This service also provides the framework for Network Access and Protection (NAP) and DirectAccess. Included in this service are two core components: Health Registration Authority and the Host Credential Authorization protocol. Print and Document Services Provides the ability for a centralized print server as well as management for printers. This service also installs the necessary Group Policy objects for printer management through Group Policy. Remote Desktop Services Provides the ability for your users to access the Remote Desktop Services on your server. These services provide presentation virtualization for your thin clients. Formerly called Terminal Services. Web Server (IIS) Provides the core infrastructure for a web server. Windows Deployment Services Installs the services for deploying Windows operating systems across the network. Windows Update Services (WSUS) Provides the management framework for Microsoft updates. This service allows you to deploy updates in a variety of options across your network.

NOTE Table 1-4 gives only a brief explanation of all the services available to Windows Server 2008 R2. For more details, please take a look at Chapter 2. You can also get more explanation of the roles at http://technet.microsoft.com/en-us/windowsserver/2008/default.aspx.

One last consideration regarding roles is that they are also dependant on what edition of Windows Server 2008 R2 you have installed. The edition you choose to install will determine which roles are available to the server and will also determine the hardware requirements. Table 1-5 describes the which roles the editions support and the additional hardware considerations. For a full role comparison table, take a look at the Microsoft site at http://www.microsoft.com/windowsserver2008/en/us/compare-roles.aspx.

Table 1-5: Windows Server 2008 R2 Edition Requirements

EditionRole ConsiderationsAdditional Hardware Considerations Web edition As the name implies, this server is designed to be a web server only. It has the ability to install two roles: DNS Server and Web Server. Limited to 4 processors and up to 32GB of RAM Standard edition Contains all the roles listed in Table 1-4, with one exception; Standard edition does not contain the Active Directory Federation Services. Additionally, the following services have limited capabilities: Active Directory Certificate Services, File Services, Network Policy and Access Services, and Remote Desktop Services. Limited to 4 processors and up to 32GB of RAM Enterprise edition Contains all the roles listed in Table 1-4. Limited to 8 processors and up to 2TB of RAM Datacenter edition Contains all the roles listed in Table 1-4. Limited to 64 processors and up to 2TB of RAM

Understand Server Core

There is also one installation option of the previously mentioned editions worth mentioning: Windows Server 2008 R2 Server Core. Like in Windows Server 2008, Windows Server 2008 R2 Server Core is a very streamlined version of Windows Server. Server Core has limited functionality and runs a subset of the roles provided by Windows Server 2008 R2. Server Core also does not have a GUI. This means all the administration is either done remotely or via a command prompt. This by no means implies that Server Core does not have usefulness in the network. The Server Core role provides a nice addition to your network without the overhead of a traditional server. This lowers the overall maintenance and security risks for the server. Server Core can also reduce the amount of patching that is required to keep the server up-to-date. The server provides support for these nine roles:

DNS ServerDHCP ServerActive Directory Domain Services (AD DS)Active Directory Lightweight Directory Services (AD LDS)File ServicesPrint and Document ServicesWeb Server (IIS)Active Directory Certificate Services (AD CS)Hyper-V

Windows Server 2008 R2 provides several new features to extend the functionality of Server Core. In Windows Server 2008 R2 Server Core, you can also now install the following:

A subset of the .NET Framework, versions 2.0, 3.0, and 3.5 PowerShellASP.NET, the same that is included in IISWoW64, required for Active Directory and Active Directory Lightweight Directory Services

Consider Your Licensing Options

When you install Windows Server 2008 R2 into your environment, you have to take into account the licensing. Overall, the licensing model has not really changed for Windows Server 2008 R2 from Windows Server 2008. Every Windows Server 2008 R2 requires two types of licenses. First, you need a server license for the rights to run the operating system, and second, you need a client access license (CAL) to allow your clients to access the server. CALs come in two flavors:

The device CAL allows access for one device for any user.The user CAL allows access for one user on any device.

Depending on your existing licensing, you may already be covered for Windows Server 2008 R2. In Windows Server 2008 R2, all of your existing CALs for Windows Server 2008 will allow you to access Windows Server 2008 R2. Again, this is very unique to this release.

There are some important licensing considerations when you use virtualization technologies inside your network. If Windows Server 2008 R2 is solely used for virtualization servers, you do not need to have CALs for the host operating system. However, you will still need CALs for the guest operating systems running on the server. There is one last potential licensing benefit for using Hyper-V on Windows Server 2008 R2. Depending on which edition you have chosen, you may not need to purchase server licenses for your virtualized instances of Windows Server 2008 R2. If you are using Windows Server 2008 R2 Enterprise edition, you are allowed to run one virtualized instance of Windows Server 2008 R2 under your server license. If you are using Windows Server 2008 R2 Enterprise edition, you are allowed to run up to four virtualized instances of Windows Server 2008 R2 under your server license. If you are using Windows Server 2008 R2 Datacenter or Itanium editions, you are allowed to run unlimited virtualized instances of Windows Server 2008 R2 under your server license. For more details and specific license questions and pricing, contact your Microsoft reseller.

Install Windows Server 2008 R2

After you have planned your environment, it is now time to install Windows Server 2008 R2. The installation process is fairly straightforward. This is mainly because of the role-based nature of Windows Server 2008 R2. You will learn more about installing roles in Chapter 2.

Perform a Windows Server 2008 R2 Full Installation

In this section, you will take a step-by-step look at the installation process for a Windows Server 2008 R2 full installation. We’ll cover the key decisions you need to be aware of as you install the operating system.

1. Insert the DVD media into the drive, and reboot the system. Upon reboot, you will see the screen shown in Figure 1-1.

Figure 1-1:Selecting your language

2. Select your chosen language, time/currency, and keyboard method, and then click Next. You will see the screen shown in Figure 1-2.

Figure 1-2:Starting the installation

This screen provides the option to install Windows Server 2008 R2 by clicking the Install Now button. There are also two other options to notice. The What To Know Before Installing Windows option provides some last-minute help documentation. The Repair Your Computer option takes you to the repair and diagnostics functions of Windows Server 2008 R2. To continue the installation, click the Install Now button.

3. The next window you see (Figure 1-3) provides you with the choice to install your edition of Windows Server 2008 R2. You can choose to install the full edition of Windows Server 2008 R2 or the Server Core version. Select your version, and click Next.

Figure 1-3:Selecting your Windows Server 2008 R2 version

WARNING If you choose Server Core, you will not be able to upgrade to a full version directly without performing a full reinstall of the server. You will, however, have the ability to use migration tools to migrate the server’s functions to a full installation of Windows Server 2008 R2.

4. Clicking the Next button will take you to the license agreement screen. This screen, shown in Figure 1-4, allows you to read, print, and agree to the license terms. Select the check box on the bottom left of the dialog box to agree to the license terms, and click Next to continue.

Figure 1-4:Licensing terms

5. The screen shown in Figure 1-5 provides you with the choice between performing an upgrade or custom installation of Windows Server 2008 R2. To perform a new installation, click Custom, and you will be taken to the next step.

Figure 1-5:Upgrading or customizing

6. The next screen, displayed in Figure 1-6, allows you to choose the location for your Windows Server 2008 R2 installation. This screen also allows you to load drivers for your SCSI hard drives.

If you are installing on a hard drive connected to a SCSI controller, select Load Driver, and insert the media with the drivers on it. You also have a full set of drive partitioning and formatting options. When you click the drive on which you want to install Windows Server 2008 R2, you are presented with the options to create new partitions or delete, format, or extend existing partitions, as shown in Figure 1-6. Choose the appropriate option, and click Next. If you do not select a partition and the only option you have is unallocated space, then the Windows Server 2008 R2 installation will create a partition on that drive by taking all the unallocated space and formatting it for you automatically with NTFS. Windows Server 2008 R2 will also automatically make a system partition of 200MB in size during this step. The 200MB partition is not assigned a drive and will not be visible in the OS. The partition holds the Windows boot files for the Windows recovery environment (winRE).

Figure 1-6:Selecting a drive and partition

7. When you select your partition, the installation will begin, and you will see a screen similar to Figure 1-7. The system may also reboot several times during this phase of installation.

Figure 1-7:Windows installation progress

8. After the final system reboot, you will be asked to configure the administrator’s password, and you will see screen similar to Figure 1-8.

Figure 1-8:Initial change of password logon

9. After you click OK, you will see a screen similar to Figure 1-9. Now you will set your administrator password. The password needs to be complex. This means the initial password needs to meet the following requirements:

Cannot contain the user’s account name or parts of the user’s full name that exceed two consecutive charactersBe at least six characters in lengthContain characters from three of the following four categories: English uppercase characters (A through Z)English lowercase characters (a through z)Base 10 digits (0 through 9)Nonalphabetic characters (for example !, $, #, or %)

There is also an option for you to create a password reset disk. By clicking this option, you can create a recovery disk, which allows you to create a new password for the user ID. You have to create this disk only once, no matter how many times the password for the account changes.

Figure 1-9:Logon window/password reset disk

After you have set the password, the Windows Server 2008 R2 installation will complete, and you will see a screen with the initial configuration tasks, as shown in Figure 1-10.

Creating a Password Reset Disk

1. Click the link Create A Password Recovery Disk. This will start the Forgotten Password Wizard.

2. Read the welcome screen, and click Next.

3. Select the drive for the password recovery disk, and click Next.

4. Type in the password for the existing user. If one exists during install, chances are you will leave this field blank and click Next.

5. You will briefly see a progress screen. When the progress reaches 100 percent, click Next.

6. Read the summary screen, and click Finish.

WARNING Although I hope you should never need the password recovery disk, it is nice to have in case of an emergency. However, it is also very important to keep the disk in a safe and secure location. It is important because anyone who can access the disk can use it to recover the password and therefore gain access to the account.

Figure 1-10:Initial configuration tasks

Perform a Windows Server 2008 R2 Server Core Installation

Installing Windows Server 2008 R2 Server Core follows a similar process as the previous steps. The only difference comes in step 3 where you would select Server Core Installation instead of Full Installation for your edition of Windows. You will learn how to add roles in Chapter 2.

Use Sconfig to Configure Your Windows Server 2008 R2 Server Core

After you install Windows Server 2008 R2 Server Core, you need to configure the basics of the server, such as the network settings, computer name, domain membership, and so on. In prior versions of Windows Server, you had to be familiar with the netsh commands in configuring these aspects of Server Core.

Although you can still configure the Server Core installation with netsh commands as you may have done in the past, in Windows Server 2008 R2 Server Core there is a new tool you can leverage called Server Configuration. Server Configuration is a DOS-style menu configuration system providing simple commands to configure your server. This tool allows you to complete these common tasks easily. After you log on to Server Core, type sconfig. You will see a screen similar to Figure 1-11.

Figure 1-11:Server Configuration tool

As you can see, this new tool is very easy to follow. For example, after you have launched sconfig, if you want to change the address, you would press the 8 key to configure the settings. Then you just need to follow the menu screens to finish the configuration.

Activating Windows Server Core

When you install Windows Server 2008 R2 in either a full installation or Server Core, you still have to activate the operating system to ensure you have a valid product. Activating will also enable your copy of Windows Server 2008 R2 to function properly. On a full server installation, there is a simple activation wizard located in the Control Panel, named Activate Windows, to take you step-by-step through the process. However, in the Server Core installation of Windows Server 2008 R2, there is no wizard, so you will have to run one of the following two commands to activate it.

If you entered the product key for your Server Core installation during the install process, then run this script:

cscript C:\windows\system32\slmgr.vbs -ato

If you did not enter the key during the install process, run the following command:

cscript C:\windows\system32\slmgr.vbs -ipk <product key>

After this command executes successfully, run this to activate Windows:

cscript C:\windows\system32\slmgr.vbs -ato

Upgrade to Windows Server 2008 R2

Upgrading to Windows Server 2008 R2 can cause you some additional planning and consideration because Windows Server 2008 R2 is released only in 64-bit versions. You cannot upgrade an x86-based system to Windows Server 2008 R2. You can only perform a migration, which I will cover in the next section. Your current operating system and edition will determine the proper path for your upgrade. It is also important to mention when you perform an upgrade, under the covers the process is really an in-place migration. Table 1-6 shows the paths you can take. If your current operating system is not listed, then it is not supported.

Table 1-6: Upgrade Paths

Existing Windows Operating SystemWindows Server 2008 R2 Upgrade Options Windows Server 2003 Standard Edition with Service Pack 2 (SP2) or Windows Server 2003 R2 Standard Edition Windows Server 2008 R2 Standard, Windows Server 2008 R2 Enterprise Windows Server 2003 Enterprise Edition with SP2 or Windows Server 2003 R2 Enterprise Edition Windows Server 2008 R2 Enterprise, Windows Server 2008 R2 Datacenter Windows Server 2003 Datacenter Edition with SP2 or Windows Server 2003 R2 Datacenter Edition Windows Server 2008 R2 Datacenter Server Core installation of Windows Server 2008 Standard with or without SP2 Server Core installation of either Windows Server 2008 R2 Standard or Windows Server 2008 R2 Enterprise Server Core installation of Windows Server 2008 Enterprise with or without SP2 Server Core installation of either Windows Server 2008 R2 Enterprise or Windows Server 2008 R2 Datacenter Server Core installation of Windows Server 2008 Datacenter Server Core installation of Windows Server 2008 R2 Datacenter Server Core installation of Windows Web Server 2008 with or without SP2 Server Core installation of either Windows Server 2008 R2 Standard or Windows Web Server 2008 R2 Full installation of Windows Server 2008 Standard with or without SP2 Full installation of either Windows Server 2008 R2 Standard or Windows Server 2008 R2 Enterprise Full installation of Windows Server 2008 Enterprise with or without SP2 Full installation of either Windows Server 2008 R2 Enterprise or Windows Server 2008 R2 Datacenter Full installation of Windows Server 2008 Datacenter with or without SP2 Full installation of Windows Server 2008 R2 Datacenter Full installation of Windows Web Server 2008 with or without SP2 Full installation of either Windows Server 2008 R2 Standard or Windows Web Server 2008 R2 Server Core installation of Windows Server 2008 R2 Standard Server Core installation of either Windows Server 2008 R2 Standard (repair in place) or Windows Server 2008 R2 Enterprise Server Core installation of Windows Server 2008 R2 Enterprise Server Core installation of either Windows Server 2008 R2 Enterprise (repair in place) or Windows Server 2008 R2 Datacenter Server Core installation of Windows Server 2008 R2 Datacenter Server Core installation of Windows Server 2008 R2 Datacenter (repair in place) Server Core installation of Windows Web Server 2008 R2 Server Core installation of either Windows Web Server 2008 R2 (repair in place) or Windows Server 2008 R2 Standard Full installation of Windows Server 2008 R2 Standard Full installation of either Windows Server 2008 R2 Standard (repair in place) or Windows Server 2008 R2 Enterprise Full installation of Windows Server 2008 R2 Enterprise Full installation of either Windows Server 2008 R2 Enterprise (repair in place) or Windows Server 2008 R2 Datacenter Full installation of Windows Server 2008 R2 Datacenter Full installation of Windows Server 2008 R2 Datacenter (repair in place) Full installation of Windows Web Server 2008 R2 Full installation of either Windows Web Server 2008 R2 (repair in place) or Windows Server 2008 R2 Standard

Performing an in-place upgrade is a destructive process in a sense. You are replacing the existing server operating system with the new one, and this is a one-way street, meaning that if the upgrade process goes awry, then you will incur downtime until you resolve the issue and restore your system. Before you perform any upgrade or migration, back up your existing server operating system and data.

1. Insert the DVD media into the drive, which will present you with the screen shown earlier in Figure 1-1.

2. When you click Install Now, you will be presented with a couple of choices on this screen, as shown in Figure 1-12. You can choose to participate in the Microsoft Customer Experience program by selecting I Want To Help Make Windows Installation Better. This program helps Microsoft identify trends for successful and unsuccessful installations and determine which updates are needed. Choosing to participate is strictly optional. You can learn more about the program by clicking What Information Will Be Sent To Microsoft?

Figure 1-12:Installation updates

You are also presented with a choice to upgrade your installation files. You should always choose to update installation files; the following are the updates included in this choice:

Installation updatesDriver updatesWindows updatesMicrosoft Windows Malicious Software Removal Tool updates

If you choose to go online and update your installation, you will see a screen similar to Figure 1-13 while downloading the updates. After you’re done downloading updates, or if you choose not to update the installation, you will proceed to the next step.

Figure 1-13:Update installation progress

3. The next step provides you with the choice to install the edition of Windows Server 2008 R2. You can choose to install the full edition of Windows Server 2008 R2 or the Server Core version. Select your version, and click Next.

4. Clicking the Next button will take you to the license agreement screen. This screen allows you to read, print, and agree to the license terms. Select the check box on the bottom left of the dialog box to agree to the license terms, and click Next to continue.

5. The next step provides you the choice between performing an upgrade or custom installation of Windows Server 2008 R2. To proceed to the next step of the upgrade, you need to choose the upgrade option.

6. The Windows Server 2008 R2 installation will perform a compatibility check, and you will see a screen similar to Figure 1-14. The report will be saved to your desktop, and you will see what devices will be affected by the Windows Server 2008 R2 upgrade. Click Next to continue.

Figure 1-14:Compatibility report

7. The Windows Server 2008 R2 upgrade will continue to the next step, and you will see a screen similar to Figure 1-15. During this phase of installation, all the necessary files, settings, and programs needed for the upgrade will be collected and analyzed. The system may also reboot several times during this phase of installation.

Figure 1-15:Upgrading Windows progress

8. After the final system reboot, the upgrade is complete, and you will be presented with a login screen. Log in, and you will finish the upgrade. You can also review the compatibility report again; it is located on the desktop. The file will be called Windows Compatibility Report.htm.

Install Windows Server 2008 R2 Server Unattended

You can also perform an unattended installation of Windows Server 2008 R2. This provides a useful method to rapidly deploy new servers in your environment. Unattended installs are completed by creating an answer file. The answer file is the file containing the main configurations for the Windows Server 2008 R2 installation. Settings can include application configuration, such as configuring the home page in Internet Explorer and controlling the desktop look-and-feel settings. To create an answer file, you first need to install the Windows Automated Installation Kit (WAIK).

Install the WAIK

The WAIK is a flexibility utility tool that allows you to customize your Windows 7 and Windows Server 2008 R2 installs. You can also create the necessary files to assist with configuration and deployments. To run the WAIK, you need to be running either Windows Server 2003 SP1, Windows Vista SP1, Windows Server 2008, Windows 7, or Windows Server 2008 R2.

1. Download the WAIK.iso file from the Microsoft website:

http://www.microsoft.com/downloads/details.aspx?familyid=4AD85860-D1F4-42A1-A46C-E039E3D0DB5D&displaylang=en

2. Burn the .iso file to a DVD.

3. Insert the DVD to install the WAIK tools; you should see Figure 1-16.

4. Click Windows AIK Setup to begin the installation.

5. Click Next on the welcome screen.

6. Click Next after you accept the license agreement.

Figure 1-16:Welcome to WAIK.

7. Pick a drive and directory to install the tools to. The tools require about 1.2GB of drive space. Then click Next.

8. Click Next to begin to the installation, and click Close on the final screen.

Create an Answer File

After you have installed the WAIK tools, then your next step is to create an answer file. The file contains configuration settings for Windows and provides the settings to your preferred desktop. To create an answer file, you will use the Windows System Image Manager (SIM). Before you create an answer file, you will need to the load the install.wim file from the Windows Server 2008 R2 DVD. The file is located in the sources directory. Copy the file to a local directory, for example c:\source.

1. Start Windows SIM by selecting Start ⇒ All Programs ⇒ Microsoft Windows AIK. Then click Windows System Image Manager.

2. In Windows SIM, select File ⇒ Select Windows Image, and navigate to the directory you copied the install.wim file to.

3. After you select the install.wim file you used in step 2, you will be presented with Figure 1-17, where you will choose the edition of Windows Server 2008 R2 for which you are creating the answer file.

Figure 1-17:Windows image selection

4. After you select the edition, you will be asked to create a catalog file; click Yes. This process can take several minutes.

5. Choose File ⇒ Create An Answer File, and your screen will look similar to Figure 1-18.

Figure 1-18:WAIK

6. You will then need to add and configure the many settings that fit your needs. For more information on configuring the settings, see the help file that comes with WAIK tool set (waik.chm).

7. When you are done modifying settings in the answer file, you need to save the file. Select File ⇒ Save Answer File. During the save process, the SIM tool will start a validation process. The validation tool will ensure your answer file is correctly formatted and the settings are configured. Before you save, you can also validate the file by selecting Tools ⇒ Validate Answer File.

8. Save the answer file with the name Autounattend.xml.

Install Windows Server 2008 R2 Unattended

After you have an answer file, then it is time to install Windows. The previous process is good for single-server deployments. However, the WAIK tools also provide resources for many deployment methods. The WAIK tool set provides many tools to quickly deploy multiple servers via a variety of sources. You will learn the DVD method to deploy Windows Server 2008 R2 unattended.

1. Copy your answer file (Autounattend.xml) to a disc or USB flash drive (UFD).

2. Insert your UFD and your Windows Server 2008 R2 DVD into the server you want to install.

3. The Windows Server 2008 R2 setup program automatically checks the removable media for a file called Autounattend.xml.

4. After the installation is complete, make sure your settings were properly installed.

5. Lastly, you need to reseal the system by running this command:

c:\windows\system32\sysprep\sysprep.exe /oobe /generalize /shutdown

Resealing the system will remove hardware-specific and unique system information. This is required if you plan to redeploy the image and properly ready the system for users.

Migrate to Windows Server 2008 R2

Choosing to perform a server migration instead of in-place upgrade has some advantages you should consider. Performing a migration does require two servers; however, this is one of the advantages. On the server you will be migrating to, you will perform a clean install of Windows Server 2008 R2, and clean installations will exhibit more stability than upgraded servers. Migrations also reduce the risk of downtime in your server environment and offer a fallback plan. During migration, the server being migrated is still running, and if the migration fails, you can start all over with the new server without impacting your environment. Lastly, migration allows you to do performance and benchmarking testing prior to fully completing the migration.

Windows Server 2008 R2 migration can be used successfully in these three scenarios:

x86 to x64 scenarios As mentioned earlier, Windows Server 2008 R2 is available only in 64-bit. Migration is the only method for the x86 hardware.

Virtual server to physical server and physical server to virtual server If you are looking to virtualization for some of your server components in your current environment, then migration is the way to go. Likewise, if you are looking to move some of your virtual servers to the physical systems, migration offers another great pathway for you.

Core Server to full server and full server to Core Server As mentioned in Table 1-6, you can perform this type of upgrade only on Windows Server 2008 R2 servers. Migration is the only way to move from a Server Core installation to a full installation of Windows Server 2008 R2. You can also turn a full server into a Server Core through this process. However, make sure your roles on the full server will be supported by Server Core.

Migration can be from x86 or x64 systems and will support the following source operating systems:

Windows Server 2003Windows Server 2003 R2Windows Server 2008, full server onlyWindows Server 2008, R2 full server or Server Core

NOTE Windows 2008 Server Core is not supported for migration since Server Core has no .NET Framework support. Additionally, the system language on both the source and the target have to be the same. For example, if the source server’s system language is English and the target server is in Spanish, then the migration tools will not work.

Migration can be performed for the following roles, features, settings, and data:

Active Directory Domain Services (AD DS)DNSDHCPFile ServicesPrint ServicesBranchCacheIP configurationLocal Users and Groups

Prior to performing the migration, you need to install the Windows Server 2008 R2 migration tools.

Install Windows Server 2008 R2 Migration Tools

The migration tools are new and provide a much improved resource for successfully migrating your environment. You will install the migration tools first on the target Windows Server 2008 R2 server and then on the source server. Prior to installing the migration tools, make sure the source servers meet the system requirements listed in Table 1-7, and verify you are, at the minimum, a member of the Administrators group on the target and source servers.

Table 1-7: Migration Tool System Requirements

Source Server OSRequirements Windows Server 2003 or Windows Server 2003 R2 25MB free drive space~LB.NET Framework 2.0~LBWindows PowerShell 1.0 or later Windows Server 2008 or 2008 R2 23MB free drive space~LBWindows PowerShell or the Server Manager command-line tool (ServerManagerCmd.exe)

First you need to install the migration tools on the Windows Server 2008 R2 target server. After the tools are installed on the target server, then you will need to create deployment folders on the target server for the source server. Lastly, to complete the installation, you will need to register the Windows Server migration tools on the source servers. You will see how to install the tools via Server Manager:

1. Open Server Manager (you can also install the tools via PowerShell if you are running Windows Server 2008 R2 Server Core) on the target server, click Features, and then select Add Features. You will see the Add Features Wizard, as shown in Figure 1-19.

Figure 1-19:Add Features Wizard

2. You may need to scroll down to select Windows Server Migration Tools. After you select Windows Server Migration Tools, click Next.

3. You will see a screen similar to Figure 1-20. Click Install to install the tools after the installation, review the summary, and then click Close. Additionally, installing the tool set may require you to restart the server, so please plan accordingly.

Figure 1-20:Windows server migration tools confirmation

4. After the tools are installed, you need to create the deployment folders on the target computer. To do this, first you need to open an administrator command prompt. Select Start ⇒ All Programs ⇒ Accessories, right-click Command Prompt, and select Run As Administrator, as shown in Figure 1-21.

Figure 1-21:Selecting Run As Administrator

5. Create a deployment folder on the target computer to hold the migration tools; for the following examples, I used c:\migration. This folder can also be a network path.

6. In the command prompt window, change to the Server Migration Tools directory. The directory by default is located at c:\windows\system32\ServerMigrationTools\ (if you installed to the default directory on the C drive). To get there quickly, you can enter the command cd %windir%\system32\servermigrationtools\ and press Enter.

7. Depending on what architecture and operating system your source system is running, you will then need to run one of the following commands. The command will create a directory with the migration tools in it, as in Figure 1-22, which shows a directory created for a 64-bit version of Windows 2003 with the name of SMT_ws03_amd64:

If your server is 64-bit Windows Server 2003, type this command and hit Enter:

SmigDeploy.exe /package /architecture amd64 /os WS03 /path c:\migration

If your server is 64-bit Windows Server 2008, type this command and hit Enter:

SmigDeploy.exe /package /architecture amd64 /os WS08 /path c:\migration

If your server is x86 Windows Server 2003, type this command and hit Enter:

SmigDeploy.exe /package /architecture X86 /os WS03/path c:\migration

If your server is x86 Windows Server 2008, type this command and hit Enter:

SmigDeploy.exe /package/ /architecture X86 /os WS08 /path c:\migration

Figure 1-22:Windows migration directory

8. Copy the folder created in step 7 to a local directory on the source computer so you can register the tools with the source server.

9. On the source server, open a command prompt. If the server is Windows Server 2003, just run the command. However, if the source server is Windows Server 2008, you will need to run an elevated command prompt. To do that, select Start ⇒ All Programs ⇒ Accessories, right-click Command Prompt, and select Run As Administrator.

10. Change to the directory you copied the files to in step 8.

11. Type .\Smigdeploy.exe, and hit Enter to register the tools. When this command is complete, you will see a status message, and a Windows PowerShell window will open. You will see a screen similar to Figure 1-23.

Figure 1-23:Windows migration install

After you install the migration tools, it is then time perform the migration.

Migrate to Windows Server 2008 R2

Regardless of the feature or role you will be migrating to Windows Server 2008 R2, you will follow three general steps after you install Windows Server 2008 R2 on the new target server:

1. Export the settings from the source server to temporary storage.

2. Import the settings to the target server from temporary storage.

3. Transfer any data and shares from the source server to the target server.

In Chapter 2, you will look at migrating specific roles and features.

Chapter 2

Adding Server Roles and Functionality

In this chapter, you will learn to:

Plan for Windows Server 2008 R2 Roles Plan for Active Directory Plan for Hyper-V Understand Remote Desktop Services Understand Windows Server 2008 R2 Features Install Windows Server 2008 R2 Roles Install Roles on a Windows Server 2008 R2 Full Server Installation Install Roles on a Windows Server 2008 R2 Server Core Installation Migrate Roles to Windows Server 2008 R2 Migrate Active Directory and DNS Migrate DHCP Services Utilize the Server Migration Tools