While not officially supported by MDT you can dynamically deploy operating systems by changing the OSGUID TS variable during the task sequence which allows you to do things like select an OS to deploy whether that be a different sku of an os (pro vs home) or an entirely different OS such as Win 11 vs Win 10.
I created a similar setup with PSD today and wanted to test and see if this was possible but disappointingly found it is locked to the image specified when generating the image to be branchcache enabled with 2pint's winpegen tool. If I removed the OSDToolkitImageName variable from the configuration.ini the task sequence would fail at the OS deployment stage with an error stating the file source cannot be found.
While Windows 10 is EOL in a couple years it would still be nice to have support for multiple skus of Windows 11 without the need for multiple deployment shares or multiple task sequences.
This is my fault actually, I was setting the OSGUID variable incorrectly. I tested deploying with and without branchcache and both worked when deploying a different OS.
While not officially supported by MDT you can dynamically deploy operating systems by changing the OSGUID TS variable during the task sequence which allows you to do things like select an OS to deploy whether that be a different sku of an os (pro vs home) or an entirely different OS such as Win 11 vs Win 10.
I created a similar setup with PSD today and wanted to test and see if this was possible but disappointingly found it is locked to the image specified when generating the image to be branchcache enabled with 2pint's winpegen tool. If I removed the OSDToolkitImageName variable from the configuration.ini the task sequence would fail at the OS deployment stage with an error stating the file source cannot be found.
While Windows 10 is EOL in a couple years it would still be nice to have support for multiple skus of Windows 11 without the need for multiple deployment shares or multiple task sequences.