I think what is meant is... let's say I have a software update group of 900 
updates, from the last year, targeted to "all workstations", which holds let's 
say, 10,000 workstations.
5 of those workstations need 3 of those 900 updates, so, assuming the deadline 
is in the past, those 5 workstations get the 3 updates.  the other 9,995 
workstations "deserve" those 900 updates--but they already have them are aren't 
applicable.  so they scan, but don't install them.
What's the reasoning behind not having a "catch-up on all deserved updates" 
ongoing deadline-in-the-past deployment of Software Updates?  and instead you 
want to micro-manage them as you've mentioned?
Maybe there's a different, less micro-manage-y way to get to your end goal. 
 


     On Wednesday, August 26, 2015 7:37 AM, "Linkey, Mike" 
<[email protected]> wrote:
   

 <!--#yiv4995652406 _filtered #yiv4995652406 {font-family:"Cambria 
Math";panose-1:2 4 5 3 5 4 6 3 2 4;} _filtered #yiv4995652406 
{font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;}#yiv4995652406 
#yiv4995652406 p.yiv4995652406MsoNormal, #yiv4995652406 
li.yiv4995652406MsoNormal, #yiv4995652406 div.yiv4995652406MsoNormal 
{margin:0in;margin-bottom:.0001pt;font-size:11.0pt;font-family:"Calibri", 
sans-serif;}#yiv4995652406 a:link, #yiv4995652406 
span.yiv4995652406MsoHyperlink 
{color:#0563C1;text-decoration:underline;}#yiv4995652406 a:visited, 
#yiv4995652406 span.yiv4995652406MsoHyperlinkFollowed 
{color:#954F72;text-decoration:underline;}#yiv4995652406 
p.yiv4995652406msonormal0, #yiv4995652406 li.yiv4995652406msonormal0, 
#yiv4995652406 div.yiv4995652406msonormal0 
{margin-right:0in;margin-left:0in;font-size:12.0pt;font-family:"Times New 
Roman", serif;}#yiv4995652406 span.yiv4995652406EmailStyle18 
{font-family:"Calibri", sans-serif;color:windowtext;}#yiv4995652406 
span.yiv4995652406EmailStyle19 {font-family:"Calibri", 
sans-serif;color:#1F497D;}#yiv4995652406 span.yiv4995652406EmailStyle20 
{font-family:"Calibri", sans-serif;color:#1F497D;}#yiv4995652406 
.yiv4995652406MsoChpDefault {font-size:10.0pt;} _filtered #yiv4995652406 
{margin:1.0in 1.0in 1.0in 1.0in;}#yiv4995652406 div.yiv4995652406WordSection1 
{}-->I am not sure exactly what you are talking about here.  Could be that I am 
not awake yet too.  From: [email protected] 
[mailto:[email protected]] On Behalf Of Jason Sandys
Sent: Tuesday, August 25, 2015 3:12 PM
To: [email protected]
Subject: [mssms] RE: Dynamic Updates collection  Why would you do this instead 
letting ConfigMgr manage this for you?  J  From: [email protected] 
[mailto:[email protected]] On Behalf Of Linkey, Mike
Sent: Tuesday, August 25, 2015 7:38 PM
To: [email protected]
Subject: [mssms] Dynamic Updates collection  Is anyone dynamically 
adding/removing computer from a collection based on whether or not they need 
updates?  I have several update groups from the past and I want to deploy them 
to a collection and only have computers that need one of the updates in the 
collection.  Then when the client installs it, it will fall out of the 
collection the next time the collection updates.  I have been going nowhere 
fast on trying to determine where to query for this information in the console. 
 SQL reports, I can get the information, but seem to be striking out on this in 
the console.  Any input would be much appreciated.  Mike L.     


  


Reply via email to