Jump to content


anyweb

How can I install System Center Configuration Manager (Current Branch) version 1902 on Windows Server 2019 with SQL Server 2017 - Part 1

Recommended Posts

Introduction

This multi-part guide will show you how to install the latest baseline version of Configuration Manager from Microsoft. The latest available baseline version at the time of writing is System Center Configuration Manager (Current Branch) version 1902. SCCM 1902 is the latest baseline version and contains many bugfixes (and quality fixes) as detailed here. I blogged how to upgrade to 1902 here. Baseline media is used to install new ConfigMgr sites or to upgrade from supported versions. For more information about what baseline versions are and why you need them, I'd recommend you read my blog post here.

This guide is aimed a new installations of SCCM. This lab is one of many hosted on my new hyper-v host, which is a very nice Lenovo P1 running Windows Server 2019 with data deduplication to make storage amazing.

Note: The SCCM 1902 Current Branch media is not yet available on MSDN or VLSC. When the new baseline media is released I'll update this note. In the meantime you can download the baseline media ISO from the Microsoft evaluation site here. This will be the same media that will make it's way to MSDN and VLSC. Once downloaded, extract the media to C:\Source\SCCM1902.

This series is broken down into the following parts:-

You can use this multi-part guide to get a hierarchy up and running on Windows Server 2019 using SQL Server 2017. The concept behind this is to guide you through all the steps necessary to get a working Configuration Manager Primary site installed (for lab use) using manual methods or automated using PowerShell. This gives you the power to automate the bits that you want to automate, while allowing you to manually do other tasks when needed. You decide which path to take. PowerShell knowledge is desired and dare I say required if you are in any way serious about Configuration Manager.

I will show you how to do most steps via two methods shown below, it's up to you to choose which method suits you best but I highly recommend automating everything that you can, using PowerShell.

  •         Method #1 - Do it manually
  •         Method #2 - Automate it with PowerShell

Downloads

The scripts used in this part of the guide are available for download here. Unzip to C:\Scripts. The scripts are placed in the corresponding folder (Part 1, Part 2 etc) and sorted into which server you should run the script on (DC01 or CM01).

Scripts.zip

Step 1. Get your lab ready

In this guide I assume you have already installed two WorkGroup joined servers with Windows Server 2019 Standard (Desktop Experience) installed. You can install the operating system on those servers in whatever way you want. If you want a PowerShell script to help you create hyper-v virtual machines you can use this one.

windows server 2019 desktop experience.png

Please configure the servers used in this guide as listed below, the SmoothWall (Linux firewall) is optional.

Server function: Domain Controller

  • Server name: DC01
  • Server info: Workgroup joined
  • IPv4 Address: 192.168.9.1
  • Subnet Mask: 255.255.255.0
  • Default Gateway: 192.168.9.199
  • DNS: 192.168.9.1

Server function: Configuration Manager Primary site

  • Server Name: CM01
  • Server info: Workgroup joined
  • IPv4 Address: 192.168.9.2
  • Subnet Mask: 255.255.255.0
  • Default Gateway: 192.168.9.199
  • DNS: 192.168.9.1

Server function: (optional) Linux firewall

  • Server name: smoothwall
  • Server info: Uses 2 legacy nics
  • eth0: 192.168.9.199
  • eth1: x.x.x.x (internet facing ip)

You will also need the following media.

  • Windows Server 2019 Standard
  • SQL Server 2017
  • System Center Configuration Manager 1902 Current Branch

Step 2. Configure Active Directory Domain Services (ADDS)

To setup Active Directory Domain Services you could manually click your way through the appropriate wizard in Server Manager or automate it using PowerShell. For your benefit I'll show you both methods below, all you have to do is choose which one suits you.

  • Method #1 - Do it manually

On the DC01, open Server Manager. Click on Add roles and features

add roles and features.PNG

On the Before You Begin screen click Next. For Installation Type select Role-based or Feature-based installation

