Jump to content


Recommended Posts

Hi all,

 

I am having an issue with clients contacting the SCCM SUP. This is a fresh install of SCCM 1702 on a server 2012 R2 and Windows 10 environment. All is working as expected, except even the Software Update Point. WSUS is on its own Server and SCCM talks to it and pulls in all the updates. I can create SU groups and used scheduled updates to inject the patches into my wim. BUT clients are not talking to SCCM SUP, all the updates have "0" required\installed against them.

The environment did have WSUS for patching previously, so I have excluded all WSUS Group Policies, by blocking inheritance on the OU. I have enabled SUP in client settings and applied them to the clients.

When I check the locationservices.log there is no trace of the "WSUS path=http://" telling the clients to go to their SCCM SUP server. Also the clients do not have any register settings created by SCCM to point them to their SUP.

I'm at a loss as to where to look now? It must be something simple!

Any advice much appreciated. 

Thanks

Kevin

Share this post


Link to post
Share on other sites

The Scan update log states that the "Software Updates client configuration policy has not been received, default settings will be used.". I'm very confused, as it is enabled on the default client policy as well as a custom client policy. Just wondering if this could be getting blocked by the AV?

 

 

 

<![LOG[Software Updates client configuration policy has not been received, default settings will be used.]LOG]!><time="16:15:11.948-60" date="06-07-2017" component="ScanAgent" context="" type="1" thread="11236" file="scantoolpolicy.cpp:648">

<![LOG[- -Recovering persisted Scan requests...]LOG]!><time="16:15:11.948-60" date="06-07-2017" component="ScanAgent" context="" type="1" thread="11236" file="scanjobmgr.cpp:118">

<![LOG[CScanAgent::CleanDeletedUpdateSources- entered. This will clean any update sources for which policy no longer exists.]LOG]!><time="16:15:11.963-60" date="06-07-2017" component="ScanAgent" context="" type="1" thread="11236" file="cscanagent.cpp:1579">

<![LOG[Software update client config event __InstanceCreationEvent received.]LOG]!><time="16:17:01.015-60" date="06-07-2017" component="ScanAgent" context="" type="1" thread="3056" file="cscanagent.cpp:1220">

<![LOG[- -Recovering persisted Scan requests...]LOG]!><time="16:17:37.642-60" date="06-07-2017" component="ScanAgent" context="" type="1" thread="9292" file="scanjobmgr.cpp:118">

<![LOG[CScanAgent::CleanDeletedUpdateSources- entered. This will clean any update sources for which policy no longer exists.]LOG]!><time="16:17:37.658-60" date="06-07-2017" component="ScanAgent" context="" type="1" thread="9292" file="cscanagent.cpp:1579">

<![LOG[- -Recovering persisted Scan requests...]LOG]!><time="16:25:58.301-60" date="06-07-2017" component="ScanAgent" context="" type="1" thread="4148" file="scanjobmgr.cpp:118">

<![LOG[CScanAgent::CleanDeletedUpdateSources- entered. This will clean any update sources for which policy no longer exists.]LOG]!><time="16:25:58.353-60" date="06-07-2017" component="ScanAgent" context="" type="1" thread="4148" file="cscanagent.cpp:1579">

<![LOG[Message received: '<?xml version='1.0' ?>             <UpdateSourceMessage MessageType='ScanByUpdateSource'>

                                <ForceScan>TRUE</ForceScan>

                                <UpdateSourceIDs>

                                                <ID>{349E5FC2-62B1-4624-8733-9C7EAC502719}                                               </ID>

                                </UpdateSourceIDs>

                </UpdateSourceMessage>'

]LOG]!><time="16:34:01.916-60" date="06-07-2017" component="ScanAgent" context="" type="1" thread="3360" file="cscanagent.cpp:1042">

<![LOG[*****ScanByUpdateSource request received with ForceReScan=2, ScanOptions=0x0000000a,  WSUSLocationTimeout = 604800]LOG]!><time="16:34:02.837-60" date="06-07-2017" component="ScanAgent" context="" type="1" thread="3360" file="cscanagent.cpp:216">

<![LOG[Sources are not current]LOG]!><time="16:34:04.556-60" date="06-07-2017" component="ScanAgent" context="" type="1" thread="3360" file="utils.cpp:104">

<![LOG[ScanJob({7B191E15-CD28-4FE8-9578-D05F84B25036}): - - - - - -Locations requested for ScanJobID={7B191E15-CD28-4FE8-9578-D05F84B25036} (LocationRequestID={40869FF1-8BCF-4021-A1A0-7FCAF8ED9B71}), will process the scan request once locations are available.]LOG]!><time="16:34:06.713-60" date="06-07-2017" component="ScanAgent" context="" type="1" thread="3360" file="utils.cpp:477">

<![LOG[Software update client config event __InstanceModificationEvent received.]LOG]!><time="16:58:03.507-60" date="06-07-2017" component="ScanAgent" context="" type="1" thread="1384" file="cscanagent.cpp:1220">

<![LOG[- -Recovering persisted Scan requests...]LOG]!><time="17:37:16.987-60" date="06-07-2017" component="ScanAgent" context="" type="1" thread="4396" file="scanjobmgr.cpp:118">

