Deploying SCCM 2016 Current Branch – Part 2

Well Part 1 was pretty brutal and it only gets worse for you from here when installing SCCM, I may be a little cynical but I enjoy the configuration of SCCM more that the act of installing everything, I am far to impatient and it has never been an easy task to get SCCM ready for install.

So today we are going to tackle my least favourite task of getting the pre-requisites installed that being said I am also behind the scenes going to get it wrong (on purpose no less) to show you the error and how to fix it so that you don’t have to blow away the box and start again 🙂 .

So what’s been done so far

So if we look at Part 1 here we can see the list of the pre-requisites that need to be done. I have copied the list and struck through what we have done so far for your convenience

  • Setup x3 Service Accounts for SCCM SQL
  • Setup x3 Service Accounts for SCCM
  • Setup x2 Service Groups for SCCM
  • Install Windows Features for SCCM
  • Install SQL Server
  • Install SQL Server Management tools
  • Install SQL Server Reporting tools
  • Set Windows firewall rules up
  • Install (but not configure) WSUS
  • Add AD SCCM Container
  • Extend the AD Schema
  • Install ADK
  • Perform a Baseline AD Health Check
  • Perform a Pre-requisite Check before installing SCCM

So as you can see from the list above we have gotten through the bulk of it, we only have to install but not configure the WSUS service for SUP to work and sort out getting a SQL Database installed (if you don’t already have one).

The reason I have put both of these in part 2 is because SQL install can go wrong if you forget to set the language character set correctly, and I want to purposefully set this incorrectly to show you how to get out of it and save the day and many hours figuring out what you should do (or even a rebuild of the box).

For WSUS this is simply an install and not a full install at this point until we get into the configuration of the SUP service.

Installing WSUS

You must install the Windows server role Windows Server Update Services on a computer before installing a software update point.

  • Open Server Manager>Manage>Add Roles & Features
  • Tick Windows Server Update Services and Accept the default requirements
  • On the next page (features Page) ensure .Net Framework 3.5 and 4.6 have been enabled
  • As we are going to be using SQL Server you need to de-select the WID Connectivity and Enable the SQL Server Connectivity
  • At this point go to the location of where you would like to store the updates, create a folder on that drive called WSUS (or whatever you like) and then create a SubFolder called SCCMUpdates
    • Reason behind the folder is a known bug with NTFS security, if you don’t put the updates into a folder they will only see the security settings of the Drive, this makes WSUS and SUP synchronisation fail.
  • So now back to the setup and enter the location you have just created
  • Click install and wait for the installation to complete before moving on to install SQL, at this point DO NOT make any configuration changes to WSUS it will fail as you don’t have SQL installed.

This bit can take a while depending on your hardware, so goo for a coffee and by the time you get back it should be installed, just click close and get ready for SQL.

Installing SQL Server for SCCM

So I am not a Database guy, I have an appreciation and an understanding of them, I just don’t like doing them and this is why I either do them first thing or as the last thing before going and doing what I need to do.

