Each imaging PC type owns a GE-Enforce install manifest. Edit the draft, then Publish to ship it to PCs. Nothing reaches a PC until you publish.
A manifest is the desired state for a PC type - the list of what should be installed. shopdb serves it; each PC checks itself every cycle and re-installs anything that drifted (uninstalled, corrupted, or overwritten). That is the "self-heal".
Each entry is one action (install an app, copy a file, write a registry value, run a script) plus a detection rule that tells the PC whether it is already correct - if not, the action runs. Entry order is execution order.
Targeting narrows an entry: the fleet-wide
common manifest uses PC types to hit a subset; a per-type
manifest already only runs on its own type, so it shows just the niche
gate it needs (CMM version, a bay number, a subtype).
Full guide: docs/GE-ENFORCE.md.
{{ scopeSummary }}
| Version | Published | Notes | |
|---|---|---|---|
| v{{ version.versionnumber }} current | {{ formatDate(version.publishedat) }} | {{ version.notes }} | |
| No published versions. | |||
Order is execution order. Put config-restore entries after their installer.
| Order | Type | Entry | |
|---|---|---|---|
| {{ entry.Type }} |
{{ entry.Name }}
{{ describeEntry(entry) }}
|
||
| No entries. | |||
Install counts for entries linked to a tracked application, from the computers collector. Only entries with a tracked app appear.
| Entry | Tracked app | Expected version | Installed | On expected version | Note |
|---|---|---|---|---|---|
| {{ row.entryname }} | {{ row.appname }} | {{ row.expectedversion || '-' }} | {{ row.installedcount === null ? '-' : row.installedcount }} | - {{ row.versionmatchcount }} | {{ row.coveragenote }} |
| No entries are linked to a tracked application yet. | |||||