Affected scope
project: foundry
Problem to solve
Foundry Deploy and Foundry Connect currently use the default Foundry branding in their application header/about surfaces. Administrators cannot provide their own organization logo for generated boot media.
This limits personalization for internal IT teams that want deployed WinPE tooling to clearly reflect their organization while still using Foundry.
Proposed solution
Add an optional branding setting in Foundry OSD that allows administrators to provide a custom logo asset.
The generated configuration/media should make the logo available to:
- Foundry Deploy.
- Foundry Connect.
The logo should be displayed in the application header area, near the existing menu/version/config warning information, without replacing critical status indicators.
The feature should:
- Be optional and disabled by default.
- Validate supported image formats and size limits.
- Copy the selected logo into the generated boot media assets.
- Preserve the default Foundry logo when no custom logo is configured.
- Avoid layout regressions when the logo is missing, invalid, too wide, or too tall.
- Use the same branding behavior in Deploy and Connect where possible.
Alternatives considered
Administrators could manually replace image assets in the generated media, but that is fragile, not discoverable, and can break when Foundry updates its runtime payloads.
Use case
A system administrator creates Foundry boot media for their organization and wants Foundry Deploy and Foundry Connect to show a company or IT department logo in the header. This makes the deployment experience feel more personalized and recognizable for technicians using the media.
Checklist
Affected scope
project: foundry
Problem to solve
Foundry Deploy and Foundry Connect currently use the default Foundry branding in their application header/about surfaces. Administrators cannot provide their own organization logo for generated boot media.
This limits personalization for internal IT teams that want deployed WinPE tooling to clearly reflect their organization while still using Foundry.
Proposed solution
Add an optional branding setting in Foundry OSD that allows administrators to provide a custom logo asset.
The generated configuration/media should make the logo available to:
The logo should be displayed in the application header area, near the existing menu/version/config warning information, without replacing critical status indicators.
The feature should:
Alternatives considered
Administrators could manually replace image assets in the generated media, but that is fragile, not discoverable, and can break when Foundry updates its runtime payloads.
Use case
A system administrator creates Foundry boot media for their organization and wants Foundry Deploy and Foundry Connect to show a company or IT department logo in the header. This makes the deployment experience feel more personalized and recognizable for technicians using the media.
Checklist