Home / server / Questions / 934565
Accepted
Nathan Hartley
Asked: 2018-10-09 13:23:45 +0800 CST

How does one build an Intune AutoPilot ready device, using SCCM, without it becoming Co-Managed?

  • 772

I would like to build devices using SCCM, much like they arrive new, for Intune AutoPilot deployments. It seemed simple enough. I created a generic Task Sequence, Then wrote a script which uninstalls the SCCM Client, gathers the device's hardware ID and then, runs "sysprep /oobe /shutdown". This script runs once the Task Sequence completes, using the Task Sequence Variable "SMSTSPostAction". All of this works beautifully, until the machine is joined to Azure AD via AutoPilot. My first sign of trouble was that the Intune Policies would not apply. I then found this message when looking at the device in Intune:

Co-management
<UserName>'s Windows PC is being co-managed between
Intune and Configuration Manager. Configuration Manager agent state is
shown below, if the state is anything other than “Healthy” there are a
few steps that help with this. 

Configuration Manager agent state
Could not connect

Details
The Configuration Manager client is currently unable to reach
the Configuration Manager management point. Make sure the client can
communicate with the server. For more information on client
communication issues, see the CcmMessaging.log, LocationServices.log,
or ClientLocation.log files on the Configuration Manager client.

Is it possible to create Intune only devices, ready to be AutoPiloted, with SCCM? If so, how?

sccm

1 Answers

  1. Best Answer

    Announced at Ignite, Windows 10 1809 will make it possible to create AutoPilot ready machines with SCCM. The secret is the ability to place a special AutoPilot configuration file on the newly imaged device, without having to install the SCCM Client.

    The article "Speeding up Windows Autopilot for existing devices" breaks down the process this way:

    1. Boot to Windows PE (no data migration steps, we assume OneDrive for Business already has the data in the cloud).
    2. Format and partition the drive (so this is clearly a wipe-and-load process, not an in-place upgrade – all data, apps, settings, etc. are cleaned from the drive).
    3. Apply the new Windows 10 OS image.
    4. Inject drivers into the applied Windows 10 installation.
    5. Copies an Autopilot configuration file into the proper location in the Windows folder structure (this enables an Autopilot user-driven experience without harvesting and uploading the hardware hash in advance).
    6. Boot into Windows 10.
    7. Install the ConfigMgr client.
    8. Sysprep the Windows 10 OS.
    9. Reboot into Windows 10 OOBE.

    More information can be found here:

    • 1