DRAG DROP
###BeginCaseStudy###
Case Study: 2
Proseware, Inc
Overview
General Overview
Proseware, Inc. is a pharmaceutical services company that has a sales department, a
marketing department, an operations department, and a human resources department.
Physical Locations
Proseware has two main offices. One of the offices is located in New York. The other office
is located in Chicago. The New York office uses a 172.16.1.0/24 network ID. The Chicago
office uses a 192.168.1.0/24 network ID.
The offices connect to each other by using a high-bandwidth, low-latency WAN link. Each
office connects directly to the Internet.
Existing Environment
The network contains an Active Directory forest named proseware.com. The forest contains
two domains named proseware.com and chicago.proseware.com. All of the user accounts and
the computer accounts in the New York office reside in the proseware.com domain. All of the
user accounts and the computer accounts in the Chicago office reside in the
chicago.proseware.com domain. All DNS zones are Active-Directory-integrated.
Each office is configured as an Active Directory site. The network ID for each office is
associated to the appropriate site.
Each office contains two domain controllers. The domain controllers were recently upgraded
from Windows Server 2008 R2 to Windows Server 2012 R2. The functional level of the
domain and the forest is Windows Server 2003.
The company uses Active Directory user attributes to store the personal information of its
employees in custom attributes.
Existing Servers
The relevant servers are configured as shown in the following table.
All servers run Windows Server 2012 R2.
DC01 has an IPv4 scope. The starting IP address in the range is 172.16.1.100 and the ending
address is 172.16.1.199.
DC03 has an IP4v scope. The starting IP address in the range is 192.168.1.100 and the ending
IP address is 192.168.1.199. There are no exclusion ranges configured on DC01 or DC03.
Requirements
Planned Changes
Proseware plans to implement the following changes:
• Deploy a read-only domain controller (RODC) to the London office.
• Give users remote access to both offices by using a VPN connection from their laptop
or tablet.
• If DC01 fails, ensure that the computers in the New York office can receive IP
addresses within 30 minutes.
• In the New York site, deploy two 50-TB, Fibre Channel SAN disk arrays. Offloaded
Data Transfer (ODX) will be used on both storage arrays. The Hyper-V hosts will use the
new SANs for virtual machine storage.
• Open three additional offices in Montreal, Atlanta, and London. The offices will
connect to each other by using a high-bandwidth, low-latency WAN link. Each office will
connect directly to the Internet.
• For legal reasons, the Montreal site will have its own forest named
montreal.proseware.com.
• The Montreal and Atlanta offices will have local IT administrators to manage the
network infrastructure of their respective office. The London office will not have a local IT
staff. Each office will have approximately 50 client computers.
Technical Requirements
Proseware identifies the following technical requirements:
• Users in the Montreal office must only be allowed to access shares that are located on
File01 and File02. The Montreal users must be prevented from accessing any other servers in
the proseware.com forest regardless of the permissions on the resources,
• Users in the New York office must be able to reconnect to the remote access VPN
servers automatically. Users in the Chicago office must use SSL to connect to the remote
access VPN servers.
• Domain controllers that run Windows Server 2012 R2 and Windows Server 2008 R2
must be able to be deployed to the proseware.com domain.
• Administrators in the New York office must be able to restore objects from the Active
Directory Recycle Bin.
• The DNS servers must be prevented from overwriting the existing DNS entries that
have been stored in cache.
• Each DNS server must be managed by an administrator from the same office as the
DNS server.
• The required time to create new fixed virtual hard disks (VHDs) on the SANs must be
minimized.
• The remote access servers must be able to restrict outgoing traffic based on IP
addresses.
• All certificates must be deployed to all of the client computers by using autoenrollment.
• All of the DHCP Server server roles must be installed on a domain controller.
• Only one DHCP server in each site must lease IP addresses at any given time.
• DHCP traffic must not cross site boundaries.
• RODCs must not contain personal user information.
###EndCaseStudy###
You need to recommend changes for the Active Directory infrastructure.
What should you recommend? To answer, drag the appropriate domain and forest functional
levels for proseware.com to the correct locations. Each functional level may be used once,
more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.
Answer: 
Explanation:
Windows Server 2008 R2 is required due to the requirement of the administrators in the New York office requiring the use of the recycle bin
This requires raising the functional forest AND domain levels to 2008r2. https://technet.microsoft.com/en-us/library/dd392261%28v=ws.10%29.aspx
Why would a functional level of Windows Server 2012 R2 also not be valid?
I don’t know. Probably just another dumb fucking question from MS. I had the same thought as you, both 2008 r2 and 2012 r2 have the recycle bin disabled by default, not sure why they are keeping it at 2008r2.
It would be valid, but not necessary since Server 2012 R2 didn’t bring any new features with its functional level.
because of this requirement:
• Domain controllers that run Windows Server 2012 R2 and Windows Server 2008 R2 must be able to be deployed to the proseware.com domain.
That will not be possible when the levels are set to Windows 2012 R2
@Answerer: that article does NOT mention the domain functional level must be 2008 R2. It only states the forest functional level must be 2008 R2.
This is it:
“Domain controllers that run Windows Server 2012 R2 and Windows Server 2008 R2 must be able to be deployed to the proseware.com domain.”
Because of that you cannot raise the domain level above 2008 R2 (and of course the forest function level too):
“Domain controllers that run Windows Server 2012 R2 and Windows Server 2008 R2
must be able to be deployed to the proseware.com domain.”
I see 3 requirements:
1) “AD Recycle Bin”
It requires 2008R2 FFL
2) “Domain controllers that run 2012 R2 and 2008 R2 must be able to be deployed”
It requires 2008R2 DFL
3) “The Montreal users must be prevented from accessing any other servers
in the proseware.com forest regardless of the permissions on the resources”
I believe this refers to Dynamic Access Control that requires 2012 DFL
I was wrong about the 3rd requirement.
It is actually referring to the next question about Forest Trust.
2008 R2 Forest and Domain…
“Domain controllers that run Windows Server 2012 R2 and Windows Server 2008 R2
must be able to be deployed to the proseware.com domain”
There is a 3rd requirement -> deploy RODC to London office. For this the FFL as he DFL must e 2003 or higher.