B
Burgess, Patrick
Good day everyone,
At our University, we have a 30% Apple client base, some of which use
Entourage 2008. One of the issues that we having deals with the Out of
Office assistant using Entourage 2008.
In our production environment, when we choose Out of Office form the Tools
menu, the applet times out while 'retrieving status' with a msgbox that
states: "Out of Office status is temporarily unavailable because Entourage
cannot connect to the server."
In our VM environment that our training department uses, it works just fine.
In both environments, all clients connect to the CAS server(s) via HTTPS.
There are major differences between the two.
Training environment has one A/D server and one Exchange server house the
CAS, HT, and MB roles. It has 10-20 people accessing during class times in
an A/D structure that has 5000 people entered.
The production environment has 6 CAS servers that people connect to via a
Cisco provided, load balancing, proxying service name. This load balancing
is 'sticky'. Most of our mailbox servers are clustered, although we have
tested in production with test accounts on non-clustered mailbox servers.
There are 48,000 mail account objects in the directory.
We believe we have ruled out performance issues on the mailbox servers and
we are working to move a CAS server out of the service name for isolation
there.
Any ideas?
At our University, we have a 30% Apple client base, some of which use
Entourage 2008. One of the issues that we having deals with the Out of
Office assistant using Entourage 2008.
In our production environment, when we choose Out of Office form the Tools
menu, the applet times out while 'retrieving status' with a msgbox that
states: "Out of Office status is temporarily unavailable because Entourage
cannot connect to the server."
In our VM environment that our training department uses, it works just fine.
In both environments, all clients connect to the CAS server(s) via HTTPS.
There are major differences between the two.
Training environment has one A/D server and one Exchange server house the
CAS, HT, and MB roles. It has 10-20 people accessing during class times in
an A/D structure that has 5000 people entered.
The production environment has 6 CAS servers that people connect to via a
Cisco provided, load balancing, proxying service name. This load balancing
is 'sticky'. Most of our mailbox servers are clustered, although we have
tested in production with test accounts on non-clustered mailbox servers.
There are 48,000 mail account objects in the directory.
We believe we have ruled out performance issues on the mailbox servers and
we are working to move a CAS server out of the service name for isolation
there.
Any ideas?