Hydration Kit For Windows Server 2019, SQL Server 2017 and ConfigMgr Current Branch

This kit builds a complete ConfigMgr Current Branch 2103 infrastructure running on Windows Server 2019 and SQL Server 2017. This kit is tested on both Hyper-V and VMware virtual platforms, but should work fine on any virtualization platform that can boot from an ISO file.

Download Link: https://deploymentresearch.com/DRFiles/HydrationCMWS2019.zip

Notes

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. That being said, I recommend getting to know the kit using the default names if you can. For a complete IP plan of the ViaMonstra network, check this link: https://viamonstra.com/pages/ip-plan

Internal network and Internet Access: Since one of the virtual machines (DC01) is also a DHCP Server, its highly recommend to deploy 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):

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

Hydration Kit Archive: Are you looking for the previous hydration kit for Windows Server 2016? Look no further, it is right here:

Hydration Kit For Windows Server 2019 and ConfigMgr Current Branch

So, again, this Kit builds a complete ConfigMgr Current Branch 2103, with Windows Server 2019 and SQL Server 2017 infrastructure, and some supporting servers. Once the build is complete, I recommend that you use the native ConfigMgr servicing option to update to latest release or Hotfix if available.

Servers

This kit allows you to automatically deploy the below list of servers. The 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 2019, DC, DHCP and DNS
  • CM01. Windows Server 2019, SQL Server 2017, and ConfigMgr Current Branch

Optional supporting servers 

  • MDT01. Windows Server 2017, SQL Server 2017 Express, and MDT 8456

Setup Overview

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

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

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

The Deployment Wizard displaying the available task sequences.
The CM01 task sequence, building a complete ConfigMgr site server with SQL Server.

Step-by-Step Guides 

Step 1 – Download the software

On the Windows machine (client or server) that you use to manage Hyper-V or VMware, create a folder for all the software needed, for example C:\Setup.

Then, for the main servers (DC01 and CM01), you need to download the following software:

Note: To download the ConfigMgr prerequisites, you run the \SMSSETUP\BIN\X64\setupdl.exe application from the ConfigMgr installation files and simply provide a folder for the download.

Running setupdl.exe to download ConfigMgr pre-requisites.

Windows ADK 10 2004 and WinPE Addon for Windows ADK 10 2004: 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 2004" for the core ADK, and then adkwinpesetup.exe /layout "C:\Setup\Windows ADK 10 2004 WinPE Addon" for the WinPE Addon.

Windows ADK 10 2004 setup files.
The Windows ADK 10 2004 WinPE Addon setup files.

Optional Servers

For the optional MDT01 server, you also need to download the following software:

Using the SQLServer2017-SSEI-Expr.exe web installer to download media.

Step 2 – Prepare the Hydration Environment

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

  • Deployment Tools
  • Imaging and Configuration Designer (ICD)
  • Configuration Designer
  • User State Migration Tool (USMT)
Running the Windows ADK 10 2004 Setup.

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 2004 WinPE Addon (adkwinpesetup.exe) with the default settings.

Running the Windows ADK 10 2004 WinPE Addon Setup.

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

Running the MDT 8456 Setup.

4. Install the MDT 8456 Hotfix.

Note: Due to a code change in Windows ADK 10 v2004 (and Windows 10 v2004 or later too) you need to download some updated files for MDT 8456. You can download these files here: https://download.microsoft.com/download/3/0/6/306AC1B2-59BE-43B8-8C65-E141EF287A5E/KB4564442/MDT_KB4564442.exe

4a. So, download the MDT 8456 hotfix (MDT_KB4564442.exe), and extract it to a folder. I extracted it to C:\Setup\MDT 8456 Update.

4b. Copy the x86 version of the new Microsoft.BDD.Utility.dll from C:\Setup\MDT 8456 Update\x86 to C:\Program Files\Microsoft Deployment Toolkit\Templates\Distribution\Tools\x86. Replace the existing file.

4c. Copy the x64 version of the new Microsoft.BDD.Utility.dll from C:\Setup\MDT 8456 Update\x64 to C:\Program Files\Microsoft Deployment Toolkit\Templates\Distribution\Tools\x64. Replace the existing file.

5. Extract the HydrationCMWS2019.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:\HydrationCMWS2019\Source

The extracted hydration kit files.  

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

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

