An example of this is the RTCUserSearchPropertySet, which

Tools such as Microsoft Identity Integration Server (MIIS) and the MIIS Active Directory Identity Integration Feature Pack (IIFP) may be utilized to synchronize a user account in one forest with a user account or contact object in another forest. Microsoft has put together a great document regarding this centralized, or resource forest, model. Within the LCS 2005 with SP1 Resource Kit is a directory, C:Program FilesMicrosoft LC 2005ResKit LcsSync, that contains documentation and example XML files for implementing the resource forest model utilizing MIIS. The resource kit contains a document that provides guidance for implementing this model. This document, Deploying_in_a_Multiple_Forest_Environment.doc, is also located in the LcsSynch directory along with the example XML files mentioned. Live Communications Server 2005 SP1 and DNS LCS uses DNS to enable automatic connectivity to LCS Standard Edition or Enterprise Edition servers without manually configuring the client to communicate with a specific Internet Protocol (IP) address or fully qualified domain name (FQDN) of a server. LCS also uses DNS to enable federation and Public Instant Messaging Connectivity (PIC) to provide communication between LCS Access Proxy servers, as mentioned in Chapter 1. To enable automatic configuration of the Microsoft Office Communicator 2005 client, you need to create the appropriate DNS records to identify the servers and protocols used to connect the client to the specified LCS server. This section identifies the required DNS records used by LCS to ensure a successful deployment. DNS Host A Records When installing LCS, the initial steps to deploy the software include preparing your Active Directory for LCS. In doing so, you will update the Active Directory schema, create new LCS properties and accounts within the Active Directory domain and forest, and create an LCS pool (if using LCS Enterprise Edition). When you create the LCS pool or install a LCS Standard Edition server, you need to have a residing DNS host A record for the pool available in DNS prior to this step or you will receive a warning in your LCS installation log file. This does not prevent you from creating an LCS pool or server, but you will still need to create the record before Communicator 2005 automatic configuration will work. The client, when enabled with automatic configuration, will perform a DNS query, searching for the name of the server or pool in DNS. If the host A record is not present, the client will not be able to sign in to the service. The query is performed using the lookup of the data listed after the @ sign portion of the user s sign-in name. For example, if the user s sign-in name is john.doe@company.com, the client will look for a corresponding DNS host A record for company.com. Figure 4-3 displays the flow of the client querying DNS for the host A record of the LCS server or pool. To enable automatic configuration and to create a DNS host A record for your LCS Server or pool, you must create the a record like the following: Company Name = ConnectedInnovation.com DNS A Host Record for a pool = LCS.ConnectedInnovation.com DNS A Host Record for a Server = Server1.ConnectedInnovation.com 75 Preparing Your Environment for Live Communications Server 2005

Note: If you are looking for good and high quality web space to host and run your jsp application check Lunarwebhost jsp web hosting services

Bookmark the permalink.

Comments are closed.