DMA OperationsGuide Microsoft Exchange Server Integration
180 Polycom, Inc.
Base:
<empty>
The base variable depends on the Base DN setting on the Microsoft
Active Directory page. If it’s set to the default, All Domains, the base
variable is empty, as shown. Otherwise, the base variable is the same as
Base DN. See “Understanding Base DN” on page 173.
Filter:
(&(objectCategory=person)(UserAccountControl:
1.2.840.113556.1.4.803:=512)(sAMAccountName=*)
(&(!(userAccountControl:1.2.840.113556.1.4.803:=2))
(sAMAccountName=<userID>)))
The first filter variable depends on the User LDAP filter setting. See
“Microsoft Active Directory Integration” on page163. The second variable
depends on the value entered in the Service account ID field on the
Microsoft Active Directory page. See “Microsoft Active Directory
Integration” on page 163.
Index used:
idx_objectCategory:32561:N
The search used this index in our testing environment, using a standard
AD configuration (no indexes added). Results may be different for a
different configuration, especially a different User LDAP filter setting.
Attributes returned:
sAMAccountName, userAccountControl,
givenName, sn
See also:
“Microsoft Active Directory Integration” on page163
“Microsoft Active Directory Page” on page165
“Active Directory Integration Procedure” on page169
“Understanding Base DN” on page 173
Microsoft Exchange Server Integration
On the Microsoft Exchange Server page, you can integrate the Polycom DMA
system with your Microsoft Exchange Server, enabling users who install the
Polycom Conferencing Add-in for Microsoft Outlook to set up Polycom
Conferencing meetings in Outlook.
When you integrate the DMA system with an Exchange server, it connects to
the Exchange server as the Polycom Conferencing user and subscribes to
notifications. The Exchange server notifies the DMA system as soon as a
meeting invitation (or other mail) arrives in the Polycom Conferencing user
inbox. It also sends heartbeat messages to verify that the subscription is
working.
If the DMA system fails to receive a heartbeat or other notification for
30 seconds, it begins checking its inbox every four minutes for new messages,
and also attempts to reestablish the subscription (push connection) each time.