Re: Fundamental Questions about Exchange Programming



Hello,

> 1) Is there a potential conlict between the ports used for LDAP by
> Exchange Server 2003 and Active Directory if BOTH are installed on the
> same machine?

Exchange 5.5 was the last version that had its own directory service. Since
Exchange 2000, the Active Directory is used. So, there is no conflict...

> 2) How does one go about resolving this (see #1) if this is the case?
Does not apply...

> 3) Does Exchange Server 2003 maintain its own store, or does it store
> user data (contacts, personal info, etc.) in Active Directory?

Active Directory.

> Also, there appears to be a somewhat confusing array of programming
> technologies for use against Exchange Server: MAPI, ADSI,
> System.DirectoryServices, LDAP, etc. and I'm trying to see how they all
> interconnect. System.DirectoryServices (in .Net) stands upon ADSI, but
> its documentation points mostly to it communicating with Active
> Directory. However, ADSI, apparently, can be used to talk to Exchange
> as well (as it is meant to be a generic interface to "directory
> services" in general) - so does the same go for
> System.DirectoryServices, can I program against Exchange with it? The
> communication to Exchange through these technologies appears to be
> through LDAP (at least one mode of communication) in that Exchange
> stores things in a directory service with an LDAP provider, but given
> that the Exchange Server I'm talking to (2003) exists on an Active
> Directory server, how do I know my LDAP queries are hitting the
> Exchange Server and not the Active Directory server?

You must distinguish between querying information about users and
information about public folders and private mailboxes. The first one is
queried with System.DirectoryServices. Extended MAPI could also work, but
I'm by no means an expert on ExMapi.

To query public folders and private mailboxes, you have several
possibilities.

For an overview about the support in .NET languages see this link:
http://support.microsoft.com/default.aspx?scid=kb;en-us;813349

In General: If your programs are running directly on the server, you can use
ExOleDB. If you are remote, you can use WebDAV. Extended MAPI is always an
option, but as I don't really know it, I can't recommend it. But according
to the link above, it is not supported in a .NET managed environment.

Hope this helps,
Henning Krause [MVP - Exchange]
==========================
Visit my website: http://www.infinitec.de
Try my free Exchange Explorer: Mistaya
(http://www.infinitec.de/software/mistaya.aspx)


<kwendex@xxxxxxxxx> wrote in message
news:1120317372.783095.316430@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> 1) Is there a potential conlict between the ports used for LDAP by
> Exchange Server 2003 and Active Directory if BOTH are installed on the
> same machine?
> 2) How does one go about resolving this (see #1) if this is the case?
> 3) Does Exchange Server 2003 maintain its own store, or does it store
> user data (contacts, personal info, etc.) in Active Directory?
>
> Also, there appears to be a somewhat confusing array of programming
> technologies for use against Exchange Server: MAPI, ADSI,
> System.DirectoryServices, LDAP, etc. and I'm trying to see how they all
> interconnect. System.DirectoryServices (in .Net) stands upon ADSI, but
> its documentation points mostly to it communicating with Active
> Directory. However, ADSI, apparently, can be used to talk to Exchange
> as well (as it is meant to be a generic interface to "directory
> services" in general) - so does the same go for
> System.DirectoryServices, can I program against Exchange with it? The
> communication to Exchange through these technologies appears to be
> through LDAP (at least one mode of communication) in that Exchange
> stores things in a directory service with an LDAP provider, but given
> that the Exchange Server I'm talking to (2003) exists on an Active
> Directory server, how do I know my LDAP queries are hitting the
> Exchange Server and not the Active Directory server?
>
> As you can tell, I have some fundamental questions here and I hope
> someone can clear my head on these topics. Thanks in advance,
>
> Ben
>


.



Relevant Pages

  • Re: DC communication problem
    ... Site in the Active Directory Sites and Services? ... > except the exchange server point to the local DC. ... > Can i force the PDC to answer first or what is wrong with my PDC??? ...
    (microsoft.public.win2000.active_directory)
  • Re: MSExchangeDSAccess, event 2114
    ... Have you recently changed Security settings, ... Is you Exchange server running ON your DC? ... What it looks like to me is that the computer can't access Active Directory ...
    (microsoft.public.exchange.admin)
  • Re: Exchange auf DC?
    ... MS nicht empfohlen ist Exchange auf einen DC zu installieren. ... Exchange Server and Active Directory are both resource-intensive applications. ... If Exchange Server is running on a domain controller, you must also make that domain controller a global catalog server. ... You should not take advantage of the /3GB startup switch in Windows because it could cause Exchange Server to consume all memory, thus reducing the memory available for Active Directory. ...
    (microsoft.public.de.exchange)
  • Re: Application Error
    ... LDAP admin limits imposed and isn't anything to worry about. ... show up when the Exchange server is rebooted? ... >>> make sure that the Exchange server is a member of the Exchange Domain ... > Technologies Inc.' #2112) ...
    (microsoft.public.exchange.admin)
  • Re: Degault global address book not updating
    ... If we are doing so and the template account has it set to ... 288807 Troubleshooting the Recipient Update Service in Exchange Server 2003 ... Microsoft Exchange Support ... > The end result of all this is that we're adding users in Active Directory ...
    (microsoft.public.exchange.admin)

Loading