role based or feature based installation.PNG

For Server Selection select Select a server from the server pool and choose DC01

server selection.PNG

For Server Roles select Active Directory Domain Services, when prompted to add features that are required for Active Directory Domain Services select Add Features

active directory domain services.PNG

select DHCP Server,when prompted to add features that are required for DHCP Server, accept the changes by clicking on Add Features

DHCP server.PNG

Select DNS Server, when prompted to add features that are required for DNS Server, accept the changes by clicking on Add Features

DNS server.PNG

Continue the the wizard by clicking Next

adds dhcp and dns selected.PNG

On the Features screen click Next

features.PNG

On the AD DS screen click Next

adds screen.PNG

On the DHCP server screen, click Next

dhcp server screen.PNG

On the DNS Server screen click Next

DNS server screen.PNG

On the Confirmation screen click Install

confirm installation selections.PNG

and then click on Close

installation progress close.PNG

 

Configure Post Deployment Configuration

After it's finished, perform the Post Deployment Configuration by clicking on Promote this server to a domain controller

post deployment configuration.PNG

select the Add a new forest option, give it a root domain name such as windowsnoob.lab.local

add a new forest.PNG

Next, depending on your requirements set the Forest functional level and Domain functional level, I've selected the default options below however you may want to configure it differently for your hierarchy,

For the password field use P@ssw0rd,

Domain controller options.PNG

Click Next when ready, for DNS options, click Next,

DNS options.PNG

Next verify the NetBIOS name and click Next

dns netbios name.PNG

To specify the location of the AD DS database, log files and so forth, either accept the defaults, or change them to something that suits your hierarchy and click Next.

ADDS paths.PNG

Next you can review the options (clicking view script will save your actions to a PowerShell script for use later if you wish). Click Next when done.

Review Options.PNG

Next, click Install to begin

Click Install to begin installation.PNG

Once it is complete making the changes it will automatically reboot the server

you are about to be signed out.PNG

After the reboot, open Server Manager again to do the Post-deployment Configuration for DHCP Server.

Post deployment configuration dhcp server.PNG

Click on Complete DHCP Configuration

dhcp config.PNG

use the defaults for DHCP Server Authorization

dhcp authorization.PNG

Click on Commit,

close dhcp server config.PNG

Click Close when done. That's how to configure ADDS and DHCP manually.

  • Method #2 - Automate it with PowerShell

To configure ADDS, DNS and DHCP automatically, use the ConfigureADDS.ps1 PowerShell script.

Note: I'd recommend that you reboot the server before running the script in case any pending operations like Windows Update are in progress as it may effect the results of the script below - I have not (yet) added in any detection for pending operations.

1. Copy the script to C:\scripts on DC01

2. Edit the variables in lines 17-32 as desired before running.

3. Start Windows PowerShell ISE as Administrator and run the script by clicking on the green triangle.

Once the script is run, it will automatically reboot the server, and after you logon, it will complete the DHCP server installation.

adds in progress.gif

Summary

Using PowerShell to automate things is the proper way to do things as a server admin. Please join me in Part 2 of this multi-part guide where you will continue setting up your new Windows Server 2019 lab with SCCM 1902 Current Branch.

 

Share this post


Link to post
Share on other sites


you are welcome !

 

Share this post


Link to post
Share on other sites

it's just a lab so I did as follows:- ConfigMgr will always eat lots of RAM, so the more you have available for it, the better.

  • CM01 = 16GB ram, 500gb hdd, 4x CPU, Hyper-v Gen 2
  • DC01 = 2GB ram, 128gb hdd, 4x CPU, Hyper-v Gen 2
  • Smoothwall = 256MBram, 128gb hdd,  Hyper-v Gen 1

Share this post


Link to post
Share on other sites

it works fine, you must be a logged in member of windows-noob.com to download the scripts, now that you are a member, please try again.

 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...