Is there some documentation somewhere that documents what needs to be done
on the Exchange 2007 server side to have the correct parameters passed to
the Entourage client during its auto setup process?
As it stands now, the Mac client must be configured manually to have a
search list in the "Search DNS" box of the Network pane for this to even
have a chance at success. This is because the Exchange server returns only
partially qualified names (e.g. "matrix" and not "matrix.place.com").
Unfortunately, in our environment, the Exchange server returns the backend
server (where the mailbox resides) and not the front-end server name that
we
must manually change it to later.
This is quite frustrating to have an auto setup process that does not work
for our Exchange environment and evidently many others from the resources
I've found on the Internet.
I'm trying to determine if this is a mis-configuration on our server's
part
or whether it is just not happening because that is Microsoft's way.
The major issues we have here are:
1.Entourage cannot connect to an Exchange 2007 mailbox if the user
includes
an email alias in the email field. Evidently for its own bizarre reasons,
Entourage is getting the mailbox name from the email address rather then
query the AD using the user's credentials?
2. We get a server certificate warning for our CAS server.
3. The free/busy server is not being detected.
I'm recommending that the Entourage user use an email in the form of
username@[EMAIL PROTECTED]
to avoid the recommended solution of entering a
longer
and more complicated server name in the form of
"server/exchange/user@[EMAIL PROTECTED]
". How many other places are experiencing
this
problem because they allow for email alias? For example, here a user's
account is in the form of the initial of the person's name and a number
sequence such as wb99. The user can set up a friendly email alias of say
"billb@[EMAIL PROTECTED]
". If this friendly name is used in Entourage,
connectivity is lost in Entourage to Exchange 2007.
