Comment on page
BuildPacks

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) I decided on BuildPacks (one word, not two)
In simple terms, its kinda like another Templates Content ... but structured a little differently. You'' start out with _Mandatory and _Template. As more features get added to BuildPacks, they will continue to grow. Content you place in _Mandatory will be applied to every New-OSBuild, just like Templates Content. The _Template BuildPack does nothing except offer you some guidance on how to they are configured. Do nothing to this directory

BuildPacks are added to a New-OSBuildTask, just like you would anything else. I have manually added 'The Company' and 'Windows 10'. I cannot add or remove _Mandatory. This is automatic. As you can see, this is the new OSBuild Task Information which only shows what you have configured (new to MMSJazz). So in this example, I am creating a customized Windows installation with nothing but BuildPacks

Simply place the DaRT Tools and Dart Config in the PEDaRT directory

This is structured a little different, but as you see, OSBuilder will find the right content that is needed and install the CAB files that are in the BuildPack. Say hello to PowerShell in WinPE

In this example, I had content in multiple BuildPacks that were applied automatically

You have some options in this one. If you use one of the Subdirs, you can keep your content organized rather than just dumping everything in one place

Have you ever wanted to add a PowerShell Module to WinPE? Just add it to PEPoshMods

Quite similar, just add the content

- Drivers
- Custom Wallpaper
- Explorer (DaRT)
- PowerShell
- PowerShell Modules


I'll come back to this, but here is how it looks in the process

- OSDrivers
- Must have Drivers
- OSExtraFiles
- Wallpaper
- OSPoshMods
- Pre-install PowerShell Modules
- OSRegistry
- Certificates
- Desktop Icons
- Theme
- Windows Explorer Default View
- OSScripts
- Execute custom PowerShell Scripts during New-OSBuild
- OSStartLayout
- Custom Start Layout Modification





Last modified 4yr ago