psadt-deploy-skill 0.30.0 → 0.30.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +20 -12
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -352,7 +352,7 @@ psadt-deploy/
|
|
|
352
352
|
│ ├─ switch-catalog/ engine defaults + JSON schema (App. L.0)
|
|
353
353
|
│ ├─ Report-Template.html the fixed dossier template
|
|
354
354
|
│ └─ app-registration.md THE Graph permission matrix + manual portal route
|
|
355
|
-
└─ tests/ Pester suite,
|
|
355
|
+
└─ tests/ Pester suite, 552 tests
|
|
356
356
|
```
|
|
357
357
|
|
|
358
358
|
Machine-local state lives outside the skill folder:
|
|
@@ -434,6 +434,25 @@ The two most recent releases are below. **[CHANGELOG.md](CHANGELOG.md)** carries
|
|
|
434
434
|
every release since 0.1.0, and nothing is ever removed from it - this section is a window onto it, not a
|
|
435
435
|
second copy to keep in sync.
|
|
436
436
|
|
|
437
|
+
### 0.30.1 - 2026-09-14
|
|
438
|
+
- **Fixed: a scheduled task will not start on battery.** `schtasks /Create` defaults
|
|
439
|
+
`DisallowStartIfOnBatteries` and `StopIfGoingOnBatteries` to TRUE, so on an unplugged laptop the task is
|
|
440
|
+
created, `/Run` returns 0, and it then sits at status **Queued** forever. Every action reported a bare
|
|
441
|
+
timeout that named no cause, and the failure followed the POWER CABLE rather than the package. The task
|
|
442
|
+
is registered from XML now, which also drops the 72-hour execution limit `/Create` imposes.
|
|
443
|
+
- **Fixed: a leftover `WindowsSandboxServer` silently broke every later run** (Windows-Sandbox#124). The
|
|
444
|
+
next sandbox came up and its scheduled tasks never executed, so a different pre-check timed out each
|
|
445
|
+
time and it read as flakiness. Broker-without-VM is now cleared at start instead of being reported as
|
|
446
|
+
"a sandbox is already running", which it is not.
|
|
447
|
+
- **Fixed: the timeout diagnostics answered their own cleanup** - they ran after the task was deleted and
|
|
448
|
+
read the process table through WMI, which is broken in the guest until GuestPrepare repairs it.
|
|
449
|
+
- **Added: an ARP dump whenever detection contradicts the action**, covering both HKLM views and every
|
|
450
|
+
`HKEY_USERS` subtree. It found the trap below in a single run. The progress window now also lists what
|
|
451
|
+
has already passed, with a tick per completed step.
|
|
452
|
+
- **Note: an EXE installer that can install per-user must be forced to per-machine** (App. L.7, BINDING).
|
|
453
|
+
Greenshot 1.3.315 without `/ALLUSERS` installed into the SYSTEM profile and registered under
|
|
454
|
+
`HKEY_USERS\S-1-5-18`; install, uninstall, reinstall and repair all returned exit 0 while an HKLM
|
|
455
|
+
detection rule correctly said "absent". With `/ALLUSERS` the full gate is GREEN. Suite 551 -> 552.
|
|
437
456
|
### 0.30.0 - 2026-09-14
|
|
438
457
|
- **Fixed: the sandbox could not test a heavy package - and it was never the package.** Smart App Control
|
|
439
458
|
is enabled in the Windows Sandbox base image while Defender is disabled, so `wintrust` asks the disabled
|
|
@@ -456,14 +475,3 @@ second copy to keep in sync.
|
|
|
456
475
|
catalog, not an application catalog, and **winget stays opt-in** including as a research source.
|
|
457
476
|
- **Faster:** staging 481 MB into the guest via `robocopy /MT` (3.6 s to 0.6 s), `-Scenarios` for partial
|
|
458
477
|
iteration runs, per-action timeout default 900 s to 600 s. Suite 503 -> 551.
|
|
459
|
-
### 0.29.1 - 2026-09-14
|
|
460
|
-
- **Fixed: Phase 5.5 mapped `Remove-MSIApplications` to `Remove-ADTApplication`**, which v4 does not
|
|
461
|
-
have - the v4 name is `Uninstall-ADTApplication`. The table's right column is now checked against the
|
|
462
|
-
installed toolkit's `FunctionsToExport`.
|
|
463
|
-
- **Fixed: Appendix A named 60012 as the v4 deferral code.** 4.1.x exits a deferral with
|
|
464
|
-
`UI.DeferExitCode`, default 1602. Deliberately NOT added to the mandatory Intune table - every install
|
|
465
|
-
command this skill writes runs `-DeployMode Silent`, where a deferral cannot happen.
|
|
466
|
-
- **Fixed: the Phase 4.3 MSI sample** put the `.mst` in `SupportFiles\` and passed an `-ArgumentList`
|
|
467
|
-
identical to the config defaults. The `.mst` belongs in `Files\` next to the MSI (`TRANSFORMSSECURE=1`);
|
|
468
|
-
extra properties go into `-AdditionalArgumentList`, because `-ArgumentList` REPLACES the defaults.
|
|
469
|
-
- **Fixed: README claimed 441 Pester tests** in three places. Suite 501 -> 503.
|