Polycom 3725-76302-001O manual Active Directory Integration Procedure

Integrations with Other Systems

Field	Description
Conference directory attribute	The name of the Active Directory attribute that contains the conference
	passcodes. In choosing an attribute, remember that passcodes must be
	numeric.
	The attribute must be in the Active Directory schema and preferably should be
	replicated across the enterprise via the Global Catalog server mechanism. But
	if the attribute isn’t in the Global Catalog, the system queries each domain
	controller for the data.
	Leave this field blank if you don’t want the system to create conference
	passcodes for the enterprise users.
Maximum characters used	Desired length of conference passcodes. The Polycom RealPresence DMA
	system strips excess characters from the beginning, not the end. If you
	specify 7, the passcodes will contain the last 7 numeric characters from the
	Active Directory attribute being used.

See also:

Microsoft Active Directory® Integration on page 152

Active Directory Integration Procedure

Before performing the procedure below, read Set Up Security on page 34 and Connect to Microsoft Active Directory® on page 36. You should also have a good idea of how many enterprise users you expect the system to retrieve.

Note: Active Directory must trust the RealPresence DMA system certificate

Unless the Allow unencrypted connections to the Active Directory security option is enabled, the RealPresence DMA system offers the same SSL server certificate that it offers to browsers connecting to the system management interface. The Microsoft Active Directory server must be configured to trust the certificate authority.

To integrate with Active Directory

1In Windows Server, add the service account (read-only user account) that the Polycom RealPresence DMA system will use to read the Active Directory. Configure this account as follows:

User can’t change password.

Password never expires.

User can only access services on the domain controllers and cannot log in anywhere.

If you are integrating the RealPresence DMA system with Lync 2013 and plan to use the automatic conference contact creation feature, the service account you create here should have full permissions to add, change, and delete entries in the OU where the conference contacts are stored, along with full administrative permissions for Lync administration to manipulate these contacts.

Polycom, Inc. 157