C
Chuck Aikman
Well, I have made some progress, thanks to the many posts here. However,
there are some things still not very clear.
First off, saying to use your "Exchange server name" is not explicit enough.
We have an Exchange organization with over 27,000 mailboxes. We have:
8 mailbox servers
4 SMTP servers
2 IMAP servers
3 OWA servers
2 Public Folder Servers
4 Active Directory servers which are also GCs
Now, I realize that most orgs may not be this large or complex, but any of
you in multi server Exchange orgs might be unsure of which servers to point
to, as I was.
Yes, you must be running Exchange 2000 SP2 or later, as the installation
docs and help files state. This is for webDAV support, as many people have
pointed out. You also must have IMAP service enabled on your Exchange
environment, as also pointed out.
The auto setup wizard is useless if you have more than one server. It
detected my mailbox server, but that server does not allow IMAP connections,
or http/webDAV or LDAP.
So, from previous IMAP configurations, I knew enough to point to our IMAP
front end for inbound mail and to our SMTP mail POs for outbound. This is
like any other IMAP config you would do to get your mail --assuming you have
used IMAP before.
I've supported e-mail clients against Exchange for a few years, so I knew
free/busy data is stored in a hidden public folder. So, I knew I should
probably point to one of our PF servers, but wasn't real clear. After trial
and error, and the post from Gil and some follow-up posts (the tip about
Outlook 2003 beta connection status was the final key), I started trying
variations. Finally, this worked for free/busy server:
<public-folder-servername>/public
i.e.: myorg-pf01/public
I did not need a trailing '/' as indicated in another thread.
NOTE: We have two administrative groups in our Exchange org and one is
associated with PF server myorg-pf01 and the other with myorg-pf02. You MUST
use the public folder server associated with your mailbox store. This may be
something you have to find out from your Exchange Administrator(s).
If your OWA service requires SSL (and it should), then you need to check the
box for "DAV service requires secure connection (SSL)"
Once I had this, I could schedule meeting requests, invite others and see
their free/busy time. I also accepted meeting requests from others.
However, I can not get any Contacts or Calendar data to sync from my server.
New appointments and meetings accepted appear, but am I wrong to expect that
my already populated Exchange Calendar and Contacts should sync with
Entourage Calendar and Address Book? Can someone clarify for me? (My
Entourage Address Book & Calendar are empty, as I have not been using
Entourage as my primary client.)
As for GAL access, you should be able to setup one of your Active Directory
domain controllers or Global Catalog Servers as a Directory Server. You will
need to check the option for authentication, as I do not believe Active
Directory allows anonymous LDAP queries. (Exchange 5.5 does allow anonymous
LDAP queries - FYI).
This update to Entourage is the first Mac LDAP tool I have seen do
authenticated queries that actually work against Active Directory. So,
that's one of several small improvements that makes this update worthwhile.
I hope this summary helps. If someone could fill me in about Calendar &
Contacts data sync, that would be great!
Regards,
Chuck Aikman
there are some things still not very clear.
First off, saying to use your "Exchange server name" is not explicit enough.
We have an Exchange organization with over 27,000 mailboxes. We have:
8 mailbox servers
4 SMTP servers
2 IMAP servers
3 OWA servers
2 Public Folder Servers
4 Active Directory servers which are also GCs
Now, I realize that most orgs may not be this large or complex, but any of
you in multi server Exchange orgs might be unsure of which servers to point
to, as I was.
Yes, you must be running Exchange 2000 SP2 or later, as the installation
docs and help files state. This is for webDAV support, as many people have
pointed out. You also must have IMAP service enabled on your Exchange
environment, as also pointed out.
The auto setup wizard is useless if you have more than one server. It
detected my mailbox server, but that server does not allow IMAP connections,
or http/webDAV or LDAP.
So, from previous IMAP configurations, I knew enough to point to our IMAP
front end for inbound mail and to our SMTP mail POs for outbound. This is
like any other IMAP config you would do to get your mail --assuming you have
used IMAP before.
I've supported e-mail clients against Exchange for a few years, so I knew
free/busy data is stored in a hidden public folder. So, I knew I should
probably point to one of our PF servers, but wasn't real clear. After trial
and error, and the post from Gil and some follow-up posts (the tip about
Outlook 2003 beta connection status was the final key), I started trying
variations. Finally, this worked for free/busy server:
<public-folder-servername>/public
i.e.: myorg-pf01/public
I did not need a trailing '/' as indicated in another thread.
NOTE: We have two administrative groups in our Exchange org and one is
associated with PF server myorg-pf01 and the other with myorg-pf02. You MUST
use the public folder server associated with your mailbox store. This may be
something you have to find out from your Exchange Administrator(s).
If your OWA service requires SSL (and it should), then you need to check the
box for "DAV service requires secure connection (SSL)"
Once I had this, I could schedule meeting requests, invite others and see
their free/busy time. I also accepted meeting requests from others.
However, I can not get any Contacts or Calendar data to sync from my server.
New appointments and meetings accepted appear, but am I wrong to expect that
my already populated Exchange Calendar and Contacts should sync with
Entourage Calendar and Address Book? Can someone clarify for me? (My
Entourage Address Book & Calendar are empty, as I have not been using
Entourage as my primary client.)
As for GAL access, you should be able to setup one of your Active Directory
domain controllers or Global Catalog Servers as a Directory Server. You will
need to check the option for authentication, as I do not believe Active
Directory allows anonymous LDAP queries. (Exchange 5.5 does allow anonymous
LDAP queries - FYI).
This update to Entourage is the first Mac LDAP tool I have seen do
authenticated queries that actually work against Active Directory. So,
that's one of several small improvements that makes this update worthwhile.
I hope this summary helps. If someone could fill me in about Calendar &
Contacts data sync, that would be great!
Regards,
Chuck Aikman