The Lync Server 2010 planning tool is available as a download that is separate from the Lync Server 2010 Enterprise Edition or Lync Server 2010 Standard Edition installation media.

Note:
Ensure that you remove all earlier versions of the Lync Server 2010 planning tool before you install the version provided for this release.

To install the planning tool, you must install the following:

• Operating system (one of the following): Windows Server 2008 with Service Pack 2 (SP2), Windows Server 2008 R2, Windows 7, Windows Vista operating system with SP2, either 32-bit or 64-bit
  
  
• .NET Framework 3.5 with SP1
  
  

As recommended in “Beginning the Planning Process” in the Planning documentation, at the start of the planning process you may have run the planning tool to get a sense of the kind of questions you would need to think about while planning your Lync Server 2010 deployment.

For the Enterprise Voice workload, in addition to highlighting available Enterprise Voice features and capabilities, the planning tool will also alert you to the mitigating factors that you need to account for in your environment, whether at central sites or branch sites. For example, if you indicate that you plan to deploy SIP trunking to provide PSTN connectivity, but that the Session Border Controller (SBC) of the Internet Telephony Service provider (ITSP) to which you connect does not support media bypass, then the tool asks you to provide the hardware specifications for the Mediation Server that will be required to process media for calls that use the SIP trunk. If the SBC of the SIP trunking ITSP supports media bypass, then media from a user at a branch site can flow directly to a gateway or other media termination point without the need for you to deploy a Mediation Server at the branch site or without having to flow over the WAN link to the central site that has the Mediation Server that controls the gateway.

Note:

Media bypass will not interoperate with every PSTN gateway, IP-PBX, and SBC. Microsoft has tested a set of PSTN gateways with certified partners and has done some testing with Cisco IP-PBXs. Certification for SBCs is underway. Media bypass is supported only with products and versions listed on Unified Communications Open Interoperability Program – Lync Server at http://go.microsoft.com/fwlink/?LinkId=214406.

The planning tool considerations for Enterprise Voice include:

• the number of sites in your deployment and the type of network connection between them
  
  
• the number of users, including the number or percentage of users that will be enabled for Enterprise Voice and for Exchange Unified Messaging (UM), at each of the sites in your deployment
  
  
• the number of calls that you expect Enterprise Voice users to generate at each site
  
  
• the number of times per day that you expect users at each site who are enabled for Exchange UM will check voice mail
  
  
• Enterprise Voice features that you want to provide to your users, including:
  
  
  1. Exchange UM voice mail
     
     
  2. Call admission control (CAC) over WAN links between sites
     
     
  3. Media bypass
     
     
• the PSTN connectivity options that you will incorporate and general information about each of them, for example:
  
  
  • the type of PSTN gateway
    
    
  • a SIP trunk to an Internet Telephony Service Provider (ITSP)
    
    
  • the type of PBX you will deploy
    
    
  • whether the PSTN connectivity option that you choose supports the new DNS load balancing and media bypass functionality that have been added to Lync Server for this release
    
    
  • the type of network line or primary rate interface (PRI) used by those devices or ITSP
    
    
• approximate WAN bandwidth requirements of each site
  
  

Using the deployment preferences you identified during the Enterprise Voice planning process (as a result of reviewing the documentation and running the planning tool), re-run the planning tool to design a topology that will now include a Mediation Server collocated with each Front End Server or a Mediation Server in a stand-alone pool, settings for your preferred Enterprise Voice capabilities, and Enterprise Voice support for users at the appropriate sites in your Lync Server environment.

Output the planning tool’s recommended topology to an XML file that is readable by Topology Builder. Then, in Topology Builder, configure the fully qualified domain name (FQDN) or Internet protocol (IP) address, port, and transport protocol for the Mediation Server and PSTN gateways that you have deployed for Enterprise Voice. If you have collocated your Mediation Servers on servers in your Front End pools, then these are configured as Front End pool settings. If you have deployed your Mediation Servers in a stand-alone pool, then the FQDN, IP address, port, and transport protocol for the Mediation Servers and PSTN gateways are configured as Mediation Server pool settings. In either case, you must also use this same information to configure the next hop pool on the Front End pool. Use Topology Builder to publish your configuration settings to the Central Management store.

After the Central Management store is updated with your new Enterprise Voice settings, running the setup files for Lync Server on each server in your deployment will install Mediation Server and configure the PSTN gateway associations with the appropriate settings.