EDIT: This post was edited on 11/28/2007 to mention KB944752.
The update is live at:
http://www.microsoft.com/downloads/details.aspx?FamilyId=41EC35E7-79A0-4ECB-A644-1ECE94178F9D&displaylang=en...
Updated Jul 01, 2019
Version 2.0
Blog Post
I still can't get the /exchange URL to work. Have any of you seen this?
As I indicated before, I have successfully removed UR5 from the CAS machine and also built a new one. I managed to remove UR5 from the CCR cluster but then noticed that it showed no updates, so I reinstalled UR4.
Still I cannot make the /exchange virtual directory come alive to allow the Entourage clients to connect.
I did discover a few interesting things along the way. When we first installed our environment we did not manually allow the WebDav Web Service Extension but Entourage still worked. Maybe it was enabled by default, though several articles I have found suggest that you will need to manually change it from ‘Prohibited’ to ‘Allowed’ in IIS. I have noticed that my CAS machine, that used to work to service the Entourage clients, now has this set to ‘Prohibited’ after installing and later removing UR5. I have set it back to ‘Allowed’ and restarted the machine, but the Entourage clients still can’t connect to Exchange.
As I indicated before, I have successfully removed UR5 from the CAS machine and also built a new one. I managed to remove UR5 from the CCR cluster but then noticed that it showed no updates, so I reinstalled UR4.
Still I cannot make the /exchange virtual directory come alive to allow the Entourage clients to connect.
I did discover a few interesting things along the way. When we first installed our environment we did not manually allow the WebDav Web Service Extension but Entourage still worked. Maybe it was enabled by default, though several articles I have found suggest that you will need to manually change it from ‘Prohibited’ to ‘Allowed’ in IIS. I have noticed that my CAS machine, that used to work to service the Entourage clients, now has this set to ‘Prohibited’ after installing and later removing UR5. I have set it back to ‘Allowed’ and restarted the machine, but the Entourage clients still can’t connect to Exchange.