B
Bill Bryson
The major issues we have here are:
1. When a person is moved from Exchange 2003 mailbox to Exchange 2007, if
Entourage e-mail setting for the user has a friendly email alias than the
Entourage client no longer can connect to an Exchange 2007 mailbox. No error
message is displayed - no new mail is retrievable. If the user tries to
send a message, he gets a -170 error message. Evidently for its own bizarre
reasons, Entourage/Exchange 2007 get the mailbox name from the email
address.
2. In the auto setup process, we get a server certificate warning for our
CAS server when trying to access an Exchange 2007 mailbox.
3. The Entourage auto setup process displays a warning that the Directory
server and Free/Busy server cannot be found. The Directory server field;
however, is filled in but the free/busy server is not being detected for an
Exchange 2007 mailbox at any phase.
4. The NETBIOS name can not be used as the domain for the auto setup process
(must use fully qualified IP name)
5. Ideally the Auto Setup process should return full qualified IP names and
the user's full name (as retrieved from the user's AD record),.
We are trying to transition from Exchange 2003 to Exchange 2007 but it
appears that the Entourage client must be modified to use a long server name
of "exchangeserver/exchange/user@domain" or the email field MUST contain the
mailbox id in it (no friendly email alias). If this friendly name is entered
in the email field in Entourage, connectivity is lost in Entourage to
Exchange 2007 for current users and the auto process setup is disrupted as
well.
Is it really the preferred solution that to access an Exchange 2007 mailbox,
that the Entourage client be updated to use an "Exchange server" field in
the format:
exchangeserver/exchange/user@domain
?
Bill
1. When a person is moved from Exchange 2003 mailbox to Exchange 2007, if
Entourage e-mail setting for the user has a friendly email alias than the
Entourage client no longer can connect to an Exchange 2007 mailbox. No error
message is displayed - no new mail is retrievable. If the user tries to
send a message, he gets a -170 error message. Evidently for its own bizarre
reasons, Entourage/Exchange 2007 get the mailbox name from the email
address.
2. In the auto setup process, we get a server certificate warning for our
CAS server when trying to access an Exchange 2007 mailbox.
3. The Entourage auto setup process displays a warning that the Directory
server and Free/Busy server cannot be found. The Directory server field;
however, is filled in but the free/busy server is not being detected for an
Exchange 2007 mailbox at any phase.
4. The NETBIOS name can not be used as the domain for the auto setup process
(must use fully qualified IP name)
5. Ideally the Auto Setup process should return full qualified IP names and
the user's full name (as retrieved from the user's AD record),.
We are trying to transition from Exchange 2003 to Exchange 2007 but it
appears that the Entourage client must be modified to use a long server name
of "exchangeserver/exchange/user@domain" or the email field MUST contain the
mailbox id in it (no friendly email alias). If this friendly name is entered
in the email field in Entourage, connectivity is lost in Entourage to
Exchange 2007 for current users and the auto process setup is disrupted as
well.
Is it really the preferred solution that to access an Exchange 2007 mailbox,
that the Entourage client be updated to use an "Exchange server" field in
the format:
exchangeserver/exchange/user@domain
?
Bill