Forum Discussion
BobClements
Microsoft
MicrosoftHow to troubleshoot onboarding devices to the new Apps Admin Center
For the latest information regarding onboarding and inventory, visit: Onboarding Devices in the Microsoft 365 Apps Admin Center - Microsoft Tech Community
Hi everyone, the Microsoft 365 Apps Ra...
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.
Hi Bob,
I've been struggling to get any devices into inventory. I've waited 5 days from enabling inventory, verified we are running a version of office that supports, can see "Monitored Devices" in Channel Metrics, but 0 "Devices", All of inventory says "Getting this info", I've changed the TAK in the portal, manually set the TAK on a couple machines, manually forced a checkin with the officesvcmgr.exe, added the "enablelocallogging" dword in the C2rSvcMgr reg entry.
I do not see the "OfficeSvcManagerAddons" in the Component Services snapin.
Any ideas? I've exhausted the troubleshooting details I can find, hoping you are still monitoring these posts.
BobClementsMicrosoft
MicrosoftHi kv8888899999999 - I just sent you a DM to get some additional information.
