###BeginCaseStudy###
Case Study: 1
Contoso Ltd (A)
Overview
Contoso, Ltd., is a healthcare company in Europe that has 2,000 users. The company is
migrating to Windows Server 2012.
The company has two main offices and two branch offices. The main offices are located in
Paris and Amsterdam. One of the branch offices is a sales office located in Berlin. The other
branch office is a research office located in Brussels.
The offices connect to each other by using a WAN link.
Current Environment
Active Directory
The network contains an Active Directory forest named contoso.com. An Active Directory
site exists for each office.
The forest contains a child domain named research.contoso.com.
The functional level of both the domains is Windows Server 2008.
In each site, there are two domain controllers for the contoso.com domain and two domain
controllers for the research.contoso.com domain. The domain controllers run Windows
Server 2008 R2.
All of the domain controllers are global catalog servers.
The FSMO roles were not moved since the domains were deployed.
Network Infrastructure
All servers run Windows Server 2008 R2.
Each user has a laptop computer that runs Windows 7.
The company has 10 print servers. Each print server contains several shared printers.
The company has 10 file servers that have the following disk configurations:
• A simple volume named C that is the System and Boot volume and is
formatted NTFS
• A mounted virtual hard disk (VHD) named DATA that is formatted
NTFS
• A simple volume named D that is formatted FAT32
• A simple volume named E that is formatted NTFS
• A Clustered Shared Volume (CSV)
The Paris office contains a server named PA1. The Amsterdam office contains a server
named AM1. Both servers have the following server roles installed:
• DNS Server
• DHCP Server
• Remote Access
The DNS servers are configured to use the DNS servers of the company’s Internet Service
Provider (ISP) as forwarders.
Users often work remotely. The users access the internal network by using an SSTP-based
VPN connection.
Requirements
Planned Changes
The company plans to implement the following changes:
• Create a child domain named sales.contoso.com. Only the domain controllers in
sales.contoso.com will host a zone for the sales.contoso.com domain. The domain
controllers in sales.contoso.com will run Windows Server 2012. The client computers
in sales.contoso.com will use the sales.contoso.com domain controllers as their DNS
servers.
• Implement two servers in the Amsterdam office and two servers in the Paris office to
replace PA1 and AMI. These new servers will run Windows Server 2012 and will not
have shared storage.
• Decommission the research.contoso.com domain. All of the users and the Group
Policy objects (GPOs) in research.contoso.com will be migrated to contoso.com.
• Migrate the existing print queues to virtualized instances of Windows Server 2012.
• Migrate the file servers to new servers that run Windows Server 2012.
• Implement RADIUS authentication for VPN connections.
• Deploy Windows Server 2012 to all new servers.
Technical Requirements
The company identifies following technical requirements:
• All changes to Group Policies must be logged.
• Network Access Protection (NAP) policies must be managed centrally.
• Core networking services in each office must be redundant if a server
fails.
• The possibility of IP address conflicts during the DHCP migration must
be minimized.
• A central log of the IP address leases and the users associated to
those leases must be created.
• All of the client computers must be able to resolve internal names and
internet names.
• Administrators in the Paris office need to deploy a series of desktop
restrictions to the entire company by using Group Policy.
• The new sales.contoso.com domain will contain a web application that
will access data from a Microsoft SQL Server located in the contoso.com
domain. The web application must use integrated Windows authentication.
Users’ credentials must be passed from the web applications to the SQL
Server.
###EndCaseStudy###
After the planned upgrade to Windows Server 2012, you restore a user account from the
Active Directory Recycle Bin.
You need to replicate the restored user account as quickly as possible.
Which cmdlets should you run?
A.
Get-ADReplicationSite and Set-ADReplicationConnection
B.
Get-ADReplicationAttributeMetadata and Compare-Object
C.
Get-ADReplicationUpToDatenessVectorTable and Set-ADReplicationSite
D.
Get ADDomainController and Sync-ADObject
Explanation:
The Get-ADDomainController cmdlet gets the domain controllers specified by the
parameters.
You can get domain controllers by setting the Identity, Filter or Discover parameters.
The Identity parameter specifies the domain controller to get. You can identify a domain
controller by its GUID, IPV4Address, global IPV6Address, or DNS host name. You can also
identify a domain controller by the name of the server object that represents the domain
controller, the Distinguished Name (DN) of the NTDS settings object or the server object, the
GUID of the NTDS settings object or the server object under the configuration partition, or
the
DN of the computer object that represents the domain controller. You can also set the
Identity parameter to a domain controller object variable, such as
$<localDomainControllerObject>, or pass a domain controller object through the pipeline to
the Identity parameter.
To search for and retrieve more than one domain controller, use the Filter parameter. The
Filter parameter uses the PowerShell Expression Language to write query strings for Active
Directory.
PowerShell Expression Language syntax provides rich type conversion support for value
types received by the Filter parameter. For more information about the Filter parameter
syntax, see
about_ActiveDirectory_Filter. You cannot use an LDAP query string with this cmdlet.
To get a domain controller by using the discover mechanism of DCLocator, use the Discover
parameter. You can provide search criteria by setting parameters such as Service,
SiteName,
DomainName, NextClosestSite, AvoidSelf, and ForceDiscover.
http://technet.microsoft.com/en-us/library/hh852293.aspx
Detailed Description
The Sync-ADObject cmdlet replicates a single object between any two domain controllers
that have partitions in common. The two domain controllers do not need to be direct
replication partners. It can also be used to populate passwords in a read-only domain
controller (RODC) cache.
http://technet.microsoft.com/en-us/library/hh852296.aspx
