Table of Contents
Advertisement
Alert 6205
Cluster <cluster>: Failed to create/manage conference contacts in Active Directory; DMA
time is skewed from Active Directory's time.
The specified cluster has attempted to create or manage Active Directory conference contacts, and failed
because the system time differs between the RealPresence DMA system and the Active Directory system.
If possible, ensure that the RealPresence DMA system and your Active Directory system both use the same
NTP server.
Click the link to go to the Admin > Integrations > Microsoft Active Directory page.
See also:
Alerts
Alert 6206
Cluster <cluster>: Failed to create/manage conference contacts in Active Directory; DNS
cannot resolve the "<setting>", <FQDN>, configured at <page>.
The specified cluster has attempted to create or manage Active Directory conference contacts, and failed.
The cluster either cannot resolve the IP address or host name configured on the Admin > Integrations >
Microsoft Active Directory page, or the Next hop address configured for the specified SIP peer on the
Network > External SIP Peers page.
Go to the page specified in the alert, and verify that the configuration is correct. If so, verify your network's
DNS configuration.
Click the link to go to the page specified in the alert.
See also:
Alerts
Alert 6207
Cluster <cluster>: Failed to create/manage conference contacts in Active Directory;
invalid domain, user name, or password.
The specified cluster has attempted to create or manage Active Directory conference contacts, and failed
because the domain, user name, or password is incorrect on the Admin > Integrations > Microsoft Active
Directory page.
Click the link to go to the Admin > Integrations > Microsoft Active Directory page, and verify that the
Domain, Domain/user name, and Password fields are correct.
See also:
Alerts
Polycom, Inc.
System Management and Maintenance
377
Advertisement
Table of Contents
