Exam Ref 70413 Designing And Implementing A Server Infrastructure Steve Suehring

Exam Ref 70413 Designing And Implementing A
Server Infrastructure Steve Suehring download
https://ebookbell.com/product/exam-ref-70413-designing-and-
implementing-a-server-infrastructure-steve-suehring-4451288
Explore and download more ebooks at ebookbell.com

Here are some recommended products that we believe you will be
interested in. You can click the link to download.
Exam Ref 70413 Designing And Implementing A Server Infrastructure Mcse
2nd Edition 2nd Edition Paul Ferrill
https://ebookbell.com/product/exam-ref-70413-designing-and-
implementing-a-server-infrastructure-mcse-2nd-edition-2nd-edition-
paul-ferrill-5107332
Exam Ref 70741 Networking With Windows Server 2016 Andrew Warren
https://ebookbell.com/product/exam-ref-70741-networking-with-windows-
server-2016-andrew-warren-46508894
Exam Ref 70533 Implementing Microsoft Azure Infrastructure Solutions
Michael Washam Rick Rainey Dan Patrick Steve Ross
https://ebookbell.com/product/exam-ref-70533-implementing-microsoft-
azure-infrastructure-solutions-michael-washam-rick-rainey-dan-patrick-
steve-ross-50200546
Exam Ref 70533 Implementing Microsoft Azure Infrastructure Solutions
Washam
https://ebookbell.com/product/exam-ref-70533-implementing-microsoft-
azure-infrastructure-solutions-washam-22029870

Exam Ref 70532 Developing Microsoft Azure Solutions Tejada
Zoinerbustamante
https://ebookbell.com/product/exam-ref-70532-developing-microsoft-
azure-solutions-tejada-zoinerbustamante-22066954
Exam Ref 70740 Installation Storage And Compute With Windows Server
2016 Kellington
https://ebookbell.com/product/exam-ref-70740-installation-storage-and-
compute-with-windows-server-2016-kellington-22066956
Exam Ref 70765 Provisioning Sql Databases Joseph Dantoni
https://ebookbell.com/product/exam-ref-70765-provisioning-sql-
databases-joseph-dantoni-22066962
Exam Ref 70345 Designing And Deploying Microsoft Exchange Server 2016
Paul Cunningham Brian Svidergol
https://ebookbell.com/product/exam-ref-70345-designing-and-deploying-
microsoft-exchange-server-2016-paul-cunningham-brian-
svidergol-33325406
Exam Ref 70484 Essentials Of Developing Windows Store Apps Using C
Indrajit Chakrabarty
https://ebookbell.com/product/exam-ref-70484-essentials-of-developing-
windows-store-apps-using-c-indrajit-chakrabarty-37206148

Exam 70-413:
Designing and
Implementing a Server
Infrastructure
Exam Ref
Steve Suehring

Published with the authorization of Microsoft Corporation by:
O’Reilly Media, Inc.
1005 Gravenstein Highway North
Sebastopol, California 95472
Copyright © 2012 by Steve Suehring
All rights reserved. No part of the contents of this book may be reproduced
or transmitted in any form or by any means without the written permission of
the publisher.
ISBN: 978-0-7356-7367-0
1 2 3 4 5 6 7 8 9 QG 7 6 5 4 3 2
Printed and bound in the United States of America.
Microsoft Press books are available through booksellers and distributors
worldwide. If you need support related to this book, email Microsoft Press
Book Support at mspinput@microsoft.com. Please tell us what you think of
this book at http://www.microsoft.com/learning/booksurvey.
Microsoft and the trademarks listed at http://www.microsoft.com/about/legal/
en/us/IntellectualProperty/Trademarks/EN-US.aspx are trademarks of the
Microsoft group of companies. All other marks are property of their respec-
tive owners.
The example companies, organizations, products, domain names, email ad-
dresses, logos, people, places, and events depicted herein are fictitious. No
association with any real company, organization, product, domain name,
email address, logo, person, place, or event is intended or should be inferred.
This book expresses the author’s views and opinions. The information con-
tained in this book is provided without any express, statutory, or implied
warranties. Neither the authors, O’Reilly Media, Inc., Microsoft Corporation,
nor its resellers, or distributors will be held liable for any damages caused or
alleged to be caused either directly or indirectly by this book.
Acquisitions and Developmental Editor: Ken Jones
Production Editor: Holly Bauer
Editorial Production: Box Twelve Communications
Technical Reviewer: Brian Svidergol
Copyeditor: Susan Shaw Dunn
Indexer: Ginny Munroe
Cover Design: Twist Creative • Seattle
Cover Composition: Zyg Group, LLC
Illustrator: Rebecca Demarest

Contents at a Glance
Introduction xv
Chapter 1 Plan and deploy a server infrastructure 1
Chapter 2 Design and implement network infrastructure services 71
Chapter 3 Design and implement network access services 109
Chapter 4 Design and implement an Active Directory
infrastructure (logical) 177
infrastructure (physical) 219
Index 245

vii
What do you think of this book? We want to hear from you!
Microsoft is interested in hearing your feedback so we can continually improve our
books and learning resources for you. To participate in a brief online survey, please visit:
www.microsoft.com/learning/booksurvey/
Contents
Introduction xv
Microsoft Certified Professional Program xvi
Acknowledgments xvi
Support & Feedback xvii
Preparing for the Exam xviii
Chapter 1 Plan and deploy a server infrastructure 1
Objective 1.1: Design an automated server installation strategy. . . . . . . . . 1
Understanding design considerations 2
Using the Windows Assessment and Deployment Kit 7
Understanding virtual server deployment 9
Objective summary 10
Objective review 11
Objective 1.2: Plan and implement a server deployment
infrastructure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Configuring multicast deployment 12
Configuring multisite topology and distribution points 14
Configuring a multi-server topology 18
Configuring WDS 19
Objective review 24
Objective 1.3: Plan and implement server upgrade and migration. . . . . . 24
Planning for role migration 25
Migrating server roles 26
Migrating servers across domains and forests 29

viii Contents
Designing a server consolidation strategy 29
Planning for capacity and resource optimization 32
Objective review 35
Objective 1.4: Plan and deploy Virtual Machine Manager services. . . . . . 36
Designing VMM service templates 36
Defining operating system profiles 41
Configuring hardware and capability profiles 44
Managing services 46
Configuring image and template libraries 47
Managing logical networks 48
Objective review 51
Objective 1.5: Plan and implement file and storage services. . . . . . . . . . . 52
Planning for file and storage service 52
Configuring the iSCSI Target Server 55
Configuring Internet Storage Name Server 58
Configuring Network File System 60
Installing device-specific modules 63
Objective review 64
Chapter summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Answers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Objective 1.1: Thought experiment 66
Objective 1.1: Review 66

ix
Contents
Chapter 2 Design and implement network infrastructure
services 71
Objective 2.1: Design and maintain a Dynamic Host
Configuration Protocol (DHCP) solution. . . . . . . . . . . . . . . . . . . . . . . . . . 71
Designing a highly available DHCP solution 72
Implementing DHCP filtering 78
Implementing and configuring a DHCP Management Pack 79
Maintaining a DHCP database 80
Objective review 82
Objective 2.2: Design a name resolution solution strategy. . . . . . . . . . . . . 83
Designing a name resolution strategy 83
Objective review 91
Objective 2.3: Design and manage an IP address management
solution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Design considerations for IP address management 92
Configuring role-based access control 96
Configuring IPAM auditing 96
Migrating IP addresses 98
Managing and monitoring multiple DHCP and DNS servers 99
Configuring data collection 100
Objective review 102
Chapter summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Answers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

x Contents
Chapter 3 Design and implement network access services 109
Objective 3.1: Design a VPN solution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
VPN design considerations 110
Security certificate deployment 111
Firewall design considerations 112
Client and site-to-site considerations 113
Bandwidth and protocol implications 113
VPN deployment configurations with CMAK 113
Objective 3.2: Design a DirectAccess solution. . . . . . . . . . . . . . . . . . . . . . . 117
Designing a DirectAccess topology 118
Migrating from Forefront UAG 118
Deploying DirectAccess 120
Using enterprise certificates 121
Objective 3.3: Implement a scalable Remote Access solution . . . . . . . . . 123
Configuring site-to-site VPN 124
Configuring packet filters 124
Implementing packet tracing 125
Implementing Multisite Remote Access 125
Configuring Remote Access clustered with NLB 130
Configuring DirectAccess 131
Objective 3.4: Design a network protection solution. . . . . . . . . . . . . . . . . 134
Understanding network protection solutions 135
Planning for capacity and server placement 136
Planning for NPS and firewall access 139
Remediation Network 140

xi
Contents
Objective 3.5: Implement a network protection solution. . . . . . . . . . . . . 141
Implementing multiple RADIUS servers 142
Configuring NAP enforcement for IPsec and 802.1X 145
Deploying and configuring the Endpoint Protection Client 157
Setting up antimalware and firewall policies 163
Monitoring compliance 168
Chapter summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Answers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
infrastructure (logical) 177
Objective 4.1: Design a forest and domain infrastructure . . . . . . . 177
Multi-forest architecture 178
Trusts 179
Functional levels 180
Domain upgrade 181
Domain migration and forest restructure 181
Hybrid cloud services 182

