System Center Configuration Manager requires a Microsoft SQL database to host all data related to clients that are being managed by the Management Server, in this post I will describe the process to SQL for Configuration Manager.
Configuration Manager SQL Installation
I assume you already installed the base OS where you will install Configuration Manager SQL database and that is been updated with latest security updates, in the lab for this post I will be using the following:
- Windows 2012 R2 with latest updates
- SQL Server 2012
- 16GB of total memory
Once the basic requirements are in place download an evaluation copy of SQL 2012 and lauch setup.exe so to begin installation and select New SQL Server Stand-alone installation or add features to an existing installation
Wait for SQL Setup Rules to run and if no errors are found on the system click on Ok and select Evaluation or input a product key if you have one
In the following page accept license terms and, if the server has an active internet connection let SQL Setup routine download updated files
Once updates for the setup routine have been installed just click on the install button and fix any issue reported by the Setup Support Rules, in the Setup Role select the SQL Server Feature Installation and click next
The only features which are required for Configuration Manager SQL Database are the Database Engine Services and SQL Reporting Services but I have also included Management Tools Basic and Complete to make database administration easier
SQL installation routine will take care of installing any necessary OS requisites as specified in the feature selection page.
In the instance configuration page select to install in a default instance and change installation paths as needed, leave instance ID name to its default value
In the Server Configuration page set SQL Services startup with the correct service accounts
[su_note note_color=”#ffff96″ text_color=”#000000″ radius=”5″]Note: In the above example I’ve left the SQL Service Accounts configuration to its default as this is a lab deployment, in a real world scenario dedicated accounts would have been configured.[/su_note]
[su_note note_color=”#ffff96″ text_color=”#000000″ radius=”5″]Note: It is essential that you select the correct SQL Collation as SCCM will not installed if the collation is anything but SQL_Latin1_General_CP1_CI_AS[/su_note]
In the Database Engine Configuration page be sure to add all needed user accounts to the SQL Server Administrators and in the Reporting Services Configuration simply leave all values to their default
Setup will ask if you want to enable Error Reporting and will be presented with a summary of installation parameters review them and wait for installation to complete
Once the setup is complete install any available updates and reboot the server before proceeding to install Configuration Manager.