Forum Discussion
Servicing Profile updating devices even in the Exclude group and not working according to settings
MicrosoftHi stevejb
Based on the items you've listed, there appears to be a few different things going on. For example, Servicing Profiles has no control over 32-bit > 64-bit changes. However, it would still be good to dive in on the other areas. If you haven't already, please navigate over to the "Monthly Enterprise" page under Servicing and click on the "Give Feedback" button. Include all the relative info and a contact email if you'd like to hear back from the team.
Hi BobClements
I too have noticed that the servicing profile for the Monthly Enterprise Channel is adding devices even though it's paused. There should only be 4 devices as I selected "Groups to Include" and NOT all devices.
Monthly Enterprise Channel: 2211 Rollout
Hope you can shed some light on this.
Regards,
Richard.
- BobClements
That is not expected. Do you recall starting with all devices or maybe targeting a group with a larger member count initially? I sent you a DM for some more info.
Hi BobClements
When I set up the the initial Profile it defaulted to all devices. I did initially select "Choose Groups to include" radio button but at the time didn't add a group. I realised a few hours later however that it had included all devices. I resumed the deployment again and now the numbers seem better but I'm not convinced all is well as there's devices in the list which shouldn't be there.
Some report as complete but the version is still 2210? According to SCCM 805 devices updated
Many thanks
Richard
- BobClements
When you make changes to the selection criteria (e.g., all devices > small group) the service can take up to 24 hours to complete the change. That appears to be what happened in this scenario. We are working to speed those evaluations up, but for now that is the behavior you can expect.
Regarding the devices showing complete - this is being addressed in an upcoming update. Those devices did complete their upgrade, but the version # is taking longer than expected to update. You can see the build # matches the 2211 update.
Thank you for sharing your experience. Keep the feedback coming.