• Article

Configure Standard Edition Server

Topic Last Modified: 2009-07-21

After you install Standard Edition server, use the Configure Server Wizard to configure it.

Note

In Office Communications Server 2007 R2, the Address Book Server is configured automatically. For details about changing configurable Address Book Server settings, see the Operations section of the Office Communications Server 2007 R2 Technical Library at https://go.microsoft.com/fwlink/?LinkID=132106.

In addition to the configurations described in the steps that follow, you can configure additional Session Initiation Protocol (SIP) server, domain, and forest settings. For details, see the documentation in the Operations section of the Office Communications Server 2007 R2 Technical Library at https://go.microsoft.com/fwlink/?LinkID=132106, the Office Communications Server 2007 R2 Edge Server Deployment Guide documentation, the Office Communications Server 2007 R2 Archiving Server Deployment Guide documentation, or the Office Communications Server 2007 R2 Monitoring Server Deployment Guide documentation. For details about configuring SIP user settings, see Configure Users.

To configure Office Communications Server Standard Edition

  1. Log on to the Standard Edition server as a member of the RTCUniversalServerAdmins group or with equivalent user rights.

  2. Do one of the following:

    • Insert the Microsoft Office Communications Server 2007 R2 CD, and then click Standard Edition.
    • If you are installing from a network share, browse to the \setup\amd64\ folder on the network share, and then double-click setupSE.exe.

  3. In the deployment tool, click Deploy Standard Edition Server.

  4. At Configure Server, click Run.

  5. On the Welcome to the Configure Pool/Server Wizard page, click Next.

  6. On the Server or Pool to Configure page, select the server from the list, and then click Next.

  7. On the SIP domains page, verify that your SIP domain appears in the list. If it does not, click the SIP domains in your environment box, type your SIP domain, and then click Add. Repeat these steps for all other SIP domains that the Standard Edition server will support.

  8. Click Next.

  9. On the Client Logon Settings page, do one of the following:

    • If the Office Communicator clients and Microsoft Office Live Meeting 2007 clients in your organization will use Domain Name System (DNS) SRV records for automatic sign-in, click Some or all clients will use DNS SRV records for automatic logon.
      If this server or pool will also be used to authenticate and redirect requests for automatic sign-in, then select the Use this server or pool to authenticate and redirect automatic client logon requests check box.

      Note

      When you configure automatic client sign-in, you must designate one (and only one) Enterprise pool or Standard Edition server to authenticate and redirect client sign-in requests.

    • If the Office Communicator clients and Live Meeting 2007 clients in your organization will not be configured to use automatic sign-in, click Clients will be manually configured for logon.

  10. Click Next.

  11. If in the previous step, you selected Some or all clients will use DNS SRV records for automatic logon, on the SIP Domains for Automatic Logon page, select the check box for the domains that will be supported by the server for automatic sign-in, and then click Next. Otherwise, skip to the next step.

  12. On the External User Access Configuration page, do one of the following:

  13. When you are finished, click Next.

  14. On the Ready to Configure Server or Pool page, review the settings that you specified, and then click Next to configure the Standard Edition server.

  15. When the files are installed and the wizard is complete, select the View the log when you click Finish check box, and then click Finish.

  16. In the log file, verify that <Success> appears under the Execution Result column, look for <Success> Execution Result at the end of each task to verify that the Standard Edition server configuration completed successfully, and then close the log window.