xii Contents
Objective 4.2: Implement a forest and domain infrastructure. . . . 184
Configuring domain rename 184
Configuring a Kerberos realm trust 188
Implementing a domain upgrade 192
Implementing a domain migration 193
Implementing a forest restructure 194
Deploying and managing a test forest 195
Objective 4.3: Design a Group Policy strategy. . . . . . . . . . . . . . . . . 198
Blocking inheritance 199
Using enforced policies 199
Using loopback processing 199
Using Windows Management Instrumentation (WMI) filters 200
Understanding site-linked GPOs 200
Using slow link processing 201
Understanding group strategies 202
Understanding OU hierarchy 202
Using Advanced Group Policy Management 202
Objective 4.4: Design an Active Directory permission model. . . . . 204
Understanding design considerations for Active
Directory permissions 205
Customizing tasks in the Delegation of Control Wizard 206
Deploying Remote Server Administrative Tools on a
client computer 208
Delegating permissions on administrative users 208
Configuring Kerberos delegation 210
Chapter summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

xiii
Contents
Answers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
infrastructure (physical) 219
Objective 5.1: Design an Active Directory sites topology. . . . . . . . 219
Understanding Active Directory topology design 220
Monitoring and resolving Active Directory replication conflicts 221
Objective 5.2: Design a domain controller strategy. . . . . . . . . . . . . 224
Global catalog and operations master roles 224
Read-only domain controllers 225
Partial attribute set 226
Domain controller cloning 226
Objective 5.3: Design and implement a branch office
infrastructure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Understanding branch office infrastructure design
considerations 229
Implementing confidential attributes 231
Delegating administration 233
Modifying the filtered attribute set 234
Configuring Password Replication Policy 236
Configuring Hash Publication 238

xiv Contents
Chapter summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Answers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Index 245

xv
Introduction
This Exam Ref is designed to assist you with studying for the MCITP exam 70-413,
“Designing and Implementing a Server Infrastructure.” This exam focuses on both the use
of server technologies to solve particular design objectives as well as the implementation of
those designs to meet certain objectives. The exam has network-related objectives and calls
on your experience with Windows Server and related technologies such as DirectAccess,
VPNs, DNS, and DHCP.
The 70-413 exam is meant for large, enterprise-scale organizations and their needs. Passing
the exam demonstrates your knowledge and experience with enterprise server technologies.
This book will review every concept described in the following exam objective domains:
■
■ Plan and deploy a server infrastructure
■
■ Design and implement network infrastructure services
■
■ Design and implement network access services
■
■ Design and implement an Active Directory infrastructure (logical)
■
■ Design and implement an Active Directory infrastructure (physical)
Even though this book covers all the technologies involved in each exam objective, it’s
not meant to be a brain dump of questions that you’ll see on the exam. In fact, this book is
meant to be used as a supplement to your own experience with and a study of the relevant
technologies in each objective. As you read the book, if you come across areas that you are
less familiar with, you should follow up on that area to obtain additional knowledge. In many
cases, the book provides links to the relevant areas in TechNet, but you should also pursue
this area using every available tool at your disposal, including other areas of Microsoft’s
website, forums, and first-hand experience. In fact, you should deploy your own infrastructure
for this exam to match the recommended lab scenarios covered not only in this book but also
in the documentation from Microsoft on these subject areas. Microsoft offers trial versions of
all software involved in this exam, and you can create a virtualized infrastructure to help your
study of the exam objectives.

xvi Introduction
Microsoft Certified Professional Program
Microsoft certifications provide the best method for proving your command of current
Microsoft products and technologies. The exams and corresponding certifications are
developed to validate your mastery of critical competencies as you design and develop, or
implement and support, solutions with Microsoft products and technologies. Computer
professionals who become Microsoft certified are recognized as experts and are sought after
throughout the industry. Certification brings various benefits to the individual and to employ-
ers and organizations.
MORE INFO OTHER MICROSOFT CERTIFICATIONS
For a full list of Microsoft certifications, go to www.microsoft.com/learning/mcp/default.asp.
Acknowledgments
This book would not have been possible without my wife’s support. She assumed nearly all
responsibility for a 9-month-old and a 4-year-old so that I could focus on getting this book
written. Ken Jones and Neil Salkind also worked out the details to make the book possible.
Even though they didn’t offer to do any diaper changes, I’ll still thank them anyway.
And the requisite thanks to Tim and Rob from Partners, as well as Jim Oliva and John
Eckendorf. Thanks to Bob, Mike, Ernie, and Tim for getting the band back together. It hasn’t
been that long since I wrote an acknowledgments section, but I can’t remember the list of
people that I usually thank, so here’s to you, person that I can’t remember when I’m writing
this early on a Sunday morning: consider yourself thanked!
One person I can’t forget to thank is you, the reader, not only for reading this acknowledg-
ments section, but also for reading this book. I invite you to contact me, either through my
website or on Twitter. Thank you!

xvii
Introduction
Support & Feedback
The following sections provide information on errata, book support, feedback, and contact
information.
Errata
We’ve made every effort to ensure the accuracy of this book and its companion content.
Any errors that have been reported since this book was published are listed on our Microsoft
Press site at oreilly.com:
http://go.microsoft.com/FWLink/?Linkid=271462
If you find an error that is not already listed, you can report it to us through the same page.
If you need additional support, email Microsoft Press Book Support at mspinput@
microsoft.com.
Please note that product support for Microsoft software is not offered through the ad-
dresses above.
We Want to Hear from You
At Microsoft Press, your satisfaction is our top priority, and your feedback our most valuable
asset. Please tell us what you think of this book at:
http://www.microsoft.com/learning/booksurvey
The survey is short, and we read every one of your comments and ideas. Thanks in ad-
vance for your input!
Stay in Touch
Let’s keep the conversation going! We’re on Twitter: http://twitter.com/MicrosoftPress.

xviii Introduction
Preparing for the Exam
Microsoft certification exams are a great way to build your resume and let the world know
about your level of expertise. Certification exams validate your on-the-job experience and
product knowledge. Although there is no substitute for on-the-job experience, preparation
through study and hands-on practice can help you prepare for the exam. We recommend
that you augment your exam preparation plan by using a combination of available study
materials and courses. For example, you might use the Exam ref and another study guide for
your “at home” preparation, and take a Microsoft Official Curriculum course for the classroom
experience. Choose the combination that you think works best for you.

1
C H A P T E R 1
Plan and deploy a server
infrastructure
Planning a server infrastructure is key to providing reliable and
resilient computing resources to meet business needs. You can
attain responsiveness by automating as much as possible in the
data center, including such things as server installation and
deployment. Virtualization is also an important element in today’s
data center. Virtual Machine Manager is the tool used for both
deployment and management of virtualization infrastructure.
Windows Server 2012 enhances File and Storage services to add
new features and more security surrounding existing options.
Objectives in this chapter:
■
■ Objective 1.1: Design an automated server installation strategy
■
■ Objective 1.2: Plan and implement a server deployment infrastructure
■
■ Objective 1.3: Plan and implement server upgrade and migration
■
■ Objective 1.4: Plan and deploy Virtual Machine Manager services
■
■ Objective 1.5: Plan and implement file and storage services
Objective 1.1: Design an automated server
installation strategy
Providing automation of server installation is important for a responsive, dynamic IT organi-
zation. Automation involves creating baseline reference images of servers and then de-
ploying those servers rapidly in response to changing business requirements or to provide
additional redundancy. Several tools are available to help with deployments, including tools
to create and manage images and a server role for deploying the images onto client or
destination computers.
i m p o r t a n t
Have you read
page xviii?
It contains valuable
information regarding
the skills you need to
pass the exam.

2 Chapter 1 Plan and deploy a server infrastructure
As has been the case in recent versions, Windows Server continues to move toward and
feature command-line tools for management alongside the normal Graphical User Interface
(GUI) interface. You should be familiar with both the GUI interface and the commands for ac-
complishing the same task.
Before deploying the servers, you need to design the strategy for supporting the deploy-
ments. This means understanding the concepts involved in automated deployment as well as
becoming familiar with the tools involved in the process.
This objective covers the following topics:
■
■ Design considerations, including images and bare metal/virtual deployment
■
■ Design of a server implementation using Windows Assessment and Deployment Kit (ADK)
■
■ Design of a virtual server deployment
Understanding design considerations
Choosing an automated server installation strategy involves several design considerations,
including the hardware and network infrastructure available for deployment. For example, a
lower-bandwidth topology changes the approach. The deployment design chosen also deter-
mines how much manual intervention is required to deploy Windows.
When considering a deployment strategy, you should look at the number of machines to
be installed. Also consider how many of the machines share the same role and have the same
hardware.
An important step in understanding the concepts involved in deployment is learning the
components that go into a deployment. Deployment is driven by image files that contain
the state of a computer, including its operating system and all settings, from a given point in
time. You can use several tools in Windows Server 2012 to create images. This chapter con-
centrates on two: Windows Deployment Services (WDS) and the Windows Assessment and
Deployment Kit (ADK).
Three primary phases are involved in Windows deployment: Design, Deployment, and
Update.
During the Design phase, you build an initial base or reference image. This is typically
accomplished using tools such as WDS, sysprep, or the ADK. Part of the ADK is the Windows
System Image Manager (Windows SIM), which assists in working with answer files.

Objective 1.1: Design an automated server installation strategy Chapter 1 3
Answer files
XML-formatted answer files provide the settings that you would normally configure when run-
ning through a manual installation of Windows. Things such as disk partitioning and network
settings can be configured through an answer file so that you don’t have to be involved in the
setup process for each and every machine deployed. You typically use Windows SIM to create
the answer files, but thanks to their XML format, you can edit them with any plain-text editor.
The Deployment phase uses that captured image along with WDS to apply the image to
one or more computers in the organization.
An Update and Manage phase enables you to update and manage the images as changes
occur to the reference image. During this phase, you can use tools such as Deployment Image
Servicing and Management (DISM) and sysprep to edit images.
Images
Windows images contain the information necessary to install a copy of Windows onto an-
other machine. Included in this information are the settings and components specific to the
computer onto which the image will be installed.
Two primary types or classes of images are available: boot and install.
BOOT IMAGES
Boot images (boot.wim), used to boot the target computer, include the setup executable as
well as the WDS client. Windows DVDs also contain boot.wim files from which other boot
images can be built. Boot images are typically added to WDS via the Add Image Wizard by
navigating to the source DVD of the operating system. The boot.wim file is normally located
in the sources folder of a Windows installation DVD.
Boot images come in two forms: Capture and Discover. Capture images enable the
computer to capture an image of itself as a .wim (Windows Image) file. Capture images are
typically taken when the computer is fully configured, with all its applications and roles. Once
captured, the image is called a reference image and should be maintained as needed for envi-
ronmental changes, such as updates or role and configuration changes.
You create Capture images inside WDS by selecting one of the available boot images and
then using the Create Capture Image Wizard. The final step in the Create Capture Image
Wizard gives the option to add the Capture Boot Image back to the WDS server, as depicted
in Figure 1-1.

