Nice condescending tone.
I am an Exchange professional. I have been working on Exchange for 10 years now. Some of the company's I have worked for had thousands of users. I have never suffered any outages or viral outbreaks. My system is configured by the book and enhanced for our particular environment. This is my job. My server uptime is 99.99%. There are no performance bottle necks in the network, anywhere in the system, or the exchange application.
I wonder what levels of quotas you have set up for your users and how heavily they use their calendars, or if you had heard the complaints of Entourage 2004 not properly reading the updates received from other users. I wonder if your users have accepted use of OWA as a "check against" their Entourage client, which mine do not.
The biggest problem is in Calendaring. People generally make a meeting request, then perform up to 20 changes on the meeting before it actually happens.
The other problem is occasionally, Entourage refuses to connect to the Exchange server. Using tcpdump, there are no requests sent to the exchange server, but the Entourage client just spins "updating inbox"
I think the technical reason this is a problem is the fact that WebDAV was implemented in Exchange2000 with SP2, thus it was an add-on. I wonder if, since HTTP is the preferred protocol for delivery of information to client, Exchange 2003 would work better with Entourage 2004 and Outlook 2003, since both rely nearly exclusively on WebDAV and MAPI/RPC over HTTP, respectively, for communication to the server.
All of this is exacerbated by the Entourage 2004 client incorrectly interpreting some of the flags in the meeting request/update/cancellation messages. And its nominal. When using MAPI clients, such as Outlook 2001 for Macintosh or Outlook 2000 or 2002 for Windows, there are no problems, period.
The end problem is this: my Exchange server has a 99.99 uptime. However, the clients have only about a 90% success/reliability rating. This makes everyone believe there is a "server" problem when it is a systemic problem called "client software incompatibility".
ideas?
Robert Liebsch
Stone Yamashita Partners