• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 446
  • Last Modified:

Allowing all users to reserve a conference room in OWA

I have Exchange 2010.  We have conference rooms setup as rooms in Exchange.  I want to allow all users to be able to schedule conference rooms through the Outlook Web Access.

I can view the schedule for the room and reserve it without Outlook.  But When I try to the same through OWA, I get the message "you do not have permission to perform this action"
0
gkotlin
Asked:
gkotlin
  • 5
  • 3
1 Solution
 
AmitIT ArchitectCommented:
That's strange. Can you setup a new test conf room and test it with OWA again. Make sure it is a room mailbox, not a normal mailbox. I guess current mailbox is also not a room mailbox.
0
 
gkotlinAuthor Commented:
I just created a new room.  It performs the same way.  I can schedule on it in Outlook, but not through OWA.
0
 
AmitIT ArchitectCommented:
Are you trying to open that as additional mailbox?
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
gkotlinAuthor Commented:
Open that?  What is that?

I go to the calendar for the room in OWA.  Click new to create a meeting or reservation and I get the error.
0
 
AmitIT ArchitectCommented:
can you run and post the result for below command.

Get-mailbox -identity roommailbox | fl
0
 
gkotlinAuthor Commented:
The operation couldn't be performed because object 'roommailbox' couldn't be found on 'myserver'
0
 
gkotlinAuthor Commented:
I figured it out.  I had to right click on the mailbox in the distribution groups list.  I selected manage full access permissions.  I added domain users to full access permissions.  Now all users can open the calendars and reserve rooms.
0
 
gkotlinAuthor Commented:
I was able to figure out that it must be a permissions issue since it worked one way, but not another.  I found where to manage permissions for the resource and added the users that need access.  It now works fine.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now