Kelly, You might want to check in on the deployment process to determine where the bottleneck exists. Is it policy updates, infrastructure issues, or content download delays. There are various adjustments that can be made to speed things up, depending on what your configuration is and where the problem lives.
I recommend you contact 1E Support, having them review your implementation and suggest strategies for optimization. From: [email protected] [mailto:[email protected]] On Behalf Of Lindenfeld, Ivan Sent: Thursday, August 29, 2013 5:50 PM To: [email protected] Subject: [mssms] RE: Lowering the SCCM Client Machine Policy Interval Users. Who needs software RIGHTNOWRIGHTNOW? I would ignore them. OR remind then how long it used to take for the helpdesk to sneakernet stuff. There is some time built into the content download process even with 1E deployed, so I wouldn't think anything lower than 15 would show any benefit. Ivan Lindenfeld From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Macone, Kelly Sent: Thursday, August 29, 2013 5:02 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] Lowering the SCCM Client Machine Policy Interval The problem: Users complain it takes too long for a software titles to start installing after shopping from the 1E software catalog. 99% of our software installers are packaged to run self-contained and they get sent down to the local hardware in the SCCM cache. We currently have the machine policy retrieval interval set to 30 minutes. I'm asking my admins to lower it to 15 minutes. Is that too low? What are you folks using for a machine policy retrieval interval? What are other factors I should consider? We bumped up our BITS rate considerably recently by the way. We are on SCCM 2007 R2. Thanks! Kelly Macone
