Unlike Jabber for Mac, Jabber for Windows uses the Active Directory connection of the computer, along with the logon credentials, to search for contacts in Jabber. Computers joined to the Kent domain will see all of the user’s information as reflected in Active Directory.
However, for those who see limited information in Jabber contact search results, this is likely to be caused by computers that are home/personally owned or KSU owned computers that are not joined to the Kent domain.
Because a Windows computer must be joined to the Kent domain in order to return complete results, an alternative method had to be implemented to allow non-domain joined machines to search the directory to at least provide an email address and phone number for all Jabber-enabled users.
In order to work around this, the Jabber for Windows installer was built to determine if a computer joined to the Kent domain. If it was not at the time of installation, a separate configuration file is created, which allows user searches to be done, but with basic results (Name, phone, email address).
1. The PC that Jabber is running on is not a KSU owned computer and/or is running a Home version of Windows. Because it is not joined to the Kent domain (or in the case of Home editions of Windows CANNOT be joined to a domain), the limited search results should be expected.
2. A KSU owned machine that is not joined to the Kent domain. Because it is not joined to the domain, the limited search results should be expected.
However, if the machine is joined to the domain and is still showing limited information during searches, it is likely that Jabber was installed BEFORE the computer was joined to the Kent domain and still contains the special configuration file. Please download the latest installer from http://support.kent.edu and re-install Jabber for Windows. It will identify that it is now joined to a domain and locate the special configuration file previously created and rename it.
3. A KSU machine that is joined to the Kent domain, but the user is logging on with local account credentials. Though the machine is joined to the domain, the logged on user is a local account, so it would not have the ability to search the domain via Jabber.
In this specific example, the search results should produce ZERO search results because the special confirmation file was not created during Jabber installation. To resolve this, the user must logon with domain credentials for the Jabber search to work properly.