Remove from Collection / Move to Collection in OSD
Sometimes it might be handy to remove a computer from the OSD collection as a final step during the task sequence. Or additionally add the computer to additional collection(s) for for example extra software deployment or another task sequence.
Now scripts need to be created therefore and in my experience this doesn't always work well.
A predefined step where the collectionname or collectionID needs to be added to add (or remove) the computer to (or from) would be much appreciated.
Bert Pinoy
shared this idea
Thanks for the suggestion. Updating status to Noted – see https://blogs.technet.microsoft.com/configmgreng/2016/03/11/configmrguv/
5 comments
-
Gibson99
commented
another upvote for this. scripts are messy and if not done properly can leave security holes (powershell remoting in particular). if this was native, it'd be so much simpler and safer! And yes, please add the option to add/remove to/from multiple collections in a single step.
-
Diego Sanches
commented
Please keep this alive, that would be a wonderful addition.
-
Rob
commented
Yes please! This is a pain in the but for years and years. It would be so much nicer to have a default action for adding and removing the device to a collection.
-
Jitesh Patel
commented
This would be excellent - although it would be great if you could select a whole tree of folders too. For example, we have numerous collections for additional applications which wouldn't be installed on a default build and need to be requested - if we could remove any machines which are reimaged from these collections, it would be a massive time saver. Writing scripts and manually amending collection IDs each time we need to update this is a nightmare to manage - some kind of SCCM GUI would be much easier!
-
WainwRIGHT
commented
We would like to see a built-in way to remove a computer from the collection when the task sequence is done running.
When selected, add a check box to let user select which collection(s) to remove the computer from.
Currently the only way to do this is with Powershell/VB (i think) This works but is messy in our view. We try to get away from scripts whenever we can.