Set of Operational SCCM Collections

Just little bug, the servers are included in "workstation" groups in some cases. For example my 2019 servers are shown as "Workstations | Windows 10 v1809"

Hello,

i use the OS version as my reference. If it’s a Windows Server 2016, the OS version is 10.0.14393

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 inner join SMS_G_System_OPERATING_SYSTEM on SMS_G_System_OPERATING_SYSTEM.ResourceID = SMS_R_System.ResourceId where SMS_G_System_OPERATING_SYSTEM.Version = "10.0.17763"

Hello,

i use the OS version as my reference. If it’s a Windows Server 2019, the OS version is 10.0.17763

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 inner join SMS_G_System_OPERATING_SYSTEM on SMS_G_System_OPERATING_SYSTEM.ResourceID = SMS_R_System.ResourceId where SMS_G_System_OPERATING_SYSTEM.Version = "10.0.17763"

Hello,

This script & collections are amazing.

But, when you'll provide an update, only choice is to remove older collections (manually or automatically).

In both cases, we loose all "deployments" based on them.

Is it possible to just add and option to only "add new collection" ? Script just detect and skip already created ones ?
Or script update the detection rule of already existing collection, but without removing it ?

Thanks again.

I've updated the script (added add/update/remove collections capability), how could i share it ?
I don't modify the original work & collections.

Hello,
In the query for the collection Clients Version | Not Latest (1910) you specify a client version '5.00.8913.100%' but when you install a client, its version is 5.00.8913.1012.
As a result, your collection contains nothing.
So I changed the value from '5.00.8913.100%' to '5.00.8913.10%' and now it is OK.
It was just to let you now.

Marc

Good day Ben!  I just downloaded this today (I we had run an older script).  I get the normal do you want to over right stuff but it ends up not adding all the new collections.  For instance "Office 365 Build Version | 1803" is the newest collection for O365 I see.  Any thoughts?

Hello,
Great list. But after creating the set i see something strange happening.
The collection Servers | Windows 2019 does not get populated. I have installed 3 days ago 2 windows server 2019 servers. They appear in the devices list.
Hope you can help.
Regards, Ernst

Any reason why the script stops at *** Collection Clients Version 1810 moved to Operational Folder ***

I've ran it 3 times and it keeps stopping at the same spot.  I let it sit overnight.

Thanks!

Mr. Lecours,

As we have now migrated to the above mentioned OS for our Hyper-V hosts, could you share with us how we might query for a Serve 2019 "datacenter core" collection?

Thanks for the consideration.

Charles

@Benoit Lecours - I've used your script as a base layer to make 16 device collections for Restart Pending clients. 

I have the script hosted on Github if you are happy for me to share the link here or I can forward it to you privately for inclusion within your already established collection. 

I'm happy either way.

Please, could you update the script to add 1809/1903 collections and update the expired/expiring collections accordingly? I've changed my expired/expiring collections to reference the feature updates accordingly to reduce the need to re-evaluate things

Hi guys and Benoit, somehow after I ran the ps1, it´s stop and do not continue.

Never finish to add the collections, always freeze.

Any idea?

Thanks