Harman RMBK-1001 - Problem (Exchange): Meeting Reservation Not Indicated on the Panel (no Error Message); Possible Solution; Creating a Service Account; Creating a Room Delegate

Appendix D: Troubleshooting
83
AMX RoomBook Scheduling Touch Panels - Instruction Manual
Problem (Exchange): Meeting Reservation Not Indicated on the Panel
(No Error Message)
When reserving a meeting (in Exchange), the meeting never shows up on the RoomBook Scheduling Panel, and the panel is not
indicating an error.
Possible Solution
The Exchange Administrator should create a Service Account and Room Delegate, and enable "Auto Accept" for meeting
reservations from RoomBook, as described below:
1) Creating a Service Account
This simply a user account. The following command creates the service account for the room:
New-Mailbox -Alias <alias> -Name <name> -FirstName <first> -LastName <last> -DisplayName <name> -
UserPrincipalName <UPN> -ResetPasswordOnNextLogon $false
2) Creating a Room Delegate
The following command creates the new mailbox for the room:
New-Mailbox -Name <name> -Alias <alias> -UserPrincipalName <UPN> -FirstName <first> -LastName <last>
-DisplayName <name> -Room}
The following command sets the various parameters for the previously created mailbox:
Set-CalendarProcessing -Identity <alias> -DeleteComments $false -DeleteSubject $false -
DeleteNonCalendarItems $false -AddOrganizerToSubject $false -TentativePendingApproval $false -
AutomateProcessing AutoAccept -AllowRecurringMeetings $true -BookingWindowInDays 1080 -
AllRequestOutOfPolicy $false -AddNewRequestsTentatively $false -ProcessExternalMeetingMessages $true
NOTE 1: In the case you want to set the ability to allow conflicting meeting requests to a room resource, you can use the
AllowConflicts parameter with the Set-CalendarProcessing command.
The AllowConflicts parameter specifies whether to allow conflicting meeting requests.
Valid input for this parameter is $true or $false. The default value is $false.
NOTE 2: In the scenario that you do not want the recurring meetings rejected when they have an end date beyond the booking
window; you will need to change the AllowConflicts parameter to $false.
When the AllowConflicts parameter is $true, a recurring meeting request is automatically declined if the meetings start on
or before the date specified by the BookingWindowInDays parameter, and the meetings extend beyond the specified date.
When the AllowConflicts parameter is $false, a recurring meeting request is automatically accepted if the meetings start on
or before the date specified by the BookingWindowInDays parameter, and the meetings extend beyond the specified date.
However, the number of meetings is reduced so meetings won't occur after the specified date.
When BookingWindowInDays is 0, an end date isn't enforced for any recurring meetings.
When BookingWindowInDays is greater than 0 and EnforceSchedulingHorizon is $true, the recurring meeting request is
automatically declined if the end date is greater that the value specified by BookingWindowInDays.
When BookingWindowInDays is greater than 0 and EnforceSchedulingHorizon is $false, the end date of a recurring meeting
is automatically truncated to the value specified by BookingWindowInDays. The following command will change the default
behavior:
Set-CalendarProcessing -Identity <alias> -BookingWindowInDays 181 -EnforceSchedulingHorizon $false
Conf iguring Delegation (Exchange 2010)
The following example illustrates configuring a delegate that can manage scheduling for the Room Mailbox:
1. In the Resource Policy tab of the mailbox Properties dialog, click Add
2. Select the user that will become a delegate of the Room Mailbox (FIG. 176):
FIG. 176
Mailbox Properties dialog - Resource Profiles tab