FIGURE 1-1 Creating a Capture image and then adding it back to the WDS server.
After a Capture image is created, it can then be deployed to the server by ensuring that
the server receiving the image is set to boot from the network with Preboot Execution Envi-
ronment (PXE). The client can then be captured.
NOTE USING SYSPREP
You must run the sysprep tool on the computer to be captured or it won’t be available for
image capture. The typical sysprep command is sysprep /generalize /shutdown.
The other boot image type, Discover images, runs the installation setup.exe in WDS mode.
This enables the client to locate the WDS server to obtain an install image. Discover images
are typically used for client computers that can’t use PXE boot or in data center scenarios
where PXE might be limited by policy.
INSTALL IMAGES
Install images (install.wim) contain the files customized for the particular image being
deployed. WDS can use boot.wim and install.wim from the product DVD during the create-
images phase, or it can use customized images for each phase.
DISM can mount both .wim files as well as Virtual Hard Disk (VHD or VHDX) files for servic-
ing. When an image is serviced, you use the Image Capture Wizard to upload it back into the
WDS server.

MORE INFO UNDERSTANDING THE DEPLOYMENT PROCESS
See http://technet.microsoft.com/library/hh825212 for a step-by-step guide to the deploy-
ment process.
Windows Deployment Services
The basis for deploying Windows is the Windows Deployment Services role in Windows
Server 2012. By default, the Windows Deployment Services role installs two roles: Deployment
Server and Transport Server. These roles require a working DHCP server on the network, a
DNS server on the network, and an NTFS volume. They also require that the account installing
the Windows Deployment Services role be a member of the local administrators group.
NOTE TRANSPORT SERVER ROLE
The Transport Server role is used in environments without Active Directory Domain Ser-
vices (AD DS), DNS, or DHCP available. The Transport Server role also excludes the WDS
image store. The Deployment Server role depends on the Transport Server role, but you
can use the Transport Server role as a standalone role.
By default, the DHCP server and the WDS servers run on different machines because WDS
communicates with clients using DHCP. However, if DHCP and WDS run on the same com-
puter, you need to add DHCP Option 60 to the DHCP scope on which client computers will
communicate with the WDS server. Option 60 enables the client computers to learn about the
WDS server in the DHCP response packet.
MORE INFO CONFIGURING DHCP AND WDS
See http://technet.microsoft.com/library/cc771734 for more information on configuring
DHCP and WDS.
In an environment with AD DS, clients can be prestaged. Doing so has the advantage of
providing additional security because you can configure the WDS server to respond only to
prestaged clients. Computers are prestaged (sometimes called known) when a computer ac-
count is created in the domain for that client computer. An Auto-Add policy option in WDS
creates the computer account automatically.
The next objective, “Plan and Implement a Server Deployment Infrastructure,” looks closer
at WDS.
MORE INFO UNDERSTANDING WDS
See http://technet.microsoft.com/library/hh831764 for more information on WDS.

Bare metal/virtual deployment
Bare metal or virtual deployments are meant for installations on computers that have no op-
erating system. Computers eligible for bare metal deployment need to be Preboot Execution
Environment (PXE) capable, and the network capacity needs to support large transfers.
Deployment to bare metal servers has these general requirements:
■
■ The client computer must be capable of network booting (PXE).
■
■ The client computer must be configured to boot without user interaction.
■
■ You need to create two unattended installation files: one for the WDS screens and one
for the setup process itself.
When a client computer boots, it selects a boot image automatically. You can configure
this with the following syntax:
WDSUTIL /Set-Device /Device:<name> /BootImagePath:<Relative Path>
The computer must be prestaged for this to work. Alternatively, you can set a default image
globally for all clients on the Boot tab of the WDS server Properties sheet (see Figure 1-2).
FIGURE 1-2 Use the Boot tab of the WDS server Properties sheet to configure the response to PXE boot
requests.

Be conscious not to create a boot loop when planning a virtual deployment. If the com-
puter is configured to boot to the network, it will continue to do so even after the installa-
tion takes place, thus continually reinstalling the image. To get around this, configure the
hard drive to have higher boot order priority than the network or configure the computer
to require F12 to continue booting by using the WDSUTIL /set-server /resetbootprogram:yes
command.
The following partitioning schemes are recommended:
For UEFI/GPT Computers:
■
■ Windows RE Tools
■
■ System
■
■ MSR
■
■ Windows
■
■ Recovery Image
For BIOS Computers:
■
■ System ■
■ Windows ■
■ Recovery Image
Using the Windows Assessment and Deployment Kit
The Windows Assessment and Deployment Kit (ADK) provides a rich set of tools for both
examining performance and deploying Windows. The assessment pieces help troubleshoot
potential problems with hardware and drivers and measure things such as energy and battery
usage. The deployment pieces of the ADK combine the Windows OEM Preinstallation Kit and
the Windows Automated Installation Kit as well as new tools related to deployment.
EXAM TIP
The Windows ADK creates customized images. Specifically, you should be familiar with the
Windows System Image Manager (SIM), the primary tool used by deployment administra-
tors. Windows SIM works with answer files and creates Windows Preinstallation Environ-
ment (Windows PE) images. It’s these Windows PE images that contain vital information
necessary for executing the initial environment for deployment.
Deployments with the ADK involve the following general steps:
1. Create a customized Windows PE.
2. Customize the environment, installing applications and settings for the environment,
and then using sysprep to generalize the operating system.
3. Keep the environment up to date.
4. Use the Application Compatibility Toolkit (ACT) to identify application issues.
5. Migrate user data using the User State Migration Tool (USMT).
6. Activate licenses using the Volume Activation Management Toolkit (VAMT).

MORE INFO USING THE WDSUTIL UTILITY
You can use the WDSUTIL command-line utility to perform many of the same tasks as the
Windows SIM MMC snap-in. See http://technet.microsoft.com/library/cc771206 for the
syntax of common operations with WDSUTIL. The copype command is also used to copy
Windows PE images.
The sysprep utility takes a computer or image and generalizes it so that it can be re-
installed. Sysprep ensures that the computer uses a unique Security Identifier (SID), thus
enabling proper licensing and domain functionality. One of the most common problems for
deployment and imaging is that sysprep wasn’t run on the reference image.
Designing a server implementation with the ADK involves creating an answer file using
the Windows SIM. The basic workflow for the SIM is to select a Windows PE image, select a
Distribution Share, and then create an answer file.
You select a .wim file by selecting Select Image from the File menu in the Windows SIM.
The Windows image shows its contents in the Windows Image pane of the Windows SIM
application. If a catalog doesn’t yet exist for the image, Windows SIM creates one.
Distribution shares are selected by choosing Select Distribution Share from the File menu.
Distribution shares must contain one of the following folders: $OEM$, Packages, or Out-of-
Box Drivers.
After you select the Windows image and distribution share, you can create a basic answer
file by using the New Answer File option from the File menu in Windows SIM.
Figure 1-3 shows the Windows SIM interface with a Windows PE image selected, a distribu-
tion share selected, and a basic answer file created.

FIGURE 1-3 The Windows System Image Manager.
Packages, in the form of .cab files, can be added to an answer file so that those packages
are installed with the image.
MORE INFO USING WINDOWS ADK TOOLS
The Windows ADK includes several other tools, such as those for assessments and volume
license activation. See http://technet.microsoft.com/library/hh825486 for more information
and a full listing of the tools in the ADK.
Understanding virtual server deployment
Virtual server deployments involve creation of a virtual hard disk (VHD with a .vhd file exten-
sion or VHDX with a .vhdx extension) and then deployment of that VHD to another computer.
This scenario is called native boot because the VHD doesn’t require an underlying operating
system.
For virtual server deployment, you need to create a VHD using a capture image from a
reference computer. The reference computer contains the configuration and applications that

you want to clone—in other words, the computer in its pristine state. The image captured
from the reference computer can be deployed to other computers, sometimes called destina-
tion computers.
Some environments use PXE boot with a WDS image. In such an environment, virtual serv-
er deployment design can continue using this method rather than the VHD/VHDX method
described.
MORE INFO DEPLOYING A VIRTUAL SERVER FOR NATIVE BOOT
See http://technet.microsoft.com/library/dd744338.aspx for more information on deploying
a virtual server for native boot.
THOUGHT EXPERIMENT
Deploying a WDS server
In the following thought experiment, apply what you’ve learned about this objec-
tive. You can find answers to these questions in the “Answers” section at the end
of this chapter.
You’re deploying a server image and will use WDS for it. As part of the rollout, you
have the Deployment Server and Transport Server components installed. A require-
ment is that the server deploys an image to multiple computers that are all PXE
capable.
1. Describe the steps necessary to ensure that the client computers will use the cor-
rect image when they’re activated, including any configuration that needs to take
place on the WDS server.
2. Describe the steps necessary to ensure that the computers can contact the WDS
server when they boot.
Objective summary
■
■ Designing an automated server deployment strategy involves several Microsoft tools,
including the Windows Assessment and Deployment Kit (ADK) and Windows Deploy-
ment Services.
■
■ The ADK creates and manages deployment images, while WDS deploys those images
to clients.
■
■ Images come in two forms: boot images and install images.

