Share via

Validate Internal Server Configuration (2007 R2 Beta)

  • Article

[This is preliminary documentation and is subject to change. Blank topics are included as placeholders.]

Use the following procedure to validate that your internal servers can connect to the Edge Servers. You need to run the following validation tasks for each server and pool or on each Standard Edition server:

  • Validate Front-End Server
  • Validate Web Components Servers
  • Validate Web Conferencing Servers
  • Validate A/V Conferencing Servers

Validate Front End Server Functionality

Use the following procedure to verify that your Front End Servers are configured correctly. This procedure must be run on each Standard Edition server, all consolidated Enterprise Edition servers for pools in the consolidated configuration, and all Front End Servers for pools in the expanded configuration that connect to Edge Servers.

To validate Front End Servers

  1. Log onto your Standard Edition server, an Enterprise Edition server for a pool the consolidated configuration or the Front End Server in a pool in the expanded configuration with an account that is a member of the RTCUniversalServerAdmins group or has equivalent permissions.

  2. In the console tree, expand the forest node, and then do one of the following:

    • On a Standard Edition server, expand Standard Edition Servers, expand the server name, right-click the FQDN of the server, point to Validation, and then click Front End Server.
    • On an Enterprise Edition server, expand Enterprise pools, expand the pool, expand Front Ends, right-click the Front End Server that you want to validate, point to Validation, and then click Front End Server.

  3. On the Welcome page, click Next.

  4. On the Select Validation Steps page:

    • Select the Validate SIP Logon (1-Party) and IM (2-Party) check box. This option verifies that the user accounts you created and enabled can be used to log on and connect.
    • Select the Validate Local Server Configuration check box to validate that the server on which you are running is configured correctly.
    • Select the Validate Connectivity check box to verify that the server has connectivity to the back-end database, other internal servers, and the Edge Servers.

  5. 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 SIP.
    • In the Server or Pool list, click the name of the server or Enterprise pool on which the user account is hosted.

  6. Click Next.

  7. 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 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.

  8. Click Next.

  9. If you have configured federation or public IM connectivity, do the following on the Federation and Public IM Connectivity page:

    • Select the Test between internal user and federated users check box.
    • In the Enter SIP User Accounts for federated use box, type the SIP URI of one or more federated user accounts (separated by semicolons) that you want to use to test this functionality. Otherwise, leave the check box cleared.

  10. Click Next.

  11. On the wizard completion page, verify that the View the log when you click Finish 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. Optionally, expand each individual task and verify that the Execution Result shows Success for the task. When you finish, close the log window.

Validate Web Components Server Functionality

Use the following procedure to verify that your Web Components are configured correctly. This procedure must be run on each Standard Edition server, all consolidated Enterprise Edition servers for pools in the consolidated configuration, and all Front End Servers for pools in the expanded configuration that connect to Edge Servers.

To validate Web Component Servers

  1. Log on to your Standard Edition server, an Enterprise Edition server for a pool the consolidated configuration, or the Web Components Server in a pool in the expanded configuration with an account that is a member of the RTCUniversalServerAdmins group or has equivalent permissions.

  2. In the console tree, expand the forest node, and then do one of the following:

    • On a Standard Edition server, expand Standard Edition Servers, expand the server name, right-click the FQDN of the server, point to Validation, and then click WebComponents Server.
    • On an Enterprise Edition server, expand Enterprise pools, expand the pool, expand Web Components, right-click the Web Components Server that you want to validate, point to Validation, and then click Web Components Server.

  3. On the Welcome page, click Next.

  4. On the Select Validation Steps page:

    • To validate that the server is configured correctly, select the Validate Local Server Configuration check box.
    • To verify that clients have connectivity to the IIS directories where the Address Book files, group expansion and meeting content, and compliance data are stored, select the Validate Connectivity check box.

  5. Click Next.

  6. On the wizard completion page, verify that the View the log when you click Finish check box is selected, and then click Finish.

  7. When the Office Communications Server 2007 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. Optionally, expand each individual task and verify that the Execution Result shows Success for the task. When you finish, close the log window.

Validate Web Conferencing Server Functionality

Use the following procedure to verify that your Web Conferencing Servers are configured correctly. This procedure must be run on each Standard Edition server, all consolidated Enterprise Edition servers for pools in the consolidated configuration, and all Web Conferencing Servers for pools in the expanded configuration that will connect to Edge Servers.

To validate Web Conferencing Servers

  1. Log on to your Standard Edition server, an Enterprise Edition server for a pool the consolidated configuration, or the Web Conferencing Server in a pool in the expanded configuration with an account that is a member of the RTCUniversalServerAdmins group or has equivalent permissions.

  2. In the console tree, expand the forest node, and then do one of the following:

    • On a Standard Edition server, expand Standard Edition Servers, expand the server name, right-click the FQDN of the server, point to Validation, and then click Web Conferencing Server.
    • On an Enterprise Edition server, expand Enterprise pools, expand the pool, expand Web Conferencing, right-click the Web Conferencing Server that you want to validate, point to Validation, and then click Web Conferencing Server.

  3. On the Welcome page, click Next.

  4. On the Select Validation Steps page:

    • To validate that the Office Communications Server is configured correctly, select the Validate Local Server Configuration check box.
    • To verify that the Web Conferencing Server has connectivity to the Front End Server and any Edge Servers, select the Validate Connectivity check box.

  5. Click Next.

  6. On the wizard completion page, verify that the View the log when you click Finish check box is selected, and then click Finish.

  7. 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. Optionally, expand each individual task and verify that the Execution Result shows Success for the task. When you finish, close the log window.

Validate A/V Conferencing Server Functionality

Use the following procedure to ensure that your A/V Conferencing Servers are configured correctly. This procedure must be run on each Standard Edition server, all consolidated Enterprise Edition servers for pools in the consolidated configuration, and all A/V Conferencing Servers for pools in the expanded configuration that connect to Edge Servers.

To validate A/V Conferencing Servers

  1. Log on to your Standard Edition server, an Enterprise Edition server in a pool in the consolidated configuration, or the Front End Server in a pool in the expanded configuration with an account that is a member of the RTCUniversalServerAdmins group or has equivalent permissions.

  2. In the console tree, expand the forest node, and then do one of the following:

    • On a Standard Edition server, expand Standard Edition Servers, expand the server name, right-click the FQDN of the server, point to Validation, and then click A/V Conferencing Server.
    • On an Enterprise Edition server, expand Enterprise pools, expand the pool, expand A/V Conferencing, right-click the A/V Conferencing Server that you want to validate, point to Validation, and then click A/V Conferencing Server.

  3. On the Welcome page, click Next.

  4. On the Select Validation Steps page:

    • To validate that the Office Communications Server is configured correctly, select the Validate Local Server Configuration check box.
    • To verify that the A/V Conferencing Server has connectivity to Front End Servers and Edge Servers, select the Validate Connectivity check box.

  5. Click Next.

  6. On the wizard completion page, verify that the View the log when you click Finish check box is selected, and then click Finish.

  7. 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. Optionally, expand each individual task and verify that the Execution Result shows Success for the task. When you finish, close the log window.