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.
Hey Bob,
I'm not sure if this post is still the most recent troubleshooting information. I'm struggling to fix/troubleshoot our config inventory capture. Some devices are capture easily and others refuse to stay in the inventory page. They will temporarily show up and then after a day or more they're gone. Our inventory is set to remove devices after 30 days, but these devices are dropping off in 1-3 days. I cannot understand why...
Somewhat similar issue to josephlamb comments.
What I've tried to do to troubleshoot this....
Replacing the TAK key registry with the TAK key that is in the apps admin config setup page.
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\cloud\office\16.0\Common\officesvcmanager
Waited 4 plus days and devices are not re-registering or checking in. Nothing shows up in the portal.
On one device, I removed the TAK registry, signed out of all office apps, removed any credentials in Windows credential manager, rebooted and signed back in. The following day the device was in the inventory page, but the TAK registry is completely missing. I manually added the registry then did a manual check in and a few hours later the device disappeared.
What's confusing me is on freshly imaged device after the user signs into the office apps. The TAK key in the registry is not the same key in config setup page. I believe it's an old one and I have no clue on why it keeps grabbing that key or why it doesn't update to the latest key. My only assumption is that the inventory page still has the devices info before we reimage the device, then it associates the old key to the device.
I would greatly appreciate any help or insight on how to troubleshoot this issue.
Thank you
MicrosoftHi edgarloyayam​ the experience you are describing sounds like devices are being dropped due to duplicate device ids. Devices can leave inventory under 1 of 2 conditions:
- The device stales out beyond the cleanup period (30 days by default) and the record is dropped.
- The device shares a unique id with another device in inventory, causing the record to be dropped unexpectedly.
Under the 2nd condition, if duplicate ids are an issue, you can expect to see devices "flapping" in and out of inventory on a daily basis. There are 2 locations to check for id duplication:
- Entra ID device id.
- Global device id HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\C2RSvcMgr.
If you need assistance diagnosing, I'd suggest opening a support case for further investigation.