■
■ Boot images contain information necessary to boot the computer and begin an instal-
lation, while install images contain the actual operating system, applications, and other
files related to the client being deployed.
■
■ When boot images contain setup information, they’re called Discover images. The
other type of boot image, Capture images, takes a snapshot of a computer and uses it
to create an image file.
Objective review
Answer the following questions to test your knowledge of the information in this objective.
You can find the answers to these questions and explanations of why each answer choice is
correct or incorrect in the “Answers” section at the end of this chapter.
1. You have a computer configured and need to take an image of it to use as the refer-
ence image for deployments. What type of boot image do you need to create to
obtain the image?
A. Preinstallation image
B. Capture image
C. Discover image
D. Virtualization image
2. You have configured a deployment and began the deployment to a client computer
and want the client computer to boot from the hard drive after installation. Which
command creates this configuration?
A. wdsutil /set-client /bootdevice:hd
B. sysprep /client-boot-reset:yes
C. wdsutil /set-server /resetbootprogram:yes
D. sysprep /set-client /primaryboot:hd
3. You need to edit an image to change its configuration. The first step is to mount the
image. What tool would you use?
A. Deployment Image Servicing and Management (DISM)
B. Windows Deployment Services (WDS)
C. Windows Image Administration
D. Advanced Image Kit (AIK)

4. When WDS and DHCP operate on the same server, which DHCP option needs to be
configured for WDS?
A. Option 31
B. Option 60
C. Boot Option 4
D. WDS Server Option
Objective 1.2: Plan and implement a server
deployment infrastructure
After designing a strategy for automated server installation, you next need to build out the
infrastructure to support the server deployment strategy.
This objective covers the following configurations:
■
■ Multicast deployment
■
■ Multisite topology and distribution points
■
■ Multi-server topology
■
■ Autonomous and replica WDS servers
Configuring multicast deployment
WDS supports multicast deployments of server images. With multicast deployments, the im-
age is sent to multiple clients simultaneously, thus using network resources more efficiently.
Multicast deployments are configured within the Windows Deployment Services MMC
snap-in. Selecting Create Multicast Transmission within the server section starts the Create
Multicast Transmission Wizard, in which you configure the name for the multicast transmis-
sion, choose which install image to use, and determine whether to auto-cast or schedule the
multicast. Figure 1-4 shows this Multicast Type dialog box.
NOTE MULTICAST DEPLOYMENTS
Multicast deployments can be done only on network hardware that supports multicast
transmissions.

Objective 1.2: Plan and implement a server deployment infrastructure Chapter 1 13
FIGURE 1-4
Configuring the type of multicast to determine when the multicast will occur to clients.
Additional configuration to multicast deployment is achieved within the server’s Properties
sheet on the Multicast tab, shown in Figure 1-5.
FIGURE 1-5 The Multicast tab within the WDS server Properties sheet.

Configuring multisite topology and distribution points
A multisite topology is typically found in large, geographically dispersed organizations in
which the costs of bandwidth and network resources are higher than the management costs
associated with maintaining a server at each deployment site. Multisite topologies help make
bandwidth consumption more efficient by placing servers closer to the clients serviced by
WDS. Each WDS instance runs WDS services and has access to a centralized image store. If cli-
ent deployments take place over a wide area network (WAN) connection, you should ensure
that enough bandwidth is available for deployments.
A multisite topology relies heavily on File Replication Services (FRS) to copy images be-
tween WDS servers. Because WDS isn’t cluster-aware, the WDS servers don’t act in conjunc-
tion with one another. However, you can manage disparate WDS servers from a single WDS
management console.
The typical scenario for a multisite topology involves prestaging and assigning clients to
their nearest or local WDS server (known as a referral server).
Prestaging clients
Prestaging clients enables you to specify client settings such as the server that should re-
spond to a deployment request, the boot image, user credentials, and other items. To add a
prestaged client, right-click Active Directory Prestaged Devices in the WDS MMC snap-in and
select Add Device to launch the Add Prestaged Device Wizard.
The Add Prestaged Device Wizard begins with a dialog box to enter the device name and
the device ID. The Device ID is an identifier (GUID, UUID, or MAC address) that enables the
WDS server to identify the client when it asks for its deployment (see Figure 1-6).

FIGURE 1-6 Prestaging a client in WDS.
Clicking Next brings up the dialog box in Figure 1-7. This dialog box enables you to set the
boot information, including the referral server from which the client obtains its installation
information. You also can override the server’s default PXE Prompt Policy here so that you can
deploy servers without needing to press F12 on the server itself to start a PXE boot. The boot
image can also be chosen in this dialog box.

FIGURE 1-7 Choosing boot information for this prestaged client in WDS.
Clicking Next reveals a dialog box in which you can specify the unattended file, as well as
create a new unattended installation file (see Figure 1-8).

FIGURE 1-8 The Client Unattend dialog box enables you to specify an unattended installation file or cre-
ate a new one.
Clicking Create New reveals the Create Client Unattend dialog box in Figure 1-9. This im-
portant dialog box includes areas to specify the disk partitions for the client, the language to
use, and the install image to use for the client.

FIGURE 1-9 The Create Client Unattend dialog box enables you to specify a good deal of information
about the client to be deployed.
MORE INFO USING TYPICAL DEPLOYMENT SCENARIOS
See http://technet.microsoft.com/library/hh831764 for more information on typical deploy-
ment scenarios.
Configuring a multi-server topology
A multi-server topology helps provide redundancy to the WDS infrastructure and can be
used to spread the load image deployment among multiple servers. Like a multisite topology,
responses to client deployment requests can be split among the servers by configuring which
servers respond to which prestaged clients.
Because WDS isn’t cluster-aware and the roles within WDS can’t be split among servers, in
essence each server operates independently, although sharing a common image store repli-
cated through DFS is typical.

With that in mind, you need to perform limited configuration within WDS in a multi-server
topology, aside from configuring the location of the image store with DFS replication.
MORE INFO UNDERSTANDING DFS REPLICATION
See http://technet.microsoft.com/library/jj127250 for more information on DFS replication.
The WDS management console also enables multiple servers to be managed from a
central location. Configure this by right-clicking Servers and selecting Add Server. The Add
Servers dialog box in Figure 1-10 enables you to choose a server to add to the local manage-
ment console.
FIGURE 1-10 Choosing a server to manage from the central location helps facilitate a multi-server
topology.
Configuring WDS
After the Windows Deployment Services role is installed, you must initialize the server itself.
In the WDS Microsoft Management Console (MMC) snap-in, select Configure Server from
the server’s right-click context menu. In the configuration wizard, set up the mode for the
server—Active Directory Domain Services (AD DS) enabled or standalone—as well as how
(and whether) to respond to client requests.
If the server is configured with both Deployment Server and Transport Server roles, you
can add images to it as the final step in the configuration wizard. If you choose to do so, the
Add Image Wizard launches, and you can then select the location where installation media
(typically a DVD) can be found.

NOTE ROLE INSTALLATION
You can configure the Deployment and Transport roles only at the time of role installation.
You can’t reconfigure the image store location or the type of server (Standalone or Active
Directory Integrated) after the server is configured.
Most settings in WDS can be reconfigured at any time from within its Properties sheet,
which you open by right-clicking the server and selecting Properties from within the Windows
Deployment Services MMC snap-in.
Configuring multiple servers to work in tandem involves ensuring that their settings match
between servers. For example, the PXE Response Policy, found in the PXE Response tab (see
Figure 1-11), sets how WDS responds to PXE requests. If you’re deploying multiple servers to
be replicas of each other, the settings found in these tabs should match.
FIGURE 1-11 The PXE Response policy determines how WDS reacts when a PXE request is received.
■
■ Do Not Respond to Any Client Computers Using this setting essentially disables
PXE responses from this WDS server.
■
■ Respond Only to Known Client Computers This WDS server responds to prestaged
computers. Any unknown client trying to contact the deployment server is placed into
the Pending Devices node inside WDS, as shown in Figure 1-12.

FIGURE 1-12 A pending device in the WDS console.
■
■ Respond to All Client Computers The WDS server provides a response to all com-
puters. Notice the check box to enable administrator approval in Figure 1-11.
Figure 1-13 shows the Client tab, which enables you to specify some of the same settings
as you could from within the prestaging wizard, such as the location of the unattended file
and whether the client will join the domain.
FIGURE 1-13 The Client tab in the WDS server Properties sheet.

EXAM TIP
Click through the Properties sheet tabs within WDS to learn the location of the various
options available for deployment configuration.
New for Windows Server 2012 is the ability for WDS to operate as a standalone server,
meaning it’s not integrated with AD DS. When a server is configured in this Standalone mode,
the AD DS tab, among other properties, isn’t configurable within the server Properties sheet,
as shown in Figure 1-14.
FIGURE 1-14 When a server operates in Standalone mode, some configuration items aren’t available.

