Hydration Kit for Windows Server 2022, SQL Server 2019 and ConfigMgr Current Branch

This kit builds a complete ConfigMgr Current Branch 2203 infrastructure running on Windows Server 2022 and SQL Server 2019, 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 other virtualization platforms like Virtual Box, KVM etc.

Download from GitHub: https://github.com/DeploymentResearch/HydrationKitWS2022

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.

Sample screenshot from the free mini course on ViaMonstra Online Academy.

Credits: Special thanks to Sven Aelterman for creating the script for configuring SQL Server 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.

Internal network and Internet Access: Since one of the virtual machines (DC01) is also a DHCP Server, its highly recommended 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 kits for Windows Server 2016 or Windows Server 2019? Look no further, they are right here:

Hydration Kit for Windows Server 2022 and ConfigMgr Current Branch

So, again, this Kit builds a complete ConfigMgr Current Branch 2203, with Windows Server 2019 and SQL Server 2019 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 2022, DC, DHCP and DNS
  • CM01. Windows Server 2022, SQL Server 2019, and ConfigMgr Current Branch

Optional supporting servers 

  • MDT01. Windows Server 2022, SQL Server 2019 Express, and MDT 8456
  • FS01. Windows Server 2022, File Server
  • DP01. Windows Server 2022, 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:

  1. Download the necessary software
  2. Install the Hydration Kit
  3. Copy the downloaded software to the Hydration Kit
  4. Create the bootable Hydration Kit ISO
  5. Create and 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 for Windows 11and 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 22H2 version of the Windows ADK for Windows 11 (10.1.22621.1), not the new 23H2 version (10.1.25398.1, released in September 2023).

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.

Windows ADK 11 setup files.
The Windows ADK 11 WinPE Addon files

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:

Using the SQL2019-SSEI-Expr.exe web installer to download media.
Selecting the Express Core version

Optional Clients

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

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 21H2, but to get full support for Windows 11, I recommend using the Windows ADK 11 21H2 version since it supports all currently supported operating systems.

Note: Again, please do not use Windows ADK for Windows 11 22H2. It's not supported by MDT 8456.

Installing Hydration Kit Prerequisites

