Is it possible to enter multiple LDAP servers in Entourage?

[limey]

My company uses Exchange 2007 with Windows 2003 on the server. Mac
clients run OS X with Entourage 2008. From all my research, I can
only see how to enter one domain controller. We have four DC's,
however. Is there any possible way in Entourage to enter multiple
DC's so that if the main one ever goes down, then users would still be
able to use the backup Exchange, etc. I would really appreciate any
help offered. If you need any more clairification, please let me
know.

Thanks in advance.

Colin

 

[Corentin Cras-Méneur]

My company uses Exchange 2007 with Windows 2003 on the server. Mac
clients run OS X with Entourage 2008. From all my research, I can
only see how to enter one domain controller. We have four DC's,
however. Is there any possible way in Entourage to enter multiple
DC's so that if the main one ever goes down, then users would still be
able to use the backup Exchange, etc. I would really appreciate any
help offered. If you need any more clairification, please let me
know.

You can enter as many LDAP servers as you want. They just won't be
associated with your e-mail account.
Tools>Account>Directory Service

There you can create independent LDAP account.

Corentin

 

[limey]

You can enter as many LDAP servers as you want. They just won't be
associated with your e-mail account.
Tools>Account>Directory Service

There you can create independent LDAP account.

Corentin

--
            --- Mac:MS MVP  http://www.cortig.net/wordpress/---
       http://www.mvps.org      -    http://mvp.support..microsoft.com
    MVPs are not MS employees    -    Les MVP ne travaillent pas pour MS
 Remove "NoSpam" to e-mail me    -      Retirez "NoSpam" pourm'écrire

So, not to sound snooty, but what is the point2 of that then? We have
a backup exchange server set up on another DC. If the primary DC with
Exchange goes down, we need a way to have it recognize the backup
one. I have added the additional LDAP servers in the directoy
utility, but need some redundancy for Exchange.

 

[Corentin Cras-Méneur]

So, not to sound snooty, but what is the point2 of that then?

Hey, I'm not a developper at MS. Don't ask me about the design of the
application ;-)

We have
a backup exchange server set up on another DC. If the primary DC with
Exchange goes down, we need a way to have it recognize the backup
one. I have added the additional LDAP servers in the directoy
utility, but need some redundancy for Exchange.

Not supported as such, but as I pointed out, you can enter the backup
server as an additional directory service and use it in case the first
one fails.

It won't be an automatic fallback, but it's at least a fairly decent
workaround as far as I am concerned.

Corentin

 

[limey]

Hey, I'm not a developper at MS. Don't ask me about the design of the
application ;-)


Not supported as such, but as I pointed out, you can enter the backup
server as an additional directory service and use it in case the first
one fails.

It won't be an automatic fallback, but it's at least a fairly decent
workaround as far as I am concerned.

Corentin

--
            --- Mac:MS MVP  http://www.cortig.net/wordpress/---
       http://www.mvps.org      -    http://mvp.support..microsoft.com
    MVPs are not MS employees    -    Les MVP ne travaillent pas pour MS
 Remove "NoSpam" to e-mail me    -      Retirez "NoSpam" pourm'écrire

Thanks for you replies. I appreciate the help.

 

[William Smith [MVP]]

So, not to sound snooty, but what is the point2 of that then? We have
a backup exchange server set up on another DC. If the primary DC with
Exchange goes down, we need a way to have it recognize the backup
one. I have added the additional LDAP servers in the directoy
utility, but need some redundancy for Exchange.

Your LDAP server is a global catalog server. These are required for
authentication or else your users will not be able to log in to their
computers. You'll be sure to keep at least one of these available on
your network for continued operation.

I suggest you create a DNS CName or alias and point it to your global
catalog server. Enter the CName as your Entourage LDAP server. If the
server goes down then point the CName to your backup global catalog server.

--

bill

Entourage Help Page <http://entourage.mvps.org/>
Entourage Help Blog <http://blog.entourage.mvps.org/>
YouTalk <http://nine.pairlist.net/mailman/listinfo/youtalk>
Twitter: follow <http://twitter.com/meck>

 

[limey]

YourLDAPserver is a global catalog server. These are required for
authentication or else your users will not be able to log in to their
computers. You'll be sure to keep at least one of these available on
your network for continued operation.

I suggest you create a DNS CName or alias and point it to your global
catalog server. Enter the CName as your EntourageLDAPserver. If the
server goes down then point the CName to your backup global catalog server.

--

bill

Entourage Help Page <http://entourage.mvps.org/>
Entourage Help Blog <http://blog.entourage.mvps.org/>
YouTalk <http://nine.pairlist.net/mailman/listinfo/youtalk>
Twitter: follow <http://twitter.com/meck>

I guess what I'm after though is to not have to manually change
information in Entourage in order for it to keep working if a domain
controller goes down. I don't want to have to manually configure 300
computers DC's from DC4 for example to DC1 in Entourage. There has to
be a way for Entourage to find the next available DC automatically.
Otherwise, this will be a real pain to configure the DC if it goes
down, then reconfigure it again when it is back online.

 

[William Smith [MVP]]

I guess what I'm after though is to not have to manually change
information in Entourage in order for it to keep working if a domain
controller goes down. I don't want to have to manually configure 300
computers DC's from DC4 for example to DC1 in Entourage. There has to
be a way for Entourage to find the next available DC automatically.
Otherwise, this will be a real pain to configure the DC if it goes
down, then reconfigure it again when it is back online.

If you use a CName then you don't have to change 300 machines. You only
have to change one DNS server.

You cannot configure Entourage with multiple server addresses. It's
simply not architected to let you do this.

Are you using Autodiscover in your Exchange environment? It's purpose is
to keep users connected when their accounts are moved to different
servers. I'm not sure, but it may also work to keep other server
information updated as well.

--

bill

Entourage Help Page <http://entourage.mvps.org/>
Entourage Help Blog <http://blog.entourage.mvps.org/>
YouTalk <http://nine.pairlist.net/mailman/listinfo/youtalk>
Twitter: follow <http://twitter.com/meck>