Today's update makes some minor additions to support OSDCloud from a Windows Setup Environment, Windows Preinstallation Environment, and Windows Recovery Environment.
Simply create a New-OSBuildTask adding the WinPEOSDCloud parameter. You can optionally add Windows Recovery Environment support by adding the WinREWiFi parameter
The OSDClould integration will add PowerShell Gallery support to WinPE WinRE and WinSE and install the OSD PowerShell Module
Keep in mind for all of this to work, you need PowerShell added, so add your ADK files as appropriate
If you enabled WinREWiFi, the latest Intel Wireless Drivers will be automatically downloaded and added to your WinRE (since WiFi only works in WinRE, not WinPE and WinSE)
Once that is done, you can now start OSDCloud from Windows Setup or Windows Recovery Environment
21.7.4 (2021 July 4) USA Independence Day
Today's update resolves an issue installing the new combined SSU + LCU. The SSU will be extracted from the LCU and applied prior to the installation of the Combined LCU, which will now succeed since you have the SSU installed
21.3.9 (2021 March Patch Tuesday)
Resolved an issue with the SetupDU update ...
20.9.29 (2020 September 29)
Made some changes to support Windows 10 2009 (20H2)
20.7.6 (2020 July 6) 2004 Update
After a LONG hiatus ... I'm back. Don't ask where I have been, I'll share soon enough, but let's just same some changes at work (I'm a Manager now), obviously COVID, and some downtime spending time with my family has taken all my free time away from the Community. I apologize for that ... but some new stuff coming! Thanks for all the DM's on Twitter wondering where the **** I have been, and it was Manel's video call today that got me rolling. What a friend!
Some internal changes to support Windows 10 version 2004 have been made as well as resolving an issue where Optional updates not downloaded would prevent Update-OSMedia and New-OSBuild from completing
20.2.26 (2020 February 26) Gary Blok Edition v2
Support for Insider Feature Update for Windows 10 2004 (20H1)
18.104.22.168 has a Variable issue ... so make sure you are on 22.214.171.124
Directory Changes in this release add ContentPacks and rename Media. ContentPacks will be fully enabled in the OSDBuilder MMSJazz Edition. Media (which contained downloaded FeatureUpdates) has been renamed to FeatureUpdates
Now more transparent if you need an Update and some other changes
These will be enabled in the OSDbuilder MMSJazz Edition, but unfortunately there is a cost. You will have to give up using Drivers, ExtraFiles, Registry, and Scripts in Templates. You have some options:
If they are not using them, delete them so you can be ready for ContentPacks
If you are using them, keep using them (for now), but you will have to migrate to ContentPacks soon enough. Adapt.
They will continue to work for existing OSDBuilder Home paths, but not be created going forward for new OSDBuilder Home paths. Can they co-exist? Sure, but at this point I am putting all efforts into BuildPacks, and would rather kill off the duplicate functionality in Templates
Can I keep using Template JSON Files?
Yes, there are no plans to change this
Why the change to ContentPacks?
For me, I never could use Template Content as much as I would have liked because while I design and support OSDBuilder, I also have my day job of supporting 'The Company'
This meant that I had to keep my content separate in different OSDBuilder Home directories ... often at times duplicating Updates, etc. It became rather time consuming, and let's be honest. I made OSDBuilder for me and my team first, and shared it with everyone else secondary (this isn't a paid job after all). So it seems I could never fully develop Templates as I actually need multiple Templates ... so after a few beers, and some silly names (LootCrate, ConfigPacks, OSDBuilderPackages, Box, BuildPacks) I decided on ContentPacks (one word, not two) because they are intended to replace the usage of the Content directories
If you are attending my MMSJazz sessions, send me a DM on Twitter so I can get you a separate build of OSDBuilder :)