In Lync Server 2013, A/V Conferencing service, Mediation service, Monitoring, and Archiving are collocated on the Front End Server, but additional configuration is required to enable them. If you do not want to collocate the Mediation Server with the Front End Server, you can deploy it as a stand-alone Mediation Server on a separate computer.

You can collocate a trusted application server with the Front End Server.

The following server roles must each be deployed on a separate computer:

• Director

• Edge Server

• Mediation Server (if not collocated with the Front End Server)

• Office Web Apps Server

You cannot collocate Persistent Chat server role with the Front End Server.

You can collocate each of the following databases on the same database server:

• Back-end database

• Monitoring database

• Archiving database

• Persistent Chat database

• Persistent Chat compliance database

You can collocate any or any or all of these databases in a single instance of SQL Server or use a separate instance of SQL Server for each, with the following limitations:

• Each instance of SQL Server can contain only a single back-end database, a single Monitoring database, a single Archiving database, a single Persistent Chat database, and a single Persistent Chat compliance database.

• The database server cannot support more than one Front End pool, one Archiving deployment, and one Monitoring deployment, but it can support one of each, regardless of whether the databases use the same instance of SQL Server or separate instances of SQL Server.

You can collocate a file share with the databases, as described later in this section.

Note:
In Lync Server 2013, you have the option of integrating Archiving storage with Exchange 2013 storage for some or all users in your deployment. You cannot deploy any servers running Lync Server or components on the same servers as the Exchange storage.

Important:

Although collocation of databases is supported, the size of the databases can grow quickly. For example, when you consider collocating the Archiving database with other databases, be aware that if you are archiving the messages of more than a few users, the disk space needed by the Archiving database can grow very large. For this reason, we do not recommend collocating multiple databases, especially the Archiving database, the Persistent Chat database, or the Persistent Chat compliance database with the back-end database.

The file share can be a separate server or can be collocated on the same server as any or all of the following:

• Database server, including the Back End Server of an Enterprise Edition Front End pool

• Archiving database

• Monitoring database

• Persistent Chat database

• Persistent Chat compliance database

A single file share can be used for multiple Front End pools, Standard Edition servers (all in the same site).

Note:
In Lync Server 2013, Monitoring and Archiving use the Lync Server file share as the Front End Server.

You cannot collocate a reverse proxy server, which is not a Lync Server 2013 component, but is required in your deployment if you want to support sharing of web content for federated users with any Lync Server 2013 server role. You can, however, implement reverse proxy support for a Lync Server 2013 deployment by configuring the support on an existing reverse proxy server in your organization that is used for other applications.

You cannot collocate any Exchange Unified Messaging (UM) component or SharePoint component with any SharePoint Server role.