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.
Hello BobClements
thanks for your reply. I've seen on one of my colleague pc that the entire path HKLM:\SOFTWARE\Policies\Microsoft\office\16.0\Common\officesvcmanager is not present, it stops to "Microsoft"; I've also seen that the path is not present on my notebook, but there is the path HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\cloud\office\16.0\Common\officesvcmanager; so, could however create the remaing \Microsoft\office\16.0\Common\officesvcmanager and then the kye TenantAssociationKey?
Thanks.
MicrosoftThat is correct. You need to create the full path (HKLM:\SOFTWARE\Policies\Microsoft\office\16.0\Common\officesvcmanager) and the corresponding value (TenantAssociationKey). This path will not be present unless you had prior Office policies on the client device.