Invalid permissions in Exchange will lead to unexpected behavior when Synergy SKY tries to process meetings. If the Exchange service account does not have appropriate calendar access, you will see authorization errors in the log. If the room resources do not have the appropriate permissions and settings configured, the Synergy SKY Software will show undesired behavior. See the chart below for the most common permissions-related questions we receive.
Common Permissions Issues
Problem
Permission to check
Permission Function
No button on endpoint, logs show "no URI found in meeting", calendar entry for room is BLANK
DeleteComments=$false
Failure to set this to $false will cause Exchange remove the body of the invitation, making it impossible for JOIN to find meeting information in the body.
Meetings show the organizer name, but we want the meeting name displayed instead OR Meetings show the meeting name, but we want the organizer to be displayed instead OR We want meeting labels to show organizer & subject
These settings determine what is shown in the Subject line of the meeting. User preference, but these must be same($true or $false.)
if: AddOrganizer=$true Delete=$false then: subject will be organizer name only
if: Add=$false Delete=$false then: subject will be default
if: Add=$true Delete=$false then: subject will be default + organizer name
if: Add=$false Delete=$true then: meeting will have no subject and incorrect OBTP/OTD info can be sent to endpoints
Meetings from users outside domain aren't showing up on endpoints or receiving buttons
ProcessExternalMeetingMessages=$true
Failure to set this to $true will tell Exchange to ignore/not accept any meetings from outside your Exchange environment coming in to that room resource. Without the meeting being accepted, Synergy SKY will not move forward with the OBTP/OTD process.
Meetings flagged Private are displaying subject info on room touch-panel
RemovePrivateProperty=$false
Failure to set this to $false may make Synergy SKY send the subject of a private meeting as OBTP/OTD information to the video endpoint.
No button on endpoint or any entry in logs. Meeting shows in room calendar, but as 'tentative' or not yet accepted.
AutomateProcessing=$true
Failure to set this to $true will stop meetings from being processed, thereby hindering JOIN from seeing the meetings. Set to $false, every incoming meeting invite would have to be accepted by someone with access to the room mailbox. For some scenarios this is preferred (e.g. C-level private room managed by an assistant) but we always recommend this to be set to $true.
