###BeginCaseStudy###
Case Study: 5
Contoso Ltd
Overview
Contoso, Ltd. is a manufacturing company that has 3,000 users.
Contoso has a data center in Toronto and 20 offices across Canada. The offices connect to
each other by using a WAN link. Each office connects directly to the Internet.
Existing Environment
Active Directory Environment
The network contains an Active Directory forest named contoso.com. The forest contains a
single domain. All domain controllers run Windows Server 2012. All servers run Windows
Server 2008 R2.
Each office contains three domain controllers. Each office is configured as an Active
Directory site.
System Center 2012 Infrastructure

Contoso has a System Center 2012 infrastructure that contains 11 servers. The servers are
configured as shown in the following table.

Contoso has a private cloud named Cloud1. Cloud1 is managed by using VMM. The
following applications run in Cloud 1:
• Microsoft Exchange Server 2010
• Microsoft SharePoint Server 2010
• A custom manufacturing application named App1
The Hyper-V hosts are managed by using VMM. TOR-H01 and TOR-H02 are nodes in a
failover cluster.
The switches that are part of the network fabric are from various manufacturers and are
managed by using SNMPv3.
App1
An application named App1 is deployed from a VMM service template that consists of one
front-end web server and one back-end database server. App1 processes credit card
information.
The instance of App1 running in the data center uses two virtual machines named VM1 and
VM2. TOR-H01 hosts VM1 and VM2.
App1 is managed by using a custom management pack named MP1. The management pack
used to monitor App1 contains a distributed application diagram named App1DAD.
The service level agreement (SLA) for App1 states that App1 must be available 99 percent of
the time.
Problem Statements
Contoso identifies the following issues:
• Currently, all Operations Manager alerts are sent by email only. Database
administrators require alerts to be sent by text message. The cell phone

numbers of the database administrators are already configured in Operations
Manager.
• Administrators report that the processor performance counters for the Hyper-V
hosts display values that are lower than the actual load on the hosts.
Requirements
Business Goals
Contoso wants to minimize hardware and software costs, whenever possible.
Planned Changes
Contoso plans to add a new web server to the App1 service template. Traffic to the new web
server will be load balanced with the existing web server by using a hardware load balancer.
Technical Requirements
Contoso identifies the following technical requirements for the planned deployment:
• Automatically apply software updates issued by Microsoft to all of the HyperV hosts.
• Automatically assign incidents to administrators when a Configuration
Manager service fails.
• Ensure that the Exchange Server administrators can request that new virtual
machines be added to the Exchange Server organization by using Internet
Explorer.
• Monitor the uptime of all the Hyper-V hosts and all the virtual machines by
using Operations Manager and VMM. Performance and Resource
Optimization (PRO)-enabled management packs will be used.
• Ensure that users have a self-service portal that provides them with the ability
to back up individual virtual machines. Users must receive an email message
confirming that the backup is complete.
• Ensure that database administrators are alerted by a text message when an
error occurs on a server that they manage. The text messages should be
delivered regardless of the current network conditions.
• Network administrators report that they currently use different tools to monitor
the port status on the switches. The network administrators want to manage all
of the switches by using Operations Manager.
App1 Requirements
Contoso identifies the following requirements for App1:
• Create an object in the App1 management pack to track the SLA.
• Ensure that multiple monitoring thresholds can be used for different instances
of App1.
• Ensure that App1 complies with the Payment Card Industry Data Security
Standard (PCI DSS).

###EndCaseStudy###

DRAG DROP
You are evaluating the deployment of System Center 2012 Service Manager and System Center 2012
Orchestrator.
You need to recommend a solution to meet the technical requirement for backups.
In which order should you perform the actions? (To answer, move all of the actions from the list of
actions to the answer area and arrange them in the correct order.)

Answer: See the explanation

Explanation:
Box 1:

Box 2: Create and synchronize an Orchestrator connector in Service Manager.
Box 3: Create a runbook in Orchestrator
Box 4: From Service Manager, create a service template that contains an automation activity.
Box 5: Create a request offering and a service offering in Service Manager

Note:
* (box 1) Step 1: Plan your deployment.
Plan Your Orchestrator Deployment
Step 2: Review the system prerequisites.
Step 3: Install Orchestrator.
Step 4: Perform post-installation tasks.
Includes:
Install an Integration Pack
* Activities that make up a service request can be mapped to runbook activities, which in turn are
mapped to an Orchestrator runbook. For example, the parameters that are necessary for a custom
start activity to invoke a runbook in Orchestrator, such as a computer name, can go into as Service
Manager as objects. You start this process by importing runbook objects into the Service Manager
database using an Orchestrator connector (box 2).

* You can implement a new request offering using an Orchestrator runbook to automate it. Then,
you can go to the Runbooks view in the Library workspace, select a runbook, and create a runbook
automation activity template (box 3). You can go to the templates view and verify that the template
is created. You can then add the Orchestrator activity template to a service request template (box 4)
and create the request offering (box 5).
How to Create a Runbook Automation Activity Template