Support Announcements for April 2014

Support Announcements for April 2014

  • Comments 6
  • Likes

Author:  Harini Muralidharan, Program Manager, Configuration Manager Sustained Engineering

System Center 2012 Configuration Manager SP1 and System Center 2012 R2 Configuration Manager support Microsoft SQL Server 2014 (upgrade):

Note:  This support statement has been updated here: 

http://blogs.technet.com/b/configmgrteam/archive/2015/03/30/updated-sc2012-configmgr-sp1-and-sc2012r2-configmgr-support-sql-server-2014.aspx 

System Center 2012 Configuration Manager SP1 and System Center 2012 R2 Configuration Manager now support upgrading an existing site database to Microsoft SQL Server 2014. 

The reporting services point site system and client status reporting feature are also supported with SQL Server 2014.

To use SQL Server 2014 for the site database, you must upgrade the instance of SQL Server to SQL Server 2014 in use at a site from one of the following versions:

  • SQL Server 2012
  • SQL Server 2008
  • SQL Server 2008 R2 

It is not supported to install a new Configuration Manager site with SQL Server 2014 installed.

The following software updates are required to use SQL Server 2014 to host the site database:

 Cumulative Update 1 for System Center 2012 R2 Configuration Manager -  http://support.microsoft.com/kb/2938441

 System Center 2012 Configuration Manager SP1 – http://support.microsoft.com/kb/2923078. To apply this hotfix, you must have Cumulative Update 4 (http://support.microsoft.com/kb/2922875)  for System Center 2012 Configuration Manager SP1 installed.

Known limitations:

Windows Server Update Services (WSUS) 3.2 Server cannot be installed on Windows Server 2008 R2 SP1 and Windows Server 2008 SP2 with SQL Server 2014 installed. With this configuration, the Configuration Manager Software updates feature will not work correctly.


System Center 2012 R2 Configuration Manager supports Microsoft Application Virtualization 5.0 SP2

System Center 2012 R2 Configuration Manager now supports Microsoft Application Virtualization (App-V) 5.0 SP2 Desktop Client and the Application Virtualization Client for Remote Desktop Services. This client release enables support for Windows 8.1 and Windows Server 2012 R2.

The following update is required –

Cumulative Update 1 for System Center 2012 R2 Configuration Manager - http://support.microsoft.com/kb/2938441


 -- Harini Muralidharan

 

Configuration Manager Resources

Documentation Library for System Center 2012 Configuration Manager

Configuration Manager 2012 Forums

System Center 2012 Configuration Manager Survival Guide

System Center Configuration Manager Support

This posting is provided "AS IS" with no warranties and confers no rights.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • nice job

  • Any word on support for SQL 2014 across the System Center suite?

  • Do you know if there is a workaround to Install an additional SMS Provider once you have upgraded your SQL 2014 instance? Seems to do the same checks on the SQL version as when you do a new installation of a site. Tried this on SCCM 2012 R2 and get the message telling you that a SQL upgrade is required.

    Thanks,

    Adam

  • You suck Microsoft - why don't your own products support the latest database?!!

  • Here's the problem with this "supportability" statement - If you want to run SQL 2014, you cant go upgrading the server from pre-SQL 2014 to SQL 2014 every time you want to move the database.
    I think someone hard coded the SQL versions in the installation routines without thinking that there might be SQL versions higher than 2012 some day. The product works just fine on SQL 2014, but the only way to get there is to sneak around the installation routine via an upgrade. Microsoft - just issue a hotfix that addresses the issue in the installation routines and make life simpler for all of us...

  • I was just following up on this blog to see if the SQL limitations were still there and I guess they are.

    I'd just like to voice that while this workaround to get on the latest SQL is nice for the stubborn ... it is not a viable solution for a production environment where we have to worry about recovery and maintenance. I just worked with a client last week who's site server crashed and we had to rebuild ... and if he were on SQL2014 (thankfully he wasn't) I would have had to install SQL _twice_ to get him up and running. Recovery and maintenance strategies are hit pretty hard by this work around to the point I'm better off telling clients "wait for REAL SQL2014 support..."