Sources are current and valid. TTLs are however, invalid.

Question

_{Monday, February 4, 2019 3:45 PM}

I am having troubles with SCCM 1806. We had an older deployment that was upgraded through the years all the way through 1810 version. As of lately I found that clients were no longer receiving updates from my SUP. We have a single server small environment with roughly 330 SCCM clients. Not huge at all. I decided to abandon our old SCCM server and removed from the network. Before abandoning the old environment my windows 10 clients were showing "Sources are current and valid. TTLs are however, invalid." in the scanagent log. After getting my new SCCM server running I still am encountering the same message. These clients don't appear to receive the updates even they should.

All replies (2)

_{Tuesday, February 5, 2019 9:09 AM}

Hi Jimmy,

1. Reconfirm the boundary and the boundary group without incorrect.

2. SCCM site server could get the latest status report of clients.

3. Run "Synchronize Software Updates" on SCCM Console\Software Library\Software Updates\All software Updates again to ensure that the deployed updates are not superseded/expired.

4. Check below:
   \Monitoring\Overview\System Status\Site Status is everything green
   \Monitoring\Overview\System Status\Component Status is everything green
   \Monitoring\Overview\Distribution Status\Content Status
   Check your Deployment packages are successfully deployed
   \Monitoring\Overview\System Status\Status Message Queries

It is difficult to confirm the cause with a single error message.
If you can't receive the update on client Software Center.
Could you please share the complete policyagent.log scanagent.log UpdatesStore.log UpdatesDeployment.log

Best regards,
Yuxiang

Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Tuesday, February 5, 2019 1:20 PM}

I have verified 1-4 suggestions. I made sure to add my site server to the default site boundary group as pointed out in other articles for the newer versions of SCCM. With that being said I have a single boundary Default-First-Site-Name active directory site for my domain. My site server shows in the site systems tab of the boundary. I  then have a boundary group that this boundary is a member of. I use that boundary group for site assignment and the site server shows in the references tab of the boundary group.