Polycom RealPresence Resource Manager System Operations Guide Configure the Connection to an External
14 Polycom, Inc.
The DNS should also have entries for your Active Directory server (if different
from the DNS).
To dynamically manage endpoints (which includes dynamic provisioning,
dynamic software update, and presence) right out-of-the-box, they must be
able to automatically discover the RealPresence Resource Manager system.
This means you must add the DNS service record (SRV record) for the
RealPresence Resource Manager system. The lookup key for this service
record is
_cmaconfig._tcp
. So the record will resemble this:
__cmaconfig._tcp.customerdomain.com 86400 IN SRV 0 0 443 Access5.customerdomain.com
For more information about DNS, DNS records, and how DNS works, see
Microsoft Technet
(http://technet.microsoft.com/en-us/library/cc772774(WS.10).aspx).
Configure the Connection to an External Enterprise
Directory
If during First Time Setup you did not configure your RealPresence Resource
Manager system to use an enterprise directory, but need to do so now, see
“Understanding Directories” on page 457.
Connecting to an enterprise directory allows users to enter their network
usernames and password to log into RealPresence Resource Manager system.
It also allows users to access the enterprise directory when selecting
conference participants.
Support of Multiple Provisioning Servers
The SRV record must point to the Provisioning Server (RealPresence Resource
Manager system) that endpoints will use for auto discovery for Dynamic
Provisioning. Two or more provisioning servers may co-reside on a network;
however only one may be used for DNS-based discovery of provisioning
services.
If more than one provisioning server is used within a environment there is no
knowledge or coordination between these environments including, but not
limited to:
• No shared directory services
• No shared management or provisioning services
• No shared scheduling
• No shared licenses
