[Service plans and windows updates]

Hi All,

I have created a number of servicing plans for my windows 10 estate but none of my clients seem to be pulling the updates down and I am getting a lot of errors appearing in my scanAgent.log BOLD and Italic below

 

- - -Evaluating Update Status...    ScanAgent    28/06/2019 15:41:01    16436 (0x4034)
- - Calling back to client on Scan request complete...    ScanAgent    28/06/2019 15:41:01    16436 (0x4034)
No CatScan history exists    ScanAgent    28/06/2019 15:41:01    2336 (0x0920)
Sources are current, but Invalid. TTL is also invalid.    ScanAgent    28/06/2019 15:41:01    2336 (0x0920)
CScanJob::Execute- Failed at AddUpdateSource, Error = 0x80004005    ScanAgent    28/06/2019 15:41:01    2336 (0x0920)
ScanJob({F3D4C70D-CFFA-4F71-8FC6-39C05B4A5B65}): CScanJob::OnScanComplete -Scan Failed with Error=0x80004005    ScanAgent    28/06/2019 15:41:01    16436 (0x4034)
ScanJob({F3D4C70D-CFFA-4F71-8FC6-39C05B4A5B65}): CScanJobManager::OnScanComplete- failed at CScanJob::OnScanComplete with error=0x80004005    ScanAgent    28/06/2019 15:41:01    16436 (0x4034)
ScanJob({F3D4C70D-CFFA-4F71-8FC6-39C05B4A5B65}): CScanJobManager::OnScanComplete -ScanJob is completed.    ScanAgent    28/06/2019 15:41:01    16436 (0x4034)
ScanJob({F3D4C70D-CFFA-4F71-8FC6-39C05B4A5B65}): CScanJobManager::OnScanComplete - Reporting Scan request complete to clients...    ScanAgent    28/06/2019 15:41:01    16436 (0x4034)
- - -Evaluating Update Status...    ScanAgent    28/06/2019 15:41:01    2336 (0x0920)
- - Calling back to client on Scan request complete...    ScanAgent    28/06/2019 15:41:01    2336 (0x0920)
Message received: '<?xml version='1.0' ?>    <UpdateSourceMessage MessageType='ScanByUpdateSource'>
        <ForceScan>TRUE</ForceScan>
        <UpdateSourceIDs>
            <ID>{03FD123B-82CD-460F-8530-E9AF08EBD153}            </ID>
        </UpdateSourceIDs>
    </UpdateSourceMessage>'
    ScanAgent    28/06/2019 15:49:06    27940 (0x6D24)
*****ScanByUpdateSource request received with ForceReScan=2, ScanOptions=0x0000000a,  WSUSLocationTimeout = 604800    ScanAgent    28/06/2019 15:49:06    27940 (0x6D24)
Sources are current, but Invalid. TTL is also invalid.    ScanAgent    28/06/2019 15:49:06    27940 (0x6D24)
ScanJob({0791C588-D3EA-481E-9BB0-A32F54D7AA6D}): - - - - - -Locations requested for ScanJobID={0791C588-D3EA-481E-9BB0-A32F54D7AA6D} (LocationRequestID={3B438046-3CCD-44E1-9C5E-AF62B12CAC02}), will process the scan request once locations are available.    ScanAgent    28/06/2019 15:49:06    27940 (0x6D24)
*****WSUSLocationUpdate received for location request guid={3B438046-3CCD-44E1-9C5E-AF62B12CAC02}    ScanAgent    28/06/2019 15:49:06    12308 (0x3014)
CScanJobMgr::UpdateSUPLocationList- Original WUA location count is 0, new location count is 1, WUA locations updated.    ScanAgent    28/06/2019 15:49:06    12308 (0x3014)
Sources are current, but Invalid. TTL is also invalid.    ScanAgent    28/06/2019 15:49:06    20656 (0x50B0)
CScanJob::Execute- Failed at AddUpdateSource, Error = 0x87d00692    ScanAgent    28/06/2019 15:49:11    20656 (0x50B0)
ScanJob({0791C588-D3EA-481E-9BB0-A32F54D7AA6D}): CScanJob::OnScanComplete -Scan Failed with Error=0x87d00692    ScanAgent    28/06/2019 15:49:11    17096 (0x42C8)
ScanJob({0791C588-D3EA-481E-9BB0-A32F54D7AA6D}): CScanJobManager::OnScanComplete- failed at CScanJob::OnScanComplete with error=0x87d00692    ScanAgent    28/06/2019 15:49:11    17096 (0x42C8)
ScanJob({0791C588-D3EA-481E-9BB0-A32F54D7AA6D}): CScanJobManager::OnScanComplete -ScanJob is completed.    ScanAgent    28/06/2019 15:49:11    17096 (0x42C8)
ScanJob({0791C588-D3EA-481E-9BB0-A32F54D7AA6D}): CScanJobManager::OnScanComplete - Reporting Scan request complete to clients...    ScanAgent    28/06/2019 15:49:11    17096 (0x42C8)
- - Calling back to client on Scan request complete...    ScanAgent    28/06/2019 15:49:11    20656 (0x50B0)
CScanAgent::ScanComplete- Scan completion received.    ScanAgent    28/06/2019 15:49:11    20656 (0x50B0)

 

TIA

[Client issues following upgrade to SCCM2012 1902]

Hi,

All clients have been updated. client version  is now 5.00.8790.1025

I tried manually uninstalling the client then re-pushing it from SCCM and this then updated all the policies and the applications started coming down.

I'm not sure if part of the issue was DNS?

I'm also trying to use the windows servicing for windows 10 but no updates are coming out to the client machines.

What would be the best log files to check for these two issues and are they on the SCCM server or the client machines?

[Client issues following upgrade to SCCM2012 1902]

Hi,

I have recently upgraded to 1902 and since doing that some of my clients are having issues getting applications.

If i manually uninstall the SCCM configuration manager client and then re-install the applications start to appear in the software center. 

Any thoughts on additional things to check?

TIA