To get as random as random can get, I use select * from sms_r_system where SMS_R_System.SMSUniqueIdentifier like "%0"
or SMS_R_System.SMSUniqueIdentifier like "%[0-9]" or SMS_R_System.SMSUniqueIdentifier like "%[a-e]" You see, the smsuniqueidentifier will always end in either a 0 through 9, or an a through e so that's 15 slices you can do easily. so %[a-e] would be about 33.3% of the clients in the 'limit to' collection (5/15 = 33%) %[0-2] would be about 20% of the client in the 'limit to' collection (3/15 = 20%) %3 would be ~6.6% (1/15) Since the uniqueidentifiers are randomly created when the client resource is created, it's as random as one can possibly get, and it's a one liner. On Tue, Jan 10, 2017 at 9:24 AM, Wendell Hutchison < [email protected]> wrote: > If you write a query rule for your collection members you can use top with > percent in the SQL. > > https://www.techonthenet.com/sql/select_top.php > > > > > > *From:* [email protected] [mailto:listsadmin@lists. > myitforum.com] *On Behalf Of *Christopher Duszynski > *Sent:* Monday, January 9, 2017 5:10 PM > *To:* [email protected] > *Subject:* [mssms] Collection for Slow Deployment > > > > Any methods to build a collection of PC that make up a subset of devices > for test deployment. > > I would like to deploy software slowly to my pc without using direct > memberships. > > > > For example: > > Collection – A %25 of my computers > > Collection – B %50 of my computers > > Collection – C %75 of my computers > > Collection – A %100 of my computers > > > > > > > > -- Thank you, Sherry Kissinger My Parameters: Standardize. Simplify. Automate Blogs: http://www.mofmaster.com, http://mnscug.org/blogs/sherry-kissinger, http://www.smguru.org
