How can I install System Center Configuration Manager (Current Branch) version 1802 on Windows Server 2016 with SQL Server 2017 - Part 4

[anyweb]

This multi-part guide will show you how to install the latest  baseline version of Configuration Manager from Microsoft. The latest available baseline version is  System Center Configuration Manager (Current Branch) version 1802 as of March 29th 2018.

How can I install System Center Configuration Manager (Current Branch) version 1802 on Windows Server 2016 with SQL Server 2017 – Part 1
How can I install System Center Configuration Manager (Current Branch) version 1802 on Windows Server 2016 with SQL Server 2017 – Part 2
How can I install System Center Configuration Manager (Current Branch) version 1802 on Windows Server 2016 with SQL Server 2017 – Part 3
How can I install System Center Configuration Manager (Current Branch) version 1802 on Windows Server 2016 with SQL Server 2017 – Part 4

You can use this multi-part guide to get a hierarchy up and running on Windows Server 2016 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 using manual methods or automating it by 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 (if possible), using PowerShell.

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

In Part 1,  you configured Active Directory Domain Services (ADDS) on AD01, then joined the Configuration Manager primary server (CM01) to the newly created domain. You then created users, usergroups and OU's in Active Directory and created the System Management Container. Finally you delegated permission to the Configuration Manager server to the System Management container. In Part 2, you configured Windows Server 2016 roles and features on the Configuration Manager primary server (CM01) and then you downloaded and installed Windows ADK 1709. Next you installed SQL Server 2017 CU5 with SQL Server Management Studio (SSMS) and Reporting Services before installing the WSUS role which uses SQL to store the SUSDB instead of the Windows Internal Database (WID). In Part 3, you downloaded and extracted the ConfigMgr content, you downloaded the ConfigMgr prerequisites and then you extended the Active Directory schema before installing System Center Configuration Manager (Current Branch) version 1802.

In this part you'll create some device collections to prepare your lab for Servicing Windows 10, whether using WAAS or Upgrade Task Sequences built into ConfigMgr. The collections create include some based on the recently released Windows 10 version 1803.

Step 1. Create some device collections

Note: Perform the following on the Configuration Manager server (CM01) as a Local Administrator

You can create collections using the ConfigMgr console and clicking your way through the wizard, you'll need to add membership queries to populate the collections, and include Include or Exclude rules as appropriate.

Method #1 – Do it manually

<to be added>

Method #2 – Automate it with PowerShell

To automate the creation of a bunch of device collections simply run the CreateDeviceCollectionsWindows10.ps1 Powershell script by starting PowerShell ISE as Administrator on the ConfigMgr server (CM01).

Summary

In this guide you created a whole bunch of collections to sort all your Windows 10 computers into easily identifiable groups based on Windows Version number, so that you can target them with policy or use Upgrade task sequences or Windows Servicing.

Downloads

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

Scripts.zip

[kevlar01]

Thanks for this!

Note: it worked for me when I started Powershell ISE via the Configuration Manager Console.

http://eddiejackson.net/SCCM/sccm_ps_1.png

Running the 'regular' Powershell ISE didn't work for me.

 

[anyweb]

glad to hear it worked, what error did you get in PowerShell ISE as a matter of interest ?

[kevlar01]

The error was the following:

 

Starting script...
Import-Module : Cannot bind argument to parameter 'Name' because it is null.

Looks like it cannot use or import the Posh CM module or something....

[anyweb]

do you see any value in the registry key mentioned in the script ?

[kevlar01]

Checked the value in the registry, it does it exist.

However, it points to C:\Program Files\Microsoft Configuration Manager\AdminConsole.

This directory doesn't exist, so that may be the issue.

[anyweb]

more than likely yes

[jsemmelroth]

Thanks for the great series.

But I have wound up being not able to install agents on clients.  This is probably because clients can't access \\CM01\SMS_MPL\Client.  (MPL being my sitecode).  Can you recommend a document describing required permissions for this environment.  I assume I simply need to drop my users group into a local group on CM01 but some experimenting has brought no joy yet and I am loath to do anything with permissions I can't immediately back out of.