You define and configure your topology by using Topology Builder. Topology Builder does not require you to be a member of the local Administrators group or a privileged domain group (such as Domain Admins). You can define your topology as a standard user. When you start Topology Builder on first use and subsequent edit sessions, you are prompted for the location where you want Topology Builder to load the current configuration document. The choices are the following:
Download topology from existing deployment Open topology from a local file
New topology
If you have already defined a topology and have established the Central Management store, you should choose to download a topology from an existing deployment. Topology Builder will read the database and retrieve the current definition. If you have an existing Central Management store, you should always choose this option.
If you have not established a Central Management store and want to edit a previously saved configuration, you should choose to open the topology from a local file. The file that you will open would be the configuration file that was saved in a previous session. You can use this option to edit the previously saved topology.
Warning:
If you already have a published topology, you should not load a local configuration file. You should choose to download the topology from an existing deployment.
Choose to create a new topology, if you want to create a new Topology Builder configuration. A previously saved design is not overwritten unless you choose to save it as the same file that you created in an earlier design session.
In each of these options, you will be prompted for a location to store the Topology Builder configuration file. The location for the file could be a local location, a shared location on an established file share, or removable media.
In This Section
Define and Configure a Topology in Topology Builder
Define and Configure a Front End Pool Define a New A/V Conferencing Server Edit or Configure Simple URLs
Define and Configure a Topology in Topology Builder
Running Topology Builder to define a new topology or to modify an existing topology does not require membership in a local administrator or privileged domain group. Topology Builder guides you through the steps necessary to define your topology for an Enterprise Edition Front End pool or a Standard Edition Front End Server, based on your configuration requirements. You must use Topology Builder to complete and publish the topology before you can install Microsoft Lync Server 2010 on servers. The following procedure includes the steps required to define a new topology.
To define a topology
1. Start Topology Builder: Click Start, click All Programs, click Microsoft Lync Server 2010, and then click Lync Server Topology Builder.
2. In Topology Builder, select New Topology. You are prompted for a location and file name for saving the topology. Give the topology file a meaningful name and accept the default extension of .tbxml. Click OK.
3. Navigate to the location where you want to save the new topology XML file, enter a name for the file, and then click Save.
4. On the Define the primary domain page, enter the name of the primary SIP domain for your organization, and then click Next.
5. On the Specify additional supported domains page, enter the names of additional domains, if any, and then click Next.
6. On the Define the first site page, enter a name and a description for the first site, and then click Next.
7. On the Specify site details page, enter the location information for the site, and then click Next.
8. On the New topology was successfully defined page, ensure the Open the New Front End Wizard when this wizard closes check box is selected, and then click Finish. After you’ve defined and saved the topology, use the New Front End Wizard to define a Front End pool or Standard Edition server for your site. For details, see Define and Configure a Front End Pool for Enterprise Edition, or see Define and Configure a Standard Edition Server for a Standard Edition server.
Define and Configure a Standard Edition Server
After you have defined your topology, use the following procedure to define a Standard Edition server for your site. For details about defining the topology, see Define and Configure a Topology in Topology Builder.
To define a Standard Edition server
1. In the Define New Front End Pool Wizard, on the Define the New Front End pool page, click Next.
2. On the Define the Front End pool FQDN page, enter a fully qualified domain name (FQDN) for the Standard Edition server you are creating, select Standard Edition Server, and then click Next.
3.
On the Select features page, select the check boxes for the features that you want on this Front End pool. For example, if you are deploying only instant messaging (IM) and presence features, you would select the Conferencing check box to allow multiparty IM, but would not select Dial-in (PSTN) conferencing, Enterprise Voice, or Call Admission Control, because they represent voice, video, and collaborative conferencing features. Conferencing – This selection enables a rich set of features including:
Instant messaging (IM) with more than two parties in an IM session
Conferencing, which includes document collaboration, application sharing, and desktop sharing
A/V conferencing, which enables users to have real-time audio/video (A/V)
conferences without the need for external services such as the Live Meeting service or a third-party audio bridge
Dial-in (PSTN) conferencing - Allows users to join the audio portion of a Lync Server 2010 conference by using a public switched telephone network (PSTN) phone without requiring an audio conferencing provider.
Enterprise Voice - Enterprise Voice is the voice over IP (VoIP) solution in Lync Server 2010 that allows users to make and receive phone calls. You would deploy this feature if you plan to use Lync Server 2010 for voice calls, voice mail, and other functions that use a hardware device or a software client.
Call admission control (CAC) – CAC determines, based on available network bandwidth, whether to allow real-time communications sessions such as voice or video calls to be established. If you have deployed only IM and presence, CAC is not needed because neither of these two features uses CAC.
Note:
Call admission control is recommended for your Front End Server in your Standard Edition deployment if you are deploying voice features or A/V conferencing.
The following table shows the available features (top) and the functions offered to users (left). The selections in the table are what you should select to enable those features for your organization.
Conferencing Dial-In Conferencing
Enterprise Voice Call Admission Control Instant messaging and presence X Conferencing X X A/V conferencing X X X
4. On the Select collocated server roles page, the Collocate Mediation Server check box is selected by default. Clear the Mediation server check box if you intend to deploy a stand-alone Mediation Server.
Warning:
The Collocate A/V Conferencing service option will be selected and will be unavailable for editing if you chose Conferencing on the Select features page in step 3 for a Standard Edition server. A Standard Edition server cannot be associated with a stand-alone A/V Conferencing Server and the A/V Conferencing service will be installed on the Standard Edition server if conferencing was selected on the Select features page.
We recommend that you collocate the Mediation Server role on the Standard Edition Front End Server if possible.For details about support for collocated or stand-alone Mediation Servers, see Components and Topologies for Mediation Server in the Planning documentation.
5. The Associate server roles with this Front End pool option allows you to define and associate server roles with the Front End Server. The three roles that are available are: Enable Archiving — defines and associates the Archiving Server that collects and stores messages incoming and outgoing from the organization. For example, you must monitor communications for regulatory compliance or quality assurance.
Enable Monitoring — defines and associates the Monitoring Server that collects information in the form of call detail records (CDRs) and call error records (CERs). In addition, the Monitoring Server collects data on the quality of network media for Enterprise Voice and A/V conferencing.
Enable a Front End pool — defines and associates a single Edge Server or a pool of Edge Servers. An Edge Server facilitates communication and collaboration between users inside the organization and people outside the organization, including federated users. There are two possible scenarios that you can use to deploy and associate the server roles:
For scenario one, you are defining a new topology for a new installation. You can approach the installation in one of two ways:
Leave all check boxes clear and proceed with defining the topology. After you have published, configured, and tested the Standard Edition Front End Server, you can run Topology Builder again to add the role servers to the topology. This strategy will allow you to test the Standard Edition server without additional complications from additional roles. After you have completed your initial testing, you can run Topology Builder again to select the roles you need to deploy.
Select roles that you need to install, and set up the hardware to accommodate the selected roles.
For scenario two, you have an existing deployment and your infrastructure is ready for new roles or you need to associate existing roles with a new Front End Server:
In this case, you will select the roles that you intend to deploy or associate with the new Front End Server. In either case, you will proceed with the definition of the roles, set up any needed hardware, and proceed with the installation.
6. On the Define the SQL store page, all options for Standard Edition are pre-populated for you. There are no selections or changes that can be made. Click Next to continue.
7. On the Define the file share page, do one of the following:
To use a file share that has already been defined in your topology, select Use a previously defined file share.
To define a new file share, select Define a new file share, in the File Server FQDN box, enter the FQDN for the existing file server where the file share is to reside, and then enter a name for the file share in the File Share box.
Important:
The file share for Lync Server 2010, Standard Edition can be located on the Front End Server. This might not be an optimal location for your organization’s
requirements, and a file server might be a better choice. You can define the file share without the file share having been created. You will need to create the file
8. On the Specify the Web Services URL page, the internal base URL is unavailable because overriding the internal base URL is not necessary for a Standard Edition server, but is for a load-balanced Front End pool.
Enter the external base URL in External Base URL. You would specify the external base URL to differentiate it from your internal domain naming. For example, your internal domain is contoso.net, but your external domain name is contoso.com. You would define the URL using the contoso.com domain name. This is also important in the case of a reverse proxy. The external base URL domain name would be the same as the domain name of the reverse proxy. Instant messaging and presence does require HTTP access to the Front End pool.
Note:
The base URL is the Web Services identity for the URL, minus the https://. For example, if the full URL for the Web Services of the server is
9. On the Specify PSTN gateways page, if the Collocate Mediation Server option on the Select collocated server roles page is selected, define your planned PSTN gateways, and then click Finish.
Important:
PSTN gateways need to be configured for the collocated Mediation Server. You can configure these later, but full functionality will be limited until the PSTN gateways are defined and configured. If you did not select Collocate Mediation Server in step 4, you will not be presented with the page to specify PSTN gateways.
10. To define a new PSTN gateway, click New next to The following gateways are associated with this mediation server.
11. In the Gateway FQDN or IP Address, type the FQDN or the IP address of the new gateway.
12. Confirm or modify the Listening port for IP/PSTN Gateway setting. The default is Port 5067.
13. For SIP Transport Protocol, select TCP or TLS, based on what your infrastructure and PSTN gateway requirements are.
Note:
Not all PSTN gateways support Transport Layer Security (TLS). Check your gateway’s documentation or contact the vendor to confirm what is supported. Transmission Control Protocol (TCP) is available, but TLS is the default setting, and is recommended for its ability to encrypt the traffic from gateway to Mediation Server.
14. Click OK. The PSTN gateway is now listed as associated with the Mediation Server. 15. Follow the previous steps (beginning with step 10), to define additional new PSTN
gateways.
16. If you have previously defined PSTN gateways, they will be listed in The following gateways are not associated with any Mediation Server box. Click Add to associate them with this Mediation Server.
Note:
You can associate more than one PSTN gateway with a Mediation Server. However, you can associate any given PSTN gateway with only one Mediation Server.
17. Click Next. If you defined other role servers on the Associate server roles with this Front End pool page, separate role configuration wizard pages will open to allow you to
Deploying Archiving Deploying Monitoring Deploying Edge Servers
18. If you did not select additional server roles to configure and deploy, or when you have finished the configuration of the additional role servers, click Finish.
Edit or Configure Simple URLs
This procedure does not require membership in a local administrator or privileged domain group. You should log on to a computer as a standard user.
Microsoft Lync Server 2010 uses simple URLs to direct internal and external calls to services on the Front End Server or on the Director, if one has been deployed. The three simple URLs that can be created are:
Meet – Connects users to the conferencing services
Dialin – Provides access for users to use dial-in conferencing
Admin – Optional URL that connects a user, typically an administrator for the Lync Server 2010 system, to Microsoft Lync Server 2010 Control Panel.
There are options to the format that you can define simple URLs. For details about these
options, see DNS Requirements for Simple URLs in the Planning documentation. A brief summary of the three simple URL formats discussed are shown for reference here:
Simple URL Examples
Meet https://meet.contoso.com Meet https://lync.contoso.com/Meet Meet https://lync.contoso.com/contosoSIPdomain/Meet Dial-in https://dialin.contoso.com Dial-in https://lync.contoso.com/Dialin Dial-in https://lync.contoso.com/contosoSIPdomain/Dialin Admin https://admin
Simple URL Examples
Admin https://admin.contoso.com
Admin https://lync.contoso.com/Admin
Admin https://lync.contoso.com/contosoSIPdomain/Admin
By default, simple URLs will be configured in the form of (for example, the dial-in simple URL): https://dialin.<SIP Domain>
Warning:
Simple URLs can contain only English alphanumeric characters (including A–Z, a–z, 0–9, and hyphens (-)). Do not use Unicode characters or underscores. Nonstandard
characters in an FQDN are often not supported by external DNS and public certification authorities (CAs).
To configure simple URLs
1. In Topology Builder, right-click the Lync Server 2010 node, and then click Edit Properties.
2. In the Simple URLs pane, select either Phone access URLs: (Dial-in) or Meeting URLs: (Meet) to edit. And then click Edit URL.
3. Update the URL to the value you want, and then click OK to save the edited URL. The example shown here has modified the Dial-in URL to https://pool01.contoso.net/dialin.
4. Edit the Meet URL by using the same steps, if necessary.
To define the optional Admin simple URL
1. In Topology Builder, right-click the Lync Server 2010 node, and then click Edit Properties.
2. In the Administrative access URL box, enter the simple URL you want for administrative access to Lync Server 2010 Control Panel, and then click OK.
Tip:
We recommend using the simplest possible URL for the Admin URL. The simplest option is https://admin.
Important:
If you change a simple URL after initial deployment, you must be aware of what changes impact your Domain Name System (DNS) records and certificates for simple URLs. If the change impacts the base of a simple URL, then you must change the DNS records and certificates as well. For example, changing from https://lync.contoso.com/Meet to https://meet.contoso.com changes the base URL from lync.contoso.com to meet.contoso.com, so you would need to change the DNS records and certificates to refer to meet.contoso.com. If you changed the simple URL from https://lync.contoso.com/Meet to
https://lync.contoso.com/Meetings, the base URL of lync.contoso.com stays the same, so no DNS or certificate changes are needed. Whenever you change a simple URL name, however, you must run the Enable-CsComputer on each Director and Front End Server to register the change.
Edit Federation Route Settings
To set a site federation route assignment, you must first have federation enabled on the Edge Server or Edge Server pool. If federation is not enabled on the Edge Server or pool, the federation route assignment settings for the site will not be available for modification.
If the federation setting at the Edge Server or pool has been configured, you select Enable at the site level. You then select an Edge or a Director from the drop-down to set as the federation route. To do this, do the following:
1. Select the site to change. 2. Right-click the site name. 3. Click Edit Properties.
4. Select Enable for the federation route.
5. Select the the Edge Server or Edge Server pools in the drop down. Important
This global setting will affect all sites. Be sure that the setting that you are configuring at this site is appropriate for all sites. Note that a local definition for the federation route takes precedent