Commands

These are the commands that I use to generate the XML files ... they are saved locally and added to OSDBuilder and OSDUpdate
Windows Catalogs (Version 10.0)
New-OSDCatalog -WsusServer WSUS -SaveDirectory $env:TEMP -OSDeployCatalog "Windows 10"
New-OSDCatalog -WsusServer WSUS -SaveDirectory $env:TEMP -OSDeployCatalog "Windows 10 1903"
New-OSDCatalog -WsusServer WSUS -SaveDirectory $env:TEMP -OSDeployCatalog "Windows 10 Dynamic Update"
New-OSDCatalog -WsusServer WSUS -SaveDirectory $env:TEMP -OSDeployCatalog "Windows Server 2016"
New-OSDCatalog -WsusServer WSUS -SaveDirectory $env:TEMP -OSDeployCatalog "Windows Server 2019"
Windows Catalogs (Legacy)
Import-Module OSDCatalog -Force
​
New-OSDCatalog -WsusServer WSUS -SaveDirectory $env:TEMP -OSDeployCatalog "Windows 7" -GridViewGetUpdates -GridViewResults
New-OSDCatalog -WsusServer WSUS -SaveDirectory $env:TEMP -OSDeployCatalog "Windows Server 2012 R2" -GridViewGetUpdates -GridViewResults
Windows Addons (version 10.0)
Import-Module OSDCatalog -Force
​
New-OSDCatalog -WsusServer WSUS -SaveDirectory $env:TEMP -OSDeployCatalog "Windows 10 Feature On Demand"
New-OSDCatalog -WsusServer WSUS -SaveDirectory $env:TEMP -OSDeployCatalog "Windows 10 Language Packs"
New-OSDCatalog -WsusServer WSUS -SaveDirectory $env:TEMP -OSDeployCatalog "Windows 10 Language Interface Packs"
Office Catalogs
Import-Module OSDCatalog -Force
New-OSDCatalog -WsusServer WSUS -SaveDirectory $env:TEMP -OSDeployCatalog "Office 2016 32-Bit"
New-OSDCatalog -WsusServer WSUS -SaveDirectory $env:TEMP -OSDeployCatalog "Office 2016 64-Bit"
New-OSDCatalog -WsusServer WSUS -SaveDirectory $env:TEMP -OSDeployCatalog "Office 2013 32-Bit"
New-OSDCatalog -WsusServer WSUS -SaveDirectory $env:TEMP -OSDeployCatalog "Office 2013 64-Bit"
New-OSDCatalog -WsusServer WSUS -SaveDirectory $env:TEMP -OSDeployCatalog "Office 2010 32-Bit"
New-OSDCatalog -WsusServer WSUS -SaveDirectory $env:TEMP -OSDeployCatalog "Office 2010 64-Bit"
​
Docs - Previous
WSUS Server
Next - Docs
Proofing
Last updated 2 years ago