Building a CM Lab - ConfigMgr [MEMCM] Server Pre-Reqs [4]

Series Post 4, adding the pre-reqs for CM on your server

This is the big one, this is our MEMCM server, so much is happening to setup this server it's going to take a few posts. This post is covering some basics, and the pre-reqs, we'll move into SQL & the actual CM Install in up coming posts.


  • ConfigMgr Server - Current Branch
  •  Name:
  •  LAN 1: Static IP (Internal Lab Network)
  •   C Drive = 100GB (1 Virtual Disk)
  •   D Drive = 50GB (1 Virtual Disk) Used for SQL Database
  •  E Drive = 500GB (1 Virtual Disk) Used for DP Content \ Source Server
  •  Memory = 8GB
  •  CPU = 4 Cores
Drive Layout.  NO_SMS_ON_DRIVE.SMS on all drives except the drive that I'm planning to hold the CM Content.

The first thing I'm going to do is save myself a bunch of time and use SCConfigMgr's PreReq Tool to get my server ready. Because this is my lab server, I'm comfortable installing Microsoft Edge and using that to connect to the internet when I need to download things like this. I would not recommend this in production, and honeslty, once this is setup and I've created an "Admin Workstation", I'll probably remove it as I'll barely ever connect to the server again.

Once I launched the Tool, I installed the Primary Site Pre Reqs
Once this is completed, I go ahead and install the prereqs for the MP & DP roles
On this screen above, I choose Management Point and click Install, then when complete, I choose Distribution Point and click Install. For now, that's all I plan to setup in my lab, if you have additional roles you want to use, you can add the prereqs now.

Now using this tool, I'm going to extend the AD Schema. The Account I'm logged in with doesn't have this right, so I need to add an account that does.

Using the Directory / Schema tool, I have it detect my DC, then I browse to where I have the file.  I've mounted the ConfigMgr ISO as drive F. The tool then so nicely shows me where to browse to so I can connect to the required exe. I also then check the box to use the alternate credentials I created in the last step.

BUMMER... ok, so apparently trying to use an account with less privilege is just making it harder on me. New Plan, add my current account (CMAdmin) into Domain Admins while I do the CM Install, then take it back out.  I can do this, because it's a lab.... OR you can run this tool directly on the DC using the domain admin account that you used to setup DNS / DHCP. That might be easier still. Same steps, just done on the DC directly.
No Surprise there, making my account domain admin resolved the issue!... but still recommend just doing this on the DC instead of remotely from the CM Server.
Now we'll create the AD Container, avoiding the need to open ADSI Editor and do this manually.

Now I'm going to ad my configmgr_servers AD Group to the with full rights.
It says success, but can we trust it?
Yes, apparently we can. Everything is here.
So lets finish up the PreReqs with the ADK - You also have to choose the WinPE addon for 1903 !

ConfigMgr Support for ADK [MS Docs] More info about the ADK [MS Docs]

Alright, we've got our server in a good place for doing the next thing... setting up SQL.

Blog Post List

Series Introduction - Building a CM Lab from Scratch

  1. Domain Controller - Setting up your Domain Controller
  2. Gateway Virtual Machine - Creating a Router for your Lab using Windows Server
  3. Certificate Authority - On Domain Controller [Optional]
  4. ConfigMgr Server Pre-Reqs (Windows Features)
  5. Configuration Settings (AD & GPOs)
  6. Source Server (File Share)
  7. ConfigMgr SQL Install
  8. ConfigMgr Install
  9. ConfigMgr Basic Settings
  10. ConfigMgr Collections & App Deployment
  11. ConfigMgr OSD
  12. ConfigMgr Reporting Services