IPCC 4.0.4 to 4.0.5 Upgrade

Unanswered Question
Feb 13th, 2007

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?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 3 (1 ratings)
Loading.
adignan Wed, 02/14/2007 - 06:16

Did you find the answer to this? I would open a TAC case on this one.

jmbuszta Wed, 02/14/2007 - 06:23

Not yet and I am hessitant to rename the profile in MSFT AD. I have not had time yet to open a TAC case.

mmelbourne Wed, 02/14/2007 - 16:23

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.

jmbuszta Wed, 02/14/2007 - 17:39

Yep, after talking with TAC it looks like UCCX 4.0.5a started FCS shipping today.

Actions

This Discussion