###BeginCaseStudy###
Case Study: 6
Proseware, Inc
Overview
Proseware, Inc. is a mechanical equipment manufacturer.
Proseware has a research department and a manufacturing department.
Existing Environment
Network Infrastructure
The network contains a single Active Directory domain named proseware.com. The domain
contains 100 Hyper-V hosts that run Windows Server 2008 R2 Service Pack 1 (SP1). The
Hyper-V hosts host 400 virtual machines.
Sixty of the virtual machines have Microsoft SQL Server 2008 R2 deployed. Both the
research department and the manufacturing department use the SQL Server virtual machines.
The infrastructure contains two private clouds. One private cloud contains all of the resources
used by the research department. The other private cloud contains all of the resources used by
the manufacturing department.
The following System Center 2012 components are installed on the network:
• Orchestrator
• Service Manager
• Operations Manager
• Configuration Manager
• Data Protection Manager (DPM)
• Virtual Machine Manager (VMM)
All servers are backed up by using DPM. The system state of the servers is not backed up.
Configuration Manager only manages client computers.
Application Infrastructure
Proseware uses a third-party help desk application to manage user incidents.
The manufacturing department uses a Microsoft .NET application named App1 that is critical
for business operations.
The research department uses a Microsoft Server Application Virtualization (Server App-V)
virtual application package named App2.
Problem Statements
Proseware identifies the following issues:
• Administrators are NOT notified when a service on any server fails.
• A virtual machine named VM2 has a service that stops and restarts often.
• When an alert is generated in Operations Manager, a help desk user has to
generate a ticket manually from the help desk application.
• A Hyper-V host named Server1 contains a virtual machine named VM1 that is
assigned a high amount of memory. Users who connect to VM1 report that it
takes a long time to access the resources on VM1. You suspect that the
memory assigned to VM1 spans more than one NUMA node.
Requirements
Planned Changes
Proseware plans to implement the following changes:
• Replace the help desk application with a new, centralized incident
management solution.
• Provide the users in the research department with an automated solution to
provision virtual machines. The users will manage their respective virtual
machine by using a self-service portal.
Technical Requirements
Proseware has identified the following technical requirements for the private cloud
infrastructure:
• The number of required virtual machine templates must be minimized.
• A centralized automated task must restart failed services on the virtual
machines.
• Administrators must be notified by an SMS message when an alert on a
manufacturing server is generated.
• Servers that are out of compliance with the Payment Card Industry Data
Security Standard (PCI DSS) must be identified.
• Administrators must be able to perform a bare metal recovery of the Hyper-V
hosts and the virtual machines by using DPM.
• In a single operation, administrators must be able to perform a rollback of the
updates applied to the servers that host App2.
• Windows Server and SQL Server configurations that do NOT adhere to
Microsoft best practices and are misconfigured must be identified.
• All virtual machines created by self-service users must use Dynamic Memory.
Administrators must be able to create virtual machines that do NOT use
Dynamic Memory.
• Administrators must be notified when an alert on a server in the research
department is generated. Between 09:00 and 17:00, the administrators must be
notified by email. After 17:00, the administrators must be notified by an SMS
message.
Monitoring Requirements
App1 must be monitored to retrieve the following information:
• The amount of time it takes to respond to user queries
• The amount of time it takes to load a webpage
• Debugging information
If App2 fails to mount on a server, an administrator must receive an alert.
###EndCaseStudy###
You need to recommend an automated solution to resolve the ticket generation issue.
What should you include in the recommendation?
A.
From Operations Manager, create diagnostic tasks. From Orchestrator, create runbooks that
forward alerts to the help desk application.
B.
From Service Manager, create a connector. From Operations Manager, configure the connector.
C.
From Service Manager, create a connector. From Orchestrator, configure connectors.
D.
From Operations Manager, create diagnostic tasks. From Orchestrator, configure connectors.
Explanation:
http://technet.microsoft.com/en-us/library/cc181012.aspx
The relevant problem statement is “- When an alert is generated in Operations Manager, a help desk
user has to generate a ticket manually from the help desk application.”
Creating a connector from SCOM to SCSM means Incidents may be automatically generated from
SCOM alerts.Another useful link for the answer
http://valentincristea.com/2013/11/28/automating-incident-problem-management-part-iiconfiguring-thescomscsm-connector/