Forum Discussion
Servicing Profiles not picking up new devices
Hi, We are currently testing the Servicing Profile feature (for M365 Apps) in our tenant. Results so far are not ideal. All our devices are built via Autopilot and enrolled into Intune and AADJ. Th...
Hi Martin,
Things have improved a bit with devices being detected and showing up. Reporting on their status is still an issue though. Many successfully updated devices still show as "In progress" or "Not started".
We are watching with interest how it handles the deployment of the latest office update.
Things have improved a bit with devices being detected and showing up. Reporting on their status is still an issue though. Many successfully updated devices still show as "In progress" or "Not started".
We are watching with interest how it handles the deployment of the latest office update.
manoth_msft
Microsoft
MicrosoftHi, we can repro the "status" flipping in our tenants, we are investigating the issue.
- Hi Martin,
Thanks for the update. My customer has allowed us to start using Servicing profiles in production now. Numbers have improved dramatically in terms of device reporting in with the latest version of the Monthly Enterprise channel. However, we see the "Failed" numbers going up and down, disappearing, and coming back. At one point it got to 80+, and now it is 1.
Devices all show the "Internal Click-to-run issue 35" message at various stages (Discover, In-progress, Completed etc). I've passed this to the team who have the support ticket asking what it means. Currently waiting on a reply.- manoth_msft
Ivan Webb Error 35 is a transient issue which is caused by the agent not being able to fetch the current status from the C2R API, e.g. caused by system reboots (as the C2R service gets reset as well). It automatically retries to fetch the status, that's why you see the number of issues fluctuating.