An error occurred while saving the commentTom commented
We have the same issue in our large Gov't enterprise. I realize you can include collections within collections, but then it's still ONE deployment. If something goes south with any of it, you have to kill the entire deployment. For example, I am doing a deployment to multiple divisions, each division is in a collection with specific exclusions for each one. I want to deploy the application to each division, not as an "uber" collection. Reason being, if something goes south in one Division (In spite of rigorous pilot tesing), I would want to just kill that one deployment and keep the rest going, not kill the entire deployment. That is the problem with nesting collections. I will just say this, I have been an SCCM admin for 3 years, I was a LANDesk admin for 12 years before that. While SCCM does many things better than LANDesk, it SUCKS in ease of use compared to LANDesk. Why in the name of all that is holy can you NOT do the most basic windows functions in SCCM, like drag and drop, or hit a letter to go to that letter in a large listing (Like in the Applications listing, which we have hundreds, just hit an "s" to get to the "S's"), instead I have to use the filter. If they had a "drag and drop" in SCCM, I could just set up the deployment (Schedule, etc) and drop the collections onto the deployment job, 1 or 100 of them. Easy-peasy. OK, I'm done venting now.