THOUGHT EXPERIMENT
Configuring a multi-server topology
In the following thought experiment, apply what you’ve learned about this objec-
tive. You can find answers to these questions in the “Answers” section at the end
of this chapter.
You need to configure a multi-server topology so that you can respond to client
deployment requests, even if one server goes offline. The overall configuration
should be such that clients can request provisioning and have as little intervention
as possible. The clients should be joined to the domain automatically and reboot
into the operating system.
1. How should you configure the image store for each server (for example, using
which tools)?
2. How should the PXE requests be configured for each server?
3. What tools or wizards should you use to automate the process as much as
possible?
Objective summary
■
■ Windows Deployment Services is configured at the server level, with the configuration
accessed through the Properties sheet.
■
■ Several items can be configured in WDS, including how the server responds to PXE
requests, whether the client will join a domain, and how networking such as multicast
and DHCP will operate.
■
■ Multicast transmissions are configured with their own wizard accessed through WDS.
Multicasting helps conserve bandwidth by deploying the image to multiple clients at
the same time.
■
■ Multi-server topologies are used when the number of clients needing to be deployed
exceeds the amount that a single server can handle or for redundancy. WDS isn’t
cluster-aware, and DFS replication is typically used to share images between servers.
■
■ Multisite topologies involve geographically diverse locations in which the cost of band-
width exceeds the cost of placing and managing a remote server for installs.
■
■ Both multi-server and multisite topologies typically use client prestaging so that clients
can be assigned to the correct or closest server.

Objective review
Answer the following questions to test your knowledge of the information in this objective.
You can find the answers to these questions and explanations of why each answer choice is
correct or incorrect in the “Answers” section at the end of this chapter.
1. Two modes of operation are available when deploying WDS. Which of the following
are not included in those modes? (Choose two.)
A. Deployment
B. Image Response
C. Transport
D. Capture
2. You’re deploying Windows Server 2012 using WDS and have multiple locations that
need an image, so you need to configure a multisite topology. Which of the following
steps is key when working with a multisite topology?
A. Configuring boot order so that the correct deployment server is chosen
B. Prestaging the client within WDS on the correct server
C. Configuring the correct image for the location chosen
D. Using multicast to ensure the most effective use of bandwidth
3. When creating a Scheduled Cast multicast deployment, with which of the following
methods can you begin deployment?
A. At a future time and/or when a threshold of clients request an image
B. At a future time and/or when the server comes online
C. Immediately or at a scheduled time
D. When the client threshold is set to met or daily
Objective 1.3: Plan and implement server
upgrade and migration
Upgrading servers, including changing their roles, and migrating servers from one role to
another are necessary tasks for administrators.
This objective covers the following topics:
■
■ Planning for role migration
■
■ Migrating server roles
■
■ Migrating servers across domains and forests

Objective 1.3: Plan and implement server upgrade and migration Chapter 1 25
■
■ Designing a server consolidation strategy
■
■ Planning for capacity and resource optimization
Planning for role migration
In general, role migration is defined as upgrades of a server’s services from one version of
an operating system to another—for example, from Windows Server 2008 to Windows Server
2012. Migration planning depends primarily on the roles you need to migrate. Migrating
AD DS requires different planning and execution than migrating File Services or other roles.
Migrations retain settings and configuration and can be used to move from physical to virtu-
alized installations of Windows.
Because Windows Server 2012 is x64-based architecture, you can migrate only from x64-
based servers. If the server isn’t x64-based, migration isn’t possible and the server will need to
have a clean install, after which the role can be configured for that server.
Windows Server Migration Tools provide a set of Windows PowerShell cmdlets to facilitate
the migration of roles. You can install these as a Feature in Windows Server 2012. Windows
Server Migration Tools can be used to migrate between the following editions of Windows
Server:
■
■ Windows Server Foundation
■
■ Windows Server Standard
■
■ Windows Server Enterprise
■
■ Windows Server Datacenter
The Windows Server Migration Tools are added to the Windows PowerShell command line
with the following command:
Add-PSSnapin Microsoft.Windows.ServerManager.Migration
After that snap-in is added, the migration-related cmdlets are available, specific to the
type of migration being performed. As previously stated, planning for migration depends
largely on what roles are being migrated. However, some steps are common to all role migra-
tion planning:
■
■ Identifying source and destination servers
■
■ Installing all critical updates to the source server
■
■ Ensuring that both the source and destination servers have the same number of net-
work adapters
■
■ Preparing a migration store file location that source and destination servers can both
access
There are also tasks related to specific roles. The following planning steps are involved in
select role migration scenarios.

Planning migration of AD DS and DNS
1. Introduce Windows Server 2012 into the domain so that the existing forest and domain
are prepared.
2. Ensure that the destination server meets the hardware requirements for the hosting
Active Directory roles.
3. Create an Active Directory backup of the source server.
4. Install Windows on the destination server, using a temporary name and IP address
because both will be changed later.
5. Ensure that the source DNS server is running correctly, as discussed in the "Migrating
server roles" section.
Planning migration of File Services servers
1. Install Windows on the destination server.
2. Ensure that the time and date are synchronized with the source server.
3. Match the same File Services features on both the source and destination servers.
4. Open TCP and UDP port 7000 on any network resources or firewalls between the
source and destination servers.
5. Verify that the destination server has enough free disk space and that any quotas allow
the free space to be used for storage.
MORE INFO UNDERSTANDING ROLE MIGRATION
See http://technet.microsoft.com/library/jj134202.aspx for more information on role migra-
tion and Windows Server Migration Tools.
Migrating server roles
After you plan how the migration will take place and perform initial steps for the migration,
you need to perform the actual migration. Like the planning stage, the steps involved in per-
forming the actual migration vary according to the type of migration being performed. This
section examines migration scenarios for common roles.
Migrating AD DS and DNS server roles
1. Add the Active Directory Domain Services role to the destination server.
2. Record the DNS settings on the source server using ipconfig /all.

MORE INFO USING IPCONFIG /ALL
See http://technet.microsoft.com/library/dd379556.aspx for more information on this
command-line tool.
3. Replicate the source server’s DNS settings onto the destination server. Use
the Dns-Service.REG and Dns-Software.REG files, which should be copied to
%windir%System32DNS on the destination server.
4. Execute the DNSconvergeCheck.cmd Convergence Verification Script to ensure that all
DNS records are replicated between the source and destination servers.
5. Ensure that the Flexible Single Master Operations (FSMO) roles are migrated, if
necessary.
MORE INFO MIGRATING FSMO
See http://go.microsoft.com/FWLink/?Linkid=70776 for more information.
6. Migrate IP addresses by changing the source server’s IP to a different IP address and
then changing the destination server to the source server’s original IP.
7. Rename the source server and use the netdom renamecomputer command to give the
destination server the source server’s original name.
8. Verify that the destination server is operating as the new domain controller.
Migrating File Services roles
1. Freeze configuration on the source server.
2. Migrate settings such as server message block (SMB), Offline Files (also called client-
side caching or CSC), DFS Namespaces, DFS Replication, File Server Resource Manager
(FSRM), and Shadow Copies of Shared Folders.
MORE INFO MIGRATING APPROPRIATE SETTINGS
See http://technet.microsoft.com/library/dd379474 for more information on each of these
items as they apply to your environment.
3. Export local users and groups. From the Windows Migration Tools PowerShell, use this
command:
Export-SmigServerSetting -User All -Group -Path <storepath>

4. Import the users from the source to the destination server:
Import-SmigServerSetting -User All -Group -Path <storepath>
5. Migrate the data.
MORE INFO MIGRATING DATA
See http://technet.microsoft.com/library/dd379474%28v=ws.10%29#BKMK_MigrateData
for more information on this step as it applies to your environment.
6. Rename and re-address the source server by changing its name and IP address.
7. Reconfigure the destination server to have the same name and address as the source.
8. Import settings from Step 2 to the destination server.
Migrating Dynamic Host Configuration Protocol (DHCP) server roles
1. Install the DHCP role onto the destination server.
2. Stop the DHCP Server service (Stop-Service DHCPserver).
3. Collect data from the source server with the Migration Tool cmdlet Export-
SmigServerSetting:
Export-SmigServerSetting –featureID DHCP –User All –Group –IPConfig –path
<storepath>
4. Delete the DHCP authorization on the source DHCP server:
Netsh DHCP delete server <server FQDN> <Server IP Address>
5. On the destination server, run the cmdlet Import-SmigServerSetting:
Import-SmigServerSetting -featureID DHCP -User All -Group -IPConfig <All | Global
| NIC> -SourcePhysicalAddress <Source IP Address> -TargetPhysicalAddress -Force
-path <storepath>
6. Start the DHCP service on the destination server:
Start-Service DHCPServer
7. Authorize the destination server (case sensitive):
netsh DHCP add server <Server FQDN> <Server IP Address>

Migrating servers across domains and forests
Server migration can occur across domains and forests, although you can’t migrate some
roles that depend on AD DS. Reasons for migrating domains and forests include organiza-
tional changes, mergers, and consolidation of regional locations. The Active Directory Migra-
tion Tool (ADMT) facilitates migration of objects across domains and across forests. Migrating
objects between forests is known as an interforest migration; migrating objects between
domains within the same forest is known as intraforest migration.
A trust relationship is typically created for both interforest and intraforest migration. The
trust enables ADMT to migrate computer resources between domains. Interforest trusts are
called Forest Trusts and can be a one-way trust or a two-way transitive trust.
MORE INFO UNDERSTANDING AND CREATING FOREST TRUSTS
See http://technet.microsoft.com/library/cc772440 for more information on Forest Trusts
and http://technet.microsoft.com/library/cc754626 for a step-by-step guide to creating a
Forest Trust.
Domain Trusts come in various forms and with various transitive properties. These include
external trusts for domains between forests, shortcut trusts that exist between domains within
a forest, and realm trusts for relationships between Active Directory domains and non-
Windows Kerberos version 5 (V5) realms.
MORE INFO UNDERSTANDING TRUST TYPES
See http://technet.microsoft.com/library/cc771568 for information on the different types of
trusts, including when to use each type.
ADMT migrates computers between domains and forests after a trust is established. Each
computer requires a restart after moving between domains, so this should be accounted for
when planning migration.
MORE INFO USING ADMT
See http://techhnet.microsoft.com/library/cc974412 for more information on using ADMT.
Designing a server consolidation strategy
The term server consolidation typically means virtualization with technology such as Hyper-V,
although that’s not always the case. Server consolidation can also mean consolidation of roles
from multiple servers onto one server. When considering this latter form of consolidation, you
must consider how consolidation of services will affect infrastructure reliability. For example,
you don’t want to place too many services or roles onto one server in case that server goes

