During activation, you will be prompted to make sure devices are not currently assigned to a current update ring, easy enough, I’ll just go and unassign any groups assigned, but this seems a bit too manual for my liking so why not automate it?
This is where my new script comes into play. As usual you can grab it from my github here
This script will do all of the work for you, but there is one part you may need to change:
## Your Group Names $broadname = "Broad" $pilotname = "Pilot" $previewname = "Preview"
Discovery of the old groups is based on a wildcard on the names above, if you’ve used anything different, amend as appropriate.
After authenticating against Azure AD, the script will go ahead and:
- Grab the Policy IDs of the current non-autopatch policies
- Finds the AAD Groups assigned to the policies
- Unassigns the groups from the old policies
- Loops through the members of each group and adds to the Windows Autopatch Device Registration Azure AD Group
- Export a copy of each old group membership to a CSV file in c:\localappdata\UpdateRings for you to reference
- Removes the old AAD Group
- Removes the old policies
This will leave you with the new groups nicely populated with all of your previous hard work and a nice clean environment to move forward with.
Note: Autopatch will automatically distribute your devices to the new rings so they may end up moving to a different ring. The script will export the contents of your previous rings to CSV files so you can compare and move as appropriate
As always, comments and suggestions more than welcome!