After the internal ring concept is implemented it should be used for processing all changes in Workplace configuration: settings, standard applications, quality updates and feature updates.
To test new settings in the rings, run ring specific settings in separate GPOs, selected by WMI filters
select * from Win32_OperatingSystem where Version like "10.%" and ProductType="1" select * from MC_MyCompanySettings where MC_Ring = "Insider"
To create collections based on the rings, the settings need to be collected by the Hardware Inventory
Add the new WMI class to the Hardware Inventory by importing from a client
Keep all properties selected
Create collections based on MC_Ring value
select * from SMS_R_System inner join SMS_G_System_MC_MYCOMPANYSETTINGS on SMS_G_System_MC_MYCOMPANYSETTINGS.ResourceId = SMS_R_System.ResourceId where SMS_G_System_MC_MYCOMPANYSETTINGS.MC_Ring = "Insider"
Create different deployments in an Automatic Deployment Rules for Software Updates with different schedules
To use rings in application deployments, a Global Condition is created and used in the Deployment Types
Create Global Condition
Use Global Condition in Application – Deployment Type – Requirements
Based on the rings involved in the current application deployment phase the list of values accepted in the Global Condition can be extended. The deployment can always point to all clients and doesn’t need to be re-deployed to different ring-based collections.
Now all changes are covered by rings. If a user joins a ring he and his machine can automatically receive different settings, updates and applications.