This kit builds a complete ConfigMgr Current Branch 2203 infrastructure running on Windows Server 2019 and SQL Server 2017 including optional Windows 10 and Windows 11 clients. 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. This kit now adds and configuring SQL Server Reporting Services, and has been updated for Windows 11 support. Another update is that you can now specify which path to install the hydration kit on.
Download from GitHub: https://github.com/DeploymentResearch/HydrationKitWS2019
Hydration Kit Video: Check out the free mini course at the ViaMonstra Online Academy covering the Hydration Kit setup (and many other tips and tricks related for creating a lab for ConfigMgr, MDT and Intune): Building the Perfect Lab for ConfigMgr, MDT, and Intune.

Credits: Special thanks to Sven Aelterman for creating the script for configuring SQL Server 2017 Reporting Services, and for graciously allowing me to include it in the hydration kit.
Notes
Customizations: This hydration kit install all servers in the corp.viamonstra.com domain, on the 192.168.25.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):
- Setting Up New Networking Features in Hyper-V for Windows 10 or Windows Server 2016/2019
https://deploymentresearch.com/558/Setting-Up-New-Networking-Features-in-Server-2016.
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 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 2016 and ConfigMgr Current / Technical Preview Branch
https://deploymentresearch.com/hydration-kit-for-windows-server-2016-and-configmgr-current-technical-preview-branch/
Hydration Kit For Windows Server 2019 and ConfigMgr Current Branch
So, again, this Kit builds a complete ConfigMgr Current Branch 2203, 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 2019, SQL Server 2017 Express, and MDT 8456
- FS01. Windows Server 2019, File Server
- DP01. Windows Server 2019, additional ConfigMgr DP
Clients
This kit also allows you to automatically deploy the below list of clients for management.
- PC001. Windows 10 Enterprise
- PC002. Windows 10 Enterprise
- PC003. Windows 11 Enterprise
- PC004. Windows 11 Enterprise
Setup Overview
Shorthand, to build the virtual machines there are five main steps you need to do:
- Download the necessary software
- Install the Hydration Kit
- Copy the downloaded software to the Hydration Kit
- Create the bootable Hydration Kit ISO
- Create and Deploy the virtual machines
Note: Detailed instructions are further down this page… See the Step-by-Step Guides section.


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:
- The Hydration Kit: https://deploymentresearch.com/DRFiles/HydrationCMWS2019.zip
- MDT 8456 (The kit is based on that platform): https://www.microsoft.com/en-us/download/details.aspx?id=54259
- BGInfo: http://technet.microsoft.com/en-us/sysinternals/bginfo
- A Windows Server 2019 Standard WIM image (single index, fully updated). The easiest way to get one is to download an already updated Windows Server 2019 ISO file, and then run this PowerShell script: https://github.com/DeploymentResearch/DRFiles/blob/master/Scripts/Export-WindowsServer2019WIMfromISO.ps1
- SQL Server 2017 Standard x64: Either a fully licensed version from VLSC or MSDN, or a 180 days trial version from the Microsoft Evaluation Center: https://www.microsoft.com/en-us/evalcenter/
- SQL Server 2017 Cumulative Update (CU) 17 (or later): https://www.microsoft.com/en-us/download/details.aspx?id=56128 (ConfigMgr only requires CU 2 for SQL Server 2017, but I recommend using the latest CU).
- SQL Server 2017 Reporting Services: https://www.microsoft.com/en-us/download/details.aspx?id=55252
- SQL Server Management Studio: https://aka.ms/ssmsfullsetup
- ConfigMgr 2203 and its prerequisites: Either a fully licensed version from VLSC or MSDN, or a 180 days trial version from the Microsoft Evaluation Center: https://www.microsoft.com/en-us/evalcenter
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.

Windows ADK for Windows 11 21H2 and the ADK WinPE Addon for Windows 11 21H2: https://docs.microsoft.com/en-us/windows-hardware/get-started/adk-install
Note #1: Make sure to get the 21H2 version of the Windows ADK for Windows 11. The new 22H2 version (released in May 2022) is not yet supported by ConfigMgr.
Note #2: To download the complete standalone Windows ADK for Windows 11 setup, run adksetup.exe /layout "C:\Setup\Windows ADK 11" for the core ADK, and then adkwinpesetup.exe /layout "C:\Setup\Windows ADK 11 WinPE Addon" for the WinPE Addon.


Optional Servers
The FS01 and DP01 optional servers don't need any extra software, but for the MDT01 server, you also need to download the following software:
- SQL Server 2017 Express: https://www.microsoft.com/en-us/download/details.aspx?id=55994
Note: Use the SQLServer2017-SSEI-Expr.exe web installer to download the Express Core media (SQLEXPR_x64_ENU.exe)

