Forum Discussion
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...
- 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.
manoth_msft
Microsoft
MicrosoftServicing Profiles is evaluating your devices on an on-going basis. The first time, profiles need to make a change on a device (read: install an update or perform a rollback), it will set the servicingprofileid. So you don't have to wait till next month, every device which gets an update through profiles, will get the ID the moment the actual update is initiated.
Thanks! For some reason none of my devices get the ID but they do get the officeupdate registries after the process you mentioned. Many were completed already so they didn't get the policy until today (couple of days after PT).
Maybe if they don't get the ID is not a big deal?
- Hey Martin, Thanks for sharing the video. Looks like, I did refer a wrong group. Verified again to fix it 🙂 Now I see the devices in 'Devices' node. Very excited to move to the next phases. Thanks once again.
- manoth_msft
Hi SN, can you confirm that the pre-requisites for using AAD groups are met? Check out https://youtu.be/RrEBevNV7pQ.If devices were added to the AAD group, those devices must be (H)ADD-J. Or have you added user accounts?
And can you see the devices you have added to the AAD group in the inventory on config.office.com? Or are they missing there as well?
- Hi Martin,
Same issue with our tenant. Have enabled servicing profile for a test AAD group and its been three weeks. Showing no devices under 'Devices' Node. Couldn't find Officeupdate key under Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\cloud\office\16.0\Common hive and no ServiceProfileID as well 😞 - manoth_msftI can confirm that a missing ServiceProfileID is not an issue/blocker for the update itself. It might impact 'offboarding' scenarios later on, meaning when you are removing devices from Servicing Profiles' scope. Please monitor if devices are getting the ID set over the next two weeks. If not, please use the feedback button (top right) to send us a brief description of the issue, reference this thread and share your tenant ID as well.
- manoth_msftThe missing ID is no big deal, you're right. I will check on our side if there are scenarios where a missing service ID is expected/not an issue.
