Topic Last Modified: 2012-09-30
As with deployment of your other Lync Server 2013 components, deployment of A/V conferencing requires that you use Topology Builder to create and publish a topology that incorporates conferencing.
Deployment Sequence
You can deploy conferencing at the same time that you deploy your initial topology or after you have deployed at least one Front End pool or Standard Edition server.
Conferencing Deployment Process
The following table provides an overview of the steps required to deploy conferencing into an existing topology.
Phase | Steps | Roles and group memberships | Documentation | ||
---|---|---|---|---|---|
Install prerequisite hardware and software |
Conferencing runs on Front End Servers of a Front End pool and Standard Edition servers. It has no additional hardware or software requirements beyond what is required to install those servers.
|
Domain user who is a member of the local Administrators group |
Supported hardware in the Supportability documentation Server software and infrastructure support in the Supportability documentation Determining your system requirements in the Planning documentation. Technical Requirements for Archiving in the Planning documentation. |
||
Create the appropriate internal topology to support conferencing |
Run Topology Builder to add conferencing to the topology, and then publish the topology. |
To define a topology, an account that is a member of the local Users group To publish the topology, an account that is a member of the Domain Admins group and RTCUniversalServerAdmins group, and that has full control permissions (read/write/modify) on the file share to be used for the Lync Server 2013 file store (so that Topology Builder can configure the required DACLs) |
Define and Configure a Topology in Topology Builder in the Deployment documentation. |
||
Configure conferencing policies and support |
Use the Lync Server 2013 Control Panel or Lync Server Management Shell to configure conferencing settings. |
RTCUniversalServerAdmins group (Windows PowerShell only) or assign users to the [] or CSAdministrator role |
Conferencing Policies in the Operations documentation. |