Forum Discussion
What does blank in ServiceProfileIdID means?
- 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.
MicrosoftHi!
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_msftRegarding 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.
Thanks for the info. Yes, I do have the entry:)
In case, after implementing the servicing profile via "by update channel" approach. If I have any issues. Do we have any possibilities to deactivate the servicing profile? So, it will roll back to previous GPO settings- manoth_msftCurrently you can't disable a servicing profile entirely. But you can scope it to an empty Azure Ad group, this will effectively out scope all devices. Once devices are out of scope, they will be offboarded and the previously set GPO configuration is in effect again.
If there are any further issues with offboarding devices, please hit the 'feedback' button on the servicing profile page and let us know about the issue.- Via update channel, if we include all the device in the servicing profile. Does it will also include servers?
