Install SCCM Prerequisites Step-By-Step Guide

Introduction

I must point out firstly that i am going to install version 1606 which i managed to download using my Microsoft Imagine account, i do intend to upgrade to CB 1806 or possibly 1810 as this is the earliest version that supports Windows 10 1809 semi-annual Channel. I already have a VM setup in my environment which is a DC/AD DS and I am going to install SCCM on another Windows 2016 Server, after that i will host a Distribution Point on another VM so all-in-all i will have 3 Servers running. Before we actually install the SCCM Software on London (My intended SCCM Primary Site, MP and DP) there is a lot of configuration you need to have in place alongside installing various features on both your Primary Site and you DC/AD DS Server. This tutorial will hopefully guide you along the way as i have tried to take as many screenshots as possible, please feel free to let me know if you think i missed anything along the way but it worked for me so im very confident i covered all the basics. I will have covered the SQL 2016 Server install (a big prerequisite) in another post which you can find here since this one is going to be quite a big post. The prerequisites i am setting up are:

  • Install Windows ADK 10
  • Create System Management Container in the Domain Controller System
  • Extend Active Directory Scheme
  • Configure IIS Role
  • Install BITS and Differential Compression
  • Install Windows Server Update Service Role

Install Windows ADK 10 (On the intended Primary site)

  • Keep the defaults as shown and click Next
  • Click No, you can of course click yes if you like. Click Next
  • Click Accept
  • At this point you can just select the User State Migration Tool but there are a few features i personally wanted so i ticked a few more boxes. I left the Microsoft SQL Server express feature unticked as i already have SQL Server 2016 installed (My next post). Click Install

Create System Management Container in the Domain Controller System (NewYork VM in my case)

  • We now need to setup a Container called System Management using ADSI Edit and add specific users to the permissions too. Open up the Server Manager and click Tools>ADSI Edit
  • p.s ADSI Edit is essentially a low-level AD editor that lets you view, change, and delete AD objects and object attributes. In terms of usefulness and potential danger, ADSI Edit is to AD what regedit or regedt32 is to the system registry
  • Right click ADSI Edit and click Connect To
  • You can leave the defaults as shown and click OK
  • Your ADSI Edit window will look similar to this now
  • Maximise the Default naming context in the left window pane and create a new Object within the System Container under your relevant domain forest as shown below (Do not create this within the root directory)
  • Select Container from the drop down class menu and click Next
  • We are going to call this container System Management, click Next
  • Once your container has been created click Finish
  • The next step is to assign permissions to the newly created container, I previously created a domain admin account within my Blackwaterconfig Forest and a couple of local admin accounts on the SCCM Primary site
  • Click Add
  • Go to the Object Types which will open a new window, tick the box for Computers and click OK
  • Enter the name of your SCCM Primary Site Computer name and click OK.
  • Ensure you give full control for the newly added accounts, click Advanced
  • Click on the account(s) you just added under the permissions tab and click Edit
  • From the drop down menu shown below select This Object and all descedant objects (Double check all the boxes are ticked as shown) and click OK and this part is complete

Extend Active Directory Schema (On your AD Server)

  • If you go to the root of your system file you will notice a new Text Document called ExtADSch, open the file and as shown you should see confirmation the process has successfully completed

Configure IIS Role

  • Half way there now, just a few more features left to go through and one of which is to install and configure IIS on your intended Primary Site. As your primary site will be your Management Point (MP) and your Distribution Point (DP) you need an IIS Service otherwise it won’t work correctly
  • Firstly, click on Add Roles and Features from your server manager on your intended Primary Site
  • I would tick the box to skip this page by default as by now you probably know the score, click Next
  • Select Role-based or feature based installation and click Next
  • Select your Server from the pool and click Next
  • Click on Web Server (IIS), add the features and ensure you tick the box for the management tools too
  • Click Next
  • Click Next (nothing to add for the features section)
  • Click Next
  • Tick the boxes as shown below (The IIS6 WMI Compatibility is especially important as you will get an error during the SCCM Setup) Click Next
  • Double check your selections and click Install
  • Click Close once the selected features have been installed

Install BITS and Differential Compression

  • The Background Intelligent Transfer Service (BITS) Compact Server is a stand-alone HTTP/HTTPS file server that provides the ability to transfer a limited number of large files asynchronously between computers. The Compact Server is built as an NT Service and uses HTTP.SYS. This applies to the MP as you will receive error messages during the SCCM Setup if you don’t enable BITS.
  • Go to the Add Roles and Features option on your Server Manager and just click next on each window until you get to the Features window, select BITS and all relevant features but don’t click Next yet
  • Add the Remote Differential Compression feature and click Next
  • Click Install
  • Click on Close once complete

Install Windows Server Update Service Role

  • I plan to create a seperate post on the whole WSUS Install and Configuration but i’ll add it at this point without actually carrying out too much configuration just yet (we can do this once SCCM is installed and we add a SUP). I already have a SQL Server which i am due to document so ensure you have SQL installed and configured before you add this feature, if you don’t have SQL installed you can skip this section.
  • Go to the Add Roles and Features option on your Server Manager and just click next on each window until you get to the Server Roles window, select Windows Server Update Services (Especially important that you tick the box for SQL Server Connectivity).  You can’t install WID on the same server hence why i didn’t tick the box. Add the features once the window appears and then Click Next
  • There is nothing to add at this point so click Next
  • Take note of the information provided in this window and click Next
  • Enter the SQL Database instance you created and check the connection, click Next
  • Click Install
  • Note at this point that you have a message letting you know that you need to carry out Post-Installation Tasks, you can launch this but i plan to configure WSUS at a later point so click Close
  • The next Step is to install SCCM which i am covering in a future post, if you haven’t configuredf SQL then ensure you check my post here which will cover the last prerequisite. Please let me know if you have any comments or questions relating to this post and hopefully this will work for you.