Both editions. Settings → PSADT Templates stores your organisation’s PSADT customisations as reusable templates. Templates are stored outside the toolkit folder, so they survive PSADT toolkit downloads and updates.
What a template contains #
- Support Files: copied to
SupportFiles/ - Files: copied to
Files/. A package’s own uploaded files win when the names are the same. - Assets: copied to
Assets/, for example your ownAppIcon.png. These win over the toolkit’s files. - Extensions Code: PowerShell added to
PSAppDeployToolkit.Extensions.psm1 - Script Functions: PowerShell functions added to the generated script, before the initialization section
Managing templates #
The list shows each template’s name (a star marks the default), description, contents and the date it was last modified.
| Action | Description |
|---|---|
| New Template | Enter a name and description. Save once, then add files on the Files tab and code on the Extensions Code and Script Functions tabs. |
| Edit (pencil) | Change the template |
| Set default (star) | New PSADT packages use this template automatically. Click again to clear. |
| Duplicate | Create a copy |
| Export | Download the template as a ZIP to share or archive |
| Import | Load a template ZIP. If a template with that name already exists, (imported) is added to the name. |
| Delete | Remove the template (asks for confirmation) |
Review imported templates. Template code runs with full rights in every package that uses it. An imported template is therefore never made the default automatically, and the app warns you when an imported template contains code.
Using a template in a package #
Choose the template on the Session Config step of a PSADT package, or choose None (stock toolkit). The template is applied in the script preview, in test runs, in every export (ZIP, IntuneWin, MSIX, App Attach) and in uploads.