OSConfig to PPKG

This is the Cheddar. If you have OSConfig customized to your liking . . . you can proceed to the Finish Line and create a Provisioning Package.
You can following this process or use the Microsoft Guide linked below
OSDeploy PowerShell Module
Before going any further, make sure you have the OSDeploy PowerShell Module installed, unless you want to create a CAB DDF file manually.
Convert OSConfig to CAB
Use New-CAB (OSDeploy PowerShell Module) to create a CAB from a Directory using the following command
1
New-CAB -SourceDirectory D:\DeploymentShare\OSDeploy\OSConfig
Copied!
When complete, you will have a DDF (Directive File) and CAB
Create a New Advanced Provisioning Package
Using WICD, create an Advanced Provisioning Package and enter some random details
All Windows desktop editions should work fine
Create a Provisioning Command
In the left Navigation Pane, expand ProvisioningCommands and PrimaryContext. In the Name field, enter OSConfig and press the Add button
Set the Command File
Select the Command on the Left Navigation Pane. In the Main window, Browse to OSConfig.ps1. Enter the following CommandLine
1
PowerShell.exe -ExecutionPolicy Bypass -File OSConfig.ps1
Copied!
Set the other values as shown
Add a Dependency Package
Now its time to add a Dependency Package. In the Left Navigation Pane, select DependencyPackages. In the Main window, Browse to the OSConfig.cab and press the Add button.
Export the Provisioning Package
Select Export from the top Menu and then select Provisioning package
Build Owner
Change the Build Owner to IT Admin
Build Security
Leave this blank for general Provisioning
Save Path
Set the proper location to save the Provisioning Package
Build
Build the Provisioning Package
Complete
Now you have a complete OSConfig as a Provisioning Package. You can now use this in your OS Deployments
See this link for guides on adding the Provisioning Package in the Task Sequence
​