Support Announcements for February 2013

Support Announcements for February 2013

  • Comments 4
  • Likes

We are announcing support changes for the following releases. These changes will be reflected in the Configuration Manager 2007 Supported Configurations and System Center 2012 Configuration Manager Supported Configurations within the next month.


Configuration Manager 2007 and System Center 2012 Configuration Manager Service Pack 1 now support Microsoft SQL Server 2012 SP1.

The following table lists the roles/features that are supported for each product with Microsoft SQL Server 2012 SP1.

Product

Roles / Features Supported

Configuration Manager 2007 SP2*

Site Database

Configuration Manager 2007 R3*

Reporting services point

Client status reporting

System Center 2012 Configuration Manager SP1

Site database

Secondary site database**


*For Configuration Manager 2007 SP2 and R3, hotfix KB2676776 http://support.microsoft.com/kb/2676776 is required.

** For a System Center 2012 Configuration Manager SP1 secondary site, you can use SQL Server 2012 SP1 or SQL Server Express 2012 SP1.

No software updates are required for System Center 2012 Configuration Manager SP1.

Note:  System Center 2012 Configuration Manager RTM (no service pack) does not support SQL Server 2012 or SQL Server 2012 SP1.


Forefront Endpoint Protection 2010 (FEP 2010) now supports SQL Server 2012 SP1.

Forefront Endpoint Protection 2010 now supports upgrading an existing Forefront Endpoint Protection database and reporting database to Microsoft SQL Server 2012 SP1.

To use SQL Server 2012 SP1 with Forefront Endpoint Protection 2010, you must upgrade the existing instance of SQL Server from SQL Server 2008, SQL Server 2008 R2 or SQL Server 2012. It is not supported to install new Forefront Endpoint Protection components on an existing or new instance of SQL Server 2012 or SQL Server 2012 SP1.

The following update is required to use Forefront Endpoint Protection with Microsoft SQL Server 2012 and 2012 SP1.

Forefront Endpoint Protection data warehouse and reports fail to get new data on SQL Server 2012 - http://support.microsoft.com/kb/2683558


System Center Security Monitoring Pack for Endpoint Protection now supports System Center 2012 Operations Manager SP1.

No software updates are required.

 

--Yvette O'Meally

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
  • Is CU2 for SQL Server 2012 SP1 supported as well or just SP1 no CU?

  • @Justin:  Short answer yes.

    Long answer:  We only publish support announcements for major releases and service packs of products we interoperate with as they can contain architectural and design changes that may affect the functionality of our products.  Certifying our products on those releases require significant test effort and may sometimes require updates to our products.

    Hotfixes and hotfix rollups/cumulative updates on the other hand are intended to be comparatively small contained bug fixes.  Installing a SQL CU would not make a Configuration Manager installation unsupported.

  • I installed SQL 2012 with SP1 Standard addition, making a named pipe called CONFIGMGR.  I then verified that TCP/IP connection was enabled and then turned on named pipe connections.  After rebooting, I started up the one service that was set to manual and verified that the other two services were running.  After all that, I could not get Configuration Manager 2012 SP1 to connect to the database.  In case it matters, I'm using a hyper-v 2012 server that is running Server 2012 Standard for the install.  I'm going to try again and let the CM installation wizard do whatever it wants to with 2008 SQL.

  • It seems my sin was to make my own instance rather than using the default instance.  CM SP1 is running on SQL 2012 SP1 not that I'm using the default instance of MSSQLSERVER.  I'm surprised by this as it actually has a blank in CM setup for you to put a particular instance name.