Windows 2003 Support as LDAP for CCM

rkeblusek · ‎06-07-2003

Does anyone know if Windows 2003 is supported as the Cisco LDAP for CallManager? If so, any limitations/concerns? If there is a Cisco testing document link that would be very helpful. I have seen Unity is tested but nothing on CallManager at this point. We have a customer that would like this and would like to use Win2003 instead of the DC directory standard in CallManager.

jasyoung · ‎06-07-2003

I don't believe that Cisco has "officially" certified that CCM may be integrated with Windows 2003 Server's LDAP service. However, we do have at least one customer that we've integrated into Windows 2003 using both CCM 3.2(2c)-spH and 3.3(2)-spC. Obviously it's going to be certified at some point. You should seek TAC guidance to see if there are any known caveats, but I think it will work for you.

dugrant · ‎06-07-2003

There is one known issue when integrating with 2003, it is documented in CSCeb02371.

The problem will be fixed with the AD Plugin released in 3.3(3). This fix will only apply to new integrations with AD.

For customers that have already extended their schema CSCeb09099, which is currently unresolved, will provide a fix.

fmarotta · ‎11-04-2003

Is callmanager integration with Windows 2003 supported? If so is there a document that states this?

Thanks

Frank

pcresswell · ‎11-05-2003

This fix is now available from TAC. I have used it and it works, although it's quite long winded.

A few of our DCs are running 2003, and CCM the CCM LDAP plugin is using one of those. We haven't had any problems with it.

Peter

rkeblusek · ‎11-05-2003

Thank you, this is helpful information.

rkeblusek · ‎11-06-2003

Do you also know if this fix works with both Unity and IPCC Express? The customer in particular does have both in their environment.

pcresswell · ‎11-06-2003

I haven't used IPCC before but if it uses the same LDAP plugin as callmanager then it will work.

It's my understanding that Unity was not affected by that bug as it used AD through Exchange and so uses the LabeledURI attribute that is add during Exchange forestprep.

Peter

pcresswell · ‎11-06-2003

By the way for AD environments that have not yet had the Call Manager Plugin installed before, you have nothing to worry about as long as you use CCM 3.3(3).

If it's a new CCM deployment you can just use CCM 3.3(3) out of the box and it will work fine even if you are running Windows 2003 DCs.

Not sure if this is relevant to you, but I thought I'd point it out in case I had given you the impression that new deployments also require the ADpreptool.

Peter