Forum Discussion

nitin4492's avatar
nitin4492
Copper Contributor
Jul 01, 2025

SCCM Client timed out during Autopilot ESP Device Preparation Phase

Hello Team,

For specific middle east IT Region, we have been getting strange issues where all autopilot devices are trying to install sccm client but gets failed in last step of Device Preparation with error code - (0x800705b4).

Earlier, we had co-management policy in Intune under enrollment. It was used to install sccm client with cmg server for autopilot provisioned devices. But it was already removed after decommissioned sccm infrastructure.

We have already raised MS Case for our tenant and we are not getting any proper assistance from Microsoft support.

We have some workaround to change Install state to 3 for Config mgr key under ESP tracking and then sccm client installation is not tracked by ESP.

We are not sure how this sccm client installation policy had been initiated in ESP when we don't have any such pol in our tenant.

Can anyone from Microsoft engineering team help us out on this problem?

 

Intune
mobile device management (mdm)

4 Replies

    • nitin4492's avatar
      nitin4492
      Copper Contributor
      Jul 02, 2025

      Thanks for comment Rahul.

      We have single ESP profile in production and issue impacted for specific region only.

      As a workaround, we have created comanagent policy under Devices->Enrollment -> Co-management  to disallow client installation and this is working fine.

      But we need to understand from Microsoft on where this client installation is triggered where we don't have any such policy\application\scripts etc.

      • rahuljindal's avatar
        rahuljindal
        Bronze Contributor
        Jul 02, 2025

        Sounds like a bug to me. I’ll suggest to open a case with MS. I’ll also encourage you to test with a fresh ESP as I have come across with policy related issues in ESP in the past. 

    • nitin4492's avatar
      nitin4492
      Copper Contributor
      Jul 01, 2025

      Thanks Rahul for reply. We do have single production ESP profile where no sccm client package is included. Is it needed to try creating new ESP profile?
      We have got one workaround to create co-management policy with below option to disallow sccm client installation and it is working fine.

      But we need to check from Microsoft  that how this sccm client installation is initated?