[cisco-voip] Question regarding AD integration and corporatedirectories...
Voll, Scott
Scott.Voll at wesd.org
Fri Sep 15 13:10:32 EDT 2006
Really it's just so you don't have to use DC directory. We have the
plugin because it's on less username / password our users have to know.
IE> if you give them access to https://CM/ccmuser they can use there
domain username and password rather then DCD username/password.
Or
IPCCx agents can also use there Domain username/password.
Really, that's the only advantage I know of.
Scott
PS. No affect on Unity
________________________________
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Tim Reimers
Sent: Friday, September 15, 2006 9:55 AM
To: Cisco Voip
Subject: [cisco-voip] Question regarding AD integration and
corporatedirectories...
Regarding the plugin for AD for the CCMs- mentioned here:
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note0
9186a0080094493.shtml
<http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note
09186a0080094493.shtml>
What does this accomplish for CCM users?
Is it a 'free' option for a 4.01 non-Unifed Messaging environment?
I'm trying to figure out if I should ask my vendor to install this as an
OEM standard option,
and what effect it may have on my existing users on CCM and users on
Unity and the Corporate Directory that now exists.
I don't quite understand the difference between having this plugin
installed and the AD changes made,
versus using the internal CCM users?
I can only find Cisco's brief discussions, that don't really give a
'features' list of what extra capabilities you have with this installed,
that you don't have without it...
Tim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20060915/04f25830/attachment.html
More information about the cisco-voip
mailing list