Resource mailboxes are specific types of mailboxes that can represent meeting rooms or shared equipment and can be included as resources in meeting requests.
The Active Directory user that is associated with a resource mailbox is a disabled account. The different types of resource mailboxes in Microsoft Exchange Server are: Room mailbox : a resource mailbox that is assigned to a meeting location, such as a conference room, auditorium, or training room. Room mailboxes can be included as resources in meeting requests.
Equipment mailbox : a resource mailbox that is assigned to a non-location specific resource, such as a portable computer projector, microphone, or a company car. Equipment mailboxes can be included as resources in meeting requests. Shared mailbox : a mailbox that is not primarily associated with a single user and is generally configured to allow logon access for multiple users.
After a shared mailbox is created by using the Exchange Management Shell , you must grant permissions to all users that require access to the shared mailbox. Even if this is not a resource mailbox, I mention it here because companies commonly use that kind of mailbox for collaboration or business needs.
You can configure resource mailbox properties for resource mailboxes. For example, you can use the ResourceCapacity, Office, and ResourceCustom parameters with the Set-Mailbox cmdlet to configure some of these settings. Custom resource properties can help users select the most appropriate room or equipment by providing additional information about the resource.
For example, you can create a custom property for room mailboxes called AV. You can add this property to all rooms that have audio-visual equipment. This allows users to identify which conference rooms have audio-visual equipment available. A custom resource cannot contain a value; it's only a flag that can be added to a resource mailbox, flags are defined globally for the Exchange organization. Before you can assign custom resource properties to a room or equipment mailbox, you must first create these properties by modifying the resource configuration of your Exchange organization.
Custom resource can be added with the Set-ResourceConfig cmdlet. Before explaining how to create the different types of room mailbox, we must focus on the settings that can be done with Set-MalboxCalendarSettings.
With this cmdlet you can configure many parameters on the resource mailbox maximum meeting duration allowed, default reminder time, etc The main parameter that interests us is AutomateProcessing which allows enabling or disabling calendar management on the resource mailbox. The three possible values are:. The AutoAccept value enables the resource booking policies to manage who can book the room and under what conditions. For each room mailbox, each user can be member of different policies: BookInPolicy : List of users who are allowed to submit in-policy meeting requests.
In-policy requests from these users will automatically be approved; RequestInPolicy : List of users who are allowed to submit in-policy meeting requests. In-policy requests from these users will be subject to approval by a delegate; RequestOutOfPolicy : List of users who are allowed to submit out-of-policy meeting requests. Out-of-policy requests from these users will be subject to approval by a delegate;.
In the context of resource mailboxes, InPolicy and OutOfPolicy simply mean whether or not the meeting invitation matches any restrictions enabled on the resource mailbox. To determine the value of the AutomateProcessing parameter, run the following command in the Exchange Management Shell. Additionally, this problem may occur if there is a corrupted delegate rule in the manager's mailbox.
Mailbox on Microsoft Exchange Server or an earlier version if you're using any version of Outlook to access the mailbox. Outlook or an earlier version if you're connecting to a mailbox on any version of Exchange Server. Or, someone who has mailbox rights must log on directly to the owner's mailbox and accept the meeting request.
Change the AutomateProcessing setting in the manager's Outlook profile, and then remove and restore the Outlook delegate or delegates :. On the Outlook File tab, select Options , and then select Mail. Under Tracking , clear the Automatically process meeting requests and responses to meeting requests and polls check box, and then select OK. Repeat step 1, select the Automatically process meeting requests and responses to meeting requests and polls check box, and then select OK.
On the File tab, select Account Settings. Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. Need more help? You can use any value that uniquely identifies the user or group. For example:. You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: "Value1","Value2", The Confirm switch specifies whether to show or hide the confirmation prompt.
How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. The ConflictPercentageAllowed parameter specifies the maximum percentage of meeting conflicts for new recurring meeting requests. The default value is 0. If a new recurring meeting request conflicts with existing reservations for the resource more than the percentage specified by this parameter, the recurring meeting request is automatically declined. When the value is 0, no conflicts are permitted for new recurring meeting requests.
The DeleteAttachments parameter specifies whether to remove attachments from all incoming messages. The DeleteComments parameter specifies whether to remove or keep any text in the message body of incoming meeting requests. The DeleteNonCalendarItems parameter specifies whether to remove or keep all non-calendar-related messages that are received by the resource mailbox.
The DeleteSubject parameter specifies whether to remove or keep the subject of incoming meeting requests. The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name FQDN. For example, dc The EnableResponseDetails parameter specifies whether to include the reasons for accepting or declining a meeting in the response email message.
The EnforceCapacity parameter specifies whether to restrict the number of attendees to the capacity of the workspace.
For example, if capacity is set to 10, then only 10 people can book the workspace. The EnforceSchedulingHorizon parameter controls the behavior of recurring meetings that extend beyond the date specified by the BookingWindowInDays parameter. The ForwardRequestsToDelegates parameter specifies whether to forward incoming meeting requests to the delegates that are configured for the resource mailbox.
The Identity parameter specifies the resource mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch. This switch enables the command to access Active Directory objects that aren't currently available in the default scope, but also introduces the following restrictions:.
A valid value is an integer from 0 through INT32 If a new recurring meeting request conflicts with existing reservations for the resource more than the number of times specified by the MaximumConflictInstances parameter value, the recurring meeting request is automatically declined.
The MaximumDurationInMinutes parameter specifies the maximum duration in minutes for meeting requests. Search related threads. Remove From My Forums. Asked by:. Archived Forums. Sign in to vote. Monday, October 26, PM.
0コメント