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 <http://trevorsullivan.net/> <http://twitter.com/pcgeek86> <http://facebook.com/trevor.sullivan> <https://plus.google.com/106658223083457664096> From: [email protected] [mailto:[email protected]] On Behalf Of Craig Andrew (OIZ) Sent: Wednesday, August 21, 2013 1:45 AM To: [email protected] 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
<<image001.gif>>
<<image002.gif>>
<<image003.gif>>
<<image004.gif>>
