You are considering several MCU deployments in order to support scheduled and ad-hoc conferences.Which of the following deployment methods should you use?

A.
The MCU uses VCS as the call control device.

B.
The MCU registers to VCS but uses Conductor to manage conferences.

C.
The MCU registers to Conductor but uses VCS to manage conferences.

D.
The MCU is configured as a media resource in Unified CM.

Explanation:
You should use a deployment method in which the multipoint control unit (MCU) uses Cisco TelePresence
Video Communication Server (VCS) as the call control device. An MCU is used primarily to connect Session
Initiation Protocol (SIP) or H.323 single-screen endpoints into virtual meeting rooms. Optimally, all participants
in a conference will be connected to a single MCU. However, when there are not enough ports on an MCU for
all of the participants, the MCU can cascade to another MCU in order to handle the load. Cascading of MCUs
through VCS must be performed manually.
An MCU that is registered to VCS but uses Conductor to manage conferences can support rendezvous and
Multiway ad hoc conferences but not scheduled conferences; the MCU does not register with Conductor. Cisco
TelePresence Conductor manages conference functions for TelePresence Servers that operate in remotely
managed mode. A Conductor or Conductor cluster supports a maximum of 30 MCUs. Unlike VCS, Conductor
is able to dynamically cascade MCUs. With dynamic cascading, MCUs are added as they are needed.
An MCU that is configured as a media resource in Cisco Unified Communications Manager (CM) can support
ad hoc conferences but not scheduled conferences. Like Conductor, Unified CM supports rendezvous and
Multiway ad hoc conferences. However, cascading, Transport Layer Security (TLS), and Binary Floor Control
Protocol (BFCP) are not supported.

Cisco: Cisco TelePresence MCU 45X0, 53X0 and MCU MSE 8510, Cisco TelePresence Deployment Guide:
Which deployment? (PDF)