Building a CM Lab – Gateway VM [2]

Series Post 2, Setting up the Gateway Virtual Machine, a virtual router

If we have a lab and we want to keep it separate from rest of our environment, we need a gateway. You can do this with a linux VM, another physical router, or several other options. For our lab, we decided to use Microsoft Windows Server to be our gateway. After setting this up, looking back, it would have been easier to setup the DC first, so I’d recommend doing that, then setting this up.

• Gateway Server
•  Name: GATEWAY.dev.recastsoftware.com
•  LAN 1: DHCP (External Network)
•  LAN 2: Static IP (Internal Lab Network) 192.168.1.1
•  Windows Roles: RAS [MS Docs]

At this point, I’ve installed Windows Server 2019, set the Name, the IP Address, ran MS Updates and installed the RAS Role by running a powershell commands: 

Install-WindowsFeature DirectAccess-VPN -IncludeManagementTools

Install-WindowsFeature Routing

Once that finishes, you can go ahead and setup the “Router” feature.

This is probably the easiest server you’ll be setting up. If you run into any issue, don’t worry, go ahead and setup the DC. Once you setup the DC, you need to remember to come back to the GATEWAY and join it to the domain.

‍

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

‍