Setting up a virtual SCCM testlab


This post is meant to guide you through setting up a simple, DIY, for your own use, test environment. This lab will be a simple Windows domain with SCCM and 1 client machine.

Everything will be setup using virtual machines on 1 single host. The example below assumes this will be done on your own workstation, but that does not have to be the case, and you can set this up remotely somewhere else as well.

This lab setup does not follow any sort of security best practices. This is meant to be a quick guide to setup a stand alone test lab environment, isolated from any other networks, accessed only by you on your own workstations. Security is of low priority here, in favour of speed and simplicity. Refine and harden security for a multi user accessible test lab environment!!

That said, lets get started.

The lab environment will consist of the following machines

  1. Windows 2016 Technical Preview – This will be the domain controller, SCCM Primary site server, database server and file server
  2. Windows 10 1511 Enterprise – This will be the test machine connected to the domain, used for most testing

We will use mostly Technical Preview items because they are free to get.

Expansion options to consider:

  1. Separate domain controller – recommended, if you have the RAM to spare.
  2. Technical workstation
  3. SCCM Central site

There is several things which needs to be downloaded first

  1. Windows Server 2016 ISO
  2. SCCM 1511 Installation installation
  3. SQL Server 2016 installation
  4. Windows 10 ISO
  5. Windows Deployment Toolkit Media

Downloading everything

In most cases, you will need to register with Microsoft to download the Server, SCCM and SQL installers. Once downloaded, you will also need to download some additional files for each installer.

ADK Setup Files

When you run ADKSetup.exe, you will be prompted to install or download the setup files needed. Choose to download to a location of your choice.


SCCM Updates

SCCM will also check for updates during install. You can predownload these files. Extract the SCCM iso to any location. Run the splash.hta file. Choose to get the latest CM updates.


When prompted, choose a download folder and click Download.


VM Setup

Today I’ll be using Oracle VirtualBox. You can also use Microsoft Hyper-V or VMWare Workstation, but VirtualBox is free. I do use VMWare Workstation at work, but it is not free (but you could use the free trial for a few weeks). Hyper-V is only available for Windows 8, 8.1 or 10 Professional and Enterprise version.

I noticed some weird network issues after installation VirtualBox and my networks adapters seemed to be bridged together. I’m still investigating this, and unsure if VirtualBox is the culprit.

Create 1 VM for Windows Server 2016 with at least 2GB of RAM allocated and 20GB of hard disk space allocated. Create 1 more VM for Windows 10 with at least 1GB of RAM allocated and 32GB of hard disk space allocated.

Set both VM Networks to Internal Only, joined to a network called “LabDomain”. You can use any other name you prefer here.


Start the Windows Server VM and proceed to install Windows Server, selecting the right setting (timezone, locale, etc). Select to install with the Desktop Experience.


Let the installation complete. At the end, you will be prompted to create an admin password. Choose your own password here, but remember what password you used. Once the login prompt appears, login as administrator. From the VirtualBox menu, select Devices, and choose Insert Guest Additions CD Image.


In your VM, open the DVD drive and run the setup. At end, do not reboot, but shutdown instead.

That’s it for now. In the next post, we will set up the DHCP and DNS names on the server, and create a new test lab domain.

Refer to other parts


Add a Comment

Your email address will not be published. Required fields are marked *