Export (0) Print
Expand All

Server Collocation in a Standard Edition Server Deployment

 

Topic Last Modified: 2011-09-28

This section describes the server roles, databases, and file shares that you can collocate in a Microsoft Lync Server 2010 Standard Edition server deployment.

Collocation of the following server roles on the same computer is supported:

  • Standard Edition server with A/V Conferencing service and Mediation service   The default configuration is collocated A/V Conferencing service and Mediation service. You can deploy Mediation service as a separate server or pool. You cannot deploy A/V Conferencing service as a separate server or pool.

  • Monitoring Server with Archiving Server   You can collocate either or both of these with the database server, as described later in this topic.

  • Standard Edition server with Monitoring Server and Archiving Server (for test purposes only)   You can collocate the Monitoring Server, Archiving Server, or both on the Standard Edition server in a test environment.

    importantImportant:
    Do not collocate these two server roles on a Standard Edition server in a production environment.

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

  • Director

  • Edge Server

  • Trusted Application Server

Collocating Microsoft Lync Server 2010, Group Chat with any server role is unsupported.

If you do not collocate either or both of the following server roles on the Front End Server, you must deploy each stand-alone server on a separate computer:

  • Stand-alone A/V Conferencing Server

  • Stand-alone Mediation Server

By default, the SQL Server Express back-end database is collocated on the Standard Edition server. You cannot move it to a separate computer. You cannot collocate other databases on the Standard Edition server.

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

  • Monitoring database

  • Archiving database

  • A back-end database for an Enterprise Edition Front End pool

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

  • Each SQL instance can contain only a single back-end database (for an Enterprise Edition Front End pool), single Monitoring database, or single Archiving database.

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

You can collocate a single Monitoring Server, a single Archiving Server, or both with the databases. You can also collocate a file share with the databases (as described later in this section).

You should not collocate the Group Chat database and compliance database (for Group Chat Server) with any database server or with Group Chat Server. These collocations are not supported.

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 a Front End pool, Archiving database, and Monitoring database

  • Monitoring Server

  • Archiving Server

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

You cannot collocate a reverse proxy server, which is not a Lync Server 2010 component but is required in your deployment if you want to support sharing of web content for federated users, with any Lync Server server role. You can, however, implement reverse proxy support for a Lync Server 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 Lync Server role.

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft