A
adroitboy
Version: 2008
Operating System: Mac OS X 10.5 (Leopard)
Processor: Intel
Email Client: Exchange
Hello. I am trying to figure out what to do with our new setup of Entourage 2008 web services and Exchange 2007.
Previously we were using entourage 2008 12.2.0 and exchange 2003. All mailboxes were migrated to the 2007 server and things stopped working well. When we talked with MS Exchange support they highly recommended that we go with Entourage Web Services edition to alleviate some of the issues that we were experiencing with our new exchange server. So, it was done and most of the username/password issues went away, only to be traded for issues with exchange e-mail not being automatically received.
Here's what I know:
not everyone has the problem.
keychains are not an issue. They have the current password and are unlocked.
I've regenerated the database (out with the old and re-sync)
I've cleared the cache if I haven't completely recreated the database
I've recreated the keychain entries
There is no send/receive schedule selected (it's unchecked) in tools > schedules. I don't think this is required though.
User/password used (not kerberos) for login
Essentially the client will sometimes sync for a little whileafter app startup, then magically will stop. There are no errors and nothing to indicate that there might be an issue. When the send/receive is clicked, mail will come in, and usually not again until clicked again.
The messages do appear in OWA and in outlook, but EWS doesn't do a thing unless manually prodded.
for the mail server, we use mail.domain.com. EWS will autodiscover <https://mail.domain.com/EWS/Exchange.asmx> if allowed to. It doesn't seem to matter which is used. mail.domain.com serves all frontend/backend roles.
Any clues as to what to do? What sequence of events to troubleshoot/resolve should I take?
SERVER INFO
Outlook Web Access host address: <https://mail.domain.com/owa>
Outlook Web Access version: 8.1.393.1
Outlook Web Access host name: mail.domain.com
Client Access server name: MAIL.domain.com
Exchange Client Access server .NET Framework version: 2.0.50727.4016
Client Access server operating system version: Microsoft Windows NT 6.0.6002 Service Pack 2
Client Access server operating system language: en-US
Microsoft Exchange Client Access server version: 8.1.240.0
Client Access server language: en-US
Client Access server time zone: Pacific Standard Time
Microsoft Exchange Client Access server platform: 64bit
Mailbox server name: MAIL.domain.com
Mailbox server Microsoft Exchange version: 8.1.240.0
Other Microsoft Exchange server roles currently installed on the Client Access server: Mailbox, Hub Transport
Authentication type associated with this Outlook Web Access session: Basic
Public logon: Yes
Operating System: Mac OS X 10.5 (Leopard)
Processor: Intel
Email Client: Exchange
Hello. I am trying to figure out what to do with our new setup of Entourage 2008 web services and Exchange 2007.
Previously we were using entourage 2008 12.2.0 and exchange 2003. All mailboxes were migrated to the 2007 server and things stopped working well. When we talked with MS Exchange support they highly recommended that we go with Entourage Web Services edition to alleviate some of the issues that we were experiencing with our new exchange server. So, it was done and most of the username/password issues went away, only to be traded for issues with exchange e-mail not being automatically received.
Here's what I know:
not everyone has the problem.
keychains are not an issue. They have the current password and are unlocked.
I've regenerated the database (out with the old and re-sync)
I've cleared the cache if I haven't completely recreated the database
I've recreated the keychain entries
There is no send/receive schedule selected (it's unchecked) in tools > schedules. I don't think this is required though.
User/password used (not kerberos) for login
Essentially the client will sometimes sync for a little whileafter app startup, then magically will stop. There are no errors and nothing to indicate that there might be an issue. When the send/receive is clicked, mail will come in, and usually not again until clicked again.
The messages do appear in OWA and in outlook, but EWS doesn't do a thing unless manually prodded.
for the mail server, we use mail.domain.com. EWS will autodiscover <https://mail.domain.com/EWS/Exchange.asmx> if allowed to. It doesn't seem to matter which is used. mail.domain.com serves all frontend/backend roles.
Any clues as to what to do? What sequence of events to troubleshoot/resolve should I take?
SERVER INFO
Outlook Web Access host address: <https://mail.domain.com/owa>
Outlook Web Access version: 8.1.393.1
Outlook Web Access host name: mail.domain.com
Client Access server name: MAIL.domain.com
Exchange Client Access server .NET Framework version: 2.0.50727.4016
Client Access server operating system version: Microsoft Windows NT 6.0.6002 Service Pack 2
Client Access server operating system language: en-US
Microsoft Exchange Client Access server version: 8.1.240.0
Client Access server language: en-US
Client Access server time zone: Pacific Standard Time
Microsoft Exchange Client Access server platform: 64bit
Mailbox server name: MAIL.domain.com
Mailbox server Microsoft Exchange version: 8.1.240.0
Other Microsoft Exchange server roles currently installed on the Client Access server: Mailbox, Hub Transport
Authentication type associated with this Outlook Web Access session: Basic
Public logon: Yes