Topic Last Modified: 2012-09-30

As with deployment of your other Lync Server 2013 components, deployment of web 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 in a Front End pool and Standard Edition servers. It has no additional hardware or software requirements beyond what is required to install those servers.

Note:
Lync Server 2013 uses Office Web Apps and the Office Web Apps Server to handle sharing and rendering of PowerPoint presentations. For information about installing and configuring the Office Web Apps Server, see Configuring Integration with Office Web Apps Server and Lync Server 2013.

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.

Lync Server 2013 now includes the MaxUploadFileSizeMb setting, which limits the size of files that can be uploaded during a meeting. The default value for this setting is 500 MB. You can adjust MaxUploadFileSizeMb using the Set-CsConferencingConfiguration cmdlet.

MaxUploadFileSizeMb does not limit the file upload setting for Lync Web App. The file size upload limit for Lync Web App is set to approximately 30MB and is controlled by the IIS web.config file: /DataCollabWeb/Int[Ext]/Handler/web.config. To configure the file size upload limit for Lync Web App, update maxRequestLength and maxAllowedContentLength in the web.config file as shown below.

Copy Code 
<system.web>
	<!-- 
		Since this handler is used to upload files to DMCU the request size (in kilobytes) 
		has to fit max allowed file size uploaded by LWA client.
		The timeout has to reflect the min client bandwidth. Timeout of 600 secs 
		and 512 Kbits of *client* bandwidth would result into aproximately 30 Mbytes 
		for LWA upload size limit.
	-->
	<httpRuntime maxRequestLength="500000" executionTimeout="600" />



				<security>
				<requestFiltering>
						 <requestLimits maxAllowedContentLength="524288000" />
				</requestFiltering>
				</security>

You must update the web.config file for each Front End Server.