Topic Last Modified: 2010-12-13

To incorporate an Edge Server or Edge Server pool into your topology design, you need to specify the fully qualified domain name (FQDN) of the server on which you want to deploy Edge Server or Edge Server pool. Prior to publishing a topology that includes the Edge Server or Edge Server pool and installing Lync Server 2010 on the server, you should have completed all prerequisites for deploying external user access. For details about these prerequisites, see Preparing for Installation of Servers in the Perimeter Network in the Deployment documentation.

The name you specify must be identical to the computer name configured on the server. By default, the computer name of a computer that is not joined to a domain is a short name, not an FQDN. Topology Builder uses FQDNs, not short names. You must configure a Domain Name System (DNS) suffix on the name of the computer to be deployed as an Edge Server or Edge Server pool that is not joined to a domain. For details about adding a DNS suffix to a computer name, see Configure DNS Records for Edge Support.
If you plan to implement an Edge Server pool in the future, select Multiple computer pool. Even though a pool is defined as two or more computers that are load balanced, you can create a single computer pool and create a pool FQDN for the single computer. When you are ready to add more computers to the pool later, you must re-run Topology Builder to define the new pool member, publish the new topology, and then setup the new Edge Server pool member through the Lync Server Deployment Wizard. You must also add the new pool member to the appropriate load balancers for the pool, DNS load balancing or hardware load balancers. In many cases, you would have both load balancing systems in place. Be sure that you are adding the new member server to both.

You can add support for external user access when you deploy your initial topology or afterward. For details about adding Edge Servers or Edge Server pool to an existing topology, see Defining Your Edge Topology in the Edge Server Deployment documentation.