SCCM 2012 – ConfigMgr on a SQL 2008 R2 Named Instance 1

When you install ConfigMgr 2012 on a separate box with a separate SQL 2008 R2 Server in a named instance remember that ConfigMgr cannot handle Dynamic Ports used by SQL!

Furthermore note the prerequisites needed for SQL on a ConfigMgr installation:

  • A dedicated SQL server or Instance for each site with Configmgr 2012.
  • The instance of the SQL Server at each site must use the following collation: SQL_Latin1_General_CP1_CI_AS.
  • For SQL 2008 R2 SP1 Cumulative Update 6 is needed. (You can run the installer with CU4 actually..) NOT Supported though!
  • Set the memory requirements.

Microsoft SQL Server will only set and use the standard port TCP 1433 to the first Default Instance (MSSQLSERVER). The Instances installed afterwards get a dynamic chosen port.

Configmgr 2012 does not support dynamic port for SQL.


SQL ports can be set in the SQL Server Configuration Manager.
Select the name you choose to call the Instance. Then choose TCP/IP.
And for All the IP1, IP2, …   delete the TCP Dynamic Ports   (remove 0)   and set a port number you find appropriate for your environment.

Dynamic Ports:


 

Static Ports:


 

When SQL Service is restarted and firewall ports a opened we can start with the Configmgr Setup.

The SSB Port is the port you have chosen +1.

Based on the name of the Instance, Configmgr will detect the port configured automatically.

One comment on “SCCM 2012 – ConfigMgr on a SQL 2008 R2 Named Instance

  1. Reply John Apr 30,2014 4:09 pm

    Thanks. This article helped me

Leave a Reply

%d bloggers like this: