###BeginCaseStudy###
Case Study: 6
Contoso Ltd Case C
Background
Overview
Contoso, Ltd., is a manufacturing company. The company has offices in Chicago and Seattle.
Each office contains two data centers. All of the data centers and sites for the company have
network connectivity to each other. The company uses a single Active Directory Domain
Services (AD DS) domain.
Contoso is growing rapidly and needs to expand its computer infrastructure.
Current Environment Chicago Office
The Chicago office contains a primary data center and a backup data center. A Hyper-V
cluster named Clusterl.contoso.com resides in the primary data center. The cluster has a
multiple network path configured. The cluster includes two unused SQL Server virtual
machines (VMs) named SQL-SERVER1 and SQL-SERVER2. The cluster also includes a
Hyper-V Host group named Chi-Primary.
Clusterl.contoso.com contains the following servers:
• CHI1-HVNODE1.contoso.com
• CHI1-HVNODE2.contoso.com
• CHI1-HVNODE3.contoso.com
• CHI1-HVNODE4.contoso.com
The backup data center for the Chicago office is located on a Hyper-V cluster named
Cluster2.contoso.com. The cluster has a single network path configured. The cluster includes
a Hyper-V Host group named Chi-Backup.
Cluster2.contoso.com contains the following servers:
• CHI2-HVNODEl.contoso.com
• CHI2-HVNODE2.contoso.com
• CHI2-HVNODE3.contoso.com
• CHI2-HVNODE4.contoso.com
In addition, the Chicago office contains two standalone Hyper-V servers named CHIHVSERVER1.contoso.com and CHI-HVSERVER2.contoso.com.
There are also four newly built servers:
• CHI-SERVERl.contoso.com
• CHI-SERVER2.contoso.com
• CHI-SERVER3.contoso.com
• CHI-SERVER4.contoso.com
All the servers in the Chicago office run Windows Server 2012. Any future servers that are
deployed in the Chicago office must also run Windows Server 2012.
All servers in the Chicaoo office use the subnet 10.20.xx.
Current Environment Seattle Office
The Seattle office contains a primary data center and a backup data center. The primary data
center is located on a Hyper-V cluster named Cluster3.contoso.com. The cluster has a
multiple network path configured. The cluster includes two unused SQL Server virtual
machines named SQL-SERVER3 and SQL-SERVERS The cluster includes a Hyper-V Host
group named Sea-Primary.
Cluster3.contoso.com contains the following servers:
• SEA3-HVNODEl.contoso.com
• SEA3-HVNODE2.contoso.com
• SEA3-HVNODE3.contoso.com
• SEA3-HVNODE4.contoso.com
The backup data center for the Seattle office is located on a Hyper-V cluster named
Cluster4.contoso.com. The cluster has a single network path configured. The cluster includes
a Hyper-V Host group named Sea-Backup.
Cluster4.contoso.com contains the following servers:
• SEA4-HVNODEl.contoso.com
• SEA4-HVNODE2.contoso.com
• SEA4-HVNODE3.contoso.com
• SEA4-HVNODE4.contoso.com
In addition, the Seattle office contains two standalone Hyper-V servers named SEAHVSERVERl.contoso.com and SEA-HVSERVER2.contoso.com.
There are also four newly built servers:
• SEA-SERVERl.contoso.com
• SEA-SERVER2.contoso.com
• SEA-SERVER3.contoso.com
• SEA-SERVER4.contoso.com
All servers in the Seattle office run Windows Server 2012 R2. Any future servers that are
deployed in the Seattle office must also run Windows Server 2012 R2.
All servers in the Seattle office use the subnet 10.10.x.x.
Business Requirements
Apps
Contoso plans to deploy new applications to make its departments more efficient.
App1
Contoso must create a new application named App1 for the human resources (HR)
department. The infrastructure for App1 must reside in a virtual environment and the data
files for App1 must reside on a single shared disk. In addition, the infrastructure for App1
must meet the following requirements:
• maximize data protection
• withstand the loss of a single guest virtual machine
• withstand the loss of a single physical server
To support App1, Contoso must deploy a new cluster named Applcluster.contoso.com. The
cluster has the following requirements:
• It must span multiple sites.
• It must support dynamic quorums.
• It must prevent failures caused by a 50% split.
App2
Contoso must create a new application named App2. To support App2, Contoso must deploy
a new SQL Server cluster. The cluster must not be part of the domain.
The server deployment team that will install the cluster has limited permissions. The server
deployment team does not have the ability to create objects in Active Directory.
Virtualization and Storage
New VMs
Any new VMs that are deployed to the Hyper-V cluster in Cluster3.contoso.com have the
following requirements:
• New SQL Server VMs must be deployed only to odd-numbered
servers in the cluster.
• All other new VM guests must be deployed to any available server in
the cluster.
New VDE
The company needs a highly available file share cluster for a new Virtual Desktop
Environment (VDE). It has the following requirements:
• The file share cluster must withstand the loss of a single server.
• The file share cluster must withstand the loss of a single network path.
• The file share cluster must use the least amount of disk space.
New virtualized SQL Server cluster
Contoso must create a new application for manufacturing. The company needs a new
virtualized SQL Server cluster named VM-SQLclusterl.contoso.com. It has the following
requirements:
• The cluster must use a shared virtual hard disk.
• The cluster must have two nodes named VM-SQLNODE1.contoso.com and VM-SQL-NODE2.contoso.com.
Highly available storage solution
The company is deploying new hardware that will replace the existing Hyper-V clusters. The
new file share cluster must have a highly available storage solution for a Hyper-V
environment. It has the following requirements:
• The new file share cluster must support guest VM clusters.
• The storage cannot reside on any of the physical Hyper-V hosts.
###EndCaseStudy###
HOTSPOT
You need to deploy the new SQL cluster for App2.
How should you complete the relevant Windows PowerShell command? To answer, select the
appropriate Windows PowerShell segment from each list in the answer area.
Answer: 
IMO
new-cluster cluster5.contoso.com -node SEA-SERVER1, SEA-SERVER2 -StaticAdress 10.10.1.100 -NoStorage -AdministrativeAccessPoint DNS
https://technet.microsoft.com/en-us/library/dn265970.aspx
•All servers must be running Windows Server 2012 R2.
I agree with Bartosz
@ bartosz – Exactly
Must be done on Seattle network to meet requirements of 2012R2 to Deploy an Active Directory-Detached Cluster
Why -NoStorage? I’m confused
I’ve been browsing on-line greater than three hours lately, but I by no means found any interesting article like yours. It is pretty worth sufficient for me. In my opinion, if all site owners and bloggers made good content material as you probably did, the net will likely be much more helpful than ever before.
http://www.bastcilkdoptb.com/
I partially agree with Bartosz.
Case:
“Contoso must create a new application named App2. To support App2, Contoso must deploy a new SQL Server cluster. The cluster must NOT be part of the domain.”
https://technet.microsoft.com/en-us/library/dn265970.aspx
“To deploy an Active Directory-detached cluster, use the New-Cluster cmdlet with the –AdministrativeAccessPoint parameter set to a value of Dns.”
“This deployment method still requires that the failover cluster nodes are JOINED to an Active Directory domain.”
In the case they say “The cluster must not be part of the domain.” so “-AdministrativeAccessPoint DNS” can’t be the answer.
-NoStorage = Causes the cluster creation to ignore shared storage. The cluster created at the end of the operation will not have shared storage. This can later be added using the “Get-ClusterAvailableDisk | Add-ClusterDisk” command.
-IgnoreNetwork = Specifies which networks to ignore during the operation. Networks with DHCP enabled are always included. Other networks need a static address to be specified using the -StaticAddress parameter or should be explicitly ignored with this -IgnoreNetwork parameter.
I think the right answer is:
new-cluster cluster5.contoso.com -node SEA-SERVER1, SEA-SERVER2 -StaticAdress 10.10.1.100 -IgonreNetwork 10.0.0.0/8 -AdministrativeAccessPoint none
I partially agree with Bartosz.
Case:
“Contoso must create a new application named App2. To support App2, Contoso must deploy a new SQL Server cluster. The cluster must NOT be part of the domain.”
https://technet.microsoft.com/en-us/library/dn265970.aspx
“To deploy an Active Directory-detached cluster, use the New-Cluster cmdlet with the –AdministrativeAccessPoint parameter set to a value of Dns.”
“This deployment method still requires that the failover cluster nodes are JOINED to an Active Directory domain.”
In the case they say “The cluster must not be part of the domain.” so “-AdministrativeAccessPoint DNS” can’t be the answer.
-NoStorage = Causes the cluster creation to ignore shared storage. The cluster created at the end of the operation will not have shared storage. This can later be added using the “Get-ClusterAvailableDisk | Add-ClusterDisk” command.
-IgnoreNetwork = Specifies which networks to ignore during the operation. Networks with DHCP enabled are always included. Other networks need a static address to be specified using the -StaticAddress parameter or should be explicitly ignored with this -IgnoreNetwork parameter.
I think the right answer is:
New-cluster Cluster5.contoso.com -node SEA-SERVER1, SEA-SERVER2 -StaticAddress 10.10.1.100 -IgnoreNetwork 10.0.0.0/8 -AdministrativeAccessPoint none
For more info about de New-Cluster cmdlet, see:
https://technet.microsoft.com/en-us/library/ee460973.aspx
FSM, please decide… You want to:
-IgnoreNetwork 10.0.0.0/8
or you want to pick a static address from the address space:
-StaticAddress 10.10.1.100
I am afraid, that both you can do not.
You conclusion about -AdministrativeAccessPoint is very correct. More we can read there: https://blogs.technet.microsoft.com/scottschnoll/2014/02/25/windows-server-2012-r2-and-database-availability-groups/ in section DAG Without a Cluster Administrative Access Point.
But in case of IPs, I think you are wrong. In my opinion the correct option must be then: -NoStorage
cluster team cannot create AD objects so DNS or AD is not an option. Only option is ‘None’
MI74 is correct.
Either we specify an IP address or we use the -IgnoreNetwork parameter.
see: https://technet.microsoft.com/en-us/library/hh847246.aspx
-StaticAddress
Specifies one or more static addresses to use when running the cmdlet. Networks with DHCP enabled are always included, but other networks need a static address to be specified using the StaticAddress parameter or should be explicitly ignored with this IgnoreNetwork parameter.
So I think it is:
New-Cluster Cluster5.contoso.com -Node SEA-SERVER1, SEA-SERVER2 -StaticAddress 10.10.1.100
The reason I think we need to give it an IP address is that its part of the requirements: “All servers in the Seattle office use the subnet 10.10.x.x.”