Apply Intune configuration profile changes after AutoPilot device enrollement?

net1994 131 Reputation points
2021-03-31T14:09:15.927+00:00

Hello all,

We have started our AutoPilot testing. So far, so good. However when we change a configuration profile in Intune, the AutoPilot systems don't seem to take the new change. During provisioning/enrollment, they get everything fine. We tried removing the PC from the group and re-adding to get the updated profile, but the system didn't get the change. We assumed as with AD GPOs, policy changes should apply after a pc checks into the domain controller on a regular interval.

Thoughts?

Microsoft Intune Configuration
Microsoft Intune Configuration
Microsoft Intune: A Microsoft cloud-based management solution that offers mobile device management, mobile application management, and PC management capabilities.Configuration: The process of arranging or setting up computer systems, hardware, or software.
1,708 questions
Microsoft Intune
Microsoft Intune
A Microsoft cloud-based management solution that offers mobile device management, mobile application management, and PC management capabilities.
4,306 questions
0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Jason Sandys 31,151 Reputation points Microsoft Employee
    2021-03-31T16:37:00.557+00:00

    What profile type exactly are you changing?

    In general, changes should be immediate (taking into account network latencies of course). See https://learn.microsoft.com/en-us/mem/intune/configuration/device-profile-troubleshoot for details.

    0 comments
  2. Crystal-MSFT 42,631 Reputation points Microsoft Vendor
    2021-04-01T04:09:09.88+00:00

    @net1994 , Thanks for posting in our Q&A. From your description, I know that once we configured the configuration profile, the Autopilot didn’t work anymore. If there's any misunderstanding, feel free to let us know.

    Based on my research, some policy settings can cause conflicts with Windows Autopilot. Please go through the following link and check if there's any conflict setting configured in our environment:
    https://learn.microsoft.com/en-us/mem/autopilot/policy-conflicts

    Hope it can help

    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

  3. Crystal-MSFT 42,631 Reputation points Microsoft Vendor
    2021-04-07T09:04:21.037+00:00

    @net1994 Thanks for your reply. I know the Autopilot enroll is successful but the device configuration policy seems not be applied.

    To check our issue, could you please collect the following information for us?

    1. Could you go to Devices > Configuration profiles > find the affected configuration profile and get a screen shot of the Properties . Get a screen shot of the setting and let us know what is the changed settings ? Also check the device status under here.
      85234-image.png
      Device Status:
      85247-image.png
    2. Go to troubleshooting + support, select the affected user and check if there’s any device configuration profile related log there.
      85159-image.png
      Note: To protect our environment, please remove any privacy.

    3.Go to affected device to check device management event log to see if there's any error with the device configuration policy. Location: "even viewer"->Applications and services logs > Microsoft > Windows > DeviceManagement-Enterprise-Diagnostics-Provider-> Admin options.

    4,Check if sync is successful on the client side, please open Settings > Accounts > Access work or school, click and open the Info option in your Azure AD account. In Device sync status, you can see if the sync was successful. If not, please click Sync to do the sync action manually and wait to be applied.

    Please check the above information and if there’s anything unclear, feel free to let us know.

    0 comments