down. Therefore, providing redundancy and separation of services to ensure uptime and reli-
ability is key when designing server consolidation.
Server consolidation by virtualization involves several steps:
1. Determine the virtualization scope.
2. Create a list of workloads.
3. Select backup and fault-tolerance approaches.
4. Summarize and analyze workload requirements.
MORE INFO USING THE WINDOWS SERVER VIRTUALIZATION GUIDE
More information about these steps and additional steps that involve execution of the
strategy can be found in the Windows Server Virtualization Guide at http://technet.microsoft
.com/library/bb897507.aspx.
Determine the virtualization scope
The first step in designing a server consolidation strategy involves defining the scope of the
project. For example, virtualizing an entire datacenter at once can be risky, as can the initial
investment. Also, if the organization has multiple data centers, each might need to have
virtualization hardware installed, which increases the initial cost of deployment. However,
deployment to those remote locations can in fact provide good pilot projects for the overall
virtualization deployment.
Create a list of workloads
Creating a list of workloads involves documenting what applications are currently deployed,
their current location, what operating system those applications use, the resources require-
ments for the workload, and the administrator or person responsible for the application or
workload.
The compatibility of the workload, specifically the ability for that application or workload to
be virtualized, should also be undertaken at this time. If a given workload isn’t compatible or
supported on virtualized infrastructure, it must be accounted for and excluded from the con-
solidation strategy. This task includes not only the technical compatibility but also the vendor’s
support and licensing model compatibility when running in a virtualized environment.
DETERMINING RESOURCE REQUIREMENTS
Determining the resource requirements for the virtualized workloads is an important facet
when creating a list of workloads. You should measure the current resources for physical ma-
chines and workloads, and then add resources to ensure that the load doesn’t meet its peak
load immediately on being virtualized.

Another Random Document on
Scribd Without Any Related Topics

che saliva dai marinai e dai passeggeri assembrati in coperta;
sorpassò, si risollevò. Il tono della raggiera ignita era pieno ed
eguale; l'astro mordace dell'elica trivellava l'aria infaticabilmente;
l'equilibrio tra ala ed ala, tra becco e coda era costante. La lieve
brezza di ponente spirava senza colpi né salti ne nodi; il mare
mutava colore qua e là, simile a un drappo broccato. Ma ora il
silenzio era pieno del rombo, che il volatore ascoltava di continuo
nell'attesa della prima pausa. La solitudine era tutta d'acqua e d'aria,
senza una vela, senza un filo di fumo, senza una linea di terra. Gli
parve di percepire una pausa nella raggiera, poi un'altra, poi più altre
intermesse. Vigilò il suo cuore, con un sorriso nella mente: il ritmo
interno s'era accelerato. «Che farci se l'Àrdea in questa bonaccia
rimanesse a galla per qualche tempo? Dovrei attendere o cercare di
colarla a fondo?» Il tono ridiveniva pieno. Il vento rinfrescava; il
soffio intaccava l'acqua e la copriva di squame; appariva lontano una
zona sempre più cupa. Egli cominciò a manovrare con attenzione più
acuta. «Compagno, compagno, sarà una bella morte! Se calcolo il
tempo e la velocità, ho già percorso circa settanta miglia marine.
Sono in mezzo al Tirreno. Ho una bella tomba profonda. Ti ricordi,
all'isola del Tino, alla Maddalena, quando chiusi nello scafandro
scendevamo verso gli orti delle Sirene?» Gli ritornava in tutto il corpo
quella gioia nuova, l'insolita leggerezza, come se il senso della
gravità fosse abolito pur sotto l'enorme peso; gli ritornava
singolarmente una strana divinità nelle mani che sole rimanevan
nude in contatto con l'acqua e potevan toccare e raccogliere per
entro alla tremula alba opalina le corolle veggenti e le mostruose
fami fiorite. «Fra quanto tempo il palombaro ridiscenderà nell'abisso
per trovare la Sirena che non trovò mai?»
E il tempo passava, e il tempo passava. E un'altra nave apparve,
navigandogli incontro diretta a levante, verso la costa d'Italia. E la
vide sotto di sé come un chiaro guscio distinto da una piumetta di
fumo. Il clamore gli giunse appena appena. Egli volava a grande
altezza, e la rapidità gli sferzava il viso entro il camaglio.
E intorno alla sua immobile aspettazione della morte incominciava
un'ansia confusa che ora pareva speranza e ora pareva rammarico e

ora pareva terrore. L'astro mordace dell'elica trivellava l'aria salsa
infaticabilmente. Egli aveva già percorso più di cento miglia marine.
«La morte poteva divenire la vita? il giorno d'immolazione divenire
giorno di trasfigurazione?»
Egli guardava di tratto in tratto le sue mani alla manovra, le sue
mani nude come quelle che sporgevano dallo scafandro; e gli pareva
che vivessero con una straordinaria potenza. Erano là, infaticabili
come le due pale dell'elica, senza tremare, senza tentare, senza
fallire. Il tono della raggiera ignita era pieno e gagliardo. Il Sole
dietro di lui salendo per l'erta feriva le ali ma non creava l'ombra. La
grande Àrdea di metallo di legno e di canape era immune dall'ombra,
come sparente, come inesistente, come cosa della riva di là, come
segno spettrale. Ma in quelle due mani le ossa i muscoli i tendini i
nervi erano tesi a un'opera disperata di vita, erano furenti di vita
come quelle che brandiscono l'arme alla suprema difesa, come
quelle che s'aggrappano al bordo del battello o alla scheggia dello
scoglio nel naufragio.
E il cuore gli tremò d'un tremito nuovo, d'un tremito che per la prima
volta moveva l'essere umano.
I minuti scoccavano, l'un dopo l'altro, come le scintille
dell'accensione. La luce e l'azzurro e l'onda fuggivano di continuo.
Quel ch'era insperato poteva esser raggiunto! Egli vedeva a faccia a
faccia il suo pilota, come in quell'altro giorno funebre quando gli
aveva chiesto: «Tu vuoi? Tu vuoi?»
E il cuore gli tremò perché v'era rinata la volontà di vivere, la volontà
di vivere per vincere.
Che poteva esser mai laggiù, in fondo alla linea dell'acqua, quella
lunga nuvola azzurra? una catena di monti? la terra? Egli guardò le
sue mani terribili. E sentì tutto il suo corpo proteso come per l'istinto
di acuirsi, di sfuggire al contrasto dell'aria, di adeguarsi alla forma
del fuso e del dardo. E sentì le sue pupille appuntate all'apparizione
lontana con una intensità che moltiplicava il senso per prodigio.
Era la terra! Era la terra!

E il suo amore del fratello e il suo dolore e il suo ardore furono il
Sole dietro a sé, sopra a sé, furono una presenza raggiante, una
immortalità incitatrice.
Era la vita! Era la vita!
Tale quel sogno sognato con tutto il peso della carne sanguigna, con
la faccia addentrata nell'origliere come la fame nella mangiatoia, col
sudore che stilla, con le pieghe dei lenzuoli che lasciano nella pelle
impronte come di percosse; e tale il suo sogno, tale il prodigio
sostenuto con la tensione di tutte le fibre, con la durezza di tutte le
ossa. E il tempo passava; e la raggiera irta rombava in ritmo; e
l'astro dell'elica trivellava il cielo.
Era la vittoria! Era la vittoria!
E come allora e assai più, di tutta la sua volontà egli fece un dardo
inflessibile, fece uno di quei dardi che i feditori chiamavano soliferro,
tutto ferro asta punta e cocca: un ferro che vedeva come nessuno
mai vide, un ferro che udiva come nessuno mai udì.
Udì in basso un lieve scricchiolìo, udì qualcosa cadere d'accanto al
suo piede sinistro. Al calore, s'accorse che s'era spezzata o
distaccata la tavoletta d'alluminio contrapposta al tubo di scarico, e
che il getto dei gas infiammati lo investiva senza riparo. Ma vedeva
la terra; la vedeva ingrandirsi, avvicinarsi di continuo, co' suoi monti,
co' suoi poggi, con le sue macchie, con le sue spiagge. Il vento ora
l'assaliva a colpi, a buffi, a rìfoli, a ràffiche.
Lottò, contrastò, assalto per assalto. Scorse e traverso l'onda eguale,
sotto di lui, una flottiglia di battelli sottomarini che navigavano con lo
scafo immerso, in manovra di battaglia. Comprese che Terranova, il
Capo Figari, Porto Cervo, Caprera, la Maddalena gli erano a
tramontana e ch'egli aveva tenuta la rotta più verso libeccio. Ma non
virò, non la mutò. Anche una volta egli aveva tracciato con l'animo
una linea più diritta di quella che le maestranze segnano col filo della
sinopia. La costa era là, deserta sterile e dorata; nella sua bassura,
propizia all'atterraggio. Scorse una muraglia informe di fichidindia;
scorse più lungi in un seno verdiccio un armento presso una capanna

