Search the Community

Dear Team, Please advise on an Windows Updates issue. Installed a 1606 sccm standalone site on W2012 R2 server, with WSUS and WDS roles. I have configured a SUP role. Have succesfully synchronised with Windows Updates online, and have download +- 35 Windows 10 Critical updates. These are visible in console, I have created a Software Update Group, and deployed this to a W10 workstation with new sccm client. Problem is updates never show up on client. Content doesnt get copied to ccmcache directory. I have viewed most of the client logs relating to Updates. Few things i see: -Failed to attach update to the automation wrapper, error = 0x87d00215 -EnumerateUpdates for action (UpdateActionInstall) - Total actionable updates = 0 -Received User delta policy update with 0 assignments -Exception System.Management.ManagementException: Generic failure (Microsoft.SoftwareCenter.Client.Data.WmiConnectionManager at ExecuteQuery) But I think problem is not on client, but on server. I have succesfully distributed other software applications to client. But updates dont come. Firewall ports 8530, 8531 are open. Windows Updates Automaticly is disabled at client via policy. Client recoginises SUP, I see my SUP in logs. and can ping via FQDN. Alle site-roles and component status are green in SCCM logs. Any help is appreciated.

Hi All Since we have upgraded our SCCM 2012 config mgr environment to update 1511 and upgraded our clients, first using the auto upgrade which proved problematic and then client push methods quite a few of the clients appear to be failing the client remediation and re-installing, often breaking the client requiring manual intervention. So far approx 150 clients have repaired themselves and utilised default settings contained in the SWDistSchema.mof file on the client machine which set the client cache location to C:\CCM\Cache and a size of just 250mb Reading posts online suggest the problem is present in update 1602. Anyone else experience this and found a fix?

I've written a blog article on how to do this using Powershell - no reboot is required once you've deployed this app, it's quick and instant. It also accepts a parameter for the cache size so that you can now have a single application with multiple deployment types - eg a cache size of 8GB for the majority of computers and another deployment type of 10GB if the computer has a a particular CAD program installed etc. You can also use this post to learn how to deploy Powershell scripts in general, and also, how to deploy powershell scripts that take parameters by studying the script I wrote (It's very simple) Here's the link