02-13-2007 10:23 AM - edited 03-14-2019 12:31 AM
I have an IPCC 4.0.4 Installation integrated with Microsoft AD LDAP and it is failing due to the 20 character limitation.
CSCO:Tue Feb 13 13:11:54 2007:csco_eftn::StringIsValidId() in: hMsi=1511, str=IPCC-LDAP-Integration
CSCO:Tue Feb 13 13:11:54 2007:csco_eftn::StringIsValidId() out: nReturn=0, *bIsValid=0, sSuperset=0123456789abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ.<>:?/|`~!@$^&*()_-+#%{}[]
Does anyone know why it is limiting the LDAP profile name in UCCX 4.0.5 to 20 charcters? How should we handle legacy implementations?
02-14-2007 06:16 AM
Did you find the answer to this? I would open a TAC case on this one.
02-14-2007 06:23 AM
Not yet and I am hessitant to rename the profile in MSFT AD. I have not had time yet to open a TAC case.
02-14-2007 04:23 PM
Looking at the very latest release notes on CCO, UCCX 4.0(5a) addresses the upgrade issue with a cluster name greater than 20 characters.
Please rate useful posts.
02-14-2007 05:39 PM
Yep, after talking with TAC it looks like UCCX 4.0.5a started FCS shipping today.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide