Question : OWA and permissions for Shared Mailbox

I have Microsoft Exchange 2007 and i created a new shared mailbox and gave a group full access and a group read access.

When i use outlook to connect to the exchange server everything is good. My problem only exists when using OWA.

When i have my test user in the group with full access everything works fine. When i remove that user from the group and add it to the group with read access it cannot open the shared mailbox anymore (see error message below).

Error Message: "You do not have permission to open this mailbox. For access or for more information, contact technical support for your organization"

It also takes about 30 minutes for the permission to change in OWA while it is almost instant in Outlook 2007. Any ideas on why that would be? I thought the information is all coming from the CAS.

Thanks in advance!!

Answer : OWA and permissions for Shared Mailbox

Check this last part of this post, this should answer  your query.

http://exchangeshare.wordpress.com/2009/07/07/how-to-setup-read-only-mailbox-in-exchange-20032007/

Its pretty simple to add and open any mailbox in Outlook but how to open it in OWA? Reason is OWA requires Full Mailbox access to open full content of OWA site, otherwise it gives an error telling that you don’t have permission to access mailbox, so what you can do in Read-Only mailbox case?

Sometime back I discussed how to open shared calendar in OWA and user can use same method here to open “Inbox” of any read only mailbox.

User can use below direct links for respective folders and give their own user id and password to open it in OWA.

Inbox https://<FQDN of server>/owa/<smtpaddress>/?cmd=contents
Subfolder of Inbox https://<FQDN of server>/owa/<smtpaddress>/?cmd=contents&f=inbox%2fSubFolder
Calendar https://<FQDN of server>/owa/<smtpaddress>/?cmd=contents&module=calendar
Contacts https://<FQDN of server>/owa/<smtpaddress>/?cmd=contents&module=Contacts
Tasks https://<FQDN of server>/owa/<smtpaddress>/?cmd=contents&module=Tasks
Random Solutions  
 
programming4us programming4us