Upravit

Sdílet prostřednictvím

Troubleshoot co-management workloads

  • Článek

This article helps you understand and troubleshoot issues that you may encounter when you configure workloads in an Intune and Configuration Manager co-management environment. For more information about how to configure workloads, see Support Tip: Configuring workloads in a co-managed environment.

Before you start

Before you start troubleshooting, it's important to collect some basic information about the issue and make sure that you follow all required configuration steps. This helps you better understand the problem and reduce the time to find a resolution. To do this, follow this checklist of pre-troubleshooting questions:

Most issues occur because one or more of these steps were not completed. If you find that a step was skipped or was not completed successfully, check the details of each step.

Frequently asked questions

What roles do I need to configure co-management?

Here are the required permissions and roles to configure co-management.

What log can I use to validate workloads and determine where policies and apps come from in a co-management scenario?

You can use the following log file on Windows 10 devices:

%WinDir%\CCM\logs\CoManagementHandler.log

What workloads are currently supported by co-management?

You can find the supported workloads here.

Which workload does the resource access policies workload belong to?

The resource access policies workload is part of the device configuration workload.

What logs can be used to verify that workloads are working correctly?

You can use the following logs in the %WinDir%\CCM\logs\ folder on the Windows 10 devices:

  • CoManagementHandler.log

    This file logs the processing of the configuration and the MDM information related to the device.

    Sample log snippet:

    Processing GET for assignment (ScopeId_<scope ID>/ConfigurationPolicy_<policy ID>)
    Getting/Merging value for setting 'CoManagementSettings_AutoEnroll'
    Merged value for setting 'CoManagementSettings_AutoEnroll' is 'true'
    Getting/Merging value for setting 'CoManagementSettings_Capabilities'
    Merged value for setting 'CoManagementSettings_Capabilities' is '7'
    Getting/Merging value for setting 'CoManagementSettings_Allow'
    Merged value for setting 'CoManagementSettings_Allow' is 'true'
    State ID and report detail hash are not changed. No need to resend. Machine is already enrolled with MDM

  • ComplRelayAgent.log

    This file logs the current configuration and what it means for the status of the compliance policies.

    Sample log snippet:

    Verifying if workload 2 is enabled in workloadFlags 7
    Result of & operation is 2
    Feature flag is ON, device should be Intune managed.
    CA workload is disabled for ConfigMgr. No compliance state to report for user SID <SID>

  • CIAgent.log

    This file logs the current configuration and what it means for the status of the resource access policies.

    Sample log snippet:

    Verifying if workload 4 is enabled in workloadFlags 7
    Result of & operation is 4
    Feature flag is ON, device should be Intune managed.
    Resource Access workload is disabled for ConfigMgr client.
    Skipping CI [ScopeId_<Scope ID>/ConfigurationPolicy_<Policy ID>]
    A different management authority is enabled for Resource Access workloads. Terminating current job.

  • WUAHandler.log

    This file logs the current configuration and what it means for the status of the Windows Update for Business policies.

    Sample log snippet:

    Verifying if workload 16 is enabled in workloadFlags 7
    Result of & operation is 0
    Feature flag is OFF, should be SCCM managed.
    SourceManager::GetIsWUfBEnabled - There is no Windows Update for Business settings assignment. Windows Update for Business is not enabled through ConfigMgr

What's the difference between Pilot Intune and Intune when I switch workloads?

The difference between Pilot Intune and Intune is subtle but important. Both allow Intune to control a configured workload.

  • The Pilot Intune setting is used to switch a workload only for the devices in a pilot collection that's created in Configuration Manager. This allows you to test in a staging environment without affecting all Windows 10 devices in the production environment.
  • The Intune setting is used when you finish testing in the staging environment and are ready to switch a workload for all Windows 10 devices that are enrolled in co-management.

Common issues

I switch the Endpoint Protection workload to Intune, but a Windows 10 device still has the policies from Configuration Manager

This behavior is expected.

When you switch this workload, the Configuration Manager policies stay on the device until the next check-in to the Intune service. When the device checks in, the Intune policies overwrite the Configuration Manager policies. This behavior makes sure that the device still has protection policies during the transition. For more information about the check-in frequency, see How long does it take for devices to get a policy, profile, or app after they are assigned?

I can't find the Client apps workload in the Workloads tab of co-management Properties

Client apps for co-managed devices is a pre-release feature. You must enable the pre-release feature to make it visible.

The Enablement tab in co-management properties displays 'Please ensure the proper prerequisites are installed.'

You receive this message if you didn't install the CMG. After you install the CMG, you receive a message that resembles the following:

CCMSETUPCMD="CCMHOSTNAME=contoso.cloudapp.net/CCM_Proxy_MutualAuth/72186325152220500 SMSSiteCode=ABC"

In this case, do the following:

I unassign Intune policies from a security group, but some settings remain

Intune doesn't revert settings (tattoo removal) if the Device Configuration workload is set to Configuration Manager. To enable tattoo removal, configure the workload in Configuration Manager, and refresh policy on the device.

More information

For more information about troubleshooting co-management issues, see the following articles:

For more information about Intune and Configuration Manager co-management and workloads, see the following articles: