70-246 · Question #217
You have a system center 2012 R2 deployment. The relevant servers on the network are configured as shown in the following table. - Server1 has component system center 2012 R2 operations maanger…
The correct answer is C. Create an operations manager configuration item (CI) connector. After deploying the Operations Manager integration pack on the Orchestrator server, you must configure a connector to Operations Manager so that runbooks can communicate with it to monitor and remediate alerts.
Question
You have a system center 2012 R2 deployment. The relevant servers on the network are configured as shown in the following table.
- Server1 has component system center 2012 R2 operations maanger;
- Server2 has component system center 2012 R2 orchestrator;
- Server3 has component file server. Server3 is monitored by using
operations manager. You need to automate the remediation of the low disk space alerts generated by server3. You deploy the operations manager integration pack. What should you do next on server2?
Options
- AInstall an operations manager gateway server on server2
- BCreate an operations manager alert connector
- CCreate an operations manager configuration item (CI) connector
- DInstall the operations manager console on server2
How the community answered
(33 responses)- A12% (4)
- B24% (8)
- C58% (19)
- D6% (2)
Why each option
After deploying the Operations Manager integration pack on the Orchestrator server, you must configure a connector to Operations Manager so that runbooks can communicate with it to monitor and remediate alerts.
An Operations Manager gateway server enables monitoring of agents in untrusted domains or DMZ networks and plays no role in enabling runbook-based automation or remediation of alerts.
An Operations Manager alert connector is a Service Manager component used to forward OM alerts into the Service Manager incident queue, not a mechanism for enabling Orchestrator runbook automation on Server2.
Creating an Operations Manager connector on Server2 (Orchestrator) establishes the authenticated communication channel between the Orchestrator engine and the Operations Manager management group on Server1. This connector is required by the integration pack so that runbook activities can subscribe to, retrieve details from, and resolve Operations Manager alerts generated by Server3. Without this connector, no integration pack activities can interact with Operations Manager to automate disk space alert remediation.
Installing the Operations Manager console is a prerequisite that must be completed before deploying the integration pack - since the pack is already deployed, this step would already have been satisfied.
Concept tested: Orchestrator Operations Manager integration pack connector configuration
Source: https://learn.microsoft.com/en-us/system-center/orchestrator/orch-integration-packs
Topics
Community Discussion
No community discussion yet for this question.