Cisco Cisco Unified Contact Center Enterprise 9.0(1)
Introduction to Cisco Unified Contact Center Enterprise Release 9.0(1)
Release Notes for Cisco Unified Contact Center Enterprise Release 9.0(1)
Page | 3
Introduction to Cisco Unified Contact Center Enterprise
Release 9.0(1)
Release 9.0(1)
These release notes describe new features and changes for Release 9.0(1) of Unified Contact Center
Enterprise (Unified CCE) software.
Enterprise (Unified CCE) software.
Change History
This table lists changes made to this guide and gives the dates those changes were made.
Change
Date
Added new section Support for Windows Server
and Required Microsoft Hotfix for AD 2012.
and Required Microsoft Hotfix for AD 2012.
April 3, 2014
System Requirements
Note
For hardware and third-party software specifications for this release, see the
Software Specification (Bill of Materials) for Cisco Unified ICM/Contact Center Enterprise &
Hosted
Hosted
.
Supported Browser
Release 9.0(1) supports Microsoft Internet Explorer 9.
Support for Active Directory Windows Server 2012
Release 9.0(1) supports Active Directory on Windows Server 2012 R2 (64-bit). For details about Active
Directory support, see Staging Guide for Unified Contact Center Enterprise at
Directory support, see Staging Guide for Unified Contact Center Enterprise at
http://www.cisco.com/c/en/us/support/customer-collaboration/unified-contact-center-enterprise/products-
installation-guides-list.html
installation-guides-list.html
.
Required Microsoft Hotfix for AD 2012
If you have computers that run Windows Server 2008 R2 in a domain environment and you use a domain
user account to log on to a Windows Server 2012-based domain controller, you cannot map the following
security identifiers (SIDS):
user account to log on to a Windows Server 2012-based domain controller, you cannot map the following
security identifiers (SIDS):
S-1-18-1 Authentication authority asserted identity
S-1-18-2 Service asserted identity
Some applications such as the User Migration Tool use these SIDs and may fail.
To resolve this issue, install the hotfix on the Windows Server 2008 R2-based computers in the domain.
See
See