Installing the Chat Server for a Single-Server Topology or the First Chat Server in a Multiple-Server Topology (2007 R2 Beta)

  • Article

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

The following section describes how to install either a single-server topology or the first server instance in a pooled topology. A server instance consists of the Lookup Server, Channel Server, and Web Service. If a Compliance Server is also to be installed, it must be installed on a separate computer.

To complete the installation of a Chat Server, including the Lookup Server, Channel Server and Web Services for Group Chat, use the following procedure.

Important

Although setup gives you the option to install Chat Server and Compliance Server simultaneously on the same server, Group Chat does not support hosting both servers on the same machine. Make sure that during install, only the Chat Server or the Compliance Server option is selected, not both.

To install a Chat Server

  1. Log on to the computer on which you want to install the Chat Server, using an account that is a member of the RTCUniversalServerAdmins or Domain Admins group, or an account that has equivalent rights.

  2. Run ServerSetup.exe.

    If appropriate version of the Visual Studio 2008 C++ Runtime is not installed, in the dialog box that indicates that it must be installed, click Yes.

    If the appropriate version of UCMA API v2.0 Redistributable is not installed, in the dialog box that indicates that it must be installed, click Yes.

  3. On the Microsoft Office Communications Server 2007, Group Chat Setup Wizard Welcome page, click Next.

  4. On the License Agreement page, review the license agreement and, if you agree to the terms and want to continue the installation, click I accept the terms in the license agreement, and then click Next.

  5. On the Customer Information page, specify your user name and organization name, and then click Next.

  6. On the Install location page, verify that the default location is <drive letter>:\Program Files\Microsoft Office Communications Server 2007\Group Chat\, and then click Next.

  7. On the Select the features page, click the drop-down list box to the left of Compliance Server, and then click the red X to specify that the Compliance Server is not to be installed on the computer. Only the Chat Server will be installed on the computer, which includes the Lookup Server, Channel Server, and Web Service.

  8. Click Next.

  9. On the Confirm Installation page, click Next.

  10. After the Installation Progress dialog box indicates completion, on the Finalizing Server Information, Machine Status page (separate window), which indicates installation of Lookup Server, Channel Server, and Web Service, but not Compliance Server, click Next.

  11. On the Group Chat Database page, in Server, specify the FQDN and instance of the server on which the SQL Server database was created for Group Chat (for example, groupchat.constoso.com\sql2005).

    Note

    The Group Chat database cannot be located on the same computer as the Group Chat servers.

  12. In Database, specify the name of the database (for example, groupchatdb).

  13. Under SQL Credentials for Temporary Use, do one of the following:

    • Click Use Windows Authentication credentials (current user).
    • Click Use SQL Authentication credentials below, and then specify the ID and the password to be used for SQL Server Authentication.

    These credentials are used only to connect to the given instance of the SQL Server database during installation.

  14. Click Next.

  15. The Gather Database State page appears. There may be a slight delay while the databases are examined. If any errors are encountered, this message lists the errors. If you are installing a second or third instance of Group Chat, the established settings from the server pool are used, and all controls on this page, except Password, are unavailable.

  16. On the Active Directory page, under Global Catalog, do one of the following:

    • Click Automatic connection configuration.
    • Click Manual connection configuration for the method of connection to AD DS, and then specify the FQDN of the global catalog server.

  17. Under Connection Settings, to use secure connections, select the Use secure connection only check box.

  18. To specify credentials to be used to connect, select the Connect as check box, and then specify the account and password to be used to connect. The account must have permission to access AD DS.

    Important

    The account must have permission to access AD DS.

  19. Under Search Options, specify the number of objects to return when searching AD DS. This number is used for group or user searches in the Admin Tool or the Group Chat Console. The default value is 200. If you specify 0, there is no limit on the number of search results returned.

  20. Click Next.

  21. On the Super User(s) page, specify one or more super users, which are the users that have administrative rights to administer MGC servers and users. The Super Users specified here will be the initial Super Users for this installation. You can add Super Users later using the Admin Tool. The user name of the installer automatically appears in the Lookup by Username. To add this user name to the Super User(s) list, click Add. To add a different user to the Super User(s) list, specify a SIP URI or user name, and then click Add.

  22. Click Next.

    Note

    If you are installing a second or third instance of Group Chat to create a pooled environment, the established settings from the server pool are used and all controls are unavailable on this page.

  23. On the Office Communications Server page, in Host, specify the FQDN of the Office Communications Server.

  24. In the Port box, select the Auto detect port check box or specify a port.

  25. Under Authentication Type, do one of the following:

    • Click TCP.
    • Click MTLS. Browse to the location of the certificate, and then select it.

  26. Click Next.

    Note

    If you are installing a second or third instance of Group Chat to create a pooled environment, the established settings from the server pool are used and all controls are unavailable, except for the Pool Communication Port, Password, and Confirm Password boxes.

  27. On the Lookup Server page, under Office Communications Server credentials, for the Lookup Server account you created prior to installation, in the SIP URI box, specify the SIP URI of the Lookup Server account. SIP URIs are case-sensitive.

  28. In the Username box, specify the name of the Lookup Server account. This can take the following forms: username@domain or domain\username.

  29. In the Password and Confirm Password boxes, type the password for the account.

  30. Under Settings Specific to this Machine, in the Pool Communication Port box, specify the port to be used for to listen to messages from other servers in the system’s server pool (to allow all servers to communicate with each other and share data such as chat history and channel settings with all other servers in the system). The default port for Lookup Server is 8010.

    Note

    The Pool Communication Port for the Lookup and Channel Servers installed on the computer must use different ports. For example, if the pool communication port for a Lookup Server is 8011, the pool communication port for the Channel Server on the computer cannot be 8011.

  31. In Service Listening Port, specify the port to be used to listen for inbound client connections. The default value for this port is 5041.

    Once selected, the installer will create a Trusted Service Setting for the Channel Server. The Trusted Service Setting will be stored in AD DS, and used by Office Communications Server to identify the Channel Server as a trusted server. As a result, the Channel Server will not explicitly register in Office Communications Server. Instead, traffic will be routed directly to this port and FQDN via a GRUU.

  32. Click Next.

  33. On the Channel Server page, In the Username box, specify the name of the Channel Server account. This can take the following forms: username@domain or domain\username. This is the Channel Server account you created before installation.

  34. In the Password and Confirm Password boxes, type the password for the account.

  35. In Pool Communication Port, specify the port to be used for to listen to messages from other servers in the system’s server pool (to allow all servers to communicate with each other and share data such as chat history and channel settings with all other servers in the system). The default port is 8011. This setting cannot be the same port used by the Lookup Server on the computer.

  36. Click Next.

  37. On the Pooled Compliance Settings page, in Compliance Repository Settings, browse to and select a network share to store a copy of any uploaded files.

  38. Under Settings, select the Enable Compliance Logging check box if you want to start compliance logging when the system is installed.

  39. Click Next.

  40. On the Web Service page, specify the directory used to store files that are uploaded to the Web Service. If you have deployed multiple Group Chat, this must be a shared network directory. The directory must be separate from the Web Service folder, and all users must have full control of the directory.

  41. Click Next.

  42. On the Installation Summary page, click Finish.

  43. On the Installation Complete page, click Close.