###BeginCaseStudy###
Case Study: 17
Graphic Design Institute, Case B
General Background
You are the systems administrator for the Graphic Design Institute (GDI). GDI is a private
liberal arts and technical college with campuses in multiple cities.
Technical Background
The campus locations, users, client computers, and servers are described in the following
table.

The campuses are connected by a fully meshed WAN.
The corporate network includes Active Directory Domain Services (AD DS). Domain
controllers are located on each campus.
GDI uses Microsoft Windows Deployment Server (WDS) to distribute images by using
Preboot Execution Environment (PXE). GDI builds images by using the Windows
Automated Installation Kit (WAIK).
GDI uses Microsoft Windows Server Update Services (WSUS) to distribute and manage
Windows security updates and software updates. All private client computers and portable
computers used by faculty and staff are members of the WSUS computer group named Staff.
All shared client computers are members of the WSUS computer group named
LabComputers. All faculty and staff users are members of the global security group named
GDI_Staff. All students are members of the global security group named GDI_Students.
Specific servers are configured as shown in the following table.

The main data center is located on the Boston campus. ADMX and ADML files are centrally
stored on BODC01.
All Charlotte servers reside in the CH_Servers organizational unit (OU). CHDATA01,
CHDATA02, CHDATA03, and CHDATA04 reside in the CH_FileServers OU.
CH_FileServers is a child OU of CH_Servers.

A Group Policy object (GPO) named ServerSettings App1ies Windows Internet Explorer
settings to all servers.
Business Requirements
After successful migrations to Windows Server 2008 R2 in Boston, New Haven, and
Tacoma, GDI plans to migrate its other campuses to Windows Server 2008 R2 in advance of
a full Windows 7 client computer deployment. Server deployment on the Austin campus must
be performed on weekends by using scheduled deployments. The post-migration environment
must meet the following business requirements:
• Maximize security
• Maximize data protection
• Maximize existing resources
• Minimize downtime
Technical Requirements
The post-migration environment must meet the following security requirements:
• All updates must be distributed by using WSUS.
• All critical updates must be installed as soon as possible.
• All drives on the Minneapolis campus servers must have Windows BitLocker Drive
Encryption enabled.
The post-migration environment must meet the following data protection requirements:
• All servers must have automated backup routines.
• All backups must be replicated to the Boston data center at the end of each business
week.
• The post-migration environment must meet the following resource requirements:
• Installations and recovery must be performed remotely.
• All department volumes on file servers must have NTFS quotas.
• Minimize download time for users who open Microsoft Office documents over the
WAN.
• Ensure that users’ files are always opened from the closest file server when available.
• Users’ files must be accessible by the same path from all campuses.
###EndCaseStudy###

You are designing a Windows Server 2008 R2 deployment strategy for the Minneapolis campus
servers. Which deployment strategy should you recommend?

A.
install from media.

B.
Use a discover image in WDS.

C.
Deploy a VHD image.

D.
Deploy a WIM image.

Explanation:

Requirements – Bitlocker is needed on all disks in Minneapolis and installations must be done
remotely
VHD Image
– according to the official MS courseware book 6433A – a VHD can not contain more than one
partition. so if true that rules VHD Images out because you need bitlocker and bitlocker requires 2
partitions. so if this is true then answer C is wrong.also

http ://technet.microsoft.com/en-us/library/dd363560.aspx
A supported .vhd image. The only supported operating systems are Windows Server 2008 R2,
Windows 7 Enterprise, and Windows 7 Ultimate. Fixed, dynamic, and differencing .vhd images are
supported. However, note that a supported image cannot contain the following:
More than one operating system.
More than one partition.
Applications or data (instead of an operating system).
A 64-bit operating system that is partitioned with a GUID partition table (GPT).
So again further evidence that C is not the right answer as Bit locker needs 2 partitions.
I’m leaning toward Answer B because
WDS Images
WDS uses two different types of images: install images and boot images. Install images are the
operating system images that will be deployed to computers running Windows Server 2008 R2,
Windows Server 2008, Windows 7, or Windows Vista. A default installation image named Install.wim
is located in the \Sources directory of the installation DVD. If you are using WDS to deploy Windows
7 to computers with different processor architectures, it will be necessary to add separate
installation images for each architecture to the WDS server.
Architecture-specific images can be found on the architecture-specific installation media; for
example, the Itanium image is located on the Itanium installation media, and the x64 default
installation image is located on the x64 installation media. Although it is possible to create custom
images, it is necessary to have only one image per processor architecture. For example, deploying
Windows Server 2008 R2 Enterprise edition x64 to a computer with two x64 processors and to a
computer with eight x64 processors in SMP configuration only requires access to the default x64
installation image. Boot images are used to start a client computer prior to the installation of the
operating system image. When a computer starts off a boot image over the network, a menu is
presented that displays the possible images that can be deployed to the computer from the WDS
server. The Windows Server 2008 R2 Boot.wim file allows for advanced deployment options, and this
file should be used instead of the Boot.wim file that is available from other sources.
In addition to the basic boot image, there are two separate types of additional boot images that can
be configured for use with WDS. The capture image is a boot image that starts the WDS capture
utility. This utility is used with a reference computer, prepared with the Sysprep utility, as a method
of capturing the reference computer’s image for deployment with WDS. The second type of
additional boot image is the discover image. Discover images are used to deploy images to
computers that are not PXE-enabled or on networks that don’t allow PXE. These images are written
to CD, DVD, or USB media and the computer is started off the media rather than off the PXE network
card, which is the traditional method of using WDS.
I’m gonna make a huge assumption that the Minneapolis servers are on a different subnet, which
makes sense because they are all different campuses for a college. but if there is a DHCP Server or IP
Helper is enabled then that wont be a problem. So B may not be the answer
Media Install
It specifically says they use WDS for deployment. WDS is all about using images so would that not
rule out media install? you can do media installs that are unattended but it requires sending a DVD
and corresponding USB key with an answer file to the site and it being inserted into the server. but
GDI uses PXE enabled network
cards so that would imply media is not used as images would be stored centrally. so I’d rule out A so
that just leaves D