Set of Operational SCCM Collections

This script will create a set of 100 SCCM collections for your various needs. These collections can be used for operational tasks afterward.

 
 
 
 
 
4.8 Star
(64)
39,747 times
Add to favorites
System Center
1/13/2020
E-mail Twitter del.icio.us Digg Facebook
  • Prompt to delete All Operational collection
    2 Posts | Last post March 29, 2018
    • Hi Benoit, 
      I last used your script very successful in July of 2017.  Today when I run 2.10.ps1
      I get a prompt to delete All Operational collection, pressing enter to continue quits the script and no new collections are installed.  I thought your script would continue past same names? 
      "Script has already been run or a collection name already exist.  Delete All Operational collection before re-executing the script!  Press enter to continue..." 
      What to do? Thank you. 
    • Working on a new version to handle that. For now, just delete the previously created collection manually and re-run the script.
  • Wrong version in query for Clients Version | 1802
    2 Posts | Last post March 29, 2018
    • $Collection77 = @{Name = "Clients Version | 1802"; Query = "select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.ClientVersion = '5.00.8634.1700'"}
      
      According to: https://buildnumbers.wordpress.com/sccm/
      
      Client version is: 5.00.8634.1007 for 1802, and not: 5.00.8634.1700 which is the console version.
      
    • Typo... fixed ! Thank you
  • Suggestion
    2 Posts | Last post March 27, 2018
    • Hello Mr. Lecours,
      
      I really like your script, so i wanted to provide you with some feedback. For the device collection "Client Version|1710" i would update the query to 
      
      select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.ClientVersion like "5.00.8577.1%" 
      
      instead of using "5.00.8577.100%" 
      
      then you will get the all clients for version 1710 even after the hotfix is applied.
      
      Otherwise thank you for saving me a whole bunch of time
      
      
    • Fixed in 2.10. Thank you
  • Windows 10 Collection queries picking up Server 2016 devices
    3 Posts | Last post March 27, 2018
    • Hi,
      
      The Windows 10 collections are picking up Server 2016 devices. I imagine we can either limit the collection to All Workstations or change the query to include:
      
      or SMS_R_System.OperatingSystemNameandVersion =
      ‘Microsoft Windows NT Workstation 10.0 (Tablet Edition)’)
    • and this:
      
      SMS_R_System.OperatingSystemNameandVersion =
      ‘Microsoft Windows NT Workstation 10.0’
    • Fixed in 2.10. Thank you.
  • no more deleting collections to update
    1 Posts | Last post January 08, 2018
    • I don't know if I can post a link here. I want to be able to help people with the same issues I had. I know it can be frustrating.
      
      I have been using this script for a while and got tired of having to delete every collection just to be able to rerun the script. I decided to update the script. Pretty much reconfigured the whole thing and now, you can run the script as many times as you would like; If the collection exists, it will continue, if it doesn't, it will create it.
      
      There might be a better way to do it, or I might be missing something. I am no expert at all in PowerShell but know enough to make things work.
      
      https://github.com/JCovarrubias7/SCCMOperationalCollections
      
      Thanks to Mr. Lecours and all credit goes to him. 
  • add win 10 builds please
    2 Posts | Last post December 08, 2017
    • 1703 + 1709
      thanks.
    • + surface pro (2017)
  • Description and Error Handling Differ
    1 Posts | Last post December 01, 2017
    • Benoit, the description states that if a collection exists the script will continue to process the rest.  That's not how the error handling actually works in the script.  Since it's catching on any error the first existing collection will trigger that catch, display the error, and exit.
  • mistake in script
    2 Posts | Last post November 27, 2017
    • Great stuff, thanks. One mistake with the latest update though - the below should be set to $Collection73 not 72
      
      $Collection72 = @{Name = "Clients Version | 1710"; Query = "select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.ClientVersion like '5.00.8577.100%'"}
    • Thanks for pointing that out. The error has been fixed.
  • Ask Latest
    1 Posts | Last post November 07, 2017
    • Your "Client Version | Not Latest" (collection 4) references 1702 and another of your collections refers to 1706.  This should be updated in the next release of scripts.  Additionally, the comment on collection 4 says "1511" and should be updated too.
      
      Thanks for the great scripts
  • Not Latest
    1 Posts | Last post November 07, 2017
    • Your "Client Version | Not Latest" (collection 4) references 1702 and another of your collections refers to 1706.  This should be updated in the next release of scripts.
21 - 30 of 73 Items