The Homelab Series – Step 8: ConfigMgr Basic Settings 

Now that ConfigMgr is installed, we need to start configuring things so that it will work correctly. Here’s what we’ll work on:  

• Set up Hierarchy Settings 
• Discovery Settings (to find clients / users / groups) 
• Distribution Point Settings (and Distribution Point Groups) 
• Set up Boundaries 
• Set up Client Settings 
• Set up Accounts 

Hierarchy settings 

1. Go to Administration 
2. Click Site Configuration 
3. Click Hierarchy settings 

In the General tab I changed Consent to Use Pre-Release Features and de-selected Only Allow Console Extensions That Are Approved for the Hierarchy. 

In the Client Upgrade section, I selected Upgrade All Clients in the Hierarchy Using Production Client and changed to Update Clients within 1 Day. 

Discovery settings 

1. Go to Administration 
2. Click Hierarchy Configuration 
3. Click Discovery Methods 

I’m going to enable: 

• AD Group Discovery 
• AD System Discovery 
• AD User Discovery 
• Heartbeat Discovery 

Make sure to configure it so that it’s checking your domain for items. As the discovery runs, you will start to see the computers in your AD show up under Assets and Compliance > devices. 

Distribution point settings 

1. Navigate to Administration 
2. Click Site Configuration 
3. Click Servers and Site System Roles 
4. Choose Get Properties on the Distribution Point Role 

5. I enabled BranchCache and Windows LEDBAT. 

6. In the Communication tab I’ve enabled Allow Clients to Connect Anonymously. If you don’t have a Network Access account, you’ll need this. I am not going to install anything sensitive in my homelab, so I’m not too worried. 

7. With a DP you will want to add it to a DP Group. Click Distribution Point Groups on the left-hand side and then right click in the empty window and select Create Group. 

8. In the window that opens, you will need to enter a name for the group as well as click Add to create the Distribution Point Group. 

Boundaries and boundary groups 

1. Navigate to Hierarchy Configuration > Boundary Groups. You should see the Default-Site-Boundary, but it will not have any servers. Right click on the Default-Site-Boundary to edit the properties. 

2. Navigate to the References tab and click Add to add the CM server to the properties. 

3. Next navigate to Hierarchy Configuration > Boundaries. Right click on the empty window and select Create Boundary.  

4. Then create an IP Subnet boundary based on what you chose for your lab’s IP subnet. 

5. Then head back to the Boundary Groups section and add a new Boundary Group. Call it something like “Homelab” and add the boundary that was just created. 

6. Then in the References tab select Use This Boundary for Site Assignment and add the site system server as you did in the previous boundary. 

Client settings 

We aren’t going to add much here for our basic environment.  

1. I’ve changed the settings to Configure BranchCache, Enable BranchCache, Configure Client Cache Size, and increase the Maximum Cache Size. 

2. Under Computer Agent I also changed the Organization name displayed in Software Center and changed PowerShell execution policy to Bypass. 

That’s it for our basic configuration. Next let’s create some applications and set up a deployment. 

Next steps    

Make your homelab more powerful. Download our free tools to help you automate, troubleshoot, and validate configurations in your test environment.   

The Homelab Series

Homelab Introduction

The Homelab

Step 1: Creating a Domain Controller with DNS

Step 2: Adding a Certificate Authority

Step 3: Setting up a Gateway VM to Be Used as a Virtual Router (Optional)

Step 4: Configuration Manager Server Prerequisites

Step 5:  Settings for Active Directory and Group Policy

Step 6: Installing SQL For ConfigMgr

Step 7: ConfigMgr Install

Step 8: ConfigMgr Basic Settings

Step 9: Configuration Manager Collections and Application Deployments

Step 10: Installing SQL Server Reporting Services

Step 11: Cloud Management Gateway (CMG) Overview