Jeremy Fontenot / Technical portfolio
Practical administration. Documented results. Original technical evidence.
Inspect the retained identity and encryption results from a physical-device Autopilot/Intune lab. Technologies: Windows Autopilot, Intune MDM, Entra join, Windows SSO, TPM, and BitLocker.
The sanitized dsregcmd result records AzureAdJoined YES, DeviceAuthStatus SUCCESS, AzureAdPrt YES, and KeySignTest PASSED. The BitLocker result records a fully encrypted OS volume using XTS-AES 128 with Protection On.
Device join, user SSO, and encryption are distinct checks. The two linked outputs support those states. They do not independently establish every OOBE stage, app installation, compliance-policy evaluation, recovery-key escrow, or the cause of a preceding provisioning issue.
Live physical-device personal-lab validation. Secrets and unique hardware/directory identifiers are excluded or redacted. Later reconfiguration of the endpoint does not invalidate the documented completed Autopilot project.
Registry status retained in the audit: COMPLETE . Evidence below is assessed by artifact type; this package does not rerun the lab.
Sanitized post-Autopilot output records Entra join, successful device authentication, and an Azure AD PRT.
Open 01-dsregcmd-sanitized.txtconfirmed explicit dsregcmd fieldsSource: projects/windows-autopilot-intune/evidence/01-dsregcmd-sanitized.txt
SHA-256: a698bb523c1316b05fd16a069494e6582d07ba630cbeb7011964ffb7f3f63100
Retained BitLocker validation records the captured encryption and protection state; this is personal-device lab evidence.
Open 04-bitlocker-validation.txtconfirmed explicit BitLocker output; not a fleet rolloutSource: projects/windows-autopilot-intune/evidence/04-bitlocker-validation.txt
SHA-256: e3fce1f7311595fb1d650065ef0d5db5d6c0fe8cbe2b4ece133c07c015649db1
