Topic Last Modified: 2010-07-14
Communications Server 2010 also includes some other changes to supported topologies regarding existing server roles, as follows:
- A richer set of supported virtualization scenarios for
Microsoft Communications Server 2010 server roles is supported.
- In Communications Server 2010, the Director is a true, unique
server role. If you deploy a server as a Director, you cannot home
users on it. Its purpose as a next-hop server for connection
requests and for the Edge Server will be preserved. (In past
versions of Communications Server, you could configure a Front End
Server as a Director, but internally it was deployed as a Front End
Server and required you to take additional configuration steps to
preserve its Director role.)
Additionally, the Director does not require a separate Back-End database running the Microsoft SQL Server database software; instead it uses a local version of SQL Server Express Edition, which is installed automatically when you deploy a Director.
A Communications Server 2010 server running as a Director is not designated as either a Standard Edition Server or Enterprise Edition server; it does not require any type of Microsoft Communications Server 2010 license.
- Mediation Server can be collocated with the Front End Server
role. This collocation is the recommended topology, unless you are
using SIP trunking or Direct SIP.
- Archiving Server and Monitoring Server can be collocated with
the Front End Server in smaller deployments.