- Provision the Office Communication Server 2007 service
- Configure the Office Communication Server 2007 service
To look up the RTC Home Server name, launch AdsiEdit.msc and locate the distinguishedName attribute of the OCS pool. Example: CN=LC Services,CN=Microsoft,CN=OCSPool,CN=Pools,CN=RTC Service,CN=Microsoft,CN=configuration,DC=Machine1,DC=test,DC=com
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.
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=Machine1,DC=test,DC=com).
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 server and Directory Web Service 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=Machine1,DC=local'. Error: There is no such object on the server.
This procedure describes how to change the configuration files for the Provisioning server and Directory Web Service.