This document provides
installation instructions for Unified CCE 11.6(1) ES34. It also contains a list
of Unified CCE issues resolved by this engineering special. Review all
installation information before installing the product. Failure to install this
engineering special as described can result in inconsistent Unified CCE
behavior.
This document contains
these sections:
In the Product Alert
Tool, you can set up profiles to receive email notification of new Field
Notices, Product Alerts, or End of Sale information for your selected products.
The Product
Alert Tool is available at https://www.cisco.com/cisco/support/notifications.html.
Below table illustrate supported Login formats
in CCE Webadmin and Websetup.
Login format are explained using below
user’s attributes.
User Details |
|
UserName |
|
Domain FQDN |
cce.local |
User's SAM Name |
C012345 |
DC's NetBios |
CSS |
Alternate Suffix available |
cce.com |
S.No. |
Login Format |
Supported in CCEAdmin |
Supported in Web setup |
1 |
Login in UPN format where UPN created with username@DomainFQDN Example:- john.kim@cce.local |
Yes |
Yes |
2 |
Login in UPN format where UPN created with username@ALTSuffix Example: -john.kim@cce.com |
Yes |
Yes |
3. |
Login in UPN format but with SAM@DomainFQDN. Example:- |
Yes |
Yes |
4. |
Login in UPN format but with SAM@NetBIOS Example:- C012345@CSS |
No |
Yes |
5. |
Login in NetBIOS format NetBIOS\SAM Example:- CSS\C012345 |
No |
Yes |
6. |
Login just SAM name Example :- C1012345 |
No |
Yes |
Note :- Login with SAM@AlternateSuffix is not supported. Login with alternate
suffix is only supported with UPN names when UPN is created with username@AlternateSuffix as mentioned in table above.
This section lists the
Unified CCE components on which you can and cannot install this engineering
special.
You can install Unified CCE
11.6(1) ES34 on these Unified CCE components:
Do not install this
engineering special on the following components other than:
1. Download
the CCE 11.6(1) ES34 from CCO.
2. Copy
the patch local to the server where it needs to be installed.
3. Stop
all UCCE application running in the UCCE Server.
4. Run
the Installer.
5. Reboot
the server after successful installation.
6. Start
all the UCCE services
1. Stop
all UCCE application running in the UCCE Server.
2. To
uninstall this patch, go to Control Panel. Select "Add or Remove
Programs". Find the installed patch in the list and select
"Remove".
3. Reboot
the server.
4. Start
all the UCCE services
Note: Remove patches in the reverse order of their installation. For example, if you installed patches 3, then 5, then 10 for a product, you must uninstall patches 10, 5, and 3, in that order, to remove the patches from that product.
This section provides a
list of significant Unified CCE defects resolved by this engineering special.
It contains these subsections:
Note: You can view more information on
and track individual Unified CCE defects using the Cisco Bug Search tool,
located at: https://bst.cloudapps.cisco.com/bugsearch/search?null.
This section lists caveats
specifically resolved by Unified CCE 11.6(1) ES34.
Caveats in this section are
ordered by UNIFIED CCE component, severity, and then identifier.
Identifier |
Severity |
Component |
Headline |
CSCvg54739 |
2 |
dbconfig |
CCEAdmin truncates the UPN FQDN |
CSCvg48617 |
2 |
security |
UCCE
- CCEAdmin - Multidomain
Forest - Alternate UPN login fails |
Caveats are ordered by
severity then defect number.
Defect Number: CSCvg48617
Component: security
Severity: 2
Headline: UCCE - CCEAdmin
- Multidomain Forest - Alternate UPN login fails
Symptom: CCE is deployed in a Multidomain forest. samAccountName
and userPrincipalName's User portion is different.
UPN defined for the forest is different from the Root Domain. Login to CCEAdmin fails using UPN.
Conditions: UPN format first.last@
Workaround:
Further Problem Description: Sadlib is making an incorrect assumption that
the username portion of the user's UPN (UserPrincipalName)
is the same as the user's SamAccountName. While it is
usually the case that the first 15 characters of the UPN user and samAcccountName are the same by default, either of these
change be changed independent of each other. An additional issue exists around
the use or Alternate UPN suffixes in credentials used for login to CCEAdmin. CCEAdmin incorrectly
truncated the UPN supplied by the user which would result in authentication
failure if that user was assigned an alternate UPN Suffix
Defect Number: CSCvg54739
Component: dbconfig
Severity: 2
Headline: CCEAdmin
truncates the UPN FQDN
Symptom: In multidomain
forest AD, user with alternate UPN suffix fails to login CCEAdmin
Conditions: User login with alternate UPN suffix
Workaround: None
Further Problem Description:
You can access current
Cisco documentation on the Support pages at the following sites:
To provide comments about
this document, send an email message to the following address:
contactcenterproducts_docfeedback@cisco.com
We appreciate your
comments.
Cisco.com is a starting
point for all technical assistance. Customers and partners can obtain
documentation, troubleshooting tips, and sample configurations from online
tools. For Cisco.com registered users, additional troubleshooting tools are
available from the TAC site.
Cisco.com provides a broad
range of features and services to help customers and partners streamline
business processes and improve productivity. Through Cisco.com, you can find
information about Cisco and our networking solutions, services, and programs.
You can also resolve technical issues with online technical support and
download software packages. Valuable online skill assessment, training, and
certification programs are also available.
Customers and partners can
self-register on Cisco.com to obtain additional personalized information and
services. Registered users can order products, check on the status of an order,
access technical support, and view benefits specific to their relationships
with Cisco.
The Cisco TAC site is
available to all customers who need technical assistance with a Cisco product
or technology that is under warranty or covered by a maintenance contract.
If you have a priority
level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to https://www.cisco.com/c/en/us/support/index.html.
P3 and P4 level problems
are defined as follows:
In each of the above cases,
use the Cisco TAC site to quickly find answers to your questions.
If you cannot resolve your
technical issue by using the TAC online resources, Cisco.com registered users
can open a case online by using the TAC Case Open tool at the following site: https://mycase.cloudapps.cisco.com/create/start/
If you have a priority
level 1(P1) or priority level 2 (P2) problem, contact TAC by telephone and
immediately open a case. To obtain a directory of toll-free numbers for your
country, go to the following sites:
P1 and P2 level problems
are defined as follows: