Forum Discussion
Autopatch static ring group for pilot
Hi D_M_K,
Correct - Edge Beta is the channel assigned to the TEST deployment ring.
You can manage the assignment of your other deployment rings or create a new ring if you wish, within the Default Autopatch group and assign an AAD group with the members you wish to have in that ring. You could also create a new Autopatch group and create a ring within that using an assigned AAD group to populate the members.
Take a look at Manage Windows Autopatch groups - Windows Deployment | Microsoft Learn for guidance on the steps to manage your groups and rings.
Regards,
Richard.
MicrosoftHi D_M_K,
Correct - Edge Beta is the channel assigned to the TEST deployment ring.
You can manage the assignment of your other deployment rings or create a new ring if you wish, within the Default Autopatch group and assign an AAD group with the members you wish to have in that ring. You could also create a new Autopatch group and create a ring within that using an assigned AAD group to populate the members.
Take a look at Manage Windows Autopatch groups - Windows Deployment | Microsoft Learn for guidance on the steps to manage your groups and rings.
Regards,
Richard.
Hi RichardLian
So using the default autopatch group, i have modified Ring1, from being Dynamic to Assigned.
I have unticked the box from Dynamic Group Distribution, and have assigned an AAD group to it, which i have called "Autopatch Pilot" (as an example).
All good, it has allowed me to save.
Now my next question is, with "Update Rings for Windows 10 and later" policy.
In this section, we have 5 automatically created rings there.
Ring1 was the one i change to Assigned. So within this Ring1's properties, i see the included group as "Windows Autopatch - Ring1". Will this eventually change to the new AAD group i assigned earlier on? Which is "Autopatch Pilot".
Or do i need to manually EDIT this assignment, and replace what is there with my AAD group?
Thanks, Dave.
- RichardLian
Hi D_M_K ,
You do not need to do anything further now. Do not edit the assignments in the Windows Autopatch update ring polices.
What you should see now is that the service has automatically added the members from your "Autopatch Pilot" AAD group, into the Windows Autopatch - Ring1 AAD group. You should be all set now.
Regards,
Richard
Thanks for your reply again.
So let me get this straight.
This is an example of what i am trying to setup.
As you can see Ring1 and Ring2 will be Assigned group with my AAD groups.
Ring3 will by dynamic. I did hear that i may need to create Ring4 and split the load between the two dynamic groups... but that is not too important right now.
So if you can help me to understand the flow of how to add a new device to Ring1 and Ring2.
Do i need to add the new device to "Windows Autopatch Device Registration" group first to register the device? If so, then wont this new device end up in Ring3 automatically?
OR
Can i skip the "Windows Autopatch Device Registration" group, and add the new device to my AAD Group "Windows AutoPatch - PrePilot" (as an example).
Thanks, Dave.
RichardLian I think i have answered some of my own question here... but if you could confirm this?
I added a device to "Windows AutoPatch - PrePilot", and what do you know, as you said, the device has ended up in "Windows AutoPatch - Ring1" group automatically. And also shows up as registered too.
So my question here is, does this mean, for devices that go in "Assigned" groups, we don't need to add them to the "Windows Autopatch Device Registration" group?
The next step is to add the Group that contains all the devices in it, to the "Windows Autopatch Device Registration". Then let the dynamic groups do its thing. What will happen to the devices that is already registered and is showing up in Ring1 and Ring2 (the Assigned Groups)? Will there be conflict? Or Autopatch will know that those devices are already registered and will leave them alone?
Thanks,
Dave