To configure an Edge Server

1. In the Deployment Wizard, on the Deploy Edge Serverpage, next to Step 3: Configure Edge Server, click Run.
   
   
2. On the Welcomepage of the Configure Office Communications Server 2007 R2 Edge Server Wizard, click Next.
   
   
3. On the Import Settings from a Filepage, do one of the following:
   
   
   • If you want to configure this server as a new Edge Server and you do not have settings that you want to import from a previously installed Edge Server, click Next.
     
     
   • If you have previously set up an Edge Server and exported the settings from it to a configuration file that you want to import on this Edge Server, select the Import Settingscheck box, type the full path and name of the file containing the settings you want to import, and then click Next.
     
     
4. On the Internal Interfacepage, do the following:
   
   
   • In the Internal Interface IP Addressbox, select the internal interface IP address.
     
     

     Note:
     Use the local IP address of the computer regardless of whether this Edge Server is load balanced.

   • In the FQDN for the internal interfacebox, type the fully qualified domain name (FQDN) of the internal interface.
     
     

     Note:
     If this server is connected to a load balancer, type the FQDN of the virtual IP address of the load balancer.

5. Click Next.
   
   
6. On the External Interfacepage, configure the IP address and the FQDN for the external interfaces of the three edge services for this server. For load balanced Edge Servers, specify the IP address and FQDN as follows:
   
   
   • For the Access Edge service specify the IP address 192.0.2.100. The default federation port is set to 5061 and cannot be changed. The default Transport Layer Security (TLS) port for remote access is 443. To specify a port other than 443 for remote user access, click 5061to use port 5061 or click Other, and then type the port number.
     
     
   • For the Web Conferencing Edge service specify the IP address of 192.0.2.102. The default TLS port is 443. To specify a port other than 443, click Other, and then type the port number.
     
     
   • For the A/V Edge service on an Edge Server specify the IP address 192.0.2.101. The default Transmission Control Protocol (TCP) port is 443. To specify a port other than 443, click Other, and then type the port number.
     
     

     Important:
     The ports that you specify in this step must be open in the external firewall. For details, see Firewall Requirements for External User Access at http://go.microsoft.com/fwlink/?LinkId=157764 .

     Note:
     Each edge service running on an Edge Server should have a separate external IP address. If you do not use a separate IP address for each, you must use separate ports for each service.

7. Click Next.
   
   
8. On the Enable Features on Access Edge Serverpage, select the features that you want to enable on this Edge Server as follows:
   
   
   • To enable remote users to connect to Office Communications Server 2007 R2 from the Internet to view presence information and exchange instant messages with internal users using this Edge Server, select the Allow remote user access to your networkcheck box.
     
     
   • To enable external anonymous users to join conferences through this Edge Server, select the Allow anonymous user to join meetingscheck box. Anonymous users are external users who do not have credentials in the Active Directory Domain Services (AD DS). Note that the remote user access and anonymous user access settings are independent; you can allow either while disallowing the other.
     
     
   • If federation will be disabled on this Edge Server, and this Edge Server will allow remote user access and you want to allow the remote users to communicate with federated users (in which the federation relationship is supported by a different Edge Server), select the Allow users to communicate with federated contactscheck box. (This option is not available or necessary when you also enable federation on this Edge Server.)
     
     
   • To enable federation or public instant messaging (IM) connectivity through the Access Edge service on this Edge Server, select the Enable federationcheck box.
     
     
   • To enable automatic discovery of federated partners, select the Allow discovery of federation partnerscheck box. We recommend this configuration. If you want to limit federation to only partner domains that you specify, do not select this option and you can configure specific federated partners after your initial deployment. For details, see Configure Federation at http://go.microsoft.com/fwlink/?LinkId=157767 .
     
     
   • To enable public IM connectivity through this Edge Server, select the Federation with selected public IM providerscheck box, and then select the public IM providers (such as Windows Live, AOL, and Yahoo!) with which you want to federate.
     
     

     Important:
     Before you can connect to a public IM provider, you must have an appropriate license and provision the connections. Public IM connectivity will not work until the provisioning process is completed. For details about licensing and completing the provisioning process, see the Office Communications Server Public IM Connectivity Provisioning Guide at http://go.microsoft.com/fwlink/?LinkId=155970 .

     Note:
     For details about configuring anonymous users and federation, see Configure the Environment at http://go.microsoft.com/fwlink/?LinkId=157766 .

9. Click Next.
   
   
10. On the FQDN of the Internal Next Hop Serverpage, in the FQDN of next hop serverbox, type or click the FQDN of the next hop server to which this Edge Server routes internal traffic or, if you are using a Director to route incoming traffic, type the FQDN of the Director, and then click Next. For Litware Inc., this value is ocsse1.litwareinc.com.
    
    
11. On the Authorized Internal SIP Domainspage, for each Session Initiation Protocol (SIP) domain to be supported in your Office Communications Server 2007 R2 deployment, in the box, type the name of the SIP domain, and then click Add. After adding all SIP domains to be supported, click Next. For Litware, this value is litwareinc.com.
    
    
12. On the Authorized Internal Serverspage, specify each internal server that can connect to your Edge Server, and click Addafter each.
    
    

    Note:
    Type the FQDN of the Director (that is, if you have one deployed), and also type the FQDN of each Enterprise pool and Standard Edition server in your organization.

13. Click Next.
    
    
14. On the summary page, review the settings that you selected, and then click Next.
    
    
15. On the wizard completion page, do the following:
    
    
    • Select the View the log when you click Finishcheck box.
      
      
    • If you want to export the server settings to a configuration file so that they can be imported to another Edge Server (to streamline the setup of that server), select Export, specify a location and name for the Extensible Markup Language (XML) file to which you want to save the server settings, and then click Save.
      
      
16. Click Finish.
    
    
17. When the Office Communications Server 2007 R2 Deployment Log opens in a Web browser window, verify that Successappears under Execution Resultin the Actioncolumn on the far right side of the screen. Expand each individual task and verify that the Execution Resultshows Successfor the task. When you finish, close the log window.