Forum Discussion
Removing user from Servicing Profile
there should be no additional steps required, accept if your devices were ConfigMgr-managed before. SCCM is not capable of performing a downgrade from a higher to a lower build/version.
Hi Martin, thanks for reaching out. The issue is cooled off by now 😉
Last Monday (14/11) my MS365 install was switch from Monthly to Semi Annual, the channel i was on before joining the servicing channel. I created a support case on the 8th but your colleagues did not have an answer yet. I removed my (Azure) user-id from the member group on 01/11. So it took almost two weeks for it to switch. After removing my (Azure) user-id i saw the number of member objects, for the specific group i was in, be decreased by 1. As stated in the Settings page by the 'Number of member objects'
In the groups to include page it speaks about devices. The group i was a member of used user-id's instead of machine names. As fas as i know, both can be used for the servicing profile and this should not be cause of the problem.
For users not in the servicing channel we use a GPO to set a specific update channel, like this;
- Computer Configuration\Policies\ Adminstrative Templates\Microsoft Office 2016 (Machine) \ Updates
- Delay downloading and installing updates for Office - Not Configured
- Update Channel - Enabled - Semi-Annual Enterprise Channel
- Update Deadline - Not Configured
One thing i noticed about the timing of me finally switching back to the SA Channel is following.
On 08/11 it was patch Tuesday. We use 3 waves for the rollout with 3 days between each wave. The group i was member of sits in the 3rd wave. So eligible 6 days after patch tuesday (being day 1) , making it the 14th. This was just the day i was switched!? I checked the friday before (11/11) but was still on Monthly and did not check during weekend. Maybe something was triggered then?
Best regards,
Richard de Wolff
- manoth_msftNov 22, 2022
Microsoft
RichardDeWolff Hi Richard, thanks for the update. As you mentioned, we indeed support device and user objects in the Azure AD groups, no change here. We have identified and fixed some bottlenecks in the Azure AD group processing. This is in line with you seeing the device being released from servicing profile around 11/14. Feel free to reach out with any further issues anytime.
- RichardDeWolffNov 23, 2022Copper Contributor
Thanks for the update. I will investigate the process again in the coming time. In case i run into trouble i will each out. Thanks