Software Center: Compliance Status: Unable to Verify the status

Qtn ldn 5 Reputation points
2023-02-21T10:41:09.9066667+00:00

Hello to all,

I hope that someone will be able to help me, I installed MECM as well as the Software Center tool, in order to deploy software, updates and also the compliance system.

However, I have a problem with compliance and I can't solve it:

The error CARELAY_WRITE_TO_AAD_ERROR refers to a communication problem with Azure Active

Directory. But I don't have Azure, I use a Local AD on a Windows Server 2019 Datacenter

Here is a Screen:

Capture

I hope that someone can give me some indications and/or explanations... thank you in advance

My respects

Sincerely

Microsoft System Center
Microsoft System Center
A suite of Microsoft systems management products that offer solutions for managing datacenter resources, private clouds, and client devices.
824 questions
Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
5,850 questions
Microsoft Configuration Manager Deployment
Microsoft Configuration Manager Deployment
Microsoft Configuration Manager: An integrated solution for for managing large groups of personal computers and servers.Deployment: The process of delivering, assembling, and maintaining a particular version of a software system at a site.
902 questions
Microsoft Configuration Manager

4 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Limitless Technology 43,931 Reputation points
    2023-02-21T19:53:55.9733333+00:00

    Hi. Thank you for your question and reaching out. I’d be more than happy to help you with your query

    It sounds like you are having an issue with the Compliance Status in Software Center. This could be due to a number of factors, such as corrupted system files, incorrect permissions, or even a problem with the server itself.

    To fix this issue, you can try running the System File Checker tool, which scans and repairs any corrupt system files. This can be done by opening the command prompt as an administrator, and then typing "sfc /scannow" without the quotes. Additionally, you can also check the permissions of the Software Center folder to make sure that the correct permissions are set.

    If the issue persists after this, you may need to reinstall Software Center or contact Microsoft support for further assistance.

    If the reply was helpful, please don’t forget to upvote or accept as answer, thank you.

  2. Limitless Technology 43,931 Reputation points
    2023-02-21T19:54:12.67+00:00

    Hi. Thank you for your question and reaching out. I’d be more than happy to help you with your query

    It sounds like you are having an issue with the Compliance Status in Software Center. This could be due to a number of factors, such as corrupted system files, incorrect permissions, or even a problem with the server itself.

    To fix this issue, you can try running the System File Checker tool, which scans and repairs any corrupt system files. This can be done by opening the command prompt as an administrator, and then typing "sfc /scannow" without the quotes. Additionally, you can also check the permissions of the Software Center folder to make sure that the correct permissions are set.

    If the issue persists after this, you may need to reinstall Software Center or contact Microsoft support for further assistance.

    If the reply was helpful, please don’t forget to upvote or accept as answer, thank you.

  3. Qtn ldn 5 Reputation points
    2023-03-01T10:16:36.38+00:00

    Can i UP the topic ? :p

  4. MottonEyeJoe 0 Reputation points
    2023-06-05T07:52:05.7+00:00

    Hello Qtn,

    does the error still persist on your end? I have experienced the very same problem and what fixed it was disabling the deployment of a compliance policy.

    Assets and Compliance -> Compliance Settings -> Compliance Policies

    I had enabled a Compliance setting to check for installed Windows updates which produced the error.

    Honestly I do not know whether this is a bug in MECM or if I had simply misconfigured the server. I do hope this can bring you a step closer to getting rid of that issue.

    0 comments