Forum Discussion

Systems_Online0101's avatar
Systems_Online0101
Copper Contributor
Mar 19, 2018

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 relatively new server OS on our DCs. Any clue what is happening? 

  • 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

    • Systems_Online0101's avatar
      Systems_Online0101
      Copper Contributor

      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's avatar
        EliOfek
        Icon for Microsoft rankMicrosoft

        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.

Resources