• Article

Validate Edge Server Configuration and Connectivity

Topic Last Modified: 2010-04-29

Use the following procedure to validate your Edge Server configuration.

To validate your Edge Server configuration

  1. Log on to each Edge Server as a member of the RTCLocalServerAdmins group or a group with equivalent user rights.

  2. In the Deployment Wizard, next to Validate Edge Server, click Run.

  3. In the Validation Wizard, on the Welcome page, click Next.

  4. On the Validation Steps page, choose any of the following options that you want to validate:

    • To validate that the server on which you are running is configured correctly, select the Validate Local Server Configuration check box.
    • To verify that the server has connectivity to internal servers, select the Validate Connectivity check box.
    • To verify that your enabled users can log on, select the Validate SIP Logon (1-Party) and IM (2-Party) check box. You can only run this verification after you create and enable your users. You need to run this check on an internal server to validate internal connectivity and verify communications with the Edge Servers, as described in step 6 of this procedure.

  5. Click Next.

  6. If you did not select the Validate SIP Logon (1-Party) and IM (2-Party) option, click Next on the next three pages and then proceed to step 11. If you selected the Validate SIP Logon (1-Party) and IM (2-Party) check box, on the User Account page, do the following:

    • Type the account name, user sign-in name, and password of a test user or other user who is enabled for Session Initiation Protocol (SIP).
    • In the Server or Pool list, click the name of the server or Enterprise pool on which the user account is hosted.

  7. Click Next.

  8. On the Second user account page, do the following:

    • Type the account name, user sign-in name, and password of a second test user or other user who is enabled for SIP. This account will be used with the first account that you specified to test instant messaging (IM) functionality between two users.
    • In the Server or Pool list, click the name of the server or Enterprise pool on which the user account is hosted.

  9. Click Next.

  10. On the Federation and Public IM Connectivity page, to test connectivity between federated domains and public IM connectivity, select the Test connectivity of internal and federated users check box, specify the SIP accounts for federated users, and then click Next.

  11. On the wizard completion page, verify that the Check this box to view log files results check box is selected, and then click Finish.

  12. When the Office Communications Server 2007 R2 Deployment Log opens in a Web browser window, verify that Success appears under Execution Result in the action column on the far right side of the screen. You can also expand each individual task and verify that the Execution Result shows Success for the task. When you finish, close the log window.

Verify Remote User Connectivity

You can test remote user connectivity by using the Office Communications Server Remote Connectivity Analyzer. This Web-based application helps IT Administrators to validate and diagnose end-to-end Office Communications Server scenarios by facilitating testing of the connectivity of a remote user to Office Communications Server. The site simulates multiple Office Communications Server client access scenarios from outside the customer's infrastructure and reports whether the test was successful. You access and run the application directly from the Office Communications Server Remote Connectivity Analyzer Web site at https://www.testocsconnectivity.com.

To use the tool, you first specify the test method:

  • Test remote client connectivity to Office Communications Server by specifying the FQDN of the Access Edge Server and the port.
  • Test remote client connectivity to Office Communications Server by using auto-discovery to find the Access Edge Server and port to which to connect.
Dd441231.security(en-us,office.13).gifSecurity Note:
You should create a test user account for this test, instead of using an account of a user in your organization. As a best practice, change the user password or delete the account after the test.

Because the test results identify exactly what failed and provides detailed information about the problem, this tool can help streamline testing and troubleshooting processes. For details about this tool and how to use it, see Remote Connectivity Analyzer in the Troubleshooting documentation. For details about troubleshooting connectivity problems of remote users, including information that can help you resolve issues related to specific messages, see Troubleshooting Network Issues with Remote or Federated Users in the Troubleshooting documentation.

Test Connectivity of Other External Users

After confirming remote user connectivity as previously described, you should ask other types of external users to try signing in using their account credentials (where applicable). Tests should include each type of external user that your organization supports, including any or all of the following:

  • Users from at least one federated domain, including A/V users.
  • Users of each public IM service provider that your organization supports (and for which provisioning has been completed).
  • Anonymous users.