[Date Prev][Date Next]
RE: OpenLDAP + Microsoft Outlook
Thank you for your symopsis it's very interesting. I guess you are saying that a "show all" feature isn't available in LDAP support in Outlook.
The information you passed about improving performance via registry entries applies to LDAP software specialists interested in the MAPI protocols. Other areas of the registry can also can be tweaked for SUID's (in which, I think, OpenLDAP users have more of an interest.) But, it's always fascinating to gather information about open protocols supported by Windows. So, thanks :)
I'm a little confused by your wording which may have not been intentional. I thought you were saying that an LDAP client interface which would provide the functions of GAL is an imitation?
I'm confused because I always thought the Exchange Organization provided SDK's and specs for Exchange Client Extensions often referred to as third party addins. You can find the section in Outlook which helps users manage them under Tools|Options|Other. Nexor, a Microsoft partner, used to provide something called Messageware which is a LDAP client plugin I used to use with Outlook 97 and 2000.
Anyway, sorry that my search for "display all" in Microsoft LDAP Services for Outlook doesn't have registry entries that you know of.
Brian Arkills <email@example.com> wrote:
>> From: firstname.lastname@example.org [mailto:email@example.com]
>> Can "display all" be achieved in Microsoft's LDAP services
>> without clicking on find and then doing a search?
>I'm not exactly sure what you are asking here; 'MS LDAP services' is pretty vague ... but I'll take a shot. :)
>Outlook is primarily designed to work with Exchange, and Exchange 2000 (e2k) especially. Exchange 2000 is tightly integrated with MS' LDAP server, Active Directory (AD). Things like the "dynamic" definition of 'all mail-enabled users' (known as the global address list or GAL) are stored as an directory entry with an attribute that has a value of a search filter. An outlook user who is a member of the e2k organization uses these special entries to get their GAL, instead of the registry entry that was mentioned in an earlier post.
>From the client point of view, they simply click on the address book button (or several other places) and a GAL is instantly presented. In the background, that entry is being queried, then a second query with the search filter from that first entry, and the results are sent sorted back to the client. I'd guess that with the release of .NET server, this support might improve even more, because AD will support VLV.
>If you are looking to improve performance with an imitation, a similar approach (where you store the search filter on a directory entry) might be a good starting place. If anyone thinks it might be worthwhile, I can share a bit more detail on how e2k does this.
>Finally, I'm not sure if you are asking about other MS ldap-enabled clients or not ... but if you are, I can address that too. There are lots ... but only a few that are useful in a general sense.
>Windows Systems Group * Windows 2000 Infrastructure Project
>"Integrity has the power to build trust. Trust is what fuels a relationship."
> John Maxwell
>"The intelligent man is open to new ideas. In fact, he looks for them."
Your favorite stores, helpful shopping tools and great gift ideas. Experience the convenience of buying online with Shop@Netscape! http://shopnow.netscape.com/
Get your own FREE, personal Netscape Mail account today at http://webmail.netscape.com/