d185e2b810
Every imaging investigation so far has meant walking to a bay and hand-copying files, and each time discovering another thing we wished we had grabbed at the same moment. This takes the lot. Read-only; changes nothing. Collects: computer name (active AND pending, which is how you tell whether the package's H<serial> -> F<serial> rename has landed or is still queued for the next reboot), dsregcmd enrollment state, the package self-checks, installed applications, everything that starts by itself, kiosk shortcut targets, Edge policy, GE-Enforce config, drivers, disk, network, provisioning sessions, and the whole of C:\Logs, Panther and the provisioning data plus the diagnostics evtx. Two things it does deliberately: Autostart is captured across all four surfaces - Run/RunOnce in BOTH registry views, all Startup folders, non-Microsoft scheduled tasks, and auto-start services outside C:\Windows. That combination is what identifies which installer planted a given autostart entry. A 32-bit installer's Run key lands under Wow6432Node where 64-bit tooling never looks, which is exactly how the old Dashboard/Lobby autostart survived an earlier purge. It TESTS the ShopDB GE-Enforce API rather than just reporting config. Config on disk proves nothing - a client can be present, configured, and never once succeed. It reports whether a client exists at all, whether anything is scheduled to run it, the configured base URL, and then actually probes the endpoint. A 401 is a good result: it proves DNS, routing and TLS work and the service answered. Only a timeout or DNS failure means unreachable. No token is sent. Deliberately avoids Win32_Product - querying it triggers an MSI reconfigure of every installed product, which is slow and can change the machine. Run it BEFORE lockdown. What it captures is known-CURRENT, not known-good: a bay straight off the line carries applications that should not be there, because preinstall.json entries without a PCTypes filter install everywhere. The point is to have an exact record of what imaging really produces so the unnecessary items can be identified and filtered. After lockdown you cannot tell whether something is absent because lockdown removed it or because imaging never installed it. Staged on the enrollment share alongside the other shopfloor-setup scripts.
17 KiB
17 KiB