Opening the Hydration Kit deployment share in Deployment Workbench.

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 2019 reference image (have to be named REFWS2019-001.wim, case sensitive), to the following folder: C:\HydrationCMWS2019\DS\Operating Systems\WS2019

Note: The WIM image should only have on index, Windows Server 2019 with Desktop Experience. Again, if you don't have an updated image of Windows Server 2019 Standard. Please follow this guide to create one: https://deploymentresearch.com/building-the-perfect-windows-server-2019-reference-image/

The Windows Server 2019 Standard image copied.

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

BGInfo copied.

3. Copy the Windows ADK 10 2004 setup files (1.13 GB) to the following folder:
C:\HydrationCMWS2019\DS\Applications\Install – Windows ADK 10\Source

The Windows ADK 10 2004 setup files copied.

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

Windows ADK 10 2004 WinPE Addon setup files copied.

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

SQL Server 2017 Standard x64 setup files copied.

6. Copy the latest SQL Server 2017 CU setup file (CU 20 when I updated this guide) to the following folder:
C:\HydrationCMWS2019\DS\Applications\Install – SQL Server 2017\Source\Updates

Note: You need to create the Updates folder.

The SQL Server 2017 CU copied.

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

The SQL Server Management Studio setup file copied.

8. Copy the ConfigMgr 2103 setup files (extract the download) to the following folder:
C:\HydrationCMWS2019\DS\Applications\Install – ConfigMgr\Source

ConfigMgr setup files copied.

9. Copy the ConfigMgr PreReqs setup files to the following folder:
C:\HydrationCMWS2019\DS\Applications\Install – ConfigMgr\PreReqs

ConfigMgr Pre-requisite files copied.

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

MDT 8456 copied.

Optional – Populate the hydration deployment share with files for MDT01

Note: These steps are only needed if you want to deploy the optional MDT01 virtual machine. 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:\HydrationCMWS2019\DS\Applications\Install – SQL Server 2017 Express\Source

SQL Server 2017 Express setup file copied.

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. Expand the Advanced Configuration node, and then select the Media node.   

3. 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 (HydrationCMWS2019.iso ) in the C:\HydrationCMWS2019\ISO folder. The HydrationCMWS2019.iso should be about 13-14 GB in size (size will vary a bit depending on your Windows Server 2019 reference image).

 

The Hydration Kit ISO file.

Step 3 – Deploy the virtual machines

All accounts, including Administrator, have a password of [email protected]. If you want a PowerShell script that creates these VMs for Hyper-V, check the C:\HydrationCMWS2019\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)
  • Network: Your lab network
  • Image file (ISO): C:\HydrationCMWS2019\ISO\HydrationCMWS2019.iso
  1. Start the DC01 virtual machine. After booting from HydrationCMWS2019.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)
  • Network: Your lab network
  • Image file (ISO): C:\HydrationCMWS2019\ISO\HydrationCMWS2019.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. Don't forget to do a final reboot after applying the updates, there is usually a pending reboot caused by the upgrade process.

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)
  • Network: Your lab network
  • Image file (ISO): C:\HydrationCMWS2019\ISO\HydrationCMWS2019.iso

Next Steps – 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:\HydrationCMWS2019\ISO\Content\Deploy\Control folder.

Note: Again, by default, all accounts, including Administrator, have a password of [email protected].

The configuration files for the Hydration Kit.

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

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

If you need to change the various service accounts, you need to to modify the Configure-CreateADStructure.wsf script in the C:\HydrationCMWS2019\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.

The Authorize DHCP action in the DC01 task sequence.

Written by Johan Arwidmark

About the author

Johan Arwidmark

5 2 votes
Article Rating
Subscribe
Notify of
guest
70 Comments
Newest
Oldest Most Voted
Inline Feedbacks
View all comments
Randolph
Randolph
3 months ago

the download link doesn't seem to be working.

Matt H
Matt H
4 months ago

Hi Johan, it appears the download link is not valid again. Can you verify?

Brad
Brad
5 months ago

Download links for the hydration kit still don't seem to be working for me.

Mayur M
Mayur M
5 months ago

Hello Johan,

Thanks for the great stuff. I have successfully setup the CM01 lab using the Hydration kit.

Awesome and appreciated always.

Thanks

Pavan
Pavan
5 months ago

