This project is read-only.

Actions items missing

Topics: missing Features
Jun 13, 2013 at 10:38 PM

Are there plans to incorporate all the options in the current 2007 Collection Commander tool? It appears the majority of them are not in this release.

Nov 6, 2013 at 5:26 PM

Just following up on the above question. I was wondering if you were planning on making the new Collection Commander tool similar to the 2007 tool? Where you can re-run advertisements, restart service, repair wmi, get last bootup, and basically all the other options.

Nov 22, 2013 at 11:05 AM
You can run any powershell you want... so you only need the PS Commands. You can copy the PS Commands from Client Center (
Let me know if you have to PS commands where you think that they are important to include...


Oct 24, 2014 at 1:38 AM
hello Roger,

Thanks for the great tools (for both this and ClientCenter!)

I was looking for a way to add selected machine(s) to a collection from the list you can pick from (based on the search results or prefix, or just browse from the top). Will this tool have a feature like that?

The closest tool I found is


Oct 24, 2014 at 11:47 AM
Hi Young

It's not in the scope of the tool to interact with the ConfigMgr Server (I know, the old Version did that...). In General the tool is designed to run PowerShell scripts against a list of Systems... So in the next release, the tool will not have "Configuration Manager" in the Name anymore because you can also use it without ConfigMgr.

In CM12, you can select multiple Devices in the Console and use the right click Option "Add selected Items to existing Device collection" to add them to a Collection...


Oct 24, 2014 at 10:24 PM
Edited Oct 24, 2014 at 10:27 PM
Hi Roger,

Thanks for the update.

I know the fact that SCCM 2012 comes with strong RBAC and Security Scope feature to effectively manage the permission per object and rich command/features for sure.
But I just wanted to give a tool to general Service Desk and Onsite Staff to run and add a machine to the (limited) list of collections for "Optional" Application Installation.

So based on the following script, I ended up created CMAdd2Coll.ps1:

My modified script is doing the following:
  1. Connect to SCCM Server based on parameter ($ServerName and $SiteCode)
  2. Load all collections under specific Folder ($ContainerName) on Device Collections
  3. Display a window form with
  4. ComputerName Field
  5. List of collections to choose from (Drop down)
  6. Add / Close Button
  7. When the user enter the computer name, select a collection, and click Add button,
  8. If the machine is listed on SCCM, perform Add-DirectMembershipRule cmdlet to add a direct membership to the specified collection.
  9. If the machine is not listed, prompt the user that "machine name is invalid. please try again"
My question is now
  1. Can I add my CMAdd2Coll.ps1 file to C:\Program Files (x86)\Collection Commander for Configuration Manager\PSScripts\Collections folder so that the user can:
  2. Right click on the computer name - Run PowerShell Code...
  3. Select PS Scripts - Collections - CMAdd2Coll.ps1 to trigger a Windows Form (with the computer name pre-populated)?
PS Scripts seems to perform PowerShell Remote only and I would like to have a way to invoke the script locally with the machine name provided to the script...

Oct 28, 2014 at 4:08 PM
This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.