I don't know anything about Office licensing, but Overview of shared computer activation for Office 365 ProPlus | Microsoft Docs contains the following statement:
If a user goes to another computer that also is enabled for shared computer activation, the same steps occur. There is a different licensing token for each computer that the user logs on to.
Given that you indicated that you export the user's license tokens, maybe that's (part of) the issue? By using UEM to persist the license tokens, a license token could end up on a different machine than the one it was created for?
Thanks for your response.
That article also states the following:
If you don't use single sign-on, you should consider using roaming profiles and include the following two folders as part of the roaming profile:
So that's what we did and it seemed to work for a while, however in the past few weeks a lot of users have license issues.
Can you tell me where in UEM you were able to specify to redirect/roam the two paths you indicate?
I have a similar environment with Windows 2012 R2 RDSH server, Office 365 ProPlus and UEM 9.3.
I've tried specifying a different folder with Group Policy for the Office licensing tokens, under the %userprofile%, but that didn't seem to work.
If you mean how to use UEM to roam settings from these locations: the UEM <LocalAppData> folder token corresponds with the %localappdata% environment variable in Windows.
If you create a custom Flex config file on the Personalization tab and enter the following in the Import/Export tab:
the content from those two folders will be saved at logoff and read back in at logon.
Please also read this, worth a try Overview of shared computer activation for Office 365 ProPlus | Microsoft Docs
Licensing token roaming Starting with Version 1704 of Office 365 ProPlus, you can configure the licensing token to roam with the user's profile or be located on a shared folder on the network. Previously, the licensing token was always saved to a specific folder on the local computer and was associated with that specific computer. In those cases, if the user signed in to a different computer, the user would be prompted to activate Office on that computer in order to get a new licensing token. The ability to roam the licensing token is especially helpful for non-persistent VDI scenarios.
To configure licensing token roaming, you can use either the Office Deployment Tool or Group Policy, or you can use Registry Editor to edit the registry. Whichever method you choose, you need to provide a folder location that is unique to the user. The folder location can either be part of the user's roaming profile or a shared folder on the network. Office needs to be able to write to that folder location. If you're using a shared folder on the network, be aware that network latency problems can adversely impact the time it takes to open Office.
- If you're using Group Policy, download the most current Office 2016 Administrative Template files (ADMX/ADML) and enable the "Specify the location to save the licensing token used by shared computer activation" policy setting. This policy setting is found under Computer Configuration\Policies\Administrative Templates\Microsoft Office 2016 (Machine)\Licensing Settings.
- If you're using the Office Deployment Tool, include the SCLCacheOverride and SCLCacheOverrideDirectory in the Property element of your configuration.xml file. For more information, see Configuration options for the Office Deployment Tool.
- To edit the registry, go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration and do the following:
- Add a string value of SCLCacheOverride and set the value to 1.
- Add a string value of SCLCacheOverrideDirectory and set the value to the path of the folder to save the licensing token.
I would like to know if %localappdata%\Microsoft\Credentials is also required. Now the thread is almost one year old i would like to know if this is still valid.
I do not see any reference to %localappdata%\Microsoft\Credentials
hope someoen can clarify this.
No. I do not save that directory and I have no issues.
Thanks for taking time respond.
It just does not work for me.
It authenticates then it keep saying unable to reach. The exact msg I forgot and I also hope on it.