###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 need to configure the role services on all file servers that are necessary to meet the technical
requirements. Which role services should you configure? (Choose all that Apply.)

A.
File Server Resource Manager

B.
BranchCache for network files

C.
Windows Search Service

D.
Distributed File System

E.
Services for Network File System

Explanation:

Requirements:
Minimize downtime for users accessing across a WAN = Branch Cache
Files Always opened from the nearest Server =DFS
Files at same path = DFS
Department volumes have Quotas
There is some debat if FSRM is needed. the original answer from Pass4Sure says that A FSRM is
required.
However if you look at the exhibit it clearly says Departmental Volumes and not departmental
shares so the question is do you need FSRM to apply quotas to a Volume? the answer is No you
dont. NTFS Quota will apply quota by right clicking on the volume then selecting properties then
selecting quotas. The differences between NTFS and FSRM quotas are basically NTFS is a disk quota,
so the accounts cannot use more than the allowed space on the complete disk. With FSRM you can
use folder quotas and differentiate it for your needs. so with NTFS if you set the quotas to 3 GB on
one volume then all users that save data to that volume can only have up to 3GB of data on the
whole volume, with FSRM quotas you can set it at the volume OR folder level.
A basic disk is a physical disk that contains primary partitions, extended partitions, or logical drives.
Partitions and logical drives on basic disks are known as basic volumes. You can only create basic
volumes on basic disks.
BranchCache
BranchCache is a wide area network (WAN) bandwidth optimization technology that is included in
the Windows Server® 2008 R2 and Windows® 7 operating systems.
To optimize WAN bandwidth, BranchCache copies content from your main office content servers
and caches the content at branch office locations, allowing client computers at branch offices to
access the content locally rather than over the WAN.
At branch offices, content is cached either on servers that are running the BranchCache feature of
Windows Server 2008 R2 or, when no server is available in the branch office, on computers running
Windows 7. After a client computer requests and receives content from the main office and the
content is cached at the branch office, other computers at the same branch office can obtain the
content locally rather than contacting the main office over the WAN link.
BranchCache helps improve content query response times for clients and servers in branch offices,
and can also help improve network performance by reducing traffic over WAN links.
The BranchCache for network files role service is part of the File Services server role. BranchCache
for network files is deeply integrated with file services and allows you to deploy a BranchCacheenabled file server.
When you deploy a BranchCache-enabled file server, BranchCache creates content information for
every file in every shared folder where BranchCache is enabled.
Distributed File System (DFS) Namespaces and DFS Replication offer simplified, highly-available
access to files, load sharing, and WAN-friendly replication. In the Windows Server® 2003 R2
operating system, Microsoft revised and renamed DFS Namespaces (formerly called DFS), replaced
the Distributed File System snap-in with the DFS Management snap-in, and introduced the new DFS
Replication feature. In the Windows Server® 2008 operating system, Microsoft added the Windows
Server 2008 mode of domain-based namespaces and added a number of usability and performance
improvements.
What does Distributed File System (DFS) do?

The Distributed File System (DFS) technologies offer wide area network (WAN)-friendly replication as
well as simplified, highly-available access to geographically dispersed files. The two technologies in
DFS are the following:
DFS Namespaces. Enables you to group shared folders that are located on different servers into one
or more logically structured namespaces. Each namespace appears to users as a single shared folder
with a series of subfolders. This structure increases availability and automatically connects users to
shared folders in the same Active Directory Domain Services site, when available, instead of routing
them over WAN connections.
DFS Replication. DFS Replication is an efficient, multiple-master replication engine that you can use
to keep folders synchronized between servers across limited bandwidth network connections. It
replaces the File Replication Service (FRS) as the replication engine for DFS Namespaces, as well as
for replicating the AD DS SYSVOL folder in domains that use the Windows Server 2008 domain
functional level.
For completion I’ve included details on FSRM
FSRM
With the increasing demand on storage resources, as organizations rely more heavily on data than
ever before, IT administrators face the challenge of overseeing a larger and more complex storage
infrastructure, while at the same time, tracking the kind of information available in it. Managing
storage resources not only includes data size and availability any more but also the enforcement of
company policies and a very good understanding of how existing storage is utilized, allowing for
sound strategic planning and proper response to organizational changes.
File Server Resource Manager is a suite of tools that allows administrators to understand, control,
and manage the quantity and type of data stored on their servers. By using File Server Resource
Manager, administrators can place quotas on folders and volumes, actively screen files, and
generate comprehensive storage reports.
This set of advanced instruments not only helps the administrator to efficiently monitor existing
storage resources but it also aids in the planning and implementation of future policy changes.