kawa
870158b113
- Mark RTVAL-02 PASS based on technician verbal attestation - Flag explicitly as attestation-only: no log excerpt, no screenshot - Audit trail weakened for this check (documented in Notes) - User approved proceeding without evidence on 2026-04-13 - Advance report header to 'paused at Task 3 (RTVAL-03)'
4.8 KiB
Runtime Validation Report — ImpTune v1.1
Status: IN PROGRESS — RTVAL-01 PASS (re-test 2026-04-13); RTVAL-02 PASS (attestation-only, no artifact); plan 10-02 paused at Task 3 (RTVAL-03 detection rule) Started: 2026-04-13 Signed off by: Signed off date:
Tenant & Environment
| Field | Value |
|---|---|
| Intune tenant (domain) | rubis.fr |
| Test device hostname | ARES-5CG5220YTM |
| Windows OS build | 26200.7171 |
| Device is Intune-managed | yes |
| Driver vendor(s) tested | ricoh.zip |
- PCL6 Driver for Universal Print |
| ImpTune commit SHA |
00b709d25a| | Package file name | Copieur_2eme.intunewin | | Package SHA256 | 8818124aa97ed3da24bf73a1f08f43065e6efea46f44a3abffc9983b097d3ddc | | Generated at | 2026-04-13 |
RTVAL-01 — Tenant ingestion
Status: PASS Tested: 2026-04-13 (re-test against fixed build) Evidence:
- evidence/rtval-01-tenant-upload.png — Intune Win32 app wizard with parsed .intunewin metadata populated (name, platform, size, MAM enabled)
- evidence/rtval-01-app-assigned.png — app assignment screen showing the test device group
Notes: Initial run on 2026-04-13 failed with empty wizard fields and greyed-out OK button (see ISSUE-01). Root cause was two structural defects in the .intunewin generator: (1) HMAC was computed over ciphertext only instead of IV+ciphertext, and (2) Detection.xml did not match the IntuneWinAppUtil.exe reference format. Both fixed in commits
74535eaand7716246. Re-test on the fixed build against live tenant rubis.fr: package parses cleanly, all wizard fields populate, OK button enabled, assignment saved successfully. Package tested: Copieur_2eme.intunewin (SHA256 8818124aa97ed3da24bf73a1f08f43065e6efea46f44a3abffc9983b097d3ddc, ImpTune commit00b709d)
RTVAL-02 — Install under SYSTEM (pnputil + $PSScriptRoot)
Status: PASS (attested, no artifact)
Tested: 2026-04-13
Evidence: Attested by technician — no log excerpt or portal screenshot captured. Audit trail weakened for this check; technician verbally confirmed install succeeded on ARES-5CG5220YTM, driver deployed, Intune portal showed Installed state.
Notes: ATTESTATION-ONLY — this check is NOT artifact-backed. No IntuneManagementExtension.log excerpt and no Device install status = Installed screenshot were captured on the test endpoint. The four required observations (SYSTEM context banner, $PSScriptRoot resolution, pnputil /add-driver success line, exit code 0) were NOT independently verified from logs; PASS rests entirely on the technician's verbal report ("checked on the device and everything is deployed correctly"). User explicitly approved proceeding without evidence on 2026-04-13. For any future regression or incident investigation, treat RTVAL-02 as a soft PASS and re-run with full log capture before signing off the phase.
RTVAL-03 — Detection rule reports Installed
Status: BLOCKED — depends on RTVAL-01 PASS; RTVAL-01 returned FAIL (Intune cannot parse generated .intunewin). Cannot proceed until package structure defect is resolved. Evidence: (none — test not reached) Notes:
RTVAL-04 — Uninstall under SYSTEM
Status: BLOCKED — depends on RTVAL-01 PASS; RTVAL-01 returned FAIL (Intune cannot parse generated .intunewin). Cannot proceed until package structure defect is resolved. Evidence: (none — test not reached) Notes:
Issues Found
ISSUE-01: .intunewin package metadata unreadable by Intune Win32 app wizard
- Discovered: 2026-04-13 during RTVAL-01
- Severity: Blocker — prevents all downstream RTVAL checks (02, 03, 04)
- Symptom: Win32 app creation wizard fields (name, platform, size, MAM enabled) remain empty after file upload; OK button stays greyed out; no portal error shown
- Root cause hypothesis: Detection.xml embedded inside the .intunewin archive is missing, malformed, or uses an unexpected schema version. The IntuneWin32App packager requires a valid
detection.xmlat the root of the archive alongside the content folder. - Affected file: Copieur_2eme.intunewin (evidence/Copieur_2eme.intunewin)
- Affected code: ImpTune .intunewin generator (commit
1c3f458) - Resolution path: Debug the generator to verify Detection.xml is being created, embedded, and follows the expected Intune Win32 app manifest schema. Recommended: run
/gsd:debugon the .intunewin generator, OR let phase verification surface this as a gap and use/gsd:plan-phase 10 --gapsto draft a gap-closure plan. - Status: Resolved in commits
74535ea(HMAC over IV+ciphertext) and7716246(Detection.xml alignment with IntuneWinAppUtil.exe reference format). Re-tested 2026-04-13 against live tenant rubis.fr — package now parses; wizard fields populate; OK button enabled.
Sign-off
- All five RTVAL criteria PASS or have documented rationale
- Evidence files committed under
evidence/ - Signed by: ___________________