A short path to what you need.

Use the dedicated Add command to stage each app in WinPE. Installation runs during SetupComplete, before OOBE.

Add-OSDStageGoogleChromeEnterprise -Architecture x64
Add-OSDStageMicrosoft365Apps -Channel MonthlyEnterprise -Language en-us

Built-in integrations including Company Portal and CMTrace Open acquire content during SetupComplete and automatically refresh a connected OSDCloud cache. Use Sync commands beforehand when preparing a fully offline deployment.

A repository hosts your packages. Its catalog.json lists the available packages and their manifests. Use that file’s URL and your actual package IDs below.

Set-OSDStageConfiguration -CatalogUri 'https://example.com/catalog.json'
Add-OSDStage -Name 'MyPackage'

Catalogs and manifests use schema 2. Each package has a manifest and a SHA-256-checked Package.zip.

Connect your repository using its catalog URL first. Replace these example IDs with your own.

Add-OSDStageFont -Id 'CompanyFonts'
Add-OSDStageCertificate -Id 'CompanyRootCA'
Add-OSDStageDriver -Id 'WorkstationDrivers'

• Fonts: machine-wide TTF/OTF installation.
• Certificates: public CA certificates; machine Root or CA store, selected in the manifest.
• Drivers: import into the Windows Driver Store. Supply boot-critical drivers through Windows deployment.

Add-OSDStageEnvironmentVariable -Name DeploymentRing -Value 'Pilot'
Add-OSDStageRegistryValue -Path 'HKLM:\SOFTWARE\Company\Deployment' `
    -Name Ring -Type String -Value 'Pilot' -Registry64

Services must exist when their configuration runs. Choose startup mode and state explicitly; no recurring enforcement is added.

# Example: replace with an existing service name.
Add-OSDStageService -Name 'VendorService' -StartupType Automatic -State Running

Stage the apps first, then explicitly select their registered handlers. Users can change these defaults later.

Add-OSDStageGoogleChromeEnterprise -Architecture x64
Add-OSDStageAdobeAcrobatUnified -Architecture x64

Add-OSDStageDefaultAssociation -Identifier @('http','https') `
    -ProgId 'ChromeHTML' -AppName 'Google Chrome'
Add-OSDStageDefaultAssociation -Identifier '.pdf' `
    -ProgId 'Acrobat.Document.DC' -AppName 'Adobe Acrobat'

Handler IDs depend on the installed app. No defaults are selected automatically.

Add-OSDStageStartPins -Pins @(
    @{ desktopAppId = 'MSEdge' }
    @{ desktopAppId = 'Microsoft.Windows.Explorer' }
)
Add-OSDStageTaskbarPins -Pins @(
    @{ desktopAppId = 'Microsoft.Windows.Explorer' }
)

Use IDs for apps installed on the device. Start uses an initial layout; taskbar configuration replaces default pins, but Windows or apps can add pins separately.

# Select an existing profile file.
$profile = Read-Host 'Full path to the Wi-Fi XML export'
Add-OSDStageWiFiProfile -Path $profile

Supports WPA2-Personal, WPA3-Personal and open profiles. Enterprise/EAP is outside scope. A working Wi-Fi adapter and driver are required.

The runtime removes its credential-bearing configuration after the import attempt. Keep your original XML private; OSDStage does not delete that source file.

Choose exact feature or capability names supported by the target Windows version.

Add-OSDStageWindowsCapability -Name 'XPS.Viewer~~~~0.0.1.0' -Action Add
Add-OSDStageWindowsCapability -Name 'OpenSSH.Client~~~~0.0.1.0' -Action Remove

Add-OSDStageWindowsFeature -Disable WorkFolders-Client

Capability additions may need Windows Update during SetupComplete. Windows optional features use the separate Add-OSDStageWindowsFeature command. Neither flow forces a restart or schedules a retry.

Choose exact provisioned package names. This example requests removal of Solitaire.

Add-OSDStageWindowsInboxCleanup -Remove Microsoft.MicrosoftSolitaireCollection

Add -DiagnoseOnly to report the selection without removing it during SetupComplete.

An attached volume labeled OSDCloud is detected automatically. Repository content is acquired while staging; most vendor content is acquired in full Windows. The drive letter can change.

Sync-OSDStageGoogleChromeEnterprise -Architecture x64
Sync-OSDStageAdobeAcrobatUnified -Architecture x64

Test-OSDStageDeployment -RequireOfflineReady -ThrowOnFailure

For disconnected deployments, prepare every selected variant first. A successful online staging check alone does not establish offline readiness.