INTUNE 0x87D1041C — VALIDATION WORKSHEET
Prepared: 17 October 2026 | Tiago Carvalho
This is a blank case worksheet, not a record of a completed tenant test.

IDENTIFY
App name / app ID:
App type (Win32 / Store / MSI LOB / other):
Device name / managed-device ID:
Windows build / IME version:
Assignment intent and scope:
Install behavior:
Package version and intended installed version:
Portal status and timestamp (include time zone):

BASELINE EVIDENCE
[ ] Capture current install command and return-code handling.
[ ] Capture detection rule or script before the change.
[ ] Record actual marker, path, version, identity and architecture.
[ ] Preserve relevant app-ID/time-window logs and installer log.
[ ] Correlate installer completion, post-install detection and reporting.

ONE TARGETED CORRECTION
Cause supported by evidence:
Rule or wrapper change:
Pilot scope / test owner:
Saved rollback configuration:
Change time (include time zone):

VALIDATION
[ ] Correct version: positive detection and functional check.
[ ] Missing marker: negative detection, in a disposable test environment.
[ ] Below-minimum version: negative detection.
[ ] Minimum accepted version: positive detection.
[ ] Newer version: result agrees with the approved update policy.
[ ] For scripts, capture exit code, STDOUT and STDERR separately.
[ ] Fresh IME processing uses the changed configuration.
[ ] Portal result matches that processing for the same app and device.
[ ] No unexplained new install attempts in the observed follow-up period.

RESULT
Local processing timestamp:
Portal result timestamp:
Evidence locations:
Unresolved observations:
Decision and next review:

PUBLICATION CAPTURES (if documenting the case)
1. Failed app row with type and timestamp.
2. Original detection rule.
3. Actual installation marker and version.
4. Relevant log excerpt for the same attempt.
5. Corrected rule and controlled test result.
6. Fresh installed status for the same app/device.
Hide account headers, tenant identifiers, unrelated user data and credentials.