This Lab Kit builds a complete ConfigMgr Current Branch 2002, and ConfigMgr TP 2010, with Windows Server 2016 and SQL Server 2017 infrastructure, and some (optional) supporting servers. This kit is tested on both Hyper-V and VMware virtual platforms, but should really work on any virtualization platform that can boot from an ISO. The kit offers a complete setup of both a primary site server running ConfigMgr Current Branch 2002 (server CM01, as well as a primary site server running ConfigMgr Technical Preview Branch 2010 (server CM02). You also find guidance on upgrading current branch platform to the latest build.

Notes

Note #1 – Customizations: This hydration kit install all servers in the corp.viamonstra.com domain, on the 192.168.1.0/24 network. If you rather use your own domain, different IP addresses etc. check out the Next Step – Customizing the Hydration Kit section in the end of this post for instructions on how to customize this kit. Also, for a complete IP plan of the ViaMonstra network, check this link: https://viamonstra.com/ip-plan

Note #2 – Internal network and Internet Access: Since one of the virtual machines (DC01) is also a DHCP Server, its highly recommend to deploy all the virtual machines on an internal virtual network, and then use the NAT feature in either Hyper-V or VMware to give the virtual machines internet access. For super-easy Internet access on Hyper-V, while still having the VMs on an isolated network, read this shiny post from Ami Arwidmark (@AArwidmark):

Setting Up New Networking Features in Server 2016 (also works in 2019)
https://deploymentresearch.com/558/Setting-Up-New-Networking-Features-in-Server-2016.

Note #3 – Advanced networking: For more complex networks (multiple sites, bandwidth throttling etc.), you may want to use a virtual router. More info here:

Using a virtual router for your lab and test environment
https://deploymentresearch.com/285/Using-a-virtual-router-for-your-lab-and-test-environment

Hydration Kit For Windows Server 2016 and ConfigMgr Current / Technical Preview Branch

So, again, this Kit builds a complete ConfigMgr 2002, and an optional ConfigMgr TP 2010 site server, with Windows Server 2016 and SQL Server 2017 infrastructure, and some (optional) supporting servers

Servers

This kit allows you to automatically deploy the below list of servers. The only server you really need to build first is DC01, since that's the domain controller, and the CM01 server will join the domain. Turns out joining a domain is tricky without a domain controller 🙂

Main servers

• DC01. Windows Server 2016, DC, DHCP and DNS
• CM01. Windows Server 2016, SQL Server 2017 Standard, ConfigMgr Current Branch 2002, and MDT 8456

Optional supporting servers for ConfigMgr Technical Preview Branch, and MDT Lite Touch (reference image builds)

• CM02. Windows Server 2016, SQL Server 2017 Standard, ConfigMgr Current Branch Technical Preview 2010
• MDT01. Windows Server 2016, SQL Server 2017 Express
• WSUS01. Windows Server 2016, SQL Server 2017 Express

Overview

Shorthand, to build the virtual machines there are three steps you need to do:

1. Download the necessary software
2. Prepare the Hydration Environment
3. Deploy the virtual machines

Note: Detailed instructions are further down this page… see the Step-by-Step Guide section.

Step-by-Step Guide 

Step 1 – Download the software

On the machine (client or server) that you use to manage Hyper-V or VMware, create the C:\Setup folder.

For the main servers, you need to download the following software:

• The Hydration Kit
  sample files (download)   
• BGInfo: http://technet.microsoft.com/en-us/sysinternals/bginfo
  MDT 8456: http://www.microsoft.com/en-us/download/details.aspx?id=54259
• A reference image of Windows Server 2016 Standard, fully patched, and .NET Framework 3.5 added to it. If you don't have one, follow this guide to create one: https://deploymentresearch.com/578/Building-the-perfect-Windows-Server-2016-reference-image
• SQL Server 2017 Standard x64: https://www.microsoft.com/en-us/evalcenter/ or from VLSC, or MSDN if you have access to those.
• SQL Server Management Studio (separate download, not included in SQL Server 2017): https://aka.ms/ssmsfullsetup
• ConfigMgr 2002+ PreReqs: https://www.microsoft.com/en-us/evalcenter/ or from VLSC or MSDN if you have access to those.

  Note: To download the ConfigMgr pre-requisites, run the SMSSETUP\BIN\X64\Setupdl.exe application from the ConfigMgr installation files.   

• Windows ADK 10 v1903 and WinPE Addon for Windows ADK 10 v1903: https://docs.microsoft.com/en-us/windows-hardware/get-started/adk-install
  
  Note: To download the complete standalone Windows ADK 10 setup, run adksetup.exe /layout "C:\Setup\Windows ADK 10 v1903" for the core ADK, and then adkwinpesetup.exe /layout "C:\Setup\Windows ADK 10 v1903 WinPE Addon" for the WinPE Addon.

For the optional servers, you need to download the following software:

• SQL Server 2017 Express: https://www.microsoft.com/en-us/sql-server/sql-server-editions-express
  
  Note: Use the web installer to download the en_sql_server_2017_express_x64_11301593.exe media
• ConfigMgr 2010 Technical Preview + PreReqs: https://www.microsoft.com/en-us/evalcenter/evaluate-system-center-configuration-manager-and-endpoint-protection-technical-preview

  Note: To download the ConfigMgr pre-requisites, run the SMSSETUP\BIN\X64\Setupdl.exe application from the ConfigMgr installation files.         

Step 2 – Prepare the Hydration Environment

1. On the Windows machine that you use to manage Hyper-V or VMware, install Windows ADK 10 v1903 (adksetup.exe) selecting only the following components:

• Deployment Tools
• Imaging and Configuration Designer (ICD)
• Configuration Designer
• User State Migration Tool (USMT)

Note: The last three are not used by the hydration kit, but are still quite useful to have, so I usually install them too.  

2. Install Windows ADK 10 v1903 WinPE Addon (adkwinpesetup.exe) with the default settings.

3. Install MDT 8456 (MicrosoftDeploymentToolkit_x64.msi) with the default settings.

4. Extract the HydrationCMWS2016.zip sample file to C:.

Note: Please use 7-zip to extract the files so that time stamps on the files are kept correct, which helps troubleshooting (when using File Explorer to extract, it resets the time stamps to current date).

You should now have the following folder containing a few sub-folders and a PowerShell script: C:\HydrationCMWS2016\Source

5. In an elevated PowerShell command prompt, create the hydration deployment share by running the following command:   C:\HydrationCMWS2016\Source\CreateHydrationDeploymentShare.ps1

6. Open Deployment Workbench, and look around. You should see applications, operating systems, and task sequences etc.

Populate the hydration deployment share with the main server setup files

Next step is to start copying the various installation files to the correct folder.

1. Copy your Windows Server 2016 reference image (have to be named REFWS2016-001.wim, case sensitive), to the following folder: C:\HydrationCMWS2016\DS\Operating Systems\WS2016

2. Copy the BGInfo file (bginfo.exe) to the following folder: C:\HydrationCMWS2016\DS\Applications\Install – BGInfo\Source

3. Copy the full Windows ADK 10 v1903 setup files (1.1 GB) to the following folder:
C:\HydrationCMWS2016\DS\Applications\Install – Windows ADK 10\Source

4. Copy the Windows ADK 10 v1903 WinPE Addon setup files (2.8 GB) to the following folder:
C:\HydrationCMWS2016\DS\Applications\Install – WinPE Addon for Windows ADK 10\Source

5. Copy the SQL Server 2017 Standard x64 setup files (the content of the ISO, not the actual ISO) to the following folder:
C:\HydrationCMWS2016\DS\Applications\Install – SQL Server 2017\Source

6. Copy the SQL Server Management Studio setup file to the following folder:
C:\HydrationCMWS2016\DS\Applications\Install – SQL Server Management Studio

7. Copy the ConfigMgr 2002 setup files (extract the download) to the following folder:
C:\HydrationCMWS2016\DS\Applications\Install – ConfigMgr\Source

8. Copy the ConfigMgr 2002 PreReqs setup files to the following folder:
C:\HydrationCMWS2016\DS\Applications\Install – ConfigMgr\PreReqs

9. Copy the MDT 8456 setup file (MicrosoftDeploymentToolkit_x64.msi) to the following folder:
C:\HydrationCMWS2016\DS\Applications\Install – MDT

Populate the hydration deployment share with the optional files for CM02, MDT01 and WSUS01

Note: These steps are only needed if you want to deploy the optional CM02, MDT01, and WSUS01 virtual machines. If you don't want this, simply skip to the next section (Create the Hydration Kit ISO (MDT offline media item)

1. Copy the SQL Server 2017 Express setup file (SQLEXPR_x64_ENU.exe) to the following folder:
C:\HydrationCMWS2016\DS\Applications\Install – SQL Server 2017 Express\Source

Create the Hydration Kit ISO (MDT offline media item)

1. Using Deployment Workbench (available on the Start screen), expand Deployment Shares, and expand Hydration ConfigMgr.   
2. Review the various nodes. The Applications, Operating Systems and Task Sequences nodes should all have some content in them.   

1. Expand the Advanced Configuration node, and then select the Media node.   

2. In the right pane, right-click the MEDIA001 item, and select Update Media Content.

Note: The media update will take a while to run, a perfect time for a coffee break.

After the media update you will have a big ISO (HydrationCMWS2016.iso ) in the C:\HydrationCMWS2016\ISO folder. The HydrationCMWS2016.iso should be about 14-15 GB in size.

Step 3 – Deploy the virtual machines

All accounts, including Administrator, have a password of P@ssw0rd. If you want a PowerShell script that creates these VMs for Hyper-V, check the C:\HydrationCMWS2016\Source\Extra folder for a sample script.

Note: If using Hyper-V, do Not configure the virtual machines for dynamic memory. If you do, the installation will take forever. Dynamic memory can be enabled when installation (hydration) is completed.

Deploying DC01

Using Hyper-V Manager or VMware Workstation/Sphere, create a virtual machine with the following settings:

• Name: DC01
• CPU: 2 vCPU
• Hard drive: 100 GB (dynamic disk)
• Memory: 2 GB (static memory if using Hyper-V)
• Network: Your lab network
• Image file (ISO): C:\HydrationCMWS2016\ISO\HydrationCMWS2016.iso

1. Start the DC01 virtual machine. After booting from HydrationCMWS2016.iso , and after WinPE has loaded, select the DC01 task sequence.   
2. Wait until the setup is complete and you see the Hydration Complete message in the final summary.   
3. Leave DC01 running while deploying the CM01 virtual machine.

Deploying CM01

Once the domain controller (DC01) is up and running, you can deploy the CM01 virtual machine. Don't forget to leave DC01 running while deploying CM01 since it is joining the domain during deployment. Use the following settings for the CM01 virtual machine:

• Name: CM01
• CPU: 4 vCPU
• Hard drive: 300 GB (dynamic disk)
• Memory: 16 GB (static memory if using Hyper-V)
• Network: Your lab network
• Image file (ISO): C:\HydrationCMWS2016\ISO\HydrationCMWS2016.iso

Post configuration of CM01

After deploying CM01, make sure the machine has access to Internet. Again either via Configure NAT in Hyper-V or VMware, or by setting up a virtual router.

Then, in the Administration workspace, in the Updates and Servicing node. Click Check for Updates, and then install the latest updates available (currently ConfigMgr Current Branch v1906). Don't forget to do a final reboot after applying the updates, there is usually a pending reboot caused by the upgrade process.

Deploying CM02 (Optional)

Once the domain controller (DC01) is up and running, you can deploy the CM01 virtual machine. Don't forget to leave DC01 running while deploying CM02 since it is joining the domain during deployment. Use the following settings for the CM02 virtual machine:

• Name: CM02
• CPU: 4 vCPU
• Hard drive: 300 GB (dynamic disk)
• Memory: 16 GB (static memory if using Hyper-V)
• Network: Your lab network
• Image file (ISO): C:\HydrationCMWS2016\ISO\HydrationCMWS2016.iso Hard drive: 300 GB (dynamic disk)

Post configuration of CM02

After deploying CM02, make sure the machine has access to Internet. Again either via Configure NAT in Hyper-V or VMware, or by setting up a virtual router.

Then, in the Administration workspace, in the Updates and Servicing node. Click Check for Updates, and then install the latest technical preview. Currently 1909.

Deploying MDT01 (Optional)

Once the domain controller (DC01) is up and running, you can deploy the optional MDT01 virtual machine. Don't forget to leave DC01 running while deploying MDT01 since it is joining the domain during deployment. Use the following settings for the MDT01 virtual machine:

• Name: MDT01
• CPU: 2 vCPU
• Hard drive: 300 GB (dynamic disk)
• Memory: 4 GB (static memory if using Hyper-V)
• Network: Your lab network
• Image file (ISO): C:\HydrationCMWS2016\ISO\HydrationCMWS2016.iso

Deploying WSUS01 (Optional)

Once the domain controller (DC01) is up and running, you can deploy the optional WSUS01 virtual machine. Don't forget to leave DC01 running while deploying WSUS01 since it is joining the domain during deployment. Use the following settings for the WSUS01 virtual machine:

• Name: WSUS01
• CPU: 2 vCPU
• Hard drive: 300 GB (dynamic disk)
• Memory:84 GB (static memory if using Hyper-V)
• Network: Your lab network
• Image file (ISO): C:\HydrationCMWS2016\ISO\HydrationCMWS2016.iso

Next Step – Customizing the Hydration Kit:

Below is a quick walk through of items to change if you need to customize the kit.  For a broader scope, please see the post Customizing the ViaMonstra Hydration Kit.

If you need to change server names, IP addresses, domain names, installation, passwords, etc. in the environment, the main configuration is stored in the four .ini files in the C:\HydrationCMWS2016\ISO\Content\Deploy\Control folder.

Note: Again, by default, all accounts, including Administrator, have a password of P@ssw0rd.

For ConfigMgr (CM01) you need to update the following files::

• C:\HydrationCMWS2016\DS\Applications\Install – ConfigMgr\ConfigMgrUnattend.ini
• C:\HydrationCMWS2016\DS\Applications\Install – SQL Server 2017\ConfigurationFile\ConfigurationManager.ini

For ConfigMgr (CM02) you need to update the following files::

• C:\HydrationCMWS2016\DS\Applications\Install – ConfigMgr Technical Preview\ConfigMgrUnattend.ini
• C:\HydrationCMWS2016\DS\Applications\Install – SQL Server 2017\ConfigurationFile\ConfigurationManager.ini

If you need to change the various service accounts, you need to to modify the Configure-CreateADStructure.wsf script in the C:\HydrationCMWS2016\DS\Applications\
Configure – Create AD Structure folder.

If you change the Administrator password, and/or domain name, you also need to update the Authorize DHCP credentials in the DC01 task sequence.

Written by Johan Arwidmark