Installing the Compliance Server (2007 R2 Beta)

  • Article

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

Before you install the Compliance Server, you need to complete the following tasks:

Warning

Although Group Chat does not support installing a second Compliance Server in the pool, you can use the following procedure to install a backup Compliance Server:

  1. Install the first Compliance Server.
  2. From the tblserveridentity table in the Group Chat database, record the server address.
  3. Install a second Compliance Server, stop the first Compliance Server, and then start the second Compliance Server.
  4. The first Compliance Server is now the backup server. To change to the Compliance Server backup, replace the server address in the tblserveridentity table with the server address that you previously recorded.

To install the Compliance Server

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

  2. From the Group Chat installation medium, run ServerSetup.exe.

  3. Do any of the following, as needed:

    • If .NET Framework 3.0 is not installed, in the dialog box that indicates that it must be installed, click Yes.
    • If the appropriate version of Microsoft Visual Studio 2005 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 v1.0 Redistributable is not installed, in the dialog box that indicates that it must be installed, click Yes.

  4. On the Microsoft Office Group Chat Server Setup Wizard Start page, click Next.

  5. On the License Agreement page, review the license agreement, click I accept the terms in the license agreement, and then click Next.

  6. On the Customer Information page, specify the user name and organization name, and then click Next. The default information is taken from system properties.

  7. On the Install Location page, verify the default location, which is C:\Program Files\Microsoft Office Communications Server 2007\Group Chat Functionality\.

  8. Click Next.

  9. On the Select 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 to be installed on the computer.

  10. Click Next.

  11. On the Confirm Installation page, click Next.

  12. After the Installation Progress page indicates completion, on the Finalizing Server Information page that indicates that the Compliance Server is installed, but the lookup server, the channel server, and the Web service are not installed, click Next.

  13. On the Group Chat Database page, in the Server box, the server on which the SQL Server database was created for Group Chat (for example, groupchat.constoso.com\sql2005).

  14. In the Database box, specify the name of the database instance (for example, groupchatdb).

    Note

    This information should be the same as that entered for the lookup servers, the channel servers, and the Web service, unless there is a separate compliance database.

  15. Under SQL Credentials for Temporary Use, click one of the following:

    • Use Windows Authentication credentials (current user)
    • Use SQL Authentication credentials below. To use SQL Server Authentication credentials, specify the ID associated with the credentials and the password.

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

  16. Click Next.

  17. On the Compliance Database page, to use the same server that contains the non-compliance database, select Use Group Chat Functionality Database for compliance data.

  18. To use a dedicated server, type the location in the Server/instance box, type the database name in the Database box, and then under SQL Credentials for Temporary Use, specify credentials to use during installation. Do not select the Use Group Chat Functionality Database for compliance data check box.

  19. Click Next.

  20. On the Gather Database State page, review the information about the state of the Group Chat and Compliance databases, and then click Next.

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

    • Click Automatic connection configuration to automatically connect to AD DS.
    • Click Manual connection configuration, and then specify the FQDN of the global catalog server you want to use for the connection.

  22. Under Connection Settings, do one of the following:

    • Click Secure connection only.
    • Click Connect as, and then specify the account and password to use to connect. The account must have permission to access AD DS.

  23. Under Search Options, specify the number of objects to return when searching AD DS. This 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.

  24. Click Next.

  25. On the Security Group page, verify that the AD Security Group box contains the AD DS security group that you created prior to installation, and then click Next.

  26. On the Super User(s) page, the Super Users box lists the super users for this Group Chat installation. Verify that the super users in the list are accounts that you want to have administrative rights to create chat rooms and add users in the Admin Tool. The user name of the installer automatically appears in the Super Users box. To specify other super users, under Lookup and Add Existing Active Directory User, specify the SIP URI or username to be used to look up the users who should be Super Users, and then click Add. (SIP URIs are case-sensitive.) You can also add Super Users later using the Admin Tool.

  27. Click Next.

  28. On the Office Communications Server page, review the information for the Lookup Server, Channel Server, and Web Service (specified when you installed those servers), and then click Next.

  29. On the Lookup Server page, review the information for the Lookup Server, Channel Server, and Web Service (specified when you installed those servers), as well as this Compliance Server, and then click Next.

  30. On the Compliance Server page, under Windows Service Credentials, specify the user name and password for the service account, which must be a member of RTCComponentUniversalServices. For example, someone@example.com.

  31. To add compliance adapters (which is required to archive compliance data in a file), click Add.

  32. Select the appropriate adapter from the provided list, or add a new adapter.

  33. In the New Compliance Adapter dialog box, specify a name for the compliance adapter. Group Chat currently supports the following compliance adapters:

    • Akonix
    • Assentor
    • Facetime
    • Default (no custom configuration required)

    The default Adapter Type is XML.

  34. In Output Directory, specify the location that you want to use to store the XML files generated by the compliance adapters. Click Browse to navigate to the folder.

  35. Under options, do the following:

    • To place the output in separate files for each channel that has activity during the specified time interval, not one large file for all channels, under Options, select the Produce separate output files for each channel check box.
    • To create a separate file to record what files are uploaded or downloaded from Group Chat channels during the time interval, select the Produce additional output files to record file upload/download events check box.
    • To perform additional queries against the Group Chat database, select the Requires full user details from non-compliance database check box. This action fills in more details for each user mentioned in the output file. It decreases performance on the Compliance Server in favor of having more information in the output file.
    • To run additional queries against the Group Chat database, select the Requires full channel details from non-compliance database check box. This action fills in more details for each chat room that is mentioned in the output file. It decreases performance on the Compliance Server in favor of having more information in the output file.

  36. To edit the configuration of the adapter, click Edit Custom Configuration.

    This configuration should either be left blank or it should contain a valid XSLT transformation script that will manipulate the standard XML output into the text output of your own design. To produce the standard XML output, leave the configuration blank.

  37. In the Conversation interval in minutes box, specify the length of a conversation for this adapter.

  38. Click OK.

  39. In the Compliance Server page, which refreshes with the new adapters added, click Next.

  40. In the Web Service page, in which the fields are inactive and they show the information set for the lookup server, channel server and Web service set for this Compliance Server, click Next.

  41. In the Installation Summary page that appears, which lists the components of the installation, click Finish.

  42. In the Installation Complete page, which contains the message <compliance account> is granted log on as a service, click Close.