WSEE on Server 2022 - Computer Monitoring Error

0

(I found this a good description, hence i used it)

As per the last two versions of WSEE, i suddenly got the error:
“Computer Monitoring Error”

And the added description of component: “MicrosoftSecurity!OnlineServicesPackageUpdate”

And the last edit i tried on it, was setting the “programsfolder” to ReadOnly, as per advise and working solution. But from these last two versions it seemed to have returned.

This solution from Mike:
You should also mark the (non-corrupt versions of the) “CloudServiceEnvironment-GB.xml” and “OnlineServicesConfigLanguageResourceFile-EN-GB.xml” files as read-only as well if they happen to exist within the “C:\ProgramData\Microsoft\Windows Server\Data\Cloud” folder.

Screenshots
  • Mike
    ;- )
  • You must to post comments.
0

Below is how I fixed the Computer monitoring error in Windows Server 2022 with WSE Installed.

Details
Can only partially assess the health of this computer. The failing components are: DeviceProviderReporting!DomainJoinStatusInfo.

Check Port 6602 and Firewall Rules.

Ensure your server and client firewalls allow inbound and outbound traffic on TCP Port 6602, as partial blocks can allow basic connection status while dropping health telemetry.

  • Mike
    Interesting… I’ve not come across that one before. Appreciate you sharing how you resolved the issue though. ; -)
  • Eddie
    Sorry, it appears that didn’t resolve the issue as it is has come back again. I tried everything I could find on Goggle to resolve the Error with no success yet.
  • You must to post comments.
0

 

Hi all,

I was originally having 2 different Computer Monitoring Errors. The first had to do with the health reporting error  “MicrosoftSecurity!OnlineServicesPackageUpdate” and the second had to do with the Computer Monitoring Error “DeviceProviderReporting!DomainJoinStatusInfo.”

The first one was resolved easily by adding 2 dummy .xml files to C:\ProgramData\Microsoft\Windows Server\Data\Cloud on the Server Side only. Never had anymore alerts after that.

I have not yet resolved the second alert issue. DeviceProviderReporting!DomainJoinStatusInfo.

  1. I have uninstalled and re-installed the Client Connector.
  2. Deleted the Windows Sever folder in C:\ProgramData\Microsoft.
  3. De-joined and re-joined the client machine.
  4. Cleared Registry of all Windows Server Essentials for the Client Machine.
  5. Note* Not all in this order.
  6. None of the above resolved the issue.

 

Thanks

  • You must to post comments.
Showing 2 results
Your Answer
Post as a guest by filling out the fields below, or you may to post using your existing user account (register to create a user account if you do not already have one). Guest's questions will be moderated before being posted. NOTE: Your email address will not be published, nor will it be used for marketing purposes, etc. (as per our privacy statement).
Name*
E-mail*
Answer Details*
Screenshots
File Name Size
There are currently no files uploaded.
Maximum number of files 4, maximum file size 5MB.
Supported file formats: gif jpeg jpg png

Featured Questions

Recent Questions & Answers

Q&A Toolbox