You are here:   Research
  |  Login

Welcome to my blog, quickest way to find articles is usually to search for them.

Minimize
Search in All Title Contents
 
     

Checking the Microsoft Compatibility Appraiser version to prevent unwanted network traffic

Apr 29 2018

Unless you’ve been living under a rock the last week, you have learned that the version of the Microsoft Compatibility Appraiser components can be the difference of your WSUS/SUP being hammered with network traffic or not. Luckily, it’s very easy to check.

Using Run Script in ConfigMgr to check the Microsoft Compatibility Appraiser version

According to Microsoft Support KB 4163525, if you are on the wrong version of Microsoft Compatibility Appraiser, that could generate unexpected high network bandwidth consumption.

Shorthand version: If you haven’t updated your machines, you may have an older Appraiser version, that may cause issues with Windows Update. So install your software updates!!! :)

More details: If the Appraiser version is 1799 for Windows 10 v1703 or earlier (including Windows 7 and Windows 8.1), or 1704 or 1752 if running Windows 10 v1709, you’re good. If not, well you better make sure the clients are allowed to upgrade, or simply disable the task that runs the utility (see the KB for details).

Anyway, to quickly see what version you have, run the following PowerShell command via the “Run Script” feature in ConfigMgr, and you’ll know.

Note: The Run Script feature in ConfigMgr requires PowerShell 3.0 or later (obviously, if you’re using PowerShell features added in later versions, you need to be on that version).

 

# Microsoft Compatibility Appraiser Version Check

$Path = 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Appraiser'
$Value = 'LastAttemptedRunDataVersion'

If (Test-Path -Path $Path){
    $ValueExist = (Get-ItemProperty $Path).$Value -ne $null
    If ($ValueExist -eq $True){
        Return (Get-ItemProperty $Path).$Value
        }
        Else{
            Return "Not Found"
        }
}
Else{
     Return "Not Found"
}

 

Wait a minute or two, and check the result. Here is the output from a ConfigMgr 1802 environment.

 

image
Run the script against a collection.

 

Happy deployment, / Johan









Find this article helpful? Sign-up to get our monthly newsletter with more helpful tips.


Happy deployment, and thanks for reading!


What our lawyers makes us say:

This information is provided "AS IS" with no warranties, confers no rights and is not supported by the authors or Deployment Artist.

Copyright © 2017 by Deployment Artist (the company behind deployment research). All rights reserved. No part of the information on this web site may be reproduced or posted in any form or by any means without the prior written permission of the publisher.

Shorthand: Don't pass off our work as yours, it's not nice.

Blog Archive

Minimize