Hmmm.. The more I think of this the less I like my options. If anything causes that limiter collection to refresh, then “stuff” will happen in the middle of the day when I don’t want it to. And the collection refresh will occur if any changes are made to limiting collections up the chain all the way back to “All Systems” – which I could envisioning happening at unexpected times and setting off a bad chain of events.
What I really think would work best is to be able to set a recurring advertisement with the ability to specify to not run the first “missed” instance. So if I have an advertisement set to run every night at 3:00AM and the computer gets the advertisement at 2:00PM, I’d like the client to not run the program until 3:00AM the next day. So upon the first time the computer falls into scope for a deployment of a recurring deployment, it should schedule the installation for the NEXT recurring time rather than the first or pervious recurring time. If recurring advertisements worked this way, and I am pretty sure they don’t, all my issues would be solved. Too bad that is not the way SCCM works. There could at least be a check box (run missed deployments?) so we could decide. If recurring advertisements just skipped previous/missed instances, everything would work great. Maybe I should take another look at Maintenance windows, I just need to work out their pitfalls. I’ve never implemented maintenance windows – so maybe these aren’t actual concerns. I’m just reading about them and thinking about some ways MWs could fail me in pretty substantial ways. If I have a deployment that goes out at 2:00AM and it is deployed with a WOL to computers that have a maintenance window at 4:00AM, will those computers wake at 2:00AM see they have an advertisement to run at 4:00AM and set themselves to wake up at 4:00AM before going back to sleep? Or does the computer just wake up at 2:00AM for the advertisement, say “nope – outside my maintenance window” and then go back to sleep and doesn’t wake itself up again at 4:00AM to install the software? Will the SCCM agent schedule a wake up to occur at the start of a maintenance window if it knows about a pending installation? If not, why not? Does everyone just set all their computers to wake up at the start of maintenance windows in power management settings? It seems like a big waste of electricity to wake computers up every night when they may only have something to do once in a while. What about laptops or other computers that are unable to do WOL or scheduled wake? If they have a maintenance window when they are always asleep, they are not allowed to WOL (over wifi usually) or be scheduled to wake up because of overheating concerns. When do they install the software, never? You might say, set a deadline so they install “eventually” but… If I set a deadline to occur and tell software to install at the deadline regardless of maintenance window, then any time after that deadline, when a machine falls into scope in the targeted collection, the computer will install the software immediately on next policy refresh. I really need it to wait until that night. If I don’t set a deadline, then computers that are never “on” at the maintenance window – like laptops – will never install the software, also bad. From: [email protected] [mailto:[email protected]] On Behalf Of Miller, Todd Sent: Thursday, December 04, 2014 11:43 AM To: [email protected] Subject: RE: [mssms] Question about Limiting Collections Thanks so much, this is great. This makes it so that I can continue to do things “the wrong way” – a huge relief. I ended up making a subselect element in the collection query like SMS_R_System.ResourceId in (select ResourceID from SMS_CM_RES_COLL_XXX00NNN) It is a little ugly, but it works – which is probably for the best. It will make it so that I only use it when I really need to. ☺ My collection is something like Computer has “some software” installed, and version is less than “current version”, and computer is in “limiter collection” From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Ryan Sent: Thursday, December 04, 2014 11:10 AM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] Question about Limiting Collections An include collection query would look like this: Select * From SMS_CM_Res_Coll_COLLECTIONID That should grab all computers in the collection On Thu, Dec 4, 2014 at 10:57 AM, Miller, Todd <[email protected]<mailto:[email protected]>> wrote: Maintenance windows shift the schedule of deployment to be client dependent, where my current workflow puts the schedule on the package and advertisement. I am not sure I can operate with the time the software gets installed to be dependent on the settings on the client. Thanks for the suggestion on the collection query. I will investigate to see if I can make collection membership of another collection be part of the criteria in a collection query. Do you happen to know off hand what attribute class contains collection memberships? I can’t find it. From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Ryan Sent: Thursday, December 04, 2014 9:40 AM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] Question about Limiting Collections Why aren't you using maintenance windows to schedule deployments? That's what they are there for. In my experience, collection refresh schedules only really apply to queries. Include and Exclude collection rules happen immediately when one collection changes. If you want your old system to work still, use a query rule to add all computers in Collection X to Collection Y instead of an include rule. On Thu, Dec 4, 2014 at 9:26 AM, Miller, Todd <[email protected]<mailto:[email protected]>> wrote: I have a question about the function of limiting collections. In SCCM 2012, they are having a undesirable effect where when a limiting collection is changed, the collections that are limited by that collection seem to reevaluate immediately. I have a workflow in 2007 that this new function disrupts. Sorry this is kind of long. Here is my workflow in SCCM 2007. I create a collection with query rules to determine what clients are eligible for the installation. This collection we will call “Deploy - App A” and I set the collection to refresh daily at 3:30AM. I create another collection named “Limiter –App A” which is initially empty. The Deploy - App A collection is set to be limited by Limiter –App A. Then I advertise an package to deploy to “Deploy – App A” and set it to run at some time in the past- I could also set it to run “as soon as possible.” Nothing happens immediately because Deploy – App A and Limiter – App A are empty. Now when I want to deploy Application A to a client, I add Computer X to the Limiter – App A collection. At 3:30AM (and not before), when the Deploy –App A collection is refreshed, the client is added to Deploy – App A and the next time the client checks in AFTER 3:30AM, the software is installed. Basically, I can drop clients or lists of clients into the Limiter collection in the middle of the day knowing that they won’t get added to the actual deployment collection until the collection is scheduled to refresh in the middle of the night. That’s how this functions in SCCM 2007. SCCM 2013 messes up this beautiful arrangement I have. Now the deployment collection ignores the collection schedule entirely. I am not even sure what that collection refresh schedule is good for anymore. As soon as I add a client to Limiter – App A, the Deploy – App A collection seems to refresh and Computer X that I just added to Limiter – App A gets added to Deploy – App A. Since the advertisement is in the past, itkicks off the installation. My ability to pre-stage installations during the day knowing the deployment collection won’t update until the middle of the night is lost. I do not have the Deployment collection set to do incremental updates, so why is it not respecting the collection update frequency? Is there a way to predictably (at a particular time) add clients to a collection where I could stage them during the day and have the collection update at a set time? There doesn’t seem to be a way for me to ensure that collections are updated only on a strict schedule anymore. ________________________________ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. ________________________________ ________________________________ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. ________________________________ ________________________________ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. ________________________________ ________________________________ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. ________________________________