Optional Clients
For the optional clients, you also need to download the following software:
- A Windows 10 Enterprise WIM image (single index, fully updated). The easiest way to get one is to download an already updated Windows 10 ISO file, and then run this PowerShell script: https://github.com/DeploymentResearch/DRFiles/blob/master/Scripts/Export-Windows10EnterpriseWIMFromISO.ps1
- A Windows 11 Enterprise WIM image (single index, fully updated). The easiest way to get one is to download an already updated Windows 11 ISO file, and then run this PowerShell script: https://github.com/DeploymentResearch/DRFiles/blob/master/Scripts/Export-Windows11EnterpriseWIMFromISO.ps1
Step 2 – Install the Hydration Kit
Installing the Hydration Kit requires that you first install Windows ADK and the Windows ADK WinPE Addon. The kit has been tested with both Windows ADK 10 and Windows ADK 11, but to get full support for Windows 11, I recommend using the Windows ADK 11 version since it supports all currently supported operating systems.
Installing Hydration Kit Prerequisites
1. On the Windows machine that you use to manage Hyper-V or VMware, install Windows ADK 11 (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 11 WinPE Addon (adkwinpesetup.exe) with the default settings.

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

4. Install the MDT 8456 Hotfix.
Note: Due to a code change in Windows 10 2004 or later (including Windows 11 and Windows Server 2022), and Windows ADK 10 2004 and later, 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. 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.
Installing the Hydration Kit
1. Extract the content from HydrationCMWS2019.zip to a folder, for example C:\HydrationKit.
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:\HydrationKit

2. In an elevated PowerShell command prompt, navigate to the C:\HydrationKit folder, and create the hydration deployment share by running the following command:
.\New-HydrationKitSetup.ps1 -Path C:\CMLab -ShareName CMLab
3. Open the Deployment Workbench, and look around. You should see applications, operating systems, and task sequences etc.

Step 3 – Copy the downloaded software to the Hydration Kit
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:\CMLab\DS\Operating Systems\WS2019
Note #1: The WIM image should only have a single index with the Windows Server 2019 with Desktop Experience edition. 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/
Note #2: If your CM01 does not have Internet access during the Hydration Kit build, make sure to also copy the microsoft-windows-netfx3-ondemand-package~31bf3856ad364e35~amd64~~.cab file to the following folder: C:\CMLab\DS\Operating Systems\WS2019\sources\sxs

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

3. Copy the Windows ADK 11 setup files (1.6 GB) to the following folder:
C:\CMLab\DS\Applications\Install – Windows ADK 11\Source

4. Copy the Windows ADK 11 WinPE Addon setup files (3 GB) to the following folder:
C:\CMLab\DS\Applications\Install – WinPE Addon for Windows ADK 11\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:\CMLab\DS\Applications\Install – SQL Server 2017\Source

6. In the C:\CMLab\DS\Applications\Install – SQL Server 2017\Source folder, create a subfolder named Updates, and copy the latest SQL Server 2017 CU setup file (CU 20 when I wrote this guide) to it.

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

8. Copy the SQL Server 2017 Reporting Services setup file to the following folder:
C:\CMLab\DS\Applications\Install – SQL Server 2017 Reporting Services\Source

9. Copy the ConfigMgr 2203 setup files (extract the download) to the following folder:
C:\CMLab\DS\Applications\Install – ConfigMgr\Source

10. Copy the ConfigMgr 2203 PreReqs setup files to the following folder:
C:\CMLab\DS\Applications\Install – ConfigMgr\PreReqs

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

12. Copy your Windows 10 reference image (must be named REFW10X64-001.wim, case sensitive), to the following folder: C:\CMLab\DS\Operating Systems\Windows 10
Note #1: The WIM image should only have a single index with the Windows 10 Enterprise edition. Please use the script to extract the correct index from a Windows 10 ISO file.

The Windows 10 Enterprise image copied.
13. Copy your Windows 11 reference image (must be named REFW11X64-001.wim, case sensitive), to the following folder: C:\CMLab\DS\Operating Systems\Windows 11
Note #1: The WIM image should only have a single index with the Windows 11 Enterprise edition. Please use the script to extract the correct index from a Windows 11 ISO file.

The Windows 11 Enterprise image 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 need this VM, 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:\CMLab\DS\Applications\Install – SQL Server 2017 Express\Source

Step 4 – Create the bootable 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:\CMLab\ISO folder. The HydrationCMWS2019.iso should be about 14-16 GB in size (size will vary a bit depending on your Windows Server 2019 reference image and software added).

Step 5 – Create and Deploy the virtual machines
First, all accounts, including Administrator, have a password of P@ssw0rd. Secondly, you either create your VM manually, and connect them to the Hydration Kit ISO. Or you can automate that process to with a bit of PowerShell.
Creating the Virtual Machines via PowerShell
If you want a PowerShell script that creates these VMs for Hyper-V, use New-LabVMsForHyperV.ps1 script from the C:\HydrationKit folder. The syntax for the scripts is as follows:
.\New-LabVMsForHyperV.ps1 -VMLocation C:\VMs -VMNetwork Internal -ISO C:\CMLab\ISO\HydrationCMWS2019.iso
Note: If using Hyper-V, do Not configure the virtual machines for dynamic memory. If you do, the installation will take a very long time. 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:\CMLab\ISO\HydrationCMWS2019.iso
- Start the DC01 virtual machine. After booting from HydrationCMWS2019.iso , and after WinPE has loaded, select the DC01 task sequence.
- Wait until the setup is complete and you see the Hydration Complete message in the final summary.
- 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:\CMLab\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:\CMLab\ISO\HydrationCMWS2019.iso
Deploying DP01 (Optional)
Once the domain controller (DC01) is up and running, you can deploy the optional DP01 virtual machine. Don't forget to leave DC01 running while deploying DP01 since it is joining the domain during deployment. Use the following settings for the MDT01 virtual machine:
- Name: DP01
- CPU: 2 vCPU
- Hard drive: 300 GB (dynamic disk)
- Memory: 4 GB (static memory)
- Network: Your lab network
- Image file (ISO): C:\CMLab\ISO\HydrationCMWS2019.iso
Deploying FS01 (Optional)
Once the domain controller (DC01) is up and running, you can deploy the optional FS01 virtual machine. Don't forget to leave DC01 running while deploying FS01 since it is joining the domain during deployment. Use the following settings for the MDT01 virtual machine:
- Name: FS01
- CPU: 2 vCPU
- Hard drive: 300 GB (dynamic disk)
- Memory: 4 GB (static memory)
- Network: Your lab network
- Image file (ISO): C:\CMLab\ISO\HydrationCMWS2019.iso
Deploying PC0001-4 (Optional)
Once the domain controller (DC01) is up and running, you can deploy the optional PC0001-4 virtual machine(s). Don't forget to leave DC01 running while deploying PC0001-4 since they are joining the domain during deployment. Use the following settings for the PC0001-4 virtual machine(s):
- Name: PC0001 / PC0002 / PC0003 / PC0004
- CPU: 2 vCPU
- Hard drive: 60 GB (dynamic disk)
- Memory: 4 GB (static memory)
- Network: Your lab network
- Image file (ISO): C:\CMLab\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:\CMLab\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:\CMLab\DS\Applications\Install – ConfigMgr\ConfigMgrUnattend.ini
- C:\CMLab\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:\CMLab\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
Copy the BGInfo file (bginfo.exe) to the following folder: C:\HydrationCMWS2019\DS\Applications\Install – BGInfo\Source
The above step needs to be corrected.
It should have been C:\CMLab\DS\Applications\Install – BGInfo\Source
We can see that the screenshot is correct.
Hi Sourav,
Thanks for letting me know, the post has been updated.
the download link doesn't seem to be working.
Fixed the link, again. Seems like bit.ly were having some issues. Sorry about that. / Johan
Hi Johan, it appears the download link is not valid again. Can you verify?
Should be fixed now, sorry about that / Johan
Download links for the hydration kit still don't seem to be working for me.
Should be ok now. I just tested.
Hello Johan,
Thanks for the great stuff. I have successfully setup the CM01 lab using the Hydration kit.
Awesome and appreciated always.
Thanks
Hello Johan,
Seem the link to download the Hydration kit is broken?
Can this be updated please?
Thanks
Sorry about that, should be fixed now.
/ Johan
I am unable to use it, is it fixed ?
Thanks
Unni
Should be, I just tested.
Sorry about that, fixed now.
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 »
Check these to posts in regards to more details on customizing the hydration kit.
Customizing the Hydration kit, PowerShell style! – By Mattias Benninge
https://deploymentresearch.com/customizing-the-hydration-kit-powershell-style-by-mattias-benninge/
Customizing the ViaMonstra Hydration Kit
https://deploymentresearch.com/customizing-the-viamonstra-hydration-kit/
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
Hi Paul,
I haven't tried build 20270, but I have tested build 20289 of WS2022 insider preview with no issues for DC01.
Windows ADK 10 1903 does not have support for WS2022, but Windows ADK 10 2004 seem to generate catalog files for WS2022 just fine. that being said, no change was needed for the unattend.xml, the WS2019 template provided in the kit worked.
/ Johan
[…] 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. […]
Hi Johan,
Is it possible to deploy CMG/CDP from this kit?
Assuming there are automation features for that, cmdlets etc. you can extend the task sequence to run those. But I have nothing ready-made in the kit for that. There are quite many things that needs to be verified for CMG to be setup, and even if I probably setup like ten of them by now, it seems like I'm running into some new issue every single time.
/ Johan
Hi, is it possible to use evaluation copies of OS and SQL in the hydration kits?
Thanks,
Martin.
Yes, you can use evaluation versions.
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.
Hi Johan,
Would you be able to tell me anything about WSUS/SUP fits into this environment? Thanks!
Sorry for the very late reply, but I have not included an automated setup of WSUS/SUP in this kit.
[…] first lab was Johan’s hydration kit. It’s incredibly powerful, customizable, and educational. Unfortunately it takes a little more […]
Well, most likely the SQL Server setup failed for whatever reason. Most commonly because the wrong SQL files have been added, but check the SQL Server installation log file to find out more.
You were correct.It helps me.
Thank you so much for kit and helping community with your skills
Can I use Server 2012 instead of 2019 for this kit?
If you import the Windows Server 2012 R2 OS Image, and modify the task sequence to use it, then it should work, but I haven't tested. That being said, I do have some older hydration kits that are based on Windows Server 2012 R2. Search the blog for hydration.
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 *****
******************************************************
I usually enable .NET Framework 3.5 in my image so it's always there. If you check the prereq section for the hydration kit you find this little note: A reference image (WIM file) of Windows Server 2019 Standard, fully patched, and with .NET Framework 3.5 added to it. If you don't have one, follow this guide to create one: https://deploymentresearch.com/building-the-perfect-windows-server-2019-reference-image/
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!
[…] 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 […]
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 »
I run a similar setup myself, many of my Hyper-V hosts are workgroup machines, so that's not an issue. It usually comes down to conflicting DHCP servers, VLAN tagging or misconfigured vm switches when it breaks.
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/
Thanks for this info, very useful.
Updated URL for this article. https://www.aftersixcomputers.com/hydration-kit-2019-join-an-existing-domain/
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 »
I had a version of the kit many years ago that configured two domain controllers, because I was running everything of my laptop, and saved/resumed the vms all the time, which AD does not like when having more than one DC. I saw your other comment, and I'm glad you got it sorted.
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 »
Thanks for the idea, sounds like a lot of fun. Should be doable if picking a subset of the servers instead of all of them. The best audience for this task would probably by computer science class in college, where the teacher sets the rules etc.
[…] 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 […]
I get the following error on CM01 "extadsch.exe mfc120.dll missing". How can I fix this?
extadsch.exe requires Visual C++ runtimes, but the SQL Server 2017 setup installs them, so you usually only get that error if SQL Server 2017 failed to install.
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
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.
Sorry for the late reply. I fixed a bug in the script that calls the utility for extending the schema. Should works as default now.
/ Johan
Quick update, I updated the script that extends them schema. I now run correctly even if no Visual C++ runtimes are installed in the server image.
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 🙂
SQL Server 2017 installs the needed runtimes, and SQL is installed before the AD schema is extended.
Quick update, I updated the script that extends them schema. I now run correctly even if no Visual C++ runtimes are installed in the server image.
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!
Nevermind; it was due to Hyper-V Enhanced Mode" being enabled. 🙂
Server 2019 keeps installing Core instead of standard with UI. Is this standard? Any way in the TS we can adjust to select UI?
The task sequence is configured to use an OS image with only one index. I don't recommend using the default Windows Server 2019 media, but rather one that has been fully updated, and that only has one index.
Anyway, if you don't want to create a better media, you can do one of two things:
1. Export the Windows Server 2019 Standard (Desktop Experience) index to a new WIM image, and name it REFWS2019-001.wim
2. Import a new OS image into Deployment Workbench, and change all task sequences to use that OS
Thank you Johan!
Also, just a heads up for "Note #2 – Internal network and Internet Access:" you don't link Ami's post. 🙂
? The link is just below Note #2….
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..
The new link is https://viamonstra.com/pages/ip-plan, I'll see if I can get a redirection in place.
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!
Make sure the CM01 machine joined the corp.viamonstra.com domain, and that DC01 is running on the same virtual switch.
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!
Quick update, I updated the script that extends them schema. I now run correctly even if no Visual C++ runtimes are installed in the server image.
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 ?
Use a media with a single index. e.g. a reference image.
nice work, keep up the good work.
Hello!
https://viamonstra.com/ip-plan does not work
-K-
Sorry about that, that paged moved to https://viamonstra.com/pages/ip-plan
is the DCxx also your DHCP?
Yes