I wonder how well a 5 minute policy interval would scale though?

From: [email protected] [mailto:[email protected]] On 
Behalf Of Johan van Dijk
Sent: Friday, August 30, 2013 10:28 AM
To: [email protected]
Subject: RE: [mssms] Lowering the SCCM Client Machine Policy Interval

14000

As long as the system can handle it's OK....(according MS during our SCCM 
Health Check)....


From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Jason Sandys
Sent: Friday, August 30, 2013 3:56 PM
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] Lowering the SCCM Client Machine Policy Interval

Wow, really? 5 minutes is well below anything I would ever recommend. Glad it's 
working for you though. How many clients do you have?

J

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Johan van Dijk
Sent: Friday, August 30, 2013 2:13 AM
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] Lowering the SCCM Client Machine Policy Interval

We have it running every 5 mins for several years now.... :)

When we migrate to 2012 we'll use the default 60 mins...since everything is in 
the catalog...

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Macone, Kelly
Sent: Thursday, August 29, 2013 11: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








Reply via email to