###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 planning a recovery strategy in the event that a file server is unable to boot into Windows.
You need to ensure that file servers can be restored from backups. What should the recovery
strategy include?
A.
Deploy backups by using WDS.
B.
Boot from the Windows Server 2008 R2 DVD into the Recovery Environment, then restore from
file server backups by using WBAdmin.
C.
Reinstall Windows Server 2008 R2 from DVD, then restore from file server backups by using
Windows Server Backup.
D.
Restore from file server backups by using NTBackup.
Explanation:
Thanks to Testy for highlighting this one.
NTBackup is not compatible with Server 2008 R2.
Your requirements are for remote backup and remote restore.
The network has WDS installed and uses PXE boot on the servers so WDS could be used to deploy a
backup.
Windows Recovery Environment (Windows RE) is an extensible recovery platform based on
Windows Preinstallation Environment (Windows PE). When the computer fails to start, Windows
automatically fails over into this environment, and the Startup Repair tool in Windows RE automates
the diagnosis and repair of an unbootable Windows Vista installation. Furthermore, Windows RE is a
starting point for various tools for manual system recovery. The primary audience of this technology
includes original equipment manufacturers (OEMs), original device manufacturers (ODMs), and
corporate IT professionals.
Image-based Recovery from Windows RE In the event that the Windows installation cannot be
repaired with Startup Repair or other manual repair steps, Windows RE can be used to launch an
image-based recovery tool.
User-created Recovery Image
Windows Vista provides end users with the ability to create a backup image of their entire operating
system.
End users can do this by using the Backup tool. The system image can be stored on an external hard
disk, on a hard disk partition other than those imaged, or on a DVD. To restore the computer by
using this system image, users must launch the restore interface from the list of Windows RE manual
tools.
Factory-created Recovery Image
To facilitate restoring a computer to its factory state, a recovery image can be placed on the
Windows RE partition. This eliminates the need for a separate recovery media in most cases.
If the Windows image format is used in the manufacturing process, the same operating system
image can be used for recovery as well. A computer manufacturer can develop an application by
using the Imaging APIs for Windows and the Windows image to restore the operating system
volume. This application can be launched from the Windows RE user interface (UI) by using
customizations provided by the ODM.