Hello Johan,
Seem the link to download the Hydration kit is broken?
Can this be updated please?
Thanks

Unni
Unni
5 months ago

I am unable to use it, is it fixed ?
Thanks
Unni

Chris
Chris
5 months ago

Hi Johan. Awesome work on this hydration kit! I've used it a couple of times and have to rebuild the lab again. I see towards the end of the docs where you say to edit the TS and also modify the four .INI files if we choose to change password and domain info. I've updated these files and still am not able to get past the DC01 auto-logon part (the password that is set is still the default one and not my new one). I've also tried updating the ts.xml and unattend.xml for DC01 (decoding the encrypted values shows possibly… Read more »

Paul Woodall
Paul Woodall
6 months ago

Hi Johan,

I have been attempting to do this with the Windows_InsiderPreview_Server_vNext_en-us_20270.iso. I did export the "Standard" index. MDT will not open the unattend.xml and errors when opening the catalog. I was able to edit the unattend.xml with WICD. When the image does install, the DC01 server does not apply the OSDComputerName which breaks stuff. I am not sure what is wrong.

Best Regards,

Paul

trackback

[…] are some readily available options out on the internet such as Johan Arwidmark's Hydration Kit or Microsoft's M365 Lab Kit, but I was interested in minimum complexity and footprint. […]

Ryan Cowell
Ryan Cowell
11 months ago

Hi Johan,

Is it possible to deploy CMG/CDP from this kit?

Martin Wheeler
Martin Wheeler
11 months ago

Hi, is it possible to use evaluation copies of OS and SQL in the hydration kits?

Thanks,
Martin.

Jouni Jokelainen
Jouni Jokelainen
1 year ago

Thanks Johan for making things a bit easier!

I only had one little glitch at the end. For some reason i got an error Can not find script file "C:\MININT\Scripts\LTICleanup.wsf"

It was not a big problem as i copied it and .vbs script needed to CM01 manually and ran it after that.

Garrett
Garrett
1 year ago

Hi Johan,

Would you be able to tell me anything about WSUS/SUP fits into this environment? Thanks!

chetan yamger
1 year ago

You were correct.It helps me.
Thank you so much for kit and helping community with your skills

kordra
kordra
1 year ago

Can I use Server 2012 instead of 2019 for this kit?

Claudio Escobedo
Claudio Escobedo
1 year ago

Hey Johan,

This is Hydration kit is awesome! I almost made it, but SCCM did not install because of the following error.

*********************************************
***** ConfigMgr Setup Bootstrapper *****
*********************************************
NOUSERINPUT was specified.
Commandline:
"D:\Deploy\Applications\Install – ConfigMgr\Source\SMSSETUP\BIN\X64\SetupWpf.exe" /Script D:\Deploy\Applications\Install – ConfigMgr\ConfigMgrUnattend.ini /NoUserInput
INFO: Checking dotnet framework versions…
Error: Dotnet 3.5 is not installed.
Setup requires both .NET Framework 3.5 SP1 to continue; however, it was not found on this computer.
Visit http://go.microsoft.com/fwlink/?LinkId=211602 for information on where to find the required versions of .NET Framework.
******************************************************
***** Exiting ConfigMgr Setup Bootstrapper *****
******************************************************

Claudio Escobedo
Claudio Escobedo
1 year ago

You are correct, I think I missed that step when I was updating my server 2019 ISO. I just disabled the extended the schema step in the CM01 task sequence. I then manually extended the schema and all was good. Thanks for all your input!

trackback

[…] that you know the problem, below is a copy of the CustomSettings_DC01.ini that is included in the Hydration Kit. I am using the format ;comment to explain the nuances with each entry so all you have to do is […]

Mike R
Mike R
1 year ago

Hi Johan I'm trying to setup a lab using your hydration kit (2019), all going fine so fab but seem to be hitting issues around the Hyper-V stage (trying to connect from one device to the other to launch the 2019 ISO via hyper-v). I have 2x W10 Pro Devices, 1 I'd like to use one as my Hyper-V management server(beefy PC) and the other (surface pro) to connect to this. They are not on any domain, both home/workgroup devices and this seems to be the issue. Non domain joined devices seem to have issues connecting to non domain joined… Read more »

Bryan Garmon
1 year ago

