Exchange/Office 365 Set Up
50
ACR-5100 Acendo Core Administrators Guide
Requirements
Exchange 2013 ServicePack1 or higher
Microsoft Documentation
The following links provide access to online Microsoft documentation regarding each of these methods for each supported Server
OS:
Configuring Exchange Room Mailboxes
The following flags attached to a Room's configuration control how meetings will appear on the Acendo Core. These flags can be
modified using the Exchange cmdlet Set-CalendarProcessing in an Exchange Management Powershell interface. These choices are
applied when a room is invited to a meeting from outside the Acendo Core unit.
Set-CalendarProcessing
parameters of particular significance:
AddOrganizerToSubject
- Controls whether the Acendo Core Service Account's First & Last name get added to meeting's
subject.
DeleteComments
- Controls whether the original Body is preserved.
DeleteSubject
- Controls whether the original Subject is preserved.
RemovePrivateProperty
- Controls whether a meeting's "Sensitivity" is preserved. This meeting property applies the same
functionality as "Privacy Mode" within Acendo Core (Please see page X).
Why Impersonation is Recommended for Exchange/Office 365
For Acendo Core, AMX recommends using a single user account, also known as credentials, with permissions to impersonate all
resources (rooms) that will be accessed by Core units. Acendo Core uses Microsoft's "streaming notifications" to subscribe to a
resource's calendar, and stay up to date with the calendar's status. This removes the need to poll continuously and is Microsoft's
own recommendation for applications such as this. For Exchange and Office 365, the server enforces limitations of access to help
prevent intentional and unintentional high traffic scenarios. This limitation is governed by tickets associated with each Mailbox or
Email Address. For example, Office 365 may only allow 10 tickets to be allocated per credentials, so only 10 end points can
subscribe to an accounts calendar at a time, making the 11th ticket receive reduced or no access. Impersonation allows us to move
which Mailbox a connection gets charged against, ultimately giving us more flexibility and less maintenance. With Impersonation,
the connection ticket is charged against the resource's allotment instead of the credential's. This allows all Rome units installed at
a site to use the same set of credentials, connect to a larger amount of resources, and not conflict with Microsoft's throttling
limitations.
Other configurations for credential to resource access include Full Access and Delegation. Full Access is the most common
configuration but each connection is charged against the credential's Mailbox, meaning every unit past the allotment will put
unnecessary strain on the server. Although Rome will do its best to communicate and stay up to date with a calendar's status, using
these configurations at any site greater than 10 units will result in Acendo Core reporting errors in communication. An installer
may choose other routes to get around these limitations such as credentials per group set, but we've found our recommendation is
the easiest to maintain when topology of a site changes.
Exchange 2013, Office 365
Exchange 2016, Office 365
Delegating Permissions:
http://technet.microsoft.com/en-us/library/jj215781%28v=exchg.150%29.aspx
(go to Create a room mailbox > Use the EAC to create a room mailbox)
Note: If you selected the option requiring that booking requests are sent to delegates,
use this section to select delegates.
• To add a delegate, click
Add
. On the Select Delegates page, select a user, click
Add
, and
then click
OK
to return to the New room mailbox page.
• To remove a delegate, select the user and then click Remove.
Assigning Full-Access Permissions:
http://technet.microsoft.com/en-us/library/jj919240%28v=exchg.150%29.aspx
Configuring Impersonation:
https://msdn.microsoft.com/en-us/library/office/dn722376(v=exchg.150).aspx
