Really? That seems very weird to me. If you deploy something to 100k machines that runs every 30 days you would need to wait 30 days to get your all your data back?
So if you wanted to get all the data back without having to wait 30 days, you set it to run once a day for the 100k machines and then back it off to 30 days? Just surprised I never noticed this. Thanks Rob From: [email protected] [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Thursday, August 4, 2016 8:24 AM To: [email protected] Subject: RE: [mssms] DCM Delay - SCCM 2012 R2 Whatever your schedule is set to, it will run somewhere in between that time. If you set it to 3 days, it will run sometime in the next 3 days for its first run. For any I need quicker results, I usually start with 2-4 hours then change it afterwards once I have the data I need. Daniel Ratliff From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Robert Spinelli Sent: Wednesday, August 03, 2016 8:03 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] DCM Delay - SCCM 2012 R2 I’m testing in my lab and 1 out 4 ran it about 2.5 hours after I deployed it and the other 3 still haven’t run it. I do see this In scheduler.log on the client.. [cid:[email protected]] Allow randomization override = 0, which means it does randomize. The line above saying deadline = 1440 minutes is 24 hours, so looks like it might randomize over 24 hours? I think I’m going to just put a call into MS, since we pay them a boatload of cash. I should make them work for it. Thanks Rob From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Sherry Kissinger Sent: Wednesday, August 3, 2016 4:23 PM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] DCM Delay - SCCM 2012 R2 Honestly, I never monitored. If I'm testing something against some test boxes, I just remotely trigger the policy refresh and then an eval. Once I send it to pilot or the entire target population, I just sit and wait for more results. On Wed, Aug 3, 2016 at 3:08 PM, Robert Spinelli <[email protected]<mailto:[email protected]>> wrote: I thought I remember that there is a 2 hour delay when you deploy a Configuration baseline to machine. Is that correct? Scenario 5 machines in a collection called DCMTEST Configuration Baseline called WinZip deployed to DCMTest collection set for compliance evaluation with simple schedule of every 3 days 5 machines pull policy and I see the Baseline in Configuration tab of SCCM control panel but Last Evaluation says N/A and Compliance Unknown When would you expect the baseline to run on all 5 machines? If there is a 2 hour delay they should all run today correct? It doesn’t spread it over 3 days that was set in simple schedule does it for all 5 machines. Thanks Rob -- Thank you, Sherry Kissinger My Parameters: Standardize. Simplify. Automate Blogs: http://www.mofmaster.com, http://mnscug.org/blogs/sherry-kissinger, http://www.smguru.org 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.