I added a few comments previously about this not working that are waiting moderator approval. I figured out what I was doing wrong and documented it. In case anyone else runs into this issue here's my blog about it. https://www.aftersixcomputers.com/index.php/2020/02/27/hydration-kit-2019-join-an-existing-domain/

Bryan Garmon
1 year ago

Instead of creating a new AD Domain, I'm trying to modify the CustomSettings_DC01.ini file to join an existing domain and then promote the server to be a DC in the existing domain. I disabled the steps in the Task Sequence to configure DHCP so I just commented out the lines in the answer file for that section. What is happening is that DC4 is getting created, the proper IP configuration is applied, it's joining the existing domain, but it's not promoting itself to a DC. Below is what I've modified the CustomSettings_DC01.ini to be. Anyone else tried this and have… Read more »

fbifido
1 year ago

I would like to suggest a very long time built blog about "https://viamonstra.com/pages/ip-plan" wait don't delete this post yet, let me finish first: This blog should be a competition as well as a leaning tool to every one. Rules: always use Microsoft Best Practices, can only use Hyper-V, must use the latest of any software & keep them up-to-date, make a note of everything you do and record the time when you are working on anything for this project, you are allowed to do little by little but remember to document your time. 3 stage blog: ============= stage1: (a) look… Read more »

trackback

[…] accessible to people just starting out. The market is already cornered on hydration kits – Johan has a shiny one he has been keeping updated for the community over the years. What I'd like to offer is some […]

Christian Säuberlich
Christian Säuberlich
1 year ago

I get the following error on CM01 "extadsch.exe mfc120.dll missing". How can I fix this?

Arlene
Arlene
1 year ago

I got the same error a few times. I just extended the schema on the DC and disabled the step in the CM01 task sequence and ran it again. It worked beautifully after that. Thanks so much for putting in the work

Claudio
Claudio
1 year ago
Reply to  Arlene

Same error for me. Just like Arlene, I just disabled the extend the schema step within the Task Sequence before moving forward with the ISO creation. When everything finished installing, just went back to the DC VM and extended the schema. After that, all is good, thanks for putting this together.

Tobias Schön
Tobias Schön
1 year ago

Hi Johan,
I think that the CM01 needs an additional Visual C++ to be able to do the extendAD thing.
It crashed on that step just now 🙂
Maybe mention that in a sentence or two 🙂

Patrick Zovistoski
Patrick Zovistoski
1 year ago

Hi Johan. For me, the DC01/CM01 task sequences are failing to automatically log back into the VM after each reboot. It seems as if the auto-logon configurations are getting stripped; how is this best handled? Thanks!

Patrick Zovistoski
Patrick Zovistoski
1 year ago

Nevermind; it was due to Hyper-V Enhanced Mode" being enabled. 🙂

John
John
1 year ago

Server 2019 keeps installing Core instead of standard with UI. Is this standard? Any way in the TS we can adjust to select UI?

John
John
1 year ago

Thank you Johan!

Also, just a heads up for "Note #2 – Internal network and Internet Access:" you don't link Ami's post. 🙂

Mandy
Mandy
1 year ago

Hi Johan,
AS usual great article…
https://viamonstra.com/ip-plan link is dead. page throws error 404. Can you share updated link or excel sheet for IP plan..Thanks in advance..

Wyatt
Wyatt
1 year ago

Hi Johan!
The schema is not extended. I have to extend after deployment. Any advice?

Modifying Active Directory Schema – with SMS extensions.
 Unable to connect to RootDSE – Cannot update Active Directory. Error code = 1355.
 Failed to extend the Active Directory schema, please find details in "C:\ExtADSch.log".

Thanks!

Wyatt
Wyatt
1 year ago

I Johan! Yes and is very strange becasue machine is joined to domain sucessfully, but the schema extension fail, and I have to run after the complete installation of CM01 machine. I will try to change the IP range of my virtual switch, but is rare.

Thank you!

Christoph Wijns
Christoph Wijns
1 year ago

Tried several times and I always get MS Server 2019 Standard Core edition (DC01) installed – no Desktop Experience – tried to change TS.xml and OperatingSystems.xml but no luck – any idea ?

Teknox
1 year ago

nice work, keep up the good work.

Kenny
Kenny
1 year ago

Hello!
https://viamonstra.com/ip-plan does not work
-K-

fbifido
1 year ago

is the DCxx also your DHCP?


>