Windows 11 compatibility Powershell scanner

Comments

6 comments

  • Colby Bouma

    What does this return on the target? You can use a Tool in Inventory for this.

    Get-CimInstance -class CIM_Processor | Select-Object Name
    0
    Comment actions Permalink
  • Wayne Osteen

    Name                                    
    ----                                    
    Intel(R) Core(TM) i5-7300U CPU @ 2.60GHz

    0
    Comment actions Permalink
  • Colby Bouma

    Huh, strange. That definitely shouldn't match.

    Add this line to Win11Compatablilty.ps1, just above line 17:

    Write-Verbose "'$($proc.name)' matched '$cpu'"

    Then add this to the Parameters field of the PowerShell Scanner you created:

    -Verbose

    Run the scanner on the troublesome target, then check the Output Log (blue link at the top of the PowerShell page of the Computer window).

    0
    Comment actions Permalink
  • Wayne Osteen

    AHA! 

    [11/30/2021 1:47:20 PM] VERBOSE: Perform operation 'Enumerate CimInstances' with following parameters, ''namespaceName' = root\cimv2,'className' = CIM_Processor'.
    [11/30/2021 1:47:21 PM] VERBOSE: Operation 'Enumerate CimInstances' complete.
    [11/30/2021 1:47:21 PM] VERBOSE: '@{Name=Intel(R) Core(TM) i5-7300U CPU @ 2.60GHz}.name' matched '300U'
    [11/30/2021 1:47:22 PM] VERBOSE: Perform operation 'Enumerate CimInstances' with following parameters, ''namespaceName' = root/cimv2/Security/MicrosoftTPM,'className' = win32_tpm'.
    [11/30/2021 1:47:23 PM] VERBOSE: Operation 'Enumerate CimInstances' complete.

    0
    Comment actions Permalink
  • Colby Bouma

    Looks like that's from the AMD list:

    0
    Comment actions Permalink
  • Wayne Osteen

    I suppose with some more selection logic, I could avoid that, but I think I'll just remove the AMD CPUs from the list. We don't have any AMDs at this time.

    Thanks for digging into it Colby!

    0
    Comment actions Permalink

Please sign in to leave a comment.