Profiles¶
A profile describes a target machine role (e.g. "standard domain workstation for HR", "sales laptop", "kiosk"): which WIM image, which base sequence, and which default applications to use.
Profile JSON structure¶
{
"id": "profil-poste-rh",
"name": "Windows 11 Pro — HR standard workstation",
"wimImage": "Win11-Pro-23H2.wim",
"wimIndex": 1,
"sequence": "Win11-Domaine-Standard",
"defaultApps": ["app-chrome", "app-sap-gui"],
"domain": {
"name": "corp.local",
"ou": "OU=RH,OU=Postes,OU=IT,DC=corp,DC=local"
},
"locale": "fr-FR",
"autologonUser": "deploy-temp"
}
| Field | Description |
|---|---|
id |
Unique identifier, used by the API and the front-end |
name |
Display name shown in the web UI |
wimImage / wimIndex |
Which .wim file and image index to apply |
sequence |
Base sequence name (see Sequences) |
defaultApps |
Catalogue app IDs pre-selected for this profile |
domain |
Domain name and target OU for JoinDomain |
locale |
Windows locale/language to apply |
autologonUser |
Temporary account used during multi-reboot deployment |
Profiles live under Profiles/*.json and are listed by GET /api/profiles.
Testing a profile in PowerShell¶
Import-Module .\Modules\ProfileManager\ProfileManager.psm1
Get-DeployProfile -Id 'profil-poste-rh'
Test-DeployProfile -Id 'profil-poste-rh' # validates JSON + referenced WIM/sequence exist