Product Documentation

Office Communication Server 2007 Services

Jun 05, 2015
CloudPortal Services Manager Office Communication Server 2007 Services deliver communication services from the cloud. Office Communication Server 2007 Services require no installation and use a WMI connection to the Office Communications Server (OCS).

Prerequisites

  • Install Microsoft Office Communications Server 2007 R2.
  • Update user access permissions to allow users to connect to Communicator:
    • If needed, change the CortexAdmins group from global to universal scope.
    • Include the RTCUniversalAdmins and RTCUniversalReadOnlyAdmins groups in the CortexAdmins group.
    • On the OCS server restart all services that use RTC credentials.
  • For OCS reports: Configure and enable the OCS Monitoring Service on the OCS server. On that server:
    • Use both TCP/IP and named pipes for local and remote connections.
    • Allow SQL Server mode and Windows Authentication mode.
    • Add a SQL Server Login that has been granted db_datareader and db_owner permissions to the following OCS databases: RTC, RTCDYN, and LCSCDR (this database is present only when OCS Monitoring is enabled).

To configure Office Communication Server Services

  1. Enable the service (top level) and create a customer plan:
    1. From the main menu, choose Configuration > System Manager > Service Deployment, and expand Office Communication Server 2007.
    2. Click Customer Plans, enter a Name for the plan such as Pool1, click Create, and click Save. Repeat this step to create a customer plan for each OCS pool.
    3. Expand Office Communication Server 2007, click Customer Plans, expand a plan name, enter the distinguished name for RTC Home Server, and click Apply changes. Repeat this step for each customer plan.

      To look up the RTC Home Server name, open the Active Directory file AdsiEdut.msc and locate the distinguishedName attribute of the OCS pool. Example: CN=LC Services,CN=Microsoft,CN=Lab1OCSPool,CN=Pools,CN=RTC Service,CN=Microsoft,CN=configuration,DC=lab1,DC=test,DC=com

    4. Click Service Settings, expand SIP Address, specify the RTC Server Name, click Apply changes, and click Save. The RTC Server Name is used for OCS reporting.
  2. From the main menu, choose Configuration > System Manager > Credentials and add credentials for the SQL Server Login account.
  3. Enable the service (location level) and configure OCS reporting:
    1. Under Service Filter, select Active Directory Location Services, choose a Location Filter if applicable, expand Office Communication Server 2007, and click Service Settings.
    2. Expand Usage Reporting and then choose the SQL Server Login account credentials for RTC Database Credentials.
    3. Enter the full RTC Server Name for the server that contains the OCS databases, click Apply Changes, and then click Save.
  4. Create and configure a user plan:
    1. Under Service Filter, select Top Environment Services, expand Office Communication Server 2007, click User Plans, enter a Name for the user plan such as Full, and click Create.
    2. Click User Plans, expand the plan, and update the settings if needed.
    3. Click Apply changes and then click Save.
    4. Under Service Filter, select Active Directory Location Services, choose a Location Filter if applicable, expand Office Communication Server 2007, click User Plans, and expand the user plan.
    5. Select the Meetings Policy check box and then select the applicable policy.
    6. Select the Unified Communications Policy check box, select the applicable policy, click Apply changes, and click Save.

To partition the address book by OU for a multi-tenant environment

In a hosted multi-tenant environment, user address book searches should return only the users and groups that are in the same OU (customer) as the user.

To limit user search results, use the Address Book Service Configuration Tool (ABSConfig.exe) to partition the address book by OU. That tool is in the Microsoft Office Communications Server 2007 R2 Resource Kit, available from the Microsoft download site.

Note: Partitioning the address book by OU does not impact a user's ability to send an instant message to other customers' users.

To update OCSSettingsLocation values in Web Services web.config files

By default, the CloudPortal Services Manager Provisioning Engine Web Services and Directory Web Services are installed with the OCSSettingsLocation set to System (for example, CN=System,DC=lab1,DC=local).

Microsoft Office Communications Server 2007 R2 allows the Service Provider to install the OCS directory at either Configuration (for example, CN=configuration,DC=server,DC=local) or System. If the OCS directory is installed at Configuration, the OCSSettingsLocation value in the web.config files for the Provisioning Engine and Directory Web Services must be updated. If the container settings for OCS and the web services do not match, Service Manager displays errors such as the following during user plan updates or user provisioning:

Server was unable to process request. ---> Failed to load the LCS/OCS policies from path 'LDAP://CN=Policies,CN=RTC Service,CN=Microsoft,CN=System,DC=lab1,DC=local'. Error: There is no such object on the server.

This procedure describes how to change the configuration files for the Services Manager Provisioning Engine Web Services and Directory Web Services.

  1. Stop the Services Manager Queue Monitor service.
  2. Log on to the Provisioning server and then open the appSettings.config file. That file is typically located in: C:Program Files (x86)CitrixCortexProvisioning Engine.
  3. Change the OCSSettingsLocation key value to CONFIGURATION and then save the file.
  4. Restart the Queue Monitor service.
  5. Log on to the server, usually the Provisioning server, where the Services Manager Directory Web Service is saved and then open the web.config file. That file is typically located in: C:Program Files (x86)CitrixCortexServicesDirectory.
  6. Change the OCSSettingsLocation key value to CONFIGURATION and then save the file.