Systems that get an error when scanning via WSUS should be reported as 'not assessed' instead of 'compliant' if scan fails for x days
When the app pool for a WSUS server is stopped or not running, and a client computer scans against it, it fails with an error. This error does not get surfaced in the AUM dashboard. Systems experiencing this error are listed as 'compliant', they should be listed as 'not assessed'.
Thomas Hughes commented
I should add more to this scneario. If a system is already compliant, and then the WSUS App pool is stopped, it appears the systems in AUM remain compliant after the scans fail. The status never updates.