That being said we are at this point and we need to get this installed, and I need to do it wrong as well, because I have done it wrong so many times over the last few years it is almost embarrassing to admit.

  • Mount the SQL Server install .iso on the SCCM Server (Windows is catching up with linux and Mac’s and can now mount .iso’s only took them the best part of 3 decades).
  • Launch from the .iso Setup.exe
  • This will bring up the SQL Server Installation Centre, from here on the right hand side click on Installation and then click on New SQL stand-alone Installation (top link)
  • On the first page the Product Key is normally filled in but if it isn’t then go ahead and fill this in (or specify a free edition)
  • Accept the license agreement on the next page and allow MS to update it (if you wish to do this as sometime MS updates can break things)
  • Allow it to download the latest updates (at this point it is clean so you may as well start with a fresh and updated SQL Server
  • It will then go and do the setup files and updates, before you get into the configuration
  • For some reason you will always get a warning regarding Windows firewall, this is OK as we have already done this in part 1.
  • On the next page we have to select the features that we need as well as set the drive Paths for the install, these are
    • Database Engine Services
    • Reporting Services – Native
    • Set the drives to your personal needs (mine will be on the S:\ Drive)
  • The next page you will need to set the Default Instance and the Instance ID or leave them as default (for Test you can leave for Prod change it to something meaningful)
  • On the first Configuration Page you are going to need the list of usernames and passwords you created in Part 1
    • The SVC_SQL_SA is the Server Agent Account
    • The SVC_SQL_DE is the Database Engine Account
    • The SVC_SQL_RS is the Reporting Services Account
  • Before you go off and click next click on the Tab called collation make sure this states SQL_Latin1_General_CP1_CI_AS, this is one of the ways I have gone wrong so many times
  • On the next page, select mixed mode Authentication and select at least one account to have unrestricted access to the Database Server (I prefer Groups for this).
  • For the next page, it will ask you if you want to setup and configure or just install SQL Reporting Services, at this point I select Install Only
  • This will then do its Checks and hopefully come back all green so that you can install SQL Server, if it doesn’t then you will need to resolve before being allowed to install.
  • Once complete close all windows, the next step is to install the SQL Server Management Tools.

Installing SQL Server Management Tools

Just when you thought you had completed the Sql configuration even more pops up, told you SQL wasn’t my favourite job.

So this used to be part of the Sql install and is now a download from Microsoft, bit now you will have to download it from here.

  • Once downloaded double click and it will bring up a window as below, click install (this can take a while so grab a coffee or paint a square on the wall and watch it dry).
  • Once complete click Close, you may need to restart at this point as well

Now we need to do a little configuration to ensure that the SQL doesn’t run away with all the memory 🙂 .

  • Open SMSS and connect to the local database
  • Once open right click on the Server Names database icon and select properties
  • Click on Memory in the new Window and then set the Memory Limits to 8Gb (you can set higher if you wish but 8Gb is the minimum)
  • click on and close SMSS

SQL Report Viewer

Report Viewer is required in order to view reports in SCCM. But to install Report Viewer, you may also be asked to install SQLClrTpyes.

To install Report Viewer and SQLClrTypes. Although SQL ClrType will be installed as part of SQL Server 2016 Management Studio installation.

If you decide to later, you might need to install Report Viewer after SQL Server 2016 installation

SQLClrType Install

You should still have the SQL Server Iso mounted you may as well get this little bit out of the way before installing SCCM

  • Mount the SQL ISO and navigaste to SQLSysClrTypes.msi
  • Agree and accept the Licence agreement 
  • Click install
  • Click finish to close the window

Install SQL Report Viewer

  • Navigate to the SQL ISO and find the ReportViewer.msi
  • Agree and accept the license agreement 
  • Click install
  • Click finish to close the window

SCCM Pre-requisite checks

So you have finally made it to the point where you are at the cusp of being able to install SCCM 2016 🙂 (how’s that paint drying?).

Now would be a good idea to run the pre-requisite check tool as well as an Active directory replication summary at the very least. I recommend a full Active Directory heath check at this point to ensure that everything is working as it should and that none of the work done so far has caused any significant issues with the Active Directory Domain Services. To initiate a Pre-requisite check you will need to follow the below steps with some caution.

  • Open PowerShell with elevated rights
  • Execute the following command
    • D:\SMSSETUP\BIN\X64\ prereqchk.exe /AdminUI”
  • This should open a window showing the results

If this result shows errors or warnings then you will be required to rectify these before proceeding with the SCCM setup procedure, however if this is a success result then you may proceed with the SCCM install.

If you are installing in production I would just ensure that DCDiag is run as well as a KCC on the domain to ensure everything is functioning as it should be, for this environment (it’s 3 brand new servers) it is not required, but highly recommended in a production install as this is where I normally find the skeletons in the closets of failed installs and other such goodness.

So we have reached the end of the Pre-requisites

Hopefully the paint has now dried that you have been watching so that we can get back to installing SCCM and all the fun stuff we like to do 🙂 . so in part 3 we are going to install the primary site and get it updated, depending on the length of the post we may do the configuration bits in Part 4. It is actually turning out to be a longer process than I remember and I only did this a few months ago in a live environment.

So your Pre-requisites check list should look like this;

  • Setup x3 Service Accounts for SCCM SQL
  • Setup x3 Service Accounts for SCCM
  • Setup x2 Service Groups for SCCM
  • Install Windows Features for SCCM
  • Install SQL Server
  • Install SQL Server Management tools
  • Install SQL Server Reporting tools
  • Set Windows firewall rules up
  • Install (but not configure) WSUS
  • Add AD SCCM Container
  • Extend the AD Schema
  • Install ADK
  • Perform a Baseline AD Health Check
  • Perform a Pre-requisite Check before installing SCCM

So I know Sarah is checking this for my Spelling and grammar, I know Sarah has little interest in this subject and so can you imagine how bored out of her skull she is right about now getting to this point.

Time to put a smile on her face and tell her that I love her 😉 .

Leave a comment

Your email address will not be published. Required fields are marked *

%d bloggers like this: