Forum Discussion
MicrosoftHow to troubleshoot onboarding devices to the new Apps Admin Center
Hi josephlamb
Great question and attention to detail. This behavior is intended. The TAK should exist under the cloud key. If Serviceability Manager is unable to pull the TAK and write it to this location we fallback to the GPO key. This is why the script remediation writes to the GPO location. If you attempt to manually write the TAK to the cloud key it will be overwritten during the next checkin. TAK delivery will be receiving some fixes in a future release to address this.
In addition, the baseline has been updated to address the TAK CI. The detection logic now properly checks both registry keys for the TAK. Previously it was only looking at the cloud key, resulting in the CI remaining non-compliant.
N/A
Microsoft
KrisDeb wrote:
Hello and thank you for all this documentation and guides.
Is there anything else we can do if our devices are not shown in the Inventory?
We followed the process from your video clip 'How to onboard devices to the Microsoft 365 Apps admin center' and used all the information from here.
The device has the TAK properly sitting in the registry, all tasks from the scheduler are running etc. but I can't find any check-ins in the logs in Temp folder and ProgramData -> Office is also empty, no sign of Inventory text file/log.
Is there anything you guys need to do from the Cloud side, I understand the device will be deleted from the cloud after 180 days but it's a long time to find out... Anything we can do more?
I can see another device will disappear as well as it's not changed for two days, just the same as it was with the first one. Will update about the progress.
Thanks.
KrisDeb a change was introduced recently that disabled logging for Serviceability Manager by default. This might be why you are not seeing the check-in messages, along with any other pertinent information. To re-enable logging add the following registry value:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\C2RSvcMgr]
"EnableLocalLogging"=dword:00000001
Once added, logging will resume during the next scheduled task execution. I will PM you if there is more investigation necessary.