Managed profiles not loading
Symptoms
- The IT-managed profiles you published don't appear in users' Deck.
- Only some managed profiles appear.
- The profile list is empty even though
ProfileManagementModeisAdminOnly.
Solutions
Confirm the policy value
Check that ManagedProfilesPath actually reached the client and points where you expect:
(Get-ItemProperty "HKLM:\SOFTWARE\Policies\Vediram\Deck").ManagedProfilesPath
(Get-ItemProperty "HKCU:\SOFTWARE\Policies\Vediram\Deck" -ErrorAction SilentlyContinue).ManagedProfilesPath
If it's missing, the policy isn't applying - see Group Policy settings not applying.
Confirm the client can read the file
The path must resolve from the client, as the user (or SYSTEM) running Deck. Test it in the same context:
Test-Path "\\fileserver\deck$\profiles.json"
Get-Content "\\fileserver\deck$\profiles.json" -Raw
A UNC path requires the client to have network access and read permission to the share. Machines that are off-network at Deck startup won't load the profiles.
Validate the JSON
An invalid file is skipped. Verify it parses and matches the schema:
Get-Content "\\fileserver\deck$\profiles.json" -Raw | ConvertFrom-Json
Each profile needs name, mode (allow or deny), and an addins array. See Managing Profiles Centrally for the full schema.
Check the daemon log
Parse errors and unreachable paths are logged:
Select-String -Path "$env:LOCALAPPDATA\Vediram\Deck\core.log" -Pattern "ManagedProfiles"
Remember when profiles load
Deck loads managed profiles when the Core daemon starts. After changing the file or the policy, refresh policy and restart Deck:
gpupdate /force
Stop-Process -Name Vediram.Deck.Core, Vediram.Deck -Force -ErrorAction SilentlyContinue
"Allow" profiles that look empty
A managed profile with mode: allow only enables add-ins that are actually present on that machine. If a machine doesn't have any of the listed add-ins, the profile enables nothing - this is expected, not a failure. Confirm the target machines have the add-ins (by ProgID) you listed.