Click-to-run Shared computer activation license token renewal period

%3CLINGO-SUB%20id%3D%22lingo-sub-186500%22%20slang%3D%22en-US%22%3EClick-to-run%20Shared%20computer%20activation%20license%20token%20renewal%20period%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-186500%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20testing%20Office%20365%20ProPlus%20deployed%20with%20shared%20computer%20activation%20in%20our%20VDI%20environment.%26nbsp%3B%20User%20activation%20appears%20to%20be%20working%20as%20expected.%26nbsp%3B%20For%20example%2C%20if%26nbsp%3BI%20edit%20an%20active%20user%20in%20the%20Office%20365%20Admin%26nbsp%3BCenter%20and%20assign%20that%20user%20a%20license%20to%20use%20Project%2C%20the%20app%20works%20as%20expected%20in%20the%20VM%20once%20the%20user%20logs%20in%20with%20Click-to-run%20authentication.%26nbsp%3B%20How%26nbsp%3Blong%26nbsp%3Bdoes%26nbsp%3Bit%20then%20take%20for%20that%20license%20token%20to%20be%20checked%20again%20for%20validity%20and%20renewed%2C%20or%20revoked%3F%26nbsp%3B%20If%20I%20next%26nbsp%3Bturn%20off%26nbsp%3Bthat%20license%20for%20the%20user%2C%20the%20Office%20365%20on%20the%20VM%20doesn't%20seem%20to%20immediately%20revoke%20their%20access%20to%20the%20application.%26nbsp%3B%20Is%20there%20a%20way%20through%20Group%20Policy%20or%20other%20method%20to%20control%20that%20grace%20period%20before%20the%20license%20token%20is%20checked%20and%20renewed%3F%26nbsp%3B%20Thank%20you%20for%20assistance.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-186500%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOn-Premises%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EProPlus%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-187020%22%20slang%3D%22en-US%22%3ERe%3A%20Click-to-run%20Shared%20computer%20activation%20license%20token%20renewal%20period%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-187020%22%20slang%3D%22en-US%22%3E%3CP%3EAll%20the%20publicly%20available%20information%20we%20have%20on%20this%20is%20summed%20here%3A%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployoffice%2Foverview-of-shared-computer-activation-for-office-365-proplus%23additional-details-about-shared-computer-activation-for-office-365-proplus%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployoffice%2Foverview-of-shared-computer-activation-for-office-365-proplus%23additional-details-about-shared-computer-activation-for-office-365-proplus%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYou%20cannot%20control%20the%20token%20expiration%2Fvalidity%20window%2C%20but%20you%20can%20certainly%20delete%20it%20from%20%25localappdata%25%5CMicrosoft%5COffice%5C16.0%5CLicensing.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Visitor

We are testing Office 365 ProPlus deployed with shared computer activation in our VDI environment.  User activation appears to be working as expected.  For example, if I edit an active user in the Office 365 Admin Center and assign that user a license to use Project, the app works as expected in the VM once the user logs in with Click-to-run authentication.  How long does it then take for that license token to be checked again for validity and renewed, or revoked?  If I next turn off that license for the user, the Office 365 on the VM doesn't seem to immediately revoke their access to the application.  Is there a way through Group Policy or other method to control that grace period before the license token is checked and renewed?  Thank you for assistance.

1 Reply
Highlighted

All the publicly available information we have on this is summed here: https://docs.microsoft.com/en-us/deployoffice/overview-of-shared-computer-activation-for-office-365-...

 

You cannot control the token expiration/validity window, but you can certainly delete it from %localappdata%\Microsoft\Office\16.0\Licensing.