It is observed that WSAS is failing only on servers. It works fine on laptops and PCs.
Here are some events seen in the agent.log.
From the log, the WSAS package failed to download.
Date: 19/3/2025 12:00:00 PM
Description: End download for package: Patch Windows System Assessment Scan Tool Package {6D417916-467C-46A7-A870-6D86D9345B61}. Status: invalid. Downloaded 0 bytes at 0 bytes per second, used 0 bytes from cache
Date: 19/3/2025 12:00:01 PM
Description: DownloadToolPackage() - Unexpected exception downloading package {6D417916-467C-46A7-A870-6D86D9345B61}
Date: 19/3/2025 12:00:01 PM
Description: Package {6D417916-467C-46A7-A870-6D86D9345B61} required for assessment is not available on endpoint
Date: 19/3/2025 12:00:01 PM
Description: Failed to launch assessment scan for provider: Traditional
Date: 19/3/2025 12:00:01 PM
Description" operation failed: Operation aborted (-2147467260)
I noticed that the environment seems to be using an identical user for App ID and ACC.
And these events are observed from the logs.
Date: 19/3/2025 12:00:00 PM
Description: Advertisement ''Windows System Assessment Scan' {1CFEC044-FFF0-40D4-A2FA-F312774116B4}' is about to run remotely from \\svr-avct-sym\PkgSvrHostC$\{6D417916-467C-46A7-A870-6D86D9345B61}\cache
Date: 19/3/2025 12:00:00 PM
Description: Advertisement ''Windows System Assessment Scan' {1CFEC044-FFF0-40D4-A2FA-F312774116B4}' is about to run remotely from \\svr-avct-sym.ict.local\PkgSvrHostC$\{6D417916-467C-46A7-A870-6D86D9345B61}\cache
Questions:
1. Is this related to certificate not being updated as per KB article
2. Or is this because of this statement in this KB article.
DO NOT enter the Application ID account information into the "Use these Credentials" option. That is not necessary and breaks things. If you want to use the App ID account for the ACC, please check the box "Use Application Credentials".
3. If the reason is No. 2, any suggestion to resolve this?
Regards,
Ain