One thing that comes to mind is that if you are sure its WMI that's failing, you can increase the memory buffers for WMI. I had to do this recently for a PowerShell script running a WMI query against our CAS.
http://social.technet.microsoft.com/wiki/contents/articles/6563.configmgr-sccm-how-to-increase-wmi-default-memory-allocation.aspx Daniel Ratliff From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Jason Sandys Sent: Wednesday, August 21, 2013 9:34 AM To: mssms@lists.myitforum.com Subject: RE: [mssms] client policy processing limits I'm curious how one gets to 1600 deployments for a single system? Are you deploying every possible update to it? J From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com]<mailto:[mailto:listsad...@lists.myitforum.com]> On Behalf Of Trevor Sullivan Sent: Wednesday, August 21, 2013 8:19 AM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: RE: [mssms] client policy processing limits Hello Andy, That's an interesting problem you're describing. Just to make sure I understand it correctly, are you saying that if you deploy too many ConfigMgr Applications, Package/Programs, Desired Configuration Management Rules, Software Updates Deployments, etc. to a single ConfigMgr 2012 SP1 CU2 client, that it quits processing them at some point? Cheers, Trevor Sullivan [WordPress Logo 32px]<http://trevorsullivan.net/> [Twitter Logo 32px] <http://twitter.com/pcgeek86> [Facebook Logo 32px] <http://facebook.com/trevor.sullivan> [Google+ Icon 32px] <https://plus.google.com/106658223083457664096> From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Craig Andrew (OIZ) Sent: Wednesday, August 21, 2013 1:45 AM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: [mssms] client policy processing limits Hi All, Does anyone know if there are specific limits on how many deployments a client can receive before dying? (ConfigMgr 2012 SP1 CU2) What I am seeing in tests just now is if I deploy enough stuff to a client, I can make it generate about 1600 policy files and the wmi goes kaput. Then I need to rebuild the repository and perform a client repair. Basically the client just doesn't do anything, but it also doesn't report any errors. After the repair, it processes the policy files and eventually falls over again, during which time if I am lucky I can install a couple of apps. What I really need to do is write some guidelines for software deployment best practice, and wondering if anyone has seen this already or has a link to MS documentation that specifies a limit on deployments/received policy per client... Thanks for any help Andy The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
<<inline: image001.gif>>
<<inline: image002.gif>>
<<inline: image003.gif>>
<<inline: image004.gif>>
