Udostępnij za pośrednictwem

Edit or configure simple URLs in Lync Server 2013

  • Artykuł

 

Topic Last Modified: 2014-02-04

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.

Lync Server 2013 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. For more information about simple URLs, see Planning for simple URLs in Lync Server 2013 in the Planning documentation. You can select the format for your simple URLs from several options. For details about these options, see DNS requirements for simple URLs in Lync Server 2013 in the Planning documentation.

By default, simple URLs will be configured in the form of (for example, the dial-in simple URL): https://dialin.<SIP Domain>

To configure simple URLs

  1. In Topology Builder, right-click the Lync Server 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 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 2013 Control Panel, and then click OK.

    Tip

    We recommend using the simplest possible URL for the Admin URL. The simplest option is https://admin.<domain>.

    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 cmdlet on each Director and Front End Server to register the change.