Troubleshoot resource explorer for devices uploaded to the admin center

Artikel
11/16/2023

Applies to: Configuration Manager (current branch)

Use the following to troubleshoot resource explorer for ConfigMgr devices in the Microsoft Intune admin center:

Common errors from the Microsoft Intune admin center

You don’t have access to view this information

Error message: You don’t have access to view this information. Make sure a proper user role is assigned from Intune.

Possible cause: The user account needs an Intune role assigned. In some cases, this error may also occur during replication of information and it resolves without intervention after a few minutes.

Unable to get resource information

Error message 1: Unable to get resource information. Make sure Microsoft Entra ID and AD user discovery are configured and the user is discovered by both. Verify that the user has proper permissions in Configuration Manager.

Possible causes: Typically, this error is caused by an issue with the admin account. Below are the most common issues with the administrative user account:

Use the same account to sign in to the admin center. The on-premises identity must be synchronized with and match the cloud identity.
Verify the account has Read permission for the device's Collection in Configuration Manager.
Make sure that Configuration Manager has discovered the administrative user account you're using to access the tenant attach features within Microsoft Intune admin center. In the Configuration Manager console, go to the Assets and Compliance workspace. Select the Users node, and find your user account.

If your account isn't listed in the Users node, check the configuration of the site's Active Directory User discovery.
Verify the discovery data. Select your user account. In the ribbon, on the Home tab select Properties. In the properties window, confirm the following discovery data:
- Microsoft Entra tenant ID: This value should be a GUID for the Microsoft Entra tenant.
- Microsoft Entra user ID: This value should be a GUID for this account in Microsoft Entra ID.
- User Principal Name: The format of this value is user@domain. For example, jqpublic@contoso.com.
If the Microsoft Entra properties are empty, check the configuration of the site's Microsoft Entra user discovery.

The site information hasn't yet synchronized

Error message: The site information hasn't yet synchronized from Configuration Manager to the Microsoft Intune admin center.

Possible causes:

This error typically occurs when newly onboarding to tenant attach. Wait an hour for the information to synchronize.
This error may also appear if the central administration site has been upgraded to a new Configuration Manager version but some child primary sites haven't been upgraded yet.

Unable to load inventory classes

Error message: Unable to load inventory classes for your environment.

Possible causes:

The list of entities may not have been uploaded from on-premises. Wait an hour then see if the error persists.
An invalid Tenant ID or Support ID may have been specified. Check the service connection point and make sure it's functioning.
Unable to successfully execute query to get classes. Wait 15 minutes to see if the error persists.

Failed to get inventory classes with data

Error message: Failed to get inventory classes with data. On-premises error 500.

Possible causes: Unexpected errors are typically caused by either service connection point, administration service, or connectivity issues.

Verify the service connection point has connectivity to the cloud using the CMGatewayNotificationWorker.log.
Verify the administrative service is healthy by reviewing the SMS_REST_PROVIDER component from site component monitoring on the central site.
IIS must be installed on provider machine. For more information, see Prerequisites for the administration service.

The user does not have permissions

Error message: Failed to get inventory classes with data. The user does not have permissions.

Possible causes: The user may not have access to the collection that the device is a part of. Verify the following items:

Use the same account to sign in to the admin center. The on-premises identity must be synchronized with and match the cloud identity.
Verify the account has Read permission for the device's Collection in Configuration Manager.
Make sure that Configuration Manager has discovered the administrative user account you're using. In the Configuration Manager console, go to the Assets and Compliance workspace. Select the Users node, and find your user account.

If your account isn't listed in the Users node, check the configuration of the site's Active Directory User discovery.

Known issues

Newly imported inventory classes fail to load

Scenario: New hardware inventory classes are imported. You can see the newly imported classes in Resource Explorer from the Configuration Manager console. When you open Resource explorer from Microsoft Intune admin center, the newly imported class doesn't have data and Failed appears at the bottom of the results pane.

Workaround: The current workaround is to restart the SMS_Executive service on the provider machine for which the administration service handles service requests. You can determine where your administration service is by reviewing the CMGatewayNotification.log and looking for your server in the URL.

Sending AdminService request with URL: https://CMsite.contoso.com/AdminService/v1.0/ ...

When the Configuration Manager site is configured to require multi-factor authentication, most tenant attach features don't work

Scenario: If the SMS provider machine that communicates with the service connection point is configured to use multi-factor authentication, you can't install applications, run CMPivot queries, and perform other actions from the admin console. You receive an error code 403, forbidden.

Workaround: The current workaround is to configure the on-premises hierarchy to the default authentication level of Windows authentication. For more information, see the Authentication section in the SMS provider article.

Next steps

Troubleshoot tenant attach

Share via