PrepAway - Latest Free Exam Questions & Answers

You need to ensure that you can create Runbook1, and then reference the runbook in Service Manager

Your company has a private cloud that is managed by using a System Center 2012 infrastructure.
A server named Server1 hosts the System Center 2012 Service Manager management server.
A server named Server2 hosts the System Center 2012 Orchestrator management server.
You plan to use a runbook named Runbook1 to update the status of Service Manager incidents.
You need to ensure that you can create Runbook1, and then reference the runbook in Service
Manager.
What should you do? (Each correct answer presents part of the solution.Choose all that apply.)

PrepAway - Latest Free Exam Questions & Answers

A.
From the Service Manager Console, add an incident event workflow.

B.
From the Service Manager Shell, run the Update-SCSMWorkflow cmdlet.

C.
From the Service Manager Console, create an Orchestrator connector.

D.
From the Orchestrator Deployment Manager, register the Integration Pack for System Center
Service Manager.

E.
From the Service Manager Console, update the Problem Status list.

F.
From the System Center 2012 Orchestrator Runbook designer, create a connection.

Explanation:
Just a draft:
Install the integration pack for SCSM on Orchstrator and configure the connection settings (SCSM
server name, User, Password) Create a new runbook
First activity -> “Monitor Object” of SCSM integration pack -> Incident Class -> On Update -> Filter
“Support Group” not equal “Tier 1”
Add 6 “Send Email” activities -> 6 different recipients -> add the text in each mail body Link all 6
“Send Email” activities with the first “Monitor Object” activity On each link delete the default rule
“On success” Add a new criteria -> Choose the “Support Group” from the data bus ->criteria of the
first link “Support Group” equals “Tier 2”
Do the same with the other Links and Support Groups.
Check in and start the runbook

http://social.technet.microsoft.com/Forums/en/administration/thread/ea41a3a4-0b40-47ee-9ecca2ecab8794bf


Leave a Reply