Forum Discussion

Copper Contributor

Apr 10, 2023

Solved

What does blank in ServiceProfileIdID means?

Hi team, In my test via "Azure AD groups". I have added my device to the servicing profile. Able to execute few functions like Pause, Rollback etc. But, when I check the Computer\HKEY_LOCAL_MACHI...

Microsoft 365 Insider

manoth_msft
Apr 11, 2023
Please check this location in the registry: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\cloud\office\16.0\Common\officeupdate. Is there a value IgnoreGPO with a data of 1? Also additional keys like targetversion or updatechannel? If yes, your device is managed by servicing profiles.

GerardoHernandez

Brass Contributor

Apr 28, 2023

manoth_msft

Hi!
What about having ServicingProfileId empty and also non existent officeupdate under HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\cloud\office\16.0\Common.

We have enrolled devices about 4 days ago. All looks good from the Console with devices showing as complete or not started but devices are not getting the configuration. We checked the office serviceability manager task schedule and it looks like is yet to run but everyday remains the same. If you run it manually it ends with an Operational Code 2 (the output been Task Scheduler successfully completed task "\Microsoft\Office\Office Serviceability Manager" , instance "{GUID here}" , action "C:\Program Files\Common Files\Microsoft Shared\ClickToRun\officesvcmgr.exe" with return code 0.), but still shows as it has never ran before. What could be happening?

manoth_msft

Microsoft

May 11, 2023

Regarding the Scheduled Task: When the scheduled task runs, it will get updated information from our service and more often than not re-create the task. That's why it shows "never run before", as this new one actually never ran before.

The ServicingProfile will be set once servicing profile sees a reason to send an updated update configuration to the device. Sample scenario: Current update is v2302, all your devices are on v2302 already, you enable servicing profiles, the services evaluated all devices and flags all as "completed", because all are already in the desired state (running v2302). But in this case no device gets a new update config sent, thus no servicingprofileid is set. Next PatchTuesday comes around, v2303 is the current one, all your devices flip back to "not started" (as they are no longer in the desired state) and will receive updated instructions the next time they check in. This is the point in time when the serviceprofileid will be set as well.

Might this be your scenario? And with PatchTuesday just a few days behind us, you should see more and more devices getting the ID set.