1. On the Windows machine that you use to manage Hyper-V or VMware, install Windows ADK 11 21H2 (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 11 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 11 WinPE Addon (adkwinpesetup.exe) with the default settings.

Running the Windows ADK 11 WinPE Addon Setup.

Note: Because the Windows ADK for Windows 11 does not include the 32-bit (x86) version of Windows PE, you'll need to create an empty x86\WinPE_OCs folder structure in the Windows ADK folder. MDT doesn't use, but still looks for, this directory.

More information can be found in this blog post: https://www.deploymentresearch.com/windows-11-deployment-using-mdt-8456-with-windows-adk-23h2-build-25398/

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 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 HotFix.

4b. Copy the x86 version of the new Microsoft.BDD.Utility.dll from C:\Setup\MDT 8456 HotFix\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 HotFix\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 the Hydration Kit download to a folder, for example C:\Setup\HydrationKit.

The folder you used should now have a sub-folder named Source, two PowerShell scripts, a readme file and a license file.

The extracted hydration kit files.  

2. In an elevated PowerShell command prompt, navigate to the C:\Setup\HydrationKit folder, and create the hydration deployment share by running the following command:  

.\New-HydrationKitSetup.ps1 -Path C:\CMLab -ShareName CMLab

Running the New-HydrationKitSetup.ps1 script.

3. 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.

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 2022 reference image (have to be named REFWS2022-001.wim, case sensitive), to the following folder: C:\CMLab\DS\Operating SystemsWS2022

Note #1: The WIM image should only have a single index with the Windows Server 2022 with Desktop Experience edition. Please use the script mentioned earlier to extract the correct index from a Windows Server 2022 ISO file.

Note #2: If your VMs 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\WS2022\sources\sxs. Failing to do so will prevent .NET Framework 3.5 from being installed if the VM does not have Internet access.

The Windows Server 2022 Standard image copied.
.NET Framework 3.5 copied

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

BGInfo copied.

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

The Windows ADK 11 setup files copied.

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

Windows ADK 11 WinPE Addon setup files copied.

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

SQL Server 2019 Standard x64 setup files copied.

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

The SQL Server 2019 CU copied to Updates folder.

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

The SQL Server Management Studio setup file copied.

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

SQL Server Reporting Services setup files copied.

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

ConfigMgr setup files copied.

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

ConfigMgr Pre-requisite files copied, showing a subset of the files.

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

MDT 8456 copied.

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 Standard image copied.

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 10 Standard image copied.

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 2019 Express setup file (SQLEXPR_x64_ENU.exe) to the following folder:
C:\CMLab\DS\Applications\Install – SQL Server 2019 Express\Source

SQL Server 2019 Express setup file copied.

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.

Creating the bootable Hydration Kit ISO file.

After the media update you will have a big ISO (HydrationCMWS2022.iso) in the C:\CMLab\ISO folder. The HydrationCMWS2022.iso should be about 14-16 GB in size (size will vary a bit depending on your Windows Server 2022 image and software added).

The Hydration Kit ISO file.

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:\Setup\HydrationKit folder. The syntax for the scripts is as follows:

.\New-LabVMsForHyperV.ps1 -VMLocation C:\VMs -VMNetwork Internal -ISO C:\CMLab\ISO\HydrationCMWS2022.iso

Running the New-LabVMsForHyperV.ps1 script.

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.

Virtual Machines created via the New-LabVMsForHyperV.ps1 script.

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\HydrationCMWS2022.iso
  1. Start the DC01 virtual machine. After booting from HydrationCMWS2022.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:\CMLab\ISO\HydrationCMWS2022.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\HydrationCMWS2022.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 DP01 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\HydrationCMWS2022.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 FS01 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\HydrationCMWS2022.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\HydrationCMWS2022.iso

Next Steps – Optional Post-ConfigMgr Install Tasks

This kit has pre-configured steps that can automatically install Configuration Manager roles depending on the goals for your lab. These steps are disabled by default and if no customizations were made to the kit, they can be enabled without adjustment.

Optional Role Install Tasks.

Optional Post-ConfigMgr Install Tasks

Currently, the kit supports the following tasks:

  • Reporting Services Point
  • Software Update Point

Reporting Services Point credentials and SSRS Instance can be updated in the following file:

  • C:\CMLab\DS\Applications\Install – ConfigMgr Reporting Services Point\HYDCMRSPConfig.PS1

Software Update Point requires additional tasks to be enabled:

WSUSContent directory and SQL Server config can be updated in the following file:

  • C:\CMLab\DS\Applications\Install – WSUS\HYDWSUSConfig.ps1

Note: The first sync of WSUS always takes some time. It may be several hours before new products are shown in the site's Software Update Point configuration. You can track WSUS synchronization by viewing WSyncMgr.log on CM01.

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 various 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.

The configuration files for the Hydration Kit.

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

  • C:\CMLab\DS\Applications\Install – ConfigMgr\ConfigMgrUnattend.ini
  • C:\CMLab\ISO\Content\Deploy\Control\CustomSettings_CM01.ini

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

Customizing with a script

With a huge thanks to Matt Bennigne, a customization script called CustomizeHydrationKit.ps1 has been updated and added to the Server 2022 kit for the first time! This script assists in changing many of the customizable parameters of the Hydration Kit, including IP addresses, domain name, time zone, and passwords.

In addition, the script will make a copy of the original configuration so that you can easily revert your changes. Upon rerunning the script on a customized Deployment Share, the script will revert all files to the original copies before applying your changes again.

Written by Johan Arwidmark

About the author

Johan Arwidmark

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

I've setup the labs, how do I go about activating the devices with licence key?

Usman
Usman
4 months ago

For some reason my PC001-4 don't seem to connect to the domain automatically. I've checked the ipconfig and it seems to be assigned from another DHCP but not sure how. All the other machines got their IP fine but it's just these and I can't change these to static to join the domain manually. any help is appreciated. thanks

Octavius
Octavius
4 months ago

in trying to deploy the PC001-4 , in the hydration script i receive any error that the .iso it is looking for is on a F: drive. is there a way to point it in the correct direction?

Octavius
Octavius
4 months ago

Hmmm have not tried that. also just saw the flame button. going to try some of the suggestions there

Danny
Danny
5 months ago

For SQL Server 2022, I had to change the config file to use domain accounts for the different services. Because of this I added a TS Step to create those service accounts ahead of the SQL server install, this way CM doesn't complain about SQL running under a local account.

danny
danny
5 months ago

Do you have an update for SQL Server 2022?
I created a config file to the best of my ability but ConfigMgr complains about the service running not running as a system account. I can pass along the ini file if needed.

Patrick
Patrick
6 months ago

.Net 3.5 was failing for me on the CM01 install (not internet connected). I added a step to the TS after BGInfo and added an application called InstallNet35 that runs the line: DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:"D:\Deploy\Applications\Install – Net35"

Dr_Ghost86
Dr_Ghost86
8 months ago

Any ideas on why the VMs from the HydrationKit are shooting down every 1 hour? Troubleshooting is telling is due to the evaluation ISO. Any ideas on how to fix it?

Last edited 8 months ago by Dr_Ghost86
Paul Andrews
Paul Andrews
9 months ago

Hey Johan, I am seeing the following error message when I launch the VM for the initial time with the HydrationCMWS2022.iso. I just click on the X at the top and it seems to process but wasn't sure if something else was as play that I needed to address.

Screenshot 2023-08-30 145851.png
Paul Andrews
Paul Andrews
9 months ago
Reply to  Andrew Johnson

Thanks Andrew that appears to have worked. Another question, any reason why WSUS/SUP task sequence step is disabled?

Also are you aware of any issues with upgrading the CM after using the hydration kit? I was get a failure when trying to upgrade the CM database. Similar to this — https://www.prajwaldesai.com/configmgr-database-upgrade-error-0x87d20b15/

Andrew Johnson
Editor
9 months ago
Reply to  Paul Andrews

Glad to hear!

Those steps are optional if you want to speed up deployment but disabled by default so you would have essentially a fresh CM install that allows you to work through adding roles. That's detailed here on GitHub: https://github.com/DeploymentResearch/HydrationKitWS2022#next-steps—optional-post-configmgr-install-tasks. Thanks for pointing it out though, because I see it was missing on this post! I've added it to this guide.

I'm not aware of any issues with the CM upgrade, but I'll spin up a new server and try it out.

Paul Andrews
Paul Andrews
9 months ago
Reply to  Andrew Johnson

Andrew,

I re-built the CM server and ran the upgrade. This time however I installed MS OBDC Driver 18 and then rebooted before performing the upgrade. This time it was successful thought I can't say for certain this was the reason.

That said I am now trying to build the workstations and once the task sequence loads and it starts laying down the OS after the reboot all I get is a black screen. Anyone report any issues with the Win 10 and Win 11 client OS deployments.

Theodore
Theodore
9 months ago

Hi, okay I am trying to reinstall all the servers again, but I am having a problem with CM01 it does not seem to want to deploy the configuration manager part.

Joshua
Joshua
9 months ago
Reply to  Theodore

Did you figure out what was wrong? I am also having this issue with multiple attempts.

Theodore Borucki
Theodore Borucki
10 months ago

Hi

To my last it it seems that the partitioning part failed. Also, it looked like the Configuration software did not deploy to the CM01 server and is there a way that you can deploy the different servers to different HDD's during the initial setup as well.

Theodore Borucki
Theodore Borucki
10 months ago

Hi When I start the server, I get this error attached, if I click yes or no nothing happens if I select the x then it closes, and I then can select the operating image. This occurs with all the builds. I also seem to get the second attached image error when I try and run the MDT01 image build, I cannot get to copy the smsts.log file from the sytem.

Screenshot 2023-07-20 202421.png
Evan J. Whitney
Evan J. Whitney
1 year ago

PC001-PC004 don’t deploy with the proper names on them, get ts error but it points to D:\deploy\operating systems, thats not where the wims are how can this be changed?

Evan J. Whitney
Evan J. Whitney
1 year ago

I did put them and name them the right names, this is the error I get when trying to install the pc's. Please note, instead of C:\ I used D:\ and all the server vms work and deployed fine.

pc0001 mdt error.JPG
Evan J. Whitney
Evan J. Whitney
1 year ago

Yes let me send all 3

mdt os folder.JPG
Evan J. Whitney
Evan J. Whitney
1 year ago

Win10 Folder

mdt win 10  folder.JPG
Evan J. Whitney
Evan J. Whitney
1 year ago

Win11 Folder

mdt win 11  folder.JPG
Evan J. Whitney
Evan J. Whitney
1 year ago

Hi Johan, I have attached the screenshot you requested showing the folder shares.

mdt ds win10-11.JPG
Evan J. Whitney
Evan J. Whitney
1 year ago

Image Path screenshot, Won't let me browse to D:\ in WinPE

pc001 mdt.JPG
Evan J. Whitney
Evan J. Whitney
1 year ago

Looks like the wim isn't in there, not sure where I messed up.

mdt f8 capture.JPG
Evan J. Whitney
Evan J. Whitney
1 year ago

I think I figured it out, before Step 4 when you create the master ISO, the Windows 10 and Windows 11 ISO's need to be but into the Operating Systems folder, then you create the Master ISO, failing to do so you will not be able to deploy the PC001-0004 VM's.

Edit: This was the issue, I can confirm this is now working. Thank you Johan for the help I appreciate it, this would be good step to add in before creating the HydrationKit ISO.

Last edited 1 year ago by Evan J. Whitney
Evan J. Whitney
Evan J. Whitney
1 year ago

PC002 Task Sequence throws an error

PC002 Bad TS.JPG
Abbed Sedkaoui
Abbed Sedkaoui
1 year ago

Look again at Step 3 the first screenshot, i bet like me, and many others who also encountered this error,
you placed the wim inside the Sources folder, i learned it the hard way looking at the log with F8 in E:\MININT…
Just placing the wim like in the screenshot in C:\CMLab\DS\Operating Systems\WS2022 cleared this issue.

Last edited 1 year ago by Abbed Sedkaoui
Evan J. Whitney
Evan J. Whitney
1 year ago
Reply to  Abbed Sedkaoui

I have all the server's working, this is the PC VM's that are not installing

Abbed Sedkaoui
Abbed Sedkaoui
1 year ago

All right, your screenshot the wim in the right folder but your error is exactly as mine,
at this time OSDisk is E:
so open this log and look for your wim name if it say something like invalid
E:
cd MININT\SMSOSD\OSDLOGS
notepad BDD.log

Last edited 1 year ago by Abbed Sedkaoui
Robert Rathbun
Robert Rathbun
1 year ago

I am experiencing the same problem others are with the OS installation under VMware. When using Hyper-V, the problem doesn't appear to occur, however with VMware ESXI the issue occurs repeatedly during CM01's installation process. Tried alternative NIC's, but the issue continues.

Logs show FQDN isn't resolving properly, but the configs are exactly the same as those under Hyper-V which works. Any recommendations?

DC01 works correctly, it's just the CM01 installation I am focused on.

Last edited 1 year ago by Robert Rathbun
Radu Bogdan
Radu Bogdan
1 year ago

Hello,

I've noticed the the CM01 doesn't join the domain, I've already tried several times and no luck. Did anyone had the same issue, am I missing something here ? Thank you.

Stout
Stout
1 year ago

Curious if you've thought about what it would take to create something similar to this in Azure using spot instances so at least the cost stays low. I would be super interested in something like that! 🙂 As always, love the Hydration kits, thanks Johan!

Yannick
Yannick
1 year ago

My VMs do not have access to the internet, so I followed the advice to copy microsoft-windows-netfx3-ondemand-package~31bf3856ad364e35~amd64~~.cab to C:\CMLab\DS\Operating Systems\WS2022\sources\sxs. However, .NET Framework 3.5 does not install and so the installation of ConfigMgr fails since it is missing. Manual installation via the Server Manager results in a freeze of the VM. So I checked the Task Sequence in MDT for the ConfigMgr Prerequisites and found that the checkbox for .NET 3.5 was not checked. However, deploying the updated ISO did not fix the issue either.

What am I missing? Thank you for helping in advance.

Best regards
Yannick

Jessie
Jessie
2 years ago

I fixed the issue. in $edition it needs to be "Windows Server 2022 Standard Evaluation (Desktop Experience)" you have "Windows Server 2022 Standard (Desktop Experience)"

Jessie
Jessie
2 years ago

A Windows Server 2022 Standard WIM image (single index, fully updated). The easiest way to get one is to download an already updated Windows Server 2022 ISO file, and then run this PowerShell script:

I go to the Microsoft eval site, and I download the ISO for Server 2022, rename the iso and when I run this script i get the following error:

WARNING: WIM Edition: Windows Server 2019 Standard (Desktop Experience) does not exist in WIM: D:\sources\install.wim, aborting…

What am I missing?

Usman
Usman
4 months ago
Reply to  Jessie

I'm experiencing the same issue, did you manage to figure this out?

Nidhish
Nidhish
2 years ago

Pls share the hydration kit for MECM CB 2203 on Windows Server 2022

Henri
Henri
2 years ago

SQL Server 2019 Cumulative Update link points to 2017 CU, not 2019. Correct link is Download SQL Server® 2019 for Microsoft® Windows Latest Cumulative Update from Official Microsoft Download Center

Tim Lay
2 years ago

I have updated the following files

ConfigurationFile.ini – line 147 with SQLSYSADMINACCOUNTS="TIMBO\Administrator" "BUILTIN\Administrators"

Install-HYDSQLServer2019.ps1 – line 133 with $OriginalSQLSYSADMINACCOUNTS = "SQLSYSADMINACCOUNTS="TIMBO\Administrator"BUILTIN\Administrators""

Note that CU15 (SQLServer2019-KB5008996-x64.exe) is in the Updates folder

But there seems to be an error displayed as indicated in attachment
Any help, much appriechated
Regards
Tim

Donut Stack
Donut Stack
2 years ago

Thank you for yet another amazing Hydration kit Johan. This one initially appeared to be rather straight forward until I hit the following problem. CM Client on my W10 client will not retrieve policy unless an additional internet connected network is attached to the W10 client. I don't intend to connect this lab to the internet unless I have to. Hydrated with default network and naming scheme, configured an "IP Range" based boundary and assigned to a boundary group with site assignment. Enabled PXE boot. Deployed an W10 client via CM Client install task sequence. W10 client is assigned to… Read more »

Syed
Syed
2 years ago

What's your Server Hardware Model?

Christian Saeuberlich
2 years ago

Step 4: copy ADK WinPE Addon. No source folder will be created with your script.

Christian Saeuberlich
2 years ago

your download URL for SQL CU14 linked to SQL CU 2017.

Adrian moss
Adrian moss
2 years ago

Hi having put a lab together i am finding i can pxe boot f12 and get the task seq menu on selecting and it running the pre check i am having reports that the boot dosk is not on the dp on checking i find it is but it still fsils at this point any ideas.

Meik
Meik
2 years ago

Great work Johan,
thanks for IT.
But the Applications.xml is not the right one.Apps are missing. PS Code Exists but the TS fire´s Error.
Thanks again

Simon
Simon
2 years ago

Hello, I have taken all the steps related to changing ip/account/domain/passwords… during the installation everything goes well, but only 1 sctipt is not executed. The DC server creates the new domain with the given password but the accounts are not created in the OU/AD. What could possibly go wrong? I double checked the script. My next step is just leave everything default and install it.

Daniel Barras
Daniel Barras
2 years ago

Question for you, Johan. Was there a change to BitLocker in Server 2022? I can use MDT to store my BitLocker keys in Windows 10, Windows 11, Server 2019, but not Server 2022. All the other keys get stored, and BitLocker is activated on the other 3 operating sytems, but not 2022. I have to go in and Activate it, then either "print" the key or store it elsewhere. My Rules contains:

BDEInstall=TPM
BDEInstallSuppress=NO
BDEWaitForEncryption=TRUE
BDEDriveSize=3000
BDEDriveLetter=S:
BDERecoveryKey=AD
BDEKeyLocation=\\<SERVERNAME>\Deploy$\RecoveryKeys
BDEAllowAlphaNumericPin=YES

I've enabled "Wait for BitLocker to complete…" in the Enable BitLocker portion of the Task Sequence.

Last edited 2 years ago by Daniel Barras
CarlT
CarlT
2 years ago

Hi Johan,
This is a very thorough and detailed procedure, You're the man !
Keep up the good work.

Jason
2 years ago

Fantastic. I look forward to joining you for the Q1 2022 lab environment discussion!


>