ATA Sizing Tool "Missing OS Data"

[Systems_Online0101]

I ran the ATA Sizing tool against our DCs. Upon viewing the results, in the "Lightweight Gateway Supported" column I see the following message "Missing OS Data" for two of the DCs. We are running a relatively new server OS on our DCs. Any clue what is happening? 

[#2]

Got this comment from the engineer who developed the tool:

Most likely the WMI queries against these DCs are failing.

Did the tool log anything like “ATTENTION: Not all selected DCs can be reached for WMI queries”?

The Sizing Tool needs to be able to fetch the OS version of the DC to determine the Lightweight Gateway requirements.

If this is the case, this is typically one of three issues:

1. WMI service not running on the DC
2. Firewall blocking WMI on the DC (Firewall WMI-In)
3. Insufficient Remote WMI permissions.  I assume this isn’t the problem if the other DCs worked (presumably domain admin)

In such a case the Sizing Tool typically guides the user to first get the following command to work before running the sizing tool again

Get-WmiObject -Class Win32_Processor -ComputerName DCNAME

[#3]

Hello Eli thanks for the response. I ran the powershell command (elevated as DA) against my DCs and it failed on some and worked on others. The ones that failed returned the following message:

Get-WmiObject : Invalid query "select * from Win32_Processor"
At line:1 char:1
+ Get-WmiObject -Class Win32_Processor -ComputerName DALAD03
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (:) [Get-WmiObject], ManagementException
+ FullyQualifiedErrorId : GetWMIManagementException,Microsoft.PowerShell.Commands.GetWmiObjectCommand

[#4]

Run the following command locally on DALAD03

Get-WmiObject -Class Win32_Processor

If it works, you need to check Firewall settings.

If it doesn’t work, you need to check if the WMI service is running.

[#5]

Odd things happening...It works but also gives some sort of Quota Violation error message (see below). I verified that the Windows Management Instrumentation service is running on this DC. Then minutes later I ran it again and it didn't even work at all - it then gave me the error message I posted in the post before.  

PS C:\Users\da_user3> Get-WmiObject -Class Win32_Processor -ComputerName dalad03

Caption : AMD64 Family 16 Model 9 Stepping 1
DeviceID : CPU0
Manufacturer : AuthenticAMD
MaxClockSpeed : 2200
Name : AMD Opteron(tm) Processor 6174
SocketDesignation : CPU socket #0

Get-WmiObject : Quota violation
At line:1 char:1
+ Get-WmiObject -Class Win32_Processor -ComputerName dalad03
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [Get-WmiObject], ManagementException
+ FullyQualifiedErrorId : GetWMIManagementException,Microsoft.PowerShell.Commands.GetWmiObjectCommand

[#6]

Oh and I forgot to mention that the Windows Management Instrumentation service is in fact running along with the Windows Remote Management (WS-Management) service is running as well. 

[#7]

Seen something similar before.

IT means you have a process (or more than 1) that is using WMI queries extensively.

You need to figure out who it is, which WMI provider is causing this.

Another option is to increase the quota, but if there is a problem, it might just take more time to fill the quota.

[#8]

Hello again Eli. So is there a tool or something with procmon I need to run on my domain controller to view WMI utilization? 

[#9]

If I remember correctly, there is a way to tell windows to audit in the event log WMI usage.

This is turned off by default.

Sorry, I don't remember the exact details on how to turn this on.

I suggest opening a support ticket with a platform engineer assigned to the case with WMI expertise who might help trace it.