Finally a 1.0 version of the Show Collection Details right-click action for ConfigMgr 2012!

I do have to admit that it took quite a while before I finally made a 1.0 version of this script/ form. Now it’s there, I also have to admit that I’m even a bit proud of it! It was a nice way of getting familiar with PowerShell and WMI.

What does it look like?

I won’t go through the list of all the fields that the tool shows, that list can be found here, but I did make a small movie for this final release with an overview about all the functionalities.

Show Collection Details of a Device

Where is it available?

As of now this final version of my Collection Details Form is publicly available via the TechNet Galleries and for a direct download, via ShowCollectionDetails_v1_0p.ps1.

>> Available via download here on the TechNet Galleries! <<

How can it be used?

To use this script as a right-click action, make sure that the folder <AdminConsoleInstallDir>\XmlStorage\Extensions\Actions\ed9dee86-eadd-4ac8-82a1-7234a4646e62 and the folder <AdminConsoleInstallDir>\XmlStorage\Extensions\Actions\3fd01cd1-9e01461e-92cd-94866b8d1f39 exist and add a XML file to those folders as specified here:

<ActionDescription Class="Group" DisplayName="Custom Actions" MnemonicDisplayName="Custom Actions" Description="Custom Actions" SqmDataPoint="53"> <ShowOn> <string>ContextMenu</string> </ShowOn> <ActionGroups> <ActionDescription Class="Executable" DisplayName="Show Collection Details" MnemonicDisplayName="Show Collection Details" Description="Show Collection Details"> <ShowOn> <string>ContextMenu</string> </ShowOn> <Executable> <FilePath>PowerShell.exe</FilePath> <Parameters>-ExecutionPolicy ByPass -WindowStyle Hidden "[SCRIPTLOCATION]\ShowCollectionDetails_v1_0p.ps1" -ResourceId "##SUB:ResourceId##" -SiteCode "##SUB:SiteCode##" -SiteServer "##SUB:__Server##"</Parameters> </Executable> </ActionDescription> </ActionGroups> </ActionDescription>


18 thoughts on “Finally a 1.0 version of the Show Collection Details right-click action for ConfigMgr 2012!

  1. Thanks for the wonderful scripts. This is going to be very helpful, provided it works for me. 🙂
    I created the XML and added the “location” of the ps1 file in the xml folder as where the script resides. But when I click from the console, the powershell window opens and then nothing comes up. Any help please?

  2. I installed the XML files in the respective folders and the custom action is there. Where do i install the PS file…?

  3. Hi Darrell,
    In the XML files there is a section called . In this section you have to specify the location of the PowerShell script, by changing [SCRIPTLOCATION], to the location where you stored the PowerShell script.

  4. Hi Kevin,
    I haven’t tested it with ConfigMgr 2007. The script is PowerShell and WMI and the biggest part of WMI is still the same, but, for example, the applications didn’t exist in ConfigMgr 2007 and they are queried by the script.
    Basically just try it and see how far you get. Please let me know the results.

  5. Hi, I have the same issue mentioned by Sameer, is anyone able to point out what is wrong with the quotes? (or is it a different issue maybe)

    this is the section for the script path from the collections.xml file

    -ExecutionPolicy ByPass -WindowStyle Hidden “C:\SOE\Tools\SCCMTools\Scripts\ShowCollectionDetails_v1_0p.ps1” -ResourceId “##SUB:ResourceId##” -SiteCode “##SUB:SiteCode##” -SiteServer “##SUB:__Server##”

    thanks for any assistance

  6. The problem is often related to copying the XML information and directly using it. Often the quotes are copied in a wrong format. Simply replacing them should fix the “issue”.

  7. Hi Peter, thanks very much for this!
    I’ve incorporated this into the console and the form comes up. But no details in any of the tab populate. Do you have any ideas on how to fix this?

  8. Hi Kevin, Sorry for the late reply. I missed out on the notification email. It sounds like a missconfiguration in the XML file. Can you try running the script from the command line to see if it works.

  9. Hey Peter!

    Thank you for the awesome script! After a little fiddling I finally got it working. I was running into the same issue as the others were where the PowerShell window would briefly appear but the form wouldn’t.

    I realized afterwards that when I copied the XML contents from both here and the Windows-Noobs forums that the file name is using the older version. I corrected the file name to match the one I downloaded from TechNet and it resolved all of my issues!!

    Been looking for something like this for awhile so thank you again!

  10. HI Peter,

    Can I ask some really stupid questions? Does this work with version 1511? do you have to specify site code, site server etc or does the PS script populate them ? The very specific directory names, what’s the significance of the names and where are these names documented ( perhaps in an SDK of sorts i suppose).

    The reason for all the question is that I don’t get the right click menu after faithfully following the instructions.

    Trying to figure out why applications appear past-due and never get installed.

    Thanks for your efforts.

  11. Hi Peter,

    Ignore my earlier questions. It’s working well. One of the comments from from earlier helped me to fix the name correctly in the xml file. With that everything works.

    Thanks a million for the wonderful script.

  12. For those who are having trouble running this – I have found a syntax change that made it work for me:
    -ExecutionPolicy Bypass -WindowStyle Hidden -file “C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\XmlStorage\Tools\ShowCollectionDetails.ps1” -ResourceId “##SUB:ResourceId##” -SiteCode “##SUB:SiteCode##” -SiteServer “##SUB:__Server##”

    Not sure if the “” is needed around powershell.exe but it works. As well, note the -File parameter before the path to the PS1 (of course substitute the path and name of your PS1. Be sure after you download you “unblock” the PS1 file

    Tested and confirmed working on Win10 x64 connected to SCCM 1702 on Server 2016

Leave a Comment