Update Rollup 5 for Exchange 2007 SP1 (announced a few days ago) has been released. The rollup is available on the Download Center here:
http://www.microsoft.com/downloads/details.aspx?FamilyId=652ED...
Published Nov 21, 2008
Version 1.0
Blog Post
Odd problem that appeared after I installed this rollup just over 2 days ago. Two servers - CAS frontend, MB backend. Updated the CAS first.
Only ONE user (so far) has begun experiencing the generic HTTP 403 (access denied) errors, when using webmail or ActiveSync on his Windows Mobile phone. Refreshing the OWA session window or re-initiating an ActiveSync manually works fine. But initially he always gets this error.
As a side note, his account had long ago been a Domain Admin, and so when I first set up the Exchange 2007 server and moved his mailbox to it, I encountered the known problem with his Active Directory account not being set to inherit permissions, thus blocking him from using OWA at all. I corrected that at the time using ADUC, and it's still set correctly to inherit.
Has anyone seen this? Any ideas?
Only ONE user (so far) has begun experiencing the generic HTTP 403 (access denied) errors, when using webmail or ActiveSync on his Windows Mobile phone. Refreshing the OWA session window or re-initiating an ActiveSync manually works fine. But initially he always gets this error.
As a side note, his account had long ago been a Domain Admin, and so when I first set up the Exchange 2007 server and moved his mailbox to it, I encountered the known problem with his Active Directory account not being set to inherit permissions, thus blocking him from using OWA at all. I corrected that at the time using ADUC, and it's still set correctly to inherit.
Has anyone seen this? Any ideas?