In this case, the customer has a strict password policy and the password
was generated via an internal web app. Normally I would also not use one
that long!
On 2016-08-22 13:57, Anthony Holloway wrote:
Wow, good to know, but I cannot say that I have ever seen a password
that long on a server before. That's a first for me. I tend to still
use 8 character length. Old habit, I'm sure.
Are you consistently deploy 16+ character passwords now a days?
On Sun, Aug 21, 2016 at 5:54 PM, Daniel Ohnesorge via cisco-voip
<cisco-voip@puck.nether.net> wrote:
Hi All,
Just wanted to make you all aware of a serious installation defect
with 11.5 that the Cisco DE's are currently investigating and will
soon be raising a new defect against.
Basically, the CUCM Publisher installation goes ahead fine but once
you try to install any subscriber (including the CUPS DB PUB), the
installation will fail after all Network and Connectivity checks
passed. It has taken TAC, BU and DE's 2 weeks to figure out what was
going wrong, it turns out that the password used for the Application
User is too long (even though it is withing documentation guidelines).
The password I used was 1 Uppercase, 14 lowercase, 1 number and 1
special character (underscore). DE's have been able to replicate the
issue in the lab using the same complexity. When using a password such
as ipcbu123 the installation is successful. This affects CUCM, CUPS
and CUC.
Thanks,
Daniel
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip