Now that we know how to check what prerequisites need to be installed or reviewed before installation begins, let’s go through each one and complete the prerequisite installation and configuration. I won’t go into to much detail on all of these, but just cover a basic setup to get you started.
Server Roles and Features
On the primary System Center server we need to install and configure a number of roles and features for SCCM to work, begin by navigating to server manager and add roles and features.
- Installation Type will be Role-based or feature installation
- Server Roles we want to select: Web Server (IIS), Windows Deployment Services, Windows Server Update Services (WSUS)
- Features we want to select: .Net Framework 3.5 Features, .Net Framework 4.7 + ASP.NET 4.7, Background Intelligent Transfer Service (BITS), Remote Differential Compression, IIS 6 WMI Compatibility
- Stick to the defaults for the rest of the Server Manager Wizard.
NOTE: It’s best practice to place the WSUS Content on it’s own drive. This will allow you to expand and manage the storage as necessary. We will also setup and configure WSUS in a later chapter, so for now you can ignore the configurations.
Windows 10 ADK
We need to download two components from the Microsoft Support page:
- Windows 10 ADK for your supported version windows
- Windows winPE Add-On for the ADK
Both can be downloaded from the Microsoft Support page.
Once you have downloaded both, install each one in order, followed by the default installation properties, unless you require additional features in the ADK during installation.
SQL Native Client
SQL Native Client will auto-install as part of the System Manager installation. Not configuration will be required for this, just note that the SQL Native Client won’t auto-update when you perform upgrades to System Center. You can download the matching SQL Native Client from Microsoft Support.
SQL Server Standalone
By default SCCM will used WID (Windows Internal Database) for database management, but for best practices it is always best to move the database to SQL management, and SCCM does come with a supported SQL License if its on the same box.
In normal circumstances due to the nature of SQL and Data-Protection, you will normally see SQL on it’s own box. But when it comes to SCCM, due to the load, O/I and the nature of the data, it’s best practice to have SQL on the same box as your Primary SCCM Server.
Download the latest SQL HERE.
You will require an Active Directory Service Account (follow your own service account naming conventions)
Service Account Name Permissions
svc_sccmsql Add to Local Administrator on the SQL server
Run SQL Server Installation Center as Administrator and select New SQL Server stand-alone installation.
Apply a license key if required and accept the license agreement.
SQL will run an installation check, and make sure all of them pass, the Windows Firewall can be an exception depending on requirements. Click Next.
Select Database Engine Service and set your directory. NOTE: It’s best practice to have your SQL Database and Logs on different drives. Click Next.
Leave the default instance name. You can create a named instance, but you will get errors during the SCCM installation “The specified SQL Server instance is not configured to use dynamic ports”. During this, you need to configure the TCP/IP properties of your SQL Server Configuration Manager.
Enter the domain SQL service account details for the Server Agent and Database Engine. Then click Collation and set the collation to SQL_Latin1_General_CP1_CI_AS
Add any additional SQL Administrators, in this case I am adding the AD Security group that contains my SQL Administrators.
Review and click INSTALL. The installation will take time depending on the speed and resources allocated to the VM/Server.
You should now have SQL Server 2017 installed on your SCCM Server. Click on Close to complete the setup.
Next go back to SQL Server Installation Center and install both the SQL Server Reporting Services and SQL Server Management Tools. Both can be installed using the default configurations.
SQL Memory Configuration
The next step is that we need to limit the SQL Memory, this is to make sure that SQL doesn’t utilise all our memory and leaves some for other stuff such as SCCM, WSUS, etc.
Run SQL Server Management Studio and login. Right click the server and select properties > Memory
Set the Minimum server memory and Maximum server memory accordingly, then click OK and Close SQL management studio.
NOTE: That the error will persist to show if you set lower than 8GB of memory for the minimum server memory allocation. For lab purposes I will be setting a minimum of 4GBs.
At this point, if we run the Prerequisite checker we should see that the only things reaming is that extend active directory schema and site server permissions.
The next step will be to extend the Active Directory Schema and set site server permissions before we proceed with the installation of our Primary Site.