###BeginCaseStudy###
Case Study: 13
Blue Yonder Airlines
Scenario
COMPANY OVERVIEW
Blue Yonder Airlines has a main office and four branch offices. Each branch office has six
satellite offices. The main office is located in Sydney. The branch offices are located in
London, New York, Bangkok, and Istanbul. The main office has 1,000 users. Each branch
office has 500 users. Each satellite office has 50 to 100 users.
PLANNED CHANGES
Each satellite office will have a single server deployed. The servers will have the following
server roles installed:
• File server
• Print server
• Read-only Domain Controller (RODC)
Each satellite office will have a local support technician who performs the following tasks:
• Manages printers.
• Manages server backups.
• Manages updates on the server.
Each support technician will only be permitted to manage the server located in his office.
You plan to implement a backup and recovery solution to restore deleted Active Directory
objects. The solution must ensure that the attributes of the deleted objects are restored to the
same state they were in before they were deleted. You plan to deploy a custom sales
Application named App2 to the portable computers of all company sales consultants. The
setup program of App2 requires local administrative privileges. App2 will be updated
monthly.
BUSINESS GOALS
Blue Yonder Airlines has the following business goals:
• Minimize server downtime.
• Minimize administrative effort.
Minimize interruptions to users caused by WAN link failures.
EXISTING ENVIRONMENT
The network contains servers that run either Windows Server 2008 R2 or Windows Server
2008. All client computers were recently replaced with new computers that run Windows 7
Enterprise.
Users do not have local administrator rights on the client computers.
Existing Active Directory/Directory Services
The network contains a single Active Directory domain named blueyonderairlines.com. The
functional level of the domain is Windows Server 2008. All domain controllers run Windows
Server 2008.
Existing Network Infrastructure
All offices have wired and wireless networks.
The main office has a file server that stores large graphics files. The files are used by all of
the users in all of the offices.

A Group Policy is used to assign an Application named App1 to all of the users in the
domain.
The branch offices contain public computers on which temporary employees can browse the
Internet and view electronic brochures. When the employees log on to the public computers,
they must all receive the same user settings. App1 must not be installed on the public
computers. The computer accounts for all of the public computers are in an organizational
unit (OU) name Public.
REQUIREMENTS
Security Requirements
All computers in the domain must have a domain-level security Group Policy object (GPO)
App1ied.
You plan to implement Network Access Protection (NAP) by using switches and wireless
access points (WAPs) as NAP enforcement points.
The public computers must meet the following security requirements:
• Only authorized Applications must be run.
• Automatic updates must be enabled and App1ied automatically.
Users must be denied access to the local hard disk drives and the network shares from the
public computers.
Technical Requirements
The file server in each branch office is configured as shown in the following table.

Each user is allocated 1 GB of storage on the Users share in their local office. Each user must
be prevented from storing files larger than 500 MB on the Data share in their local office.
Blue Yonder Airlines must meet the following requirements for managing App2:
• Sales consultants must use the latest version of the Application.
• When a new version of App2 is installed, the previous version must be uninstalled. Sales
consultants must be able to run App2 when they are disconnected from the network.
###EndCaseStudy###

You need to recommend a solution to ensure that users in the London office can access the graphics
files in the main office. The solution must meet the company’s business goals. What should you
recommend?

A.
Configure the client computers to use BranchCache in Distributed Cache mode.

B.
Deploy a standalone Distributed File System (DFS) namespace. Configure a DFS Replication group.

C.
Deploy a domainbased Distributed File System (DFS) namespace. Configure a DFS Replication
group.

D.
Deploy a BranchCache server that operates in Hosted Cache mode. Configure the client
computers to use the BranchCache server.

Explanation:

BranchCach is a Server 2008 R2 feature
http ://technet.microsoft.com/en-us/library/cc731545.aspx
Review Requirements for DFS Replication
Applies To: Windows Server 2008 R2
Before you can deploy DFS Replication, you must configure your servers as follows:
Extend (or update) the Active Directory Domain Services (AD DS) schema to include Windows Server
2003 R2, Windows Server 2008, or Windows Server 2008 R2 schema additions. To use read-only
replicated folders, the schema must include the Windows Server 2008 or newer schema additions.
For information about extending the AD DS schema, see the Microsoft Web site at (http
://go.microsoft.com/fwlink/?LinkId=93051).
Ensure that all servers in a replication group are located in the same forest. You cannot enable
replication across servers in different forests.
Verify that all members of the replication group are running Windows Server 2008 R2, Windows
Server 2008, or Windows Server 2003 R2. DFS Replication is supported on all x64 editions of
Windows Server 2008 R2 and all x64 and x86 editions of Windows Server 2008. DFS Replication is
not available for Itanium-Based Systems.
Install DFS Replication on all servers that will act as members of a replication group.
Install the DFS Management snap-in on a server to manage replication. This server cannot run a
Server Core installation of the Windows Server 2008 operating system.

Contact your antivirus software vendor to check that your antivirus software is compatible with DFS
Replication.
Store replicated folders on NTFS volumes.
To include a failover cluster in a replication group, the failover cluster must be running Windows
Server 2008 R2. Install and configure the failover cluster feature and then use the High Availability
Wizard to create a clustered File Server instance before adding the instance as a replication group
member. For more information, see Add a Failover Cluster to a Replication Group.
On a server that is running a version of Windows older than Windows Server 2008 R2, locate
replicated folders for failover clusters in the local storage of a node. Versions of the DFS Replication
service older than Windows Server 2008 R2 are not designed to coordinate with cluster components,
and the service will not fail over to another node.