Showing results for 
Search instead for 
Did you mean: 

CCE 12.0 now supported on Windows Server 2016


This is to announce the support for Windows Server 2016 and MS SQL server 2017 on CCE 12.0


This will cover UCCE, PCCE, ICM and HCS-CC solutions.


Operating System change:

- All Windows-based Enterprise components, including Router, Logger, AW/HDS/DDS, PGs, CVP, ECE, CCMP/CCDM now support Windows Server 2016 only


MS SQL server version change:

- CCE 12.0 AW, HDS/DDS and Logger now supports MS SQL Server 2017 only


No impact on:

ECE, CCMP/CCDM 12.0 will continue to run on MS SQL Server 2016 only

- CVP 12.0 will continue to run on Informix v12.10

- There are no changes in platform for VOS-based appliances such as Finesse, CUIC, VVB, IdS, Live Data



What happens to new customers?

All new CCE 12.0 orders will now get media that natively installs only on the updated platform.


What happens to existing customers?

Customers who have already ordered Release 12.0(1) have the following options:

  1. If you have already deployed (or are in advanced stages of deployment) CCE 12.0 on Windows Server 2012

- Cisco supports inline (common ground) upgrade of Windows and MS SQL server. For details, refer the detailed step-by-step procedure outlined at Reach out to Cisco TAC for support

- For new installs or upgrade orders placed till 12-July-2019, Cisco will continue to provide support till 31-July-2020 on the older platform (i.e. Windows Server 2012R2, SQL Server 2014). Reach out to your Cisco account team to get necessary support.


  1. If you haven't yet deployed or in early stage of planning

- You can obtain the new media for Windows Server 2016 by going to the PUT tool and requesting a 12.x to 12.x upgrade (with valid SWSS)

- Deploy the media directly on Windows Server 2016

- Link to PUT tool:


Note that Engineering Specials (and Maintenance Releases) on CCE 12.0 going forward will be based on the updated platform.


For additional details, refer to the updated CCE 12.0 Release Notes, Compatibility Matrix, and Install/Upgrade Guide.





Abhiram Kramadhati does this mean a customer is required to upgrade to Windows 2016 and SQL 2017 (depending on application) to get Cisco TAC Support?


I share the same concern as snagelipphone. The compatibility matrix has even been changed to remove support for Windows Server 2012. I upgraded a customer three weeks ago without issues, but now have serious concerns.

Archana Pandey

If we look at the compatibility Matrix it only speaks about Windows 2016 n Sql 2017 . And if you see at the Date of the Document its Jan 2019 .

Now my lab is build for 2012 without any issues . But we cant proceed with Production Upgrade to UccE 12 because 2012 support has been removed .

My concern is why is the date not updated on the compatibility matrix . Atleast it doesnt makes us engineer sound stupid that we overlooked this . When we know that 2012 support has just been ended . 

Cisco Employee

Yes, we have updated our compatibility for Release 12.0 with respect to Microsoft now support Windows Server 2016 (and SQL Server 17 for specific components) only – it was a deliberate, proactive decision in the long-term interest of our customers. We at Cisco are very conscious about taking the right decisions towards our end customers – we believe that if a customer hasn’t deployed to production yet, they’re better off directly jumping on Windows Server 2016 before they go to production. Otherwise, they’d have to anyway plan a maintenance window at a later point (which is far worse). Therefore, we’re saving the customer future pain.


We received strong field feedback over the past few months since we released v12 that it was imperative to support our newest major release on the latest Microsoft platforms - to be compliant towards IT policy of many large Enterprises. Microsoft Server 2012 R2 is already past end of mainstream support, and extended support for the same is already within sight. This was a problem, and we needed to ensure that our latest release would have a reasonable supported life, not restricted by the support cycle of our dependent platform.


To help make this transition in the least disruptive manner, we have ensured the following steps:

  1. There’s practically no internal app change, only installer changes (i.e. packaging). This means that all 3rd party integrations will work as-is (compared to previously-provided Release 12.0 on Windows Server 2012 R2). This greatly saves any potential re-testing.
  2. There’s a very simple inline OS/DB upgrade mechanism (as mentioned above) -> it can be very easily done in staging, rather than pushing out to production.

Does 12.0 ECE support installing SQL 2017 and running it in 2016 Compatibility mode?

Recognize Your Peers
Content for Community-Ad