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.
I found this post when I'm trying to understand why 2 users devices are not present in the list; I elaborated it and ask this: is this possible that I can't see them beacuse I installed it with the Office deployment tool and not directly from the users portal?
If so, what I can do? We haven't Endpoint manager, so maybe we can create the entry in the Windows registry and insert the TAK and this help to discover the devices? What is the correct location?
--
Thanks,
Marco
MicrosoftMarcoMangianteIM deployment using the ODT is supported and should not impact onboarding.
First I would confirm the missing devices meet the following requirements:
- Microsoft 365 Apps for enterprise or Microsoft 365 Apps for business, Version 2008 or later
- A version of Windows 10 supported by Microsoft 365 Apps for enterprise or Microsoft 365 Apps for business
- Microsoft 365 (or Office 365) for Business Standard, Business Premium, A3, A5, E3, or E5 subscription plan
- Client devices can reach the following endpoints:
Overview of inventory in the Microsoft 365 Apps admin center - Deploy Office | Microsoft Docs
If the requirements look good, you can manually stamp the TAK in the registry using the following steps:
- Copy your current TAK from the Apps Admin Center portal (Settings).
- Create a new REG_SZ registry value titled "TenantAssociationKey" in the following location: HKLM:\SOFTWARE\Policies\Microsoft\office\16.0\Common\officesvcmanager
- Add your TAK to this value.
- Open a terminal window and run the following command: "C:\Program Files\Common Files\microsoft shared\ClickToRun\officesvcmgr.exe" /checkin
If there are no additional blockers, I would expect to see the device appear in Inventory within 5 minutes.