<![LOG[ScanJob({7B191E15-CD28-4FE8-9578-D05F84B25036}): CScanJob::Scan - Recovered Scan request with LocationRequestID={40869FF1-8BCF-4021-A1A0-7FCAF8ED9B71}. It is still waiting for Locations, will process the scan request once Locations are available.]LOG]!><time="17:37:17.019-60" date="06-07-2017" component="ScanAgent" context="" type="1" thread="4396" file="utils.cpp:477">

<![LOG[CScanAgent::CleanDeletedUpdateSources- entered. This will clean any update sources for which policy no longer exists.]LOG]!><time="17:37:17.019-60" date="06-07-2017" component="ScanAgent" context="" type="1" thread="4396" file="cscanagent.cpp:1579">

<![LOG[- -Recovering persisted Scan requests...]LOG]!><time="09:38:43.471-60" date="06-08-2017" component="ScanAgent" context="" type="1" thread="6872" file="scanjobmgr.cpp:118">

<![LOG[ScanJob({7B191E15-CD28-4FE8-9578-D05F84B25036}): CScanJob::Scan - Recovered Scan request with LocationRequestID={40869FF1-8BCF-4021-A1A0-7FCAF8ED9B71}. It is still waiting for Locations, will process the scan request once Locations are available.]LOG]!><time="09:38:43.565-60" date="06-08-2017" component="ScanAgent" context="" type="1" thread="6872" file="utils.cpp:477">

<![LOG[CScanAgent::CleanDeletedUpdateSources- entered. This will clean any update sources for which policy no longer exists.]LOG]!><time="09:38:43.580-60" date="06-08-2017" component="ScanAgent" context="" type="1" thread="6872" file="cscanagent.cpp:1579">

<![LOG[- -Processing Scan Job TTL invalidity request]LOG]!><time="16:28:11.219-60" date="06-08-2017" component="ScanAgent" context="" type="1" thread="2804" file="scanjobmgr.cpp:610">

<![LOG[Message received: '<?xml version='1.0' ?>             <UpdateSourceMessage MessageType='ScanByUpdateSource'>

                                <ForceScan>TRUE</ForceScan>

                                <UpdateSourceIDs>

                                                <ID>{349E5FC2-62B1-4624-8733-9C7EAC502719}                                               </ID>

                                </UpdateSourceIDs>

                </UpdateSourceMessage>'

]LOG]!><time="16:28:13.769-60" date="06-08-2017" component="ScanAgent" context="" type="1" thread="2804" file="cscanagent.cpp:1042">

<![LOG[*****ScanByUpdateSource request received with ForceReScan=2, ScanOptions=0x0000000a,  WSUSLocationTimeout = 604800]LOG]!><time="16:28:13.769-60" date="06-08-2017" component="ScanAgent" context="" type="1" thread="2804" file="cscanagent.cpp:216">

<![LOG[Sources are not current]LOG]!><time="16:28:13.805-60" date="06-08-2017" component="ScanAgent" context="" type="1" thread="2804" file="utils.cpp:104">

<![LOG[ScanJob({60E34093-608A-479C-849B-82745C72A00E}): - - - - - -Locations requested for ScanJobID={60E34093-608A-479C-849B-82745C72A00E} (LocationRequestID={8711969D-99B1-48E3-8014-118A3BDD3EC0}), will process the scan request once locations are available.]LOG]!><time="16:28:13.974-60" date="06-08-2017" component="ScanAgent" context="" type="1" thread="2804" file="utils.cpp:477">

Share this post


Link to post
Share on other sites

Ok so finally figured this out. On the ScanAgent.log I was seeing a lot of "Sources are not current" messages. This led me to dig further and that the SUP MUST be in the default boundaries group, which I didn't know. It apparently is new to 1702?!?!

Once I added the SUP to the default group clients started reporting in instantly!

 

Hope this helps someone out there.

 

Regards

Kevin

  • Like 1
  • Thanks 1

Share this post


Link to post
Share on other sites

On 6/12/2017 at 11:27 AM, khawkins said:

Ok so finally figured this out. On the ScanAgent.log I was seeing a lot of "Sources are not current" messages. This led me to dig further and that the SUP MUST be in the default boundaries group, which I didn't know. It apparently is new to 1702?!?!

Once I added the SUP to the default group clients started reporting in instantly!

 

Hope this helps someone out there.

 

Regards

Kevin

THANKS A LOT, I spent 1 week of my life until I find your post.

Share this post


Link to post
Share on other sites

Man... 

On 6/12/2017 at 1:27 PM, khawkins said:

Ok so finally figured this out. On the ScanAgent.log I was seeing a lot of "Sources are not current" messages. This led me to dig further and that the SUP MUST be in the default boundaries group, which I didn't know. It apparently is new to 1702?!?!

Once I added the SUP to the default group clients started reporting in instantly!

 

Hope this helps someone out there.

 

Regards

Kevin

You are genius !!... had raise support ticket with MS for this 2 weeks agony.... which BTW even MS could not identify... just followed your guideline and worked straightway after restarting CCM agent....thanks a million !!

 

Cheers...!

 

Share this post


Link to post
Share on other sites

3 hours ago, Abdul Rahman said:

Man... 

You are genius !!... had raise support ticket with MS for this 2 weeks agony.... which BTW even MS could not identify... just followed your guideline and worked straightway after restarting CCM agent....thanks a million !!

 

Cheers...!

 

You're welcome, I remember pulling my hair out over that one for a long time. Will never forget it either.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.