conica. Scoprì in una calanca una lista di sabbione, contro una
macchia cupa forse di ginepri, forse di lentischi. La scelse per
atterrarsi. S'atterrò nel sogno e nel prodigio, sicuro e lieve,
dismemorato e inconsapevole, quasi al frangente dell'onda.
Non clamore, non tuono di trionfo; non moltitudine pallida di facce,
irta di mani. Silenzio selvaggio, erma gloria; e il mattino ancor
fresco; e il respiro del mare fanciullo che le braccia piegate della
terra cullavano; e la parola della segreta nutrice che sa la vita e la
morte e ciò che deve nascere e ciò che non può morire e il tempo di
tutto. «Figlio, non v'è dio se non sei tu quello.»
Egli restò attonito e intento per alcuni istanti. Poi fece l'atto di
balzare su la sabbia; ma lo spasimo della bruciatura profonda gli
strappò un grido, lo trattenne. Allora discese cauto, cercando intorno
un sostegno. Sedette sul lido solitario; e si pose a distaccare dal
piede incotto i resti del cuoio incarbonito. Come aveva esausta la
forza e non sosteneva lo strazio, scivolò fino alla riva; e tenne il
piede immerso nel mare.

OPERE di GABRIELE D'ANNUNZIO
Prose scelte L. 4
ROMANZI
Il Piacere 5 —
L'Innocente 4 —
Trionfo della Morte 5 —
Le Vergini delle Rocce 5 —
Il Fuoco 5 —
Le Novelle della Pescara 4 —
Forse che sì forse che no 5 —
POESIE
Canto novo; Intermezzo 4 —
L'Isottéo; la Chimera 4 —
Poema paradisiaco; Odi navali 4 —
La Canzone di Garibaldi: La Notte di Caprera 1 50
In morte di Giuseppe Verdi. Canzone 1 —
Nel primo centenario della nascita di Vittore
Hugo — MDCCCII-MCMII — ode
— 50
Elegie romane 3 50
Laudi del Cielo del Mare della Terra e degli Eroi
Vol. I: Laus Vitæ. Legato in finta pergamena 8 —

— Legato in vera pergamena 12 —
Vol. II: Elettra — Alcione. Legato in finta
pergamena 10 —
— Legato in vera pergamena 14 —
Edizione economica delle Laudi:
Laus Vitæ 4 —
Elettra 3 50
Alcione 3 50
L'Allegoria dell'Autunno 1 —
DRAMI
Francesca da Rimini 7 50
— Legata in pergamena con fregi i nastri 12 —
— Edizione economica 4 —
La Figlia di Iorio, tragedia in tre atti 4 —
— Legata in pelle, stile Cinquecento 10 —
La Fiaccola sotto il moggio, tragedia 4 —
— Legata in pelle, stile antico 10 —
La Città morta, tragedia in cinque atti 4 —
La Gioconda, tragedia in quattro atti 4 —
La Gloria, tragedia in cinque atti 4 —
I Sogni delle Stagioni
Sogno d'un mattino di primavera 2 —
Sogno d'un tramonto d'autunno 2 —
Più che l'amore, tragedia moderna 4 —
La Nave, tragedia in un prologo e tre episodi 5 —
Fedra, tragedia in tre atti 5 —
In preparazione:

Poesie scelte.
Le faville del maglio.
La madre folle, romanzo.

Nota del Trascrittore
Ortografia e punteggiatura originali sono state
mantenute, così come le grafie alternative (battè/batté,
bramosia/bramosìa, gorgoglio/gorgòglio/gorgóglio e
simili), correggendo senza annotazione minimi errori
tipografici.

*** END OF THE PROJECT GUTENBERG EBOOK FORSE CHE SÌ
FORSE CHE NO ***
Updated editions will replace the previous one—the old editions
will be renamed.
Creating the works from print editions not protected by U.S.
copyright law means that no one owns a United States
copyright in these works, so the Foundation (and you!) can copy
and distribute it in the United States without permission and
without paying copyright royalties. Special rules, set forth in the
General Terms of Use part of this license, apply to copying and
distributing Project Gutenberg™ electronic works to protect the
PROJECT GUTENBERG™ concept and trademark. Project
Gutenberg is a registered trademark, and may not be used if
you charge for an eBook, except by following the terms of the
trademark license, including paying royalties for use of the
Project Gutenberg trademark. If you do not charge anything for
copies of this eBook, complying with the trademark license is
very easy. You may use this eBook for nearly any purpose such
as creation of derivative works, reports, performances and
research. Project Gutenberg eBooks may be modified and
printed and given away—you may do practically ANYTHING in
the United States with eBooks not protected by U.S. copyright
law. Redistribution is subject to the trademark license, especially
commercial redistribution.
START: FULL LICENSE

THE FULL PROJECT GUTENBERG LICENSE

PLEASE READ THIS BEFORE YOU DISTRIBUTE OR USE THIS WORK
To protect the Project Gutenberg™ mission of promoting the
free distribution of electronic works, by using or distributing this
work (or any other work associated in any way with the phrase
“Project Gutenberg”), you agree to comply with all the terms of
the Full Project Gutenberg™ License available with this file or
online at www.gutenberg.org/license.
Section 1. General Terms of Use and
Redistributing Project Gutenberg™
electronic works
1.A. By reading or using any part of this Project Gutenberg™
electronic work, you indicate that you have read, understand,
agree to and accept all the terms of this license and intellectual
property (trademark/copyright) agreement. If you do not agree
to abide by all the terms of this agreement, you must cease
using and return or destroy all copies of Project Gutenberg™
electronic works in your possession. If you paid a fee for
obtaining a copy of or access to a Project Gutenberg™
electronic work and you do not agree to be bound by the terms
of this agreement, you may obtain a refund from the person or
entity to whom you paid the fee as set forth in paragraph 1.E.8.
1.B. “Project Gutenberg” is a registered trademark. It may only
be used on or associated in any way with an electronic work by
people who agree to be bound by the terms of this agreement.
There are a few things that you can do with most Project
Gutenberg™ electronic works even without complying with the
full terms of this agreement. See paragraph 1.C below. There
are a lot of things you can do with Project Gutenberg™
electronic works if you follow the terms of this agreement and
help preserve free future access to Project Gutenberg™
electronic works. See paragraph 1.E below.

1.C. The Project Gutenberg Literary Archive Foundation (“the
Foundation” or PGLAF), owns a compilation copyright in the
collection of Project Gutenberg™ electronic works. Nearly all the
individual works in the collection are in the public domain in the
United States. If an individual work is unprotected by copyright
law in the United States and you are located in the United
States, we do not claim a right to prevent you from copying,
distributing, performing, displaying or creating derivative works
based on the work as long as all references to Project
Gutenberg are removed. Of course, we hope that you will
support the Project Gutenberg™ mission of promoting free
access to electronic works by freely sharing Project Gutenberg™
works in compliance with the terms of this agreement for
keeping the Project Gutenberg™ name associated with the
work. You can easily comply with the terms of this agreement
by keeping this work in the same format with its attached full
Project Gutenberg™ License when you share it without charge
with others.
1.D. The copyright laws of the place where you are located also
govern what you can do with this work. Copyright laws in most
countries are in a constant state of change. If you are outside
the United States, check the laws of your country in addition to
the terms of this agreement before downloading, copying,
displaying, performing, distributing or creating derivative works
based on this work or any other Project Gutenberg™ work. The
Foundation makes no representations concerning the copyright
status of any work in any country other than the United States.
1.E. Unless you have removed all references to Project
Gutenberg:
1.E.1. The following sentence, with active links to, or other
immediate access to, the full Project Gutenberg™ License must
appear prominently whenever any copy of a Project
Gutenberg™ work (any work on which the phrase “Project

Gutenberg” appears, or with which the phrase “Project
Gutenberg” is associated) is accessed, displayed, performed,
viewed, copied or distributed:
This eBook is for the use of anyone anywhere in the United
States and most other parts of the world at no cost and
with almost no restrictions whatsoever. You may copy it,
give it away or re-use it under the terms of the Project
Gutenberg License included with this eBook or online at
www.gutenberg.org. If you are not located in the United
States, you will have to check the laws of the country
where you are located before using this eBook.
1.E.2. If an individual Project Gutenberg™ electronic work is
derived from texts not protected by U.S. copyright law (does not
contain a notice indicating that it is posted with permission of
the copyright holder), the work can be copied and distributed to
anyone in the United States without paying any fees or charges.
If you are redistributing or providing access to a work with the
phrase “Project Gutenberg” associated with or appearing on the
work, you must comply either with the requirements of
paragraphs 1.E.1 through 1.E.7 or obtain permission for the use
of the work and the Project Gutenberg™ trademark as set forth
in paragraphs 1.E.8 or 1.E.9.
1.E.3. If an individual Project Gutenberg™ electronic work is
posted with the permission of the copyright holder, your use and
distribution must comply with both paragraphs 1.E.1 through
1.E.7 and any additional terms imposed by the copyright holder.
Additional terms will be linked to the Project Gutenberg™
License for all works posted with the permission of the copyright
holder found at the beginning of this work.
1.E.4. Do not unlink or detach or remove the full Project
Gutenberg™ License terms from this work, or any files

containing a part of this work or any other work associated with
Project Gutenberg™.
1.E.5. Do not copy, display, perform, distribute or redistribute
this electronic work, or any part of this electronic work, without
prominently displaying the sentence set forth in paragraph 1.E.1
with active links or immediate access to the full terms of the
Project Gutenberg™ License.
1.E.6. You may convert to and distribute this work in any binary,
compressed, marked up, nonproprietary or proprietary form,
including any word processing or hypertext form. However, if
you provide access to or distribute copies of a Project
Gutenberg™ work in a format other than “Plain Vanilla ASCII” or
other format used in the official version posted on the official
Project Gutenberg™ website (www.gutenberg.org), you must,
at no additional cost, fee or expense to the user, provide a copy,
a means of exporting a copy, or a means of obtaining a copy
upon request, of the work in its original “Plain Vanilla ASCII” or
other form. Any alternate format must include the full Project
Gutenberg™ License as specified in paragraph 1.E.1.
1.E.7. Do not charge a fee for access to, viewing, displaying,
performing, copying or distributing any Project Gutenberg™
works unless you comply with paragraph 1.E.8 or 1.E.9.
1.E.8. You may charge a reasonable fee for copies of or
providing access to or distributing Project Gutenberg™
electronic works provided that:
• You pay a royalty fee of 20% of the gross profits you derive
from the use of Project Gutenberg™ works calculated using the
method you already use to calculate your applicable taxes. The
fee is owed to the owner of the Project Gutenberg™ trademark,
but he has agreed to donate royalties under this paragraph to
the Project Gutenberg Literary Archive Foundation. Royalty

