Forum Discussion
Solved
New PC not visible in https://config.office.com
Hi, I use https://config.office.com to update my apps for Enterprise, this works well. However, I now have a new pc, registered in azure, apps for enterprise installed and logged in with a valid...
- As mentioned above, the min version is 2008. The device on v2004 just don't know how to register into the tenant. So update the device to version 2008 or newer and the device should be able to register. Documentation on min version requirement: https://docs.microsoft.com/en-us/deployoffice/admincenter/inventory#requirements-for-using-inventory
manoth_msft
Microsoft
MicrosoftHi, check out: https://techcommunity.microsoft.com/t5/microsoft-365-apps-for/how-to-troubleshoot-onboarding-devices-to-the-new-apps-admin/m-p/2183203
Basic checks are:
- Is the device running at least version 2008?
- If not, update to latest build.
- Has the device the TAK key set? (HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Cloud\Office\16.0\Common\officesvcmanager)
- If not, make sure that the same user which was used to activate Office is used to launch the application at least once.
- Has the Scheduled Task been created and ran at least once? (Task Scheduler > Microsoft > Office > Office Serviceability Manager)
- If not ran, ran it once manually.
- If not created, restart C2R service and re-check.
Feel free to report back your findings here.
office version = Version 2004 Build 1730.20352 C2R
The 'Cloud' key does not exist under HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\
When should this key have been created?
The 'Cloud' key does not exist under HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\
When should this key have been created?
- manoth_msftAs mentioned above, the min version is 2008. The device on v2004 just don't know how to register into the tenant. So update the device to version 2008 or newer and the device should be able to register. Documentation on min version requirement: https://docs.microsoft.com/en-us/deployoffice/admincenter/inventory#requirements-for-using-inventory
- Ok, tx, indeed version is the problem
- and forgotten, the user who activated office was the same as the one that launched the application