Home

Autopilot Self deploying mode suddenly fails with Windows 1903

%3CLINGO-SUB%20id%3D%22lingo-sub-1069376%22%20slang%3D%22en-US%22%3EAutopilot%20Self%20deploying%20mode%20suddenly%20fails%20with%20Windows%201903%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1069376%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3EThis%20week%20began%20we%20experiencing%20strange%20behaviour%20and%20constant%20autopilot%20failures%20in%20the%3C%2FP%3E%3CP%3Escenario%20that%20has%20worked%20like%20a%20charm%20until%20now.%20Last%20week%20was%20everything%20fine.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECase%20description%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1.%20Deploy%20Windows%201903%20Finnish%20with%20December%202019%20CU.%3C%2FP%3E%3CP%3E2.%20Installation%20takes%20place%20with%20a%20USB%20stick%20provided%20with%20a%20simple%20autounattend.xml.%3C%2FP%3E%3CP%3E3.%20After%20OS%20deployment%20collect%20and%20upload%20autopilot%20info%20to%20Autopilot%20service%20successfully.%3C%2FP%3E%3CP%3E4.%20Finally%20Sysprep.exe%20%2Foobe%20%2Fshutdown.%3C%2FP%3E%3CP%3E5.%20Concerns%20at%20least%20two%20HP%20laptop%20models%20that%20have%20TPM%202.0%20%2B%20attestation%20feature.%3C%2FP%3E%3CP%3EConcerns%20at%20least%207%20computers%3B%20in%20fact%20any%20computer%20that%20is%20tested.%3C%2FP%3E%3CP%3EWhen%20re-installing%20any%20device%3A%20delete%20records%20from%20AzureAD%2CIntune%2CAutopilot%20Service.%3C%2FP%3E%3CP%3E6.%20Stops%20in%20Enrollment%20Status%20Page%3A%20Failed%3A3%200x801C0003.%3C%2FP%3E%3CP%3E7.%20in%20the%20collected%20logs%20I%20can%20see%20%22No%20valid%20EK%20certs%20found%22%20that%20refers%20to%20TPM%20and%20attestation%20problem.%3C%2FP%3E%3CP%3E8.%20Tested%20time%20sync%20during%20OOBE.%3C%2FP%3E%3CP%3E9.%20TPM%20chipset%20manufacturer%20is%20Infenon.%20Tested%20connection%20to%20pki.infenion.com%20that%20is%20functional.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20want%20underline%20that%20independent%20of%20model%2C%20device%20or%20even%20Azure%20tenant%20this%20behaviour%20has%20been%20recongnized%20first%20time%20this%20week%20Monday.%20The%20OSD%20setup%20itself%26nbsp%3B%20is%20the%20same.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnyone%20else%20experiencing%20similar%20behaviour%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1069376%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EIntune%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMobile%20Device%20Management%20(MDM)%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1071690%22%20slang%3D%22en-US%22%3ERE%3A%20Autopilot%20Self%20deploying%20mode%20suddenly%20fails%20with%20Windows%201903%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1071690%22%20slang%3D%22en-US%22%3EIt%20turned%20that%20the%20recent%20Intune%20Service%20update%20(1912)%20caused%20this%20issue.%20It%20concerned%20especially%20Self%20deploying%20mode%20and%20white%20glove%20processes.%20Root%20cause%3A%20%22A%20recent%20standard%20service%20update%20contained%20a%20code%20regression%20that%20impacted%20Windows%20Autopilot.%22%3C%2FLINGO-BODY%3E
Sami_S755
New Contributor

Hello,

This week began we experiencing strange behaviour and constant autopilot failures in the

scenario that has worked like a charm until now. Last week was everything fine.

 

Case description:

 

1. Deploy Windows 1903 Finnish with December 2019 CU.

2. Installation takes place with a USB stick provided with a simple autounattend.xml.

3. After OS deployment collect and upload autopilot info to Autopilot service successfully.

4. Finally Sysprep.exe /oobe /shutdown.

5. Concerns at least two HP laptop models that have TPM 2.0 + attestation feature.

Concerns at least 7 computers; in fact any computer that is tested.

When re-installing any device: delete records from AzureAD,Intune,Autopilot Service.

6. Stops in Enrollment Status Page: Failed:3 0x801C0003.

7. in the collected logs I can see "No valid EK certs found" that refers to TPM and attestation problem.

8. Tested time sync during OOBE.

9. TPM chipset manufacturer is Infenon. Tested connection to pki.infenion.com that is functional.

 

I want underline that independent of model, device or even Azure tenant this behaviour has been recongnized first time this week Monday. The OSD setup itself  is the same.

 

Anyone else experiencing similar behaviour ?

 

1 Reply
Highlighted
It turned that the recent Intune Service update (1912) caused this issue. It concerned especially Self deploying mode and white glove processes. Root cause: "A recent standard service update contained a code regression that impacted Windows Autopilot."
Related Conversations
Autopilot and sccm issue
zolabus in Microsoft Intune on
1 Replies
Company Portal Failing to Install - 0x80073CF0
nitvit610 in Microsoft Intune on
1 Replies
App has been blocked by system admin
nitvit610 in Microsoft Intune on
1 Replies