Your company has a datacenter in Los Angeles.
The datacenter contains a private cloud that is managed by using a System Center 2012
infrastructure.
A server named VMM1 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 Book1 to update the status of Service Manager incidents.
You need to ensure that you can create Book1, and then reference the runbook in Service Manager.
What should you do? (Each correct answer presents part of the solution. Choose all that apply.)

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

B.
From the Service Manager Shell, run the Set-SCDWJobSchedulecmdlet.

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

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

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

F.
From the Service Manager Shell, run the Enable-SCDWJobSchedulecmdlet.

Explanation:
Install the integration pack for SCSM on Orchestrator 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
To create an Orchestrator connector
In the Service Manager console, click Administration.
In the Administration pane, expand Administration, and then click Connectors.
In the Tasks pane, under Connectors, click Create Connector, and then click Orchestrator connector.
Perform these steps to complete the Orchestrator Connector Wizard:
On the Before You Begin page, click Next.
On the General page, in the Name box, type a name for the new connector. Make sure that Enable
this connector is selected, and then click Next.
On the Connection page, in the Server Information area, type the URL of the Orchestrator Web
service, depending on which version of Orchestrator you are using:
For Orchestrator Beta, type the URL of the Orchestrator Web service in the form of
http://<computer>:<port>/
Orchestrator.svc, where <computer> is the name of the computer hosting the web service and
<port> is the
port number where the web service is installed. (The default port number is 81.)
For Orchestrator RC, type the URL of the Orchestrator Web service in the form of
http://<computer>:<port>/
Orchestrator2012/Orchestrator.svc, where <computer> is the name of the computer hosting the
web service and <port> is the port number where the web service is installed. (The default port
number is 81.)
On the Connection page, in the Credentials area, either select an existing account or click New, and
then do the following:
In the Run As Account dialog box, in the Display name box, type a name for the Run As account. In
the Account list, select Windows Account. Enter the credentials for an account that has rights to
connect Orchestrator, and then click OK. On the Connection page, click Test Connection.
Note
Special characters (such as the ampersand [&]) in the User Name box are not supported.
In the Test Connection dialog box, make sure that the message “The connection to the server was
successful” appears, and then click OK. On the Connection page, click Next.
On the Folder page, select a folder, and then click Next.
On the Web Console URL page, type the URL for the Orchestrator web console in the form of
http://<computer>:port (the default port number is 82), and then click Next.
On the Summary page, make sure that the settings are correct, and then click Create.
On the Completion page, make sure that you receive the message “Orchestrator connector
successfully created,” and then click Close.
To validate the creation of an Orchestrator connector
In the Connectors pane, locate the Orchestrator connector that you created.
Review the Status column for a status of Finished Success.
Note
Allow sufficient time for the import process to finish if you are importing a large number of
runbooks.
In the Service Manager console, click Library.
In the Library pane, expand Library, and then click Runbooks.
Review the Runbooks pane, and note that your runbooks have been imported.

http://technet.microsoft.com/en-us/library/hh519779.aspx
The Integration Pack for System Center Service Manager is an add-in for Opalis Integration Server 6.3
that enables you to use System Center Service Manager to coordinate and use operational data in an
existing IT environment comprised of service desk systems, configuration management systems,,
and event monitoring systems,, including specifically BMC Remedy IT Service Management Suite,
BMC Atrium, and HP Service Manager 7 and HP Service Center 6.2.
With this integration pack, you can also create workflows that interact with and transfer information
to the integration packs for System Center Operations Manager, System Center Data Protection
Manager, System Center Configuration Manager, and System Center Virtual Machine Manager.
Opalis, a Microsoft Subsidiary, is committed to helping you protect your privacy, while delivering
software that brings you the performance, power, and convenience you want. For more information,
seetheOpalis 6.3
Privacy Statement (http://go.microsoft.com/fwlink/?LinkID=202690).
http://technet.microsoft.com/en-us/library/gg464964.aspx