Exactly what I am trying to accomplish and I have done it this way since we started. But we had a problem with machines not getting updates and the MS support dude says to remove those so the clients that already have them installed don’t keep scanning for them. Did not make sense to me and I thought that was wrong. But I was just trying to determine if there was a way to handle this if MS is saying that was not right.
Will just keep doing it the way I always have which is what you described here. From: [email protected] [mailto:[email protected]] On Behalf Of Sherry Kissinger Sent: Wednesday, August 26, 2015 8:40 AM To: [email protected] Subject: Re: [mssms] RE: Dynamic Updates collection 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]<mailto:[email protected]>> wrote: 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]> [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Tuesday, August 25, 2015 3:12 PM To: [email protected]<mailto:[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]> [mailto:[email protected]] On Behalf Of Linkey, Mike Sent: Tuesday, August 25, 2015 7:38 PM To: [email protected]<mailto:[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.
