Forum Discussion
ATA Sizing Tool "Missing OS Data"
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 r...
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
EliOfek
Microsoft
MicrosoftRun 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.
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 #0Get-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.GetWmiObjectCommandOh 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.
- EliOfek
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.