payments must be paid within 60 days following each date on
which you prepare (or are legally required to prepare) your
periodic tax returns. Royalty payments should be clearly marked
as such and sent to the Project Gutenberg Literary Archive
Foundation at the address specified in Section 4, “Information
about donations to the Project Gutenberg Literary Archive
Foundation.”
• You provide a full refund of any money paid by a user who
notifies you in writing (or by e-mail) within 30 days of receipt
that s/he does not agree to the terms of the full Project
Gutenberg™ License. You must require such a user to return or
destroy all copies of the works possessed in a physical medium
and discontinue all use of and all access to other copies of
Project Gutenberg™ works.
• You provide, in accordance with paragraph 1.F.3, a full refund of
any money paid for a work or a replacement copy, if a defect in
the electronic work is discovered and reported to you within 90
days of receipt of the work.
• You comply with all other terms of this agreement for free
distribution of Project Gutenberg™ works.
1.E.9. If you wish to charge a fee or distribute a Project
Gutenberg™ electronic work or group of works on different
terms than are set forth in this agreement, you must obtain
permission in writing from the Project Gutenberg Literary
Archive Foundation, the manager of the Project Gutenberg™
trademark. Contact the Foundation as set forth in Section 3
below.
1.F.
1.F.1. Project Gutenberg volunteers and employees expend
considerable effort to identify, do copyright research on,
transcribe and proofread works not protected by U.S. copyright

law in creating the Project Gutenberg™ collection. Despite these
efforts, Project Gutenberg™ electronic works, and the medium
on which they may be stored, may contain “Defects,” such as,
but not limited to, incomplete, inaccurate or corrupt data,
transcription errors, a copyright or other intellectual property
infringement, a defective or damaged disk or other medium, a
computer virus, or computer codes that damage or cannot be
read by your equipment.
1.F.2. LIMITED WARRANTY, DISCLAIMER OF DAMAGES - Except
for the “Right of Replacement or Refund” described in
paragraph 1.F.3, the Project Gutenberg Literary Archive
Foundation, the owner of the Project Gutenberg™ trademark,
and any other party distributing a Project Gutenberg™ electronic
work under this agreement, disclaim all liability to you for
damages, costs and expenses, including legal fees. YOU AGREE
THAT YOU HAVE NO REMEDIES FOR NEGLIGENCE, STRICT
LIABILITY, BREACH OF WARRANTY OR BREACH OF CONTRACT
EXCEPT THOSE PROVIDED IN PARAGRAPH 1.F.3. YOU AGREE
THAT THE FOUNDATION, THE TRADEMARK OWNER, AND ANY
DISTRIBUTOR UNDER THIS AGREEMENT WILL NOT BE LIABLE
TO YOU FOR ACTUAL, DIRECT, INDIRECT, CONSEQUENTIAL,
PUNITIVE OR INCIDENTAL DAMAGES EVEN IF YOU GIVE
NOTICE OF THE POSSIBILITY OF SUCH DAMAGE.
1.F.3. LIMITED RIGHT OF REPLACEMENT OR REFUND - If you
discover a defect in this electronic work within 90 days of
receiving it, you can receive a refund of the money (if any) you
paid for it by sending a written explanation to the person you
received the work from. If you received the work on a physical
medium, you must return the medium with your written
explanation. The person or entity that provided you with the
defective work may elect to provide a replacement copy in lieu
of a refund. If you received the work electronically, the person
or entity providing it to you may choose to give you a second
opportunity to receive the work electronically in lieu of a refund.

If the second copy is also defective, you may demand a refund
in writing without further opportunities to fix the problem.
1.F.4. Except for the limited right of replacement or refund set
forth in paragraph 1.F.3, this work is provided to you ‘AS-IS’,
WITH NO OTHER WARRANTIES OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR ANY PURPOSE.
1.F.5. Some states do not allow disclaimers of certain implied
warranties or the exclusion or limitation of certain types of
damages. If any disclaimer or limitation set forth in this
agreement violates the law of the state applicable to this
agreement, the agreement shall be interpreted to make the
maximum disclaimer or limitation permitted by the applicable
state law. The invalidity or unenforceability of any provision of
this agreement shall not void the remaining provisions.
1.F.6. INDEMNITY - You agree to indemnify and hold the
Foundation, the trademark owner, any agent or employee of the
Foundation, anyone providing copies of Project Gutenberg™
electronic works in accordance with this agreement, and any
volunteers associated with the production, promotion and
distribution of Project Gutenberg™ electronic works, harmless
from all liability, costs and expenses, including legal fees, that
arise directly or indirectly from any of the following which you
do or cause to occur: (a) distribution of this or any Project
Gutenberg™ work, (b) alteration, modification, or additions or
deletions to any Project Gutenberg™ work, and (c) any Defect
you cause.
Section 2. Information about the Mission
of Project Gutenberg™

Project Gutenberg™ is synonymous with the free distribution of
electronic works in formats readable by the widest variety of
computers including obsolete, old, middle-aged and new
computers. It exists because of the efforts of hundreds of
volunteers and donations from people in all walks of life.
Volunteers and financial support to provide volunteers with the
assistance they need are critical to reaching Project
Gutenberg™’s goals and ensuring that the Project Gutenberg™
collection will remain freely available for generations to come. In
2001, the Project Gutenberg Literary Archive Foundation was
created to provide a secure and permanent future for Project
Gutenberg™ and future generations. To learn more about the
Project Gutenberg Literary Archive Foundation and how your
efforts and donations can help, see Sections 3 and 4 and the
Foundation information page at www.gutenberg.org.
Section 3. Information about the Project
Gutenberg Literary Archive Foundation
The Project Gutenberg Literary Archive Foundation is a non-
profit 501(c)(3) educational corporation organized under the
laws of the state of Mississippi and granted tax exempt status
by the Internal Revenue Service. The Foundation’s EIN or
federal tax identification number is 64-6221541. Contributions
to the Project Gutenberg Literary Archive Foundation are tax
deductible to the full extent permitted by U.S. federal laws and
your state’s laws.
The Foundation’s business office is located at 809 North 1500
West, Salt Lake City, UT 84116, (801) 596-1887. Email contact
links and up to date contact information can be found at the
Foundation’s website and official page at
www.gutenberg.org/contact

Section 4. Information about Donations to
the Project Gutenberg Literary Archive
Foundation
Project Gutenberg™ depends upon and cannot survive without
widespread public support and donations to carry out its mission
of increasing the number of public domain and licensed works
that can be freely distributed in machine-readable form
accessible by the widest array of equipment including outdated
equipment. Many small donations ($1 to $5,000) are particularly
important to maintaining tax exempt status with the IRS.
The Foundation is committed to complying with the laws
regulating charities and charitable donations in all 50 states of
the United States. Compliance requirements are not uniform
and it takes a considerable effort, much paperwork and many
fees to meet and keep up with these requirements. We do not
solicit donations in locations where we have not received written
confirmation of compliance. To SEND DONATIONS or determine
the status of compliance for any particular state visit
www.gutenberg.org/donate.
While we cannot and do not solicit contributions from states
where we have not met the solicitation requirements, we know
of no prohibition against accepting unsolicited donations from
donors in such states who approach us with offers to donate.
International donations are gratefully accepted, but we cannot
make any statements concerning tax treatment of donations
received from outside the United States. U.S. laws alone swamp
our small staff.
Please check the Project Gutenberg web pages for current
donation methods and addresses. Donations are accepted in a
number of other ways including checks, online payments and

credit card donations. To donate, please visit:
www.gutenberg.org/donate.
Section 5. General Information About
Project Gutenberg™ electronic works
Professor Michael S. Hart was the originator of the Project
Gutenberg™ concept of a library of electronic works that could
be freely shared with anyone. For forty years, he produced and
distributed Project Gutenberg™ eBooks with only a loose
network of volunteer support.
Project Gutenberg™ eBooks are often created from several
printed editions, all of which are confirmed as not protected by
copyright in the U.S. unless a copyright notice is included. Thus,
we do not necessarily keep eBooks in compliance with any
particular paper edition.
Most people start at our website which has the main PG search
facility: www.gutenberg.org.
This website includes information about Project Gutenberg™,
including how to make donations to the Project Gutenberg
Literary Archive Foundation, how to help produce our new
eBooks, and how to subscribe to our email newsletter to hear
about new eBooks.

Welcome to our website – the perfect destination for book lovers and
knowledge seekers. We believe that every book holds a new world,
offering opportunities for learning, discovery, and personal growth.
That’s why we are dedicated to bringing you a diverse collection of
books, ranging from classic literature and specialized publications to
self-development guides and children's books.
More than just a book-buying platform, we strive to be a bridge
connecting you with timeless cultural and intellectual values. With an
elegant, user-friendly interface and a smart search system, you can
quickly find the books that best suit your interests. Additionally,
our special promotions and home delivery services help you save time
and fully enjoy the joy of reading.
Join us on a journey of knowledge exploration, passion nurturing, and
personal growth every day!
ebookbell.com

Exam Ref 70413 Designing And Implementing A Server Infrastructure Steve Suehring

More Related Content

Similar to Exam Ref 70413 Designing And Implementing A Server Infrastructure Steve Suehring (20)

Recently uploaded (20)

Exam Ref 70413 Designing And Implementing A Server Infrastructure Steve Suehring