Blog
Sccm SQL 2017 Installation
Installation guide
Sccm SQL 2017 Installation : We will go through the complete SCCM SQL 2017 Install Guide to install and configure SQL before installing SCCM Current Branch 1806 or higher
- Execute Setup.exe from the SQL installation media, select New SQL server stand-alone installation
Important Info
Note that some steps in the wizard are automatically skipped when no action is required. For example, Products Updates, Install setup Files and Install Rules might be skipped.
Select the Database Engine feature and specify the SQL installation directory. This is the directory for the program files and shared features
INSTALL SQL SERVER MANAGEMENT STUDIO (SSMS)
· Back in the SQL Server Installation Center, click on Install SQL Server Management tools.
· Back in the SQL Server Installation Center, click on Install SQL Reporting Services.
At the time of this writing, the latest SQL Cumulative Update is CU17. We will install it in order to have an updated SQL Installation. Note that CU2 is the minimum requirement
· Download and execute SQL 2017 CU17
· Accept the license terms and click Next
SPN CREATION
When you configure SQL Server to use the local system account, a Service Principal Name (SPN) for the account is automatically created in Active Directory Domain Services. When the local system account is not in use, you must manually register the SPN for the SQL Server service account.
Since we are using a domain account, we must run the Setspn tool on a computer that resides in the domain of the SQL Server. It must use Domain Administrator credentials to run.
Run both commands to create the SPN, Change the server name and account name in each commands.
- setspn -A MSSQLSvc/yourservername:1433 yourdomain\SQLSA
- setspn -A MSSQLSvc/yourserver.fullfqdn.com:1433 yourdomain\SQLSA
To verify the domain user SPN is correctly registered, use the Setspn -L command
- setspn –L yourdomain\SQLSA
SQL CONFIGURATION
SCCM setup verifies that SQL Server reserves a minimum of 8 GB of memory for the primary site. To avoid, the warning, we’ll set the SQL Server memory limits to 8GB-12GB (80% of available RAM).
- Open SQL Server Management Studio
- Right click the top SQL Server instance node
- Select Properties
- In the Memory tab define a limit for the minimum and maximum server memory. Configure and limit the memory to 80% of your server available RAM. In my case I have 16GB available.
- Minimum 8192
Maximum 12288
DATABASE SIZING
We always recommend creating the SCCM database before the setup. This is not mandatory, SCCM will create the database for you during setup but will not create it the optimal way. We strongly recommend to watch The Top Ten Lessons Learned in Managing SQL session from MMS2013 which cover it all.
We follow the guide made by MVP, Kent Agerlund to estimate my DB sizing need. Visit his blog post and download the provided Excel file. Input your values in the blue cells and keep it for the next part. We’ll create the DB using those values using a script in the next section.
For this blog post, We’ve created a Database for 2000 clients, 2 processors, 2 cores and 16GB RAM.
To create the database, you can use Kent’s script and input your values (as returned previously in the Excel file) OR use the following one which is really simple:
The Name value will become your Site Code during the SCCM installation. Be sure to select a unique Site Code.
- **Replace all XXX value with your 3 character Site Code**
- **Change the values of the Filename, Size, MaxSize and FileGrowth. Change the location of the file to your SQL and Logs drives**
USE master
CREATEDATABASECM_XXX
ON
(NAME=CM_XXX_1,FILENAME='E:\SCCMDB\CM_XXX_1.mdf',SIZE=7560,MAXSIZE=Unlimited,FILEGROWTH=2495)
LOGON
(NAME=XXX_log,FILENAME='G:\SCCMLogs\CM_XXX.ldf',SIZE=4990,MAXSIZE=4990,FILEGROWTH=512)
ALTERDATABASECM_XXX
ADDFILE(NAME=CM_XXX_2,FILENAME='E:\SCCMDB\CM_XXX_2.mdf',SIZE=7560,MAXSIZE=Unlimited,FILEGROWTH=2495)
REVIEW THE SITE DATABASE PROPERTIES
- Open SQL Management Studio
- Right-click your DB, Select Properties
- In the General tab, verify that the SQL collation name is SQL_Latin1_General_CP1_CI_AS
· Verify that the file is located on your SQL Volume
· Change the database owner to SA. By default the owner will be the account that created the database.
· Open SQL Management Studio
· Right-click your DB, Select Delete
Run the following scripts to size the TempDB. (using the value returned by the Excel file)
**Change the values of Filename, Size, MaxSize and FileGrowth. Change the location of the file to your TempDB drives**
use mastergoalter database tempdb modify file (name='tempdev', filename='F:\SCCMTempDB\tempDB.MDF', SIZE= 4536, MAXSIZE = Unlimited, FILEGROWTH = 512)goalter database tempdb modify file (name='templog', filename='G:\SCCMLogs\templog.LDF', SIZE= 2268, MAXSIZE = Unlimited, FILEGROWTH = 512)goREVIEW THE TEMPDB PROPERTIES
- Open SQL Management Studio
- In System Database, Right click the TempDB, select Properties
- In the File Tab, verify that your database files has been created with the script value
- Ensure that the TempDB and log are on the TempDB volume
To ensure proper SQL communication, verify that settings are set accordingly in SQL Network configuration
· Open SQL Server Configuration Manager
· Go to SQL Server Network Configuration / Protocols for MSSQLServer
· On the Right Pane, right-click TCP/IP and select Properties
· In the Protocol tab
o Enable: YES
o Listen All : NO
· IP1 (which should have your Server IP)
o Active : YES
o Enabled : YES
· All other IP and IP ALL
o Active : YES
o Enabled : NO
o TCP Dynamic Ports : Blank value
o TCP Port : 1433
The server is now ready for the SCCM installation. We will now run the prerequisite checker and proceed to the complete SCCM Installation. We will install a stand-alone Primary site.
SCCM Training
Live Instructor-led Online Training
Click here for SCCM Course Content