1.) Open cmd with run as administrator privilege on the affected server. Execute the below command and send screenshot if any error message comes:
2.) Open wbemtest tool with run as administrator privilege on the AppManager server.
3.) Connect to the affected server by providing credentials used in AppManager while adding the monitor and execute the following queries one by one and send us the screenshot:
a. Select * from Win32_PerfRawData_PerfOS_Processor
b. Select AvailableMBytes from Win32_PerfRawData_PerfOS_Memory
c. Select * from Win32_PerfRawData_Tcpip_NetworkInterface
4.) Check that remote computer’s firewall should allow DCOM protocol and remote computer management.
5.) Check if Windows Remote Management (WS-Management), Windows Management Instrumentation services are running on remote server. Try restarting the services and check wbemtest again, if data hasn't come previously.
6.) If data is coming through wbemtest, check in AppManager the affected server by polling it 1-2 times.
If data is not coming still then reconstruct WMI repository on target server, restart Windows Remote Management (WS-Management), Windows Management Instrumentation services and then check again by polling the affected monitor.
Please ask the customer to find the articles given by Microsoft related to WMI issue :
Error: I’ve verified that the namespace, class, and property names are correct, yet my script still doesn’t work
Error: I’m getting an 0x80041010 (“Invalid Class”) error
Also, ask the customer to check the hotfixes related to WMI issue in the following link :