hi

we have CAS server with WSUS upstream server due to some issue we have reconfigured/reinstalled the WSUS and reconfigured the SUP. Now in Primary SCCM (downstream) server console updates required are showing 0

Hi,

First, please make sure SUP is working, you can check WCM.log, WSUSCtrl.log.

Since you have reconfigured the SUP, try to run update scan cycle and check if it get updated.

Hi

we are getting error in SCANagent.log in all the systems:

![LOG[CScanAgent::HandleMessage - ScanByUpdateSource failed. Error = 0x87d00600]LOG]!><time="17:48:06.265-330" date="06-29-2015" component="ScanAgent" context="" type="3" thread="5028" file="cscanagent.cpp:1100">

0x87d00600 = Scan Tool Policy not found. Source: System Center Configuration Manager

Have you already examined the logs (on the primary) Daniel mentioned?

hi

we are not getting any error in the WCM.log and WSUSCtrl.log only error we are getting is on the scanagent.log

In WSUS also clients are showing not yet reported but 4-5 clients are updated but error found in the scanagent.log and updates required showing 0

If you rebuild an upstream without rebuilding the downstreams, I've seen it where your downstream metadata can become out of sync because the downstreams suddenly have many expired updates that the upstream isn't now aware of since it was just rebuilt.  Then the downstreams which previously had all of these old/expired updates declined suddenly change them as not approved since the upstream no longer has them as declined (since it doesn't know about them anymore) and the clients have to begin evaluating all these updates again for applicability (since it will evaluate any that aren't declined).  I had to fix it by temporarily making the new upstream server a downstream server of one of the existing downstreams to get it in sync (via the WSUS console) and then making it the new upstream server after the sync completes.  Otherwise you could reinstall the downstreams and it would accomplish the same thing.  Just a possibility...

If you rebuild an upstream without rebuilding the downstreams, I've seen it where your downstream metadata can become out of sync because the downstreams suddenly have many expired updates that the upstream isn't now aware of since it was just rebuilt.  Then the downstreams which previously had all of these old/expired updates declined suddenly change them as not approved since the upstream no longer has them as declined (since it doesn't know about them anymore) and the clients have to begin evaluating all these updates again for applicability (since it will evaluate any that aren't declined).  I had to fix it by temporarily making the new upstream server a downstream server of one of the existing downstreams to get it in sync (via the WSUS console) and then making it the new upstream server after the sync completes.  Otherwise you could reinstall the downstreams and it would accomplish the same thing.  Just a possibility...

• Marked as answer by Daniel JiSunMicrosoft contingent staff, Moderator Tuesday, July 07, 2015 7:58 AM

If you rebuild an upstream without rebuilding the downstreams, I've seen it where your downstream metadata can become out of sync because the downstreams suddenly have many expired updates that the upstream isn't now aware of since it was just rebuilt.  Then the downstreams which previously had all of these old/expired updates declined suddenly change them as not approved since the upstream no longer has them as declined (since it doesn't know about them anymore) and the clients have to begin evaluating all these updates again for applicability (since it will evaluate any that aren't declined).  I had to fix it by temporarily making the new upstream server a downstream server of one of the existing downstreams to get it in sync (via the WSUS console) and then making it the new upstream server after the sync completes.  Otherwise you could reinstall the downstreams and it would accomplish the same thing.  Just a possibility...

• Marked as answer by Daniel JiSunMicrosoft contingent staff, Moderator Tuesday, July 07, 2015 7:58 AM

If you rebuild an upstream without rebuilding the downstreams, I've seen it where your downstream metadata can become out of sync because the downstreams suddenly have many expired updates that the upstream isn't now aware of since it was just rebuilt.  Then the downstreams which previously had all of these old/expired updates declined suddenly change them as not approved since the upstream no longer has them as declined (since it doesn't know about them anymore) and the clients have to begin evaluating all these updates again for applicability (since it will evaluate any that aren't declined).  I had to fix it by temporarily making the new upstream server a downstream server of one of the existing downstreams to get it in sync (via the WSUS console) and then making it the new upstream server after the sync completes.  Otherwise you could reinstall the downstreams and it would accomplish the same thing.  Just a possibility...

• Marked as answer by SPV4645 19 hours 28 minutes ago

If you rebuild an upstream without rebuilding the downstreams, I've seen it where your downstream metadata can become out of sync because the downstreams suddenly have many expired updates that the upstream isn't now aware of since it was just rebuilt.  Then the downstreams which previously had all of these old/expired updates declined suddenly change them as not approved since the upstream no longer has them as declined (since it doesn't know about them anymore) and the clients have to begin evaluating all these updates again for applicability (since it will evaluate any that aren't declined).  I had to fix it by temporarily making the new upstream server a downstream server of one of the existing downstreams to get it in sync (via the WSUS console) and then making it the new upstream server after the sync completes.  Otherwise you could reinstall the downstreams and it would accomplish the same thing.  Just a possibility...

• Marked as answer by SPV4645 19 hours 28 minutes ago