Public log
Corrections
When a published KBY Technologies page turns out to be wrong or unsafe, it is corrected or taken down, and the change is listed here, newest first, with the date (UTC), what was wrong and what changed.
Where a sweep corrected many pages at once, the entry gives the count and names only the pages the change record names. Withdrawn pages are not linked because they no longer load.
Found something wrong? Use Report a problem at the end of any article. Reports go to the site owner and are used to correct pages.
Withdrawn. Its remediation script reassigned every stalled device to a different MDM server with no person approving it and no limit per run, which could move devices away from another team's or tenant's server. It may return once that step needs a person's approval.
- Fixing Stalled Automated Device Enrollment Loops for Goodpost 2269/ops-playbook/macos-device-management/fixing-stalled-automated-device-enrollment-loops-for-good
Step 3 now says to back up the BitLocker recovery key and local administrator credentials before a Retire, because a Retire removes the Entra ID record of an Entra-joined device that is not registered in Autopilot. Step 4 now deletes the device from Intune before deregistering it from Autopilot.
Vendor documentation the correction relied on
Steps 4 and 6 gained the same note about what a Retire does to an Entra-joined device, and the hybrid Remove-ADComputer step now says to back up any BitLocker recovery information held in Active Directory first. That step is marked untested.
Vendor documentation the correction relied on
The rollback section offered Retire for lost or compromised devices. It now names Wipe for them, says what a Retire does to an Entra-joined device, and says to back up the BitLocker recovery key and local administrator credentials first.
Vendor documentation the correction relied on
An undefined pilot drill, "revoke and reissue a device from the console", was removed. Step 3 now warns against using device-record deletion in Kandji or certificate revocation in Jamf as drills.
The "Apple ID ownership loss" failure mode treated every lost account as needing a new push certificate and a full re-enrolment. It now separates an account that can be recovered (recover it, then renew) from one that is gone.
Withdrawn. Its Stage 3 runbook deleted every managed device idle for 60 days, on every platform, with no scoping.
- Automating Stale Device Cleanup and Alerts in Intunepost 2277/graduate/automation-and-service-operations/automating-stale-device-cleanup-and-alerts-in-intune
Withdrawn. Its rollback deleted a batch of Entra ID device objects, which cannot be undone and deletes their BitLocker recovery keys.
- Deploying Windows Autopilot Device Preparation for New Hirespost 2536/graduate/endpoint-and-device-management/deploying-windows-autopilot-device-preparation-for-new-hires
Vendor documentation the correction relied on
Withdrawn. Step 7 ran profiles renew -type enrollment across a whole Smart Group as a routine check-in.
- Ending macOS Password Lockout Tickets With Bootstrap Token Auditspost 2056/ops-playbook/macos-automation-scripting/ending-macos-password-lockout-tickets-with-bootstrap-token-audits
Withdrawn. Stage 6 decommissioned AD FS on a time gate alone, without first checking that no relying party still had traffic, and Stage 1 removed "orphaned SIDs" with no definition and no backup.
- Zero-Downtime Cloud Identity Migration from ADpost 364/tech-fundamentals/zero-downtime-cloud-identity-migration-from-ad
A failure-table row told readers to remove the device's Entra ID record, with no exception for Autopilot devices and no warning that deleting a device also deletes its BitLocker keys and cannot be undone. The row now covers both. (The page was withdrawn the same day; see the entry above.)
- Automating Stale Device Cleanup and Alerts in Intunepost 2277/graduate/automation-and-service-operations/automating-stale-device-cleanup-and-alerts-in-intune
Vendor documentation the correction relied on
Step 5 deleted the device's Entra ID object with Remove-MgDevice, and the rollback said it could be restored. Deleted devices cannot be recovered, so the deletion step was removed and the rollback corrected.
Vendor documentation the correction relied on
The earlier correction told readers never to delete any device's Entra ID object by hand. That advice is now limited to devices registered in Windows Autopilot, which is what Microsoft's guidance covers.
Vendor documentation the correction relied on
The guide told readers to delete the device's Entra ID object by hand, to deregister it from Autopilot without first deleting it from Intune, and to Retire a lost or stolen device. It now deletes the device from Intune first, names Wipe for lost or stolen devices, and no longer deletes the Entra ID object by hand.
Vendor documentation the correction relied on