Hi

We have 1 CAS and 1 PRIMARY. CAS having upstream WSUS with its DB on SQL and PRIMARY having downstream WSUS with its DB on SQL. There was a issue on CAS WSUS and we were unable to reinstall it on SQL DB so we reinstalled WSUS on internal DB and reconfigured SUP role on CAS.

The PRIMARY WSUS and SUP are syncing with CAS and the updates are available in the PRIMARY server console. The required column on the software updates console are showing zero. We checked the scan errors on the clients and its displaying the following errors.

CUpdatesScan::ScanByUpdates - failed at call to CScanAgent::ScanByUpdates(), error=0x87d00600          ScanAgent                26/06/2015 2:45:42 PM  5652 (0x1614)

CScanAgent::ScanByUpdates - Update Source Policies not found no scan will be performed, returning E_FAIL_POLICY_NOT_FOUND    ScanAgent          26/06/2015 2:45:42 PM  5652 (0x1614)

and also the admin$ of the clients are not accessible. please let me know whether admin$ accessible is required even after client deployment for other operations.

Please help to eradicate the update scan error.

First, although you probably can't change this now, for others reading this thread and considering doing the same, having a single primary site and a single CAS is completely useless and a waste of resources.

As for the admin$ share, no this is not required after client installation. All client agent communication is client agent initiated in ConfigMgr. (Editorial: Why in the world you would disable the admin shares is beyond me, but that's a side point -- please don't say security because that's simply not accepted or recommended by any reputable security guidelines.)

As for your actual issue, this thread should get you started, but doesn't have an actual solutiuon:

https://social.technet.microsoft.com/Forums/systemcenter/en-US/091ee5ad-b10c-484b-b135-de64af71672b/sccm-is-not-deploying-patches-to-clients-windows-7?forum=configmgrsum

Hi Jason,

thanks for you reply.

Actually there was a SUP syncronization issue on primary site server.

Got it resolved by changing registry value on CAS HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\COMPONENTS\SMS_REPLICATION_MANAGER

Followed the below blogs

https://social.technet.microsoft.com/Forums/en-US/2a31c4c0-f674-4c3e-9e2b-1451d8531809/sccm-2012-primary-site-to-cas-supwsus-sync-not-working?forum=configmanagersecurity

https://social.technet.microsoft.com/Forums/systemcenter/en-US/d5a5ae26-d07a-4fd4-ab1e-213e06149945/issue-with-replmgr?forum=configmgrgeneral

Thanks

Sunny