[cisco-voip] RE: CallManager Active Directory Issue
Mike Armstrong
mfa at crec.ifas.ufl.edu
Fri Oct 15 10:27:02 EDT 2004
Is there any possibility that the schema had already been extended? I would
suspect that a duplicate extension request would fail in some fashion, and
unfortunately the CCM message doesn't return much detail. You might also
look in the logs on the DC to see if there's any more detailed explanation
for the failures.
Mike Armstrong
UF/IFAS CREC
Date: Thu, 14 Oct 2004 16:44:24 -0400
From: "Yunming Song" <yunming.song at digiconasp.com>
Subject: [cisco-voip] CallManager Active Directory Issue
To: <cisco-voip at puck.nether.net>
Cc: Yunming Song <yunming.song at digiconasp.com>
Message-ID: <007e01c4b22e$972412e0$53851742 at digiconasp.com>
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
reply-type=original
Hi Group,
Under CallManager 3.3(4)sr2, we are installing Cisco Customer Directory
Configuration Plugin,
from Publisher server (MCS-7825), attempting to integrate with existing
Corporate Active Directory
generates the following errors:
"Failed to modify Active Directory Schema. Addition of attributes failed"
"Failed to modify Active Directory Schema. Addition of objectclasses failed"
"Failed to configure Active Directory. Addition of default containers and
profiles failed."
"... Addition of system userprofiles failed"
"... Addition of system users failed"
We have verified that we are connecting to the schema master for the domain,
using a Schema Admin
and Enterprise Admin account. The schema master shows significant cpu
activity just before the first
failure message is displayed on the Publisher server.
We have also verified the registry key
HKLM\System\CurrentControlSet\Services\NTDS\Parameters\Schema Update Allowed
is set on the Microsoft Active Directory Server to 1
Our A/D infrastructure consists of 4 domain controllers across 2 physical
locations. The schema master
is not located at the same location as the Publisher server from which we
are running
the Directory Configuration Plugin, however we are allowing all IP traffic
between the two locations
and have confirmed that the 2 servers are at least talking to each other.
Any input/idea is pretty much appreciated!
thanks a lot,
Yunming Song
Digicon Corporation
571-323-5030 (o)
yunming.song at digiconasp.com
More information about the cisco-voip
mailing list