Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

Microsoft 365 Apps on a Remote Desktop server: turn on shared computer activation

Technical article
Troubleshooting

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

Microsoft's page for Remote Desktop Services (RDS) says that to install Microsoft 365 Apps on shared computers you "have to use the Office Deployment Tool and enable shared computer activation". Without it, activation is the ordinary per-user kind, which Microsoft says covers "a limited number of devices, such as 5 PCs". Microsoft's troubleshooting page lists the messages for shared computer activation faults, among them "The products we found in your account cannot be used to activate Office in shared computer scenarios." (the plan lacks support) and "UNLICENSED PRODUCT Most features are turned off because a shared computer license isn't available." (no licensing token was obtained). It ties none of them to a server that lacks the setting. Microsoft's overview says that if the user isn't licensed, or closes the Activate Office dialog box, no licensing token is obtained and Office is in "reduced functionality mode", where the user "can view and print Office documents, but can't create or edit documents". Whether a server without the setting shows that mode, check on your own server. The fix is to enable shared computer activation on the server (the setting is SharedComputerLicensing = 1), restart the server, confirm every user has a plan that supports it, and reset any activation that was made before the setting was turned on.

What the error means

Microsoft's overview says shared computer activation "is required for scenarios where multiple users share the same computer and the users are logging in with their own account." One listed example is "Multiple users access an instance of Office that is hosted through Remote Desktop Services (RDS)."

With the setting on, each user who signs in gets their own licensing token. In Microsoft's words: "Each user gets a unique licensing token. Just because one user activates Microsoft 365 Apps on the computer doesn't mean Microsoft 365 Apps is activated for all other users who sign in the computer."

The token is stored in the user's profile folder, %localappdata%\Microsoft\Office\16.0\Licensing by default. It "is valid only for 30 days", and Microsoft 365 Apps tries to renew it while the user is signed in and using the apps. The RDS page says licence renewal "occurs every few days", so internet access is needed regularly, not only at the 30-day mark. A user who does not sign in for 30 days can have the token expire, and the next use contacts the Office Licensing Service on the internet for a new one.

Two licensing facts decide whether this can work at all:

  • The plan must support it. Microsoft lists any plan with Microsoft 365 Apps for enterprise, plans with the desktop Project or Visio, and Microsoft 365 Business Premium. The page says Business Premium "is the only business plan that includes support for shared computer activation", and that Business Standard does not.
  • The server must be able to reach the Office Licensing Service. The overview notes that TLS 1.2 must be enabled by default on the operating system.

Likely causes

Cause What you see How to confirm
Shared computer activation is not turned on Activation problems for users; Microsoft requires the setting for RDS but lists no message for its absence File > Account > About shows a Product ID instead of "Shared Computer Activation", or SharedComputerLicensing is missing or 0 on the server
The user's plan does not support it Activation does not work for those users only; the message "The products we found in your account cannot be used to activate Office in shared computer scenarios." Compare the user's assigned plan with the supported list
The user has no Microsoft 365 Apps licence assigned No licensing token; reduced functionality mode and "UNLICENSED PRODUCT Most features are turned off because a shared computer license isn't available." The licence is missing in the admin center
It was turned on after users had activated Setting is correct but users are still not licensed Users activated before the change; Microsoft says the activation must be reset
The token could not be obtained Activation prompts that do not complete Connectivity, TLS 1.2, or a token path that is not writable
Unsupported Windows Server version Support not offered Server version against the RDS deployment page

Prove the cause before changing anything

All of these only read.

  1. Read the setting on the server:
reg query "HKLM\SOFTWARE\Microsoft\Office\ClickToRun\Configuration" /v SharedComputerLicensing

Microsoft's registry method uses a string value (Reg_SZ) called SharedComputerLicensing with a setting of 1 under that key. If no value is returned, shared computer activation was not turned on that way. A Group Policy may set it, so also check the policy "Use shared computer activation".

  1. Or list the whole key with PowerShell:
Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Office\ClickToRun\Configuration"
  1. Check the user's plan and licence in the Microsoft 365 admin center. Microsoft's overview says: "Make sure you assign each user a license for Microsoft 365 Apps and that users sign in the shared computer with their own user account."
  2. Check the Windows Server version against the RDS deployment page. It states that Microsoft 365 Apps is not supported on Windows Server 2008 R2, 2012 or 2012 R2, and gives support periods for 2016, 2019 and 2022 (see Risks and limits).
  3. Check that the user has a token folder after signing in: %localappdata%\Microsoft\Office\16.0\Licensing in that user's profile.

Example (illustrative): rds01 at contoso.com.au serves 25 users. Twenty have Microsoft 365 Business Premium and five have Business Standard. reg query shows no SharedComputerLicensing value. After the setting is turned on, 20 of 25 users, 80 per cent, are on a plan that supports it; the five on Business Standard are not, because Microsoft says that plan does not include shared computer activation, and those five can meet the message "The products we found in your account cannot be used to activate Office in shared computer scenarios." Moving those five to a plan that supports it, or giving them another way to run the apps, is a licensing decision rather than a server fix.

Fix

Enable shared computer activation on an installed server

Microsoft names three methods for a server that already has Microsoft 365 Apps: Group Policy, the registry, or the Support and Recovery Assistant. The device must be rebooted to apply the change; no reinstall is needed. Group Policy applies only where the apps are Microsoft 365 Apps for enterprise: Microsoft says Microsoft 365 Apps for business "doesn't support the use of Group Policy to enable shared computer activation".

For the registry route, first save the current key. Create C:\Temp first if it does not exist:

reg export "HKLM\SOFTWARE\Microsoft\Office\ClickToRun\Configuration" C:\Temp\c2r-config-before.reg

Risk: the next command edits the Office Click-to-Run configuration key for the whole server. Impact: every user's Office on that server switches to shared computer activation after the restart. Back-out: if the value did not exist before, remove only that value with reg delete "HKLM\SOFTWARE\Microsoft\Office\ClickToRun\Configuration" /v SharedComputerLicensing, without /f, so that it asks first; always include /v, because Microsoft's page says that without a value name "all entries and subkeys under the subkey will be deleted". If the value existed before, run reg import C:\Temp\c2r-config-before.reg. Restart after either.

Then add the value:

New-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Office\ClickToRun\Configuration" -Name "SharedComputerLicensing" -Value "1" -PropertyType String

Disruptive step: restart the server. Impact: all sessions on it end and unsaved work is lost. Choose a time with no users, or drain the server with the method your RDS design uses first. Back-out: none for the restart itself; the registry back-out above reverses the setting.

New installs

When Microsoft 365 Apps is installed fresh on an RDS server, the RDS deployment page says to use the Office Deployment Tool with a configuration file that includes:

<Property Name="SharedComputerLicensing" Value="1" />

The Office Customization Tool has a Shared Computer option in the Product activation section (Microsoft's deployment page uses "Licensing and activation"). The ODT options page says the default is 0 when the property is not specified. Users' accounts must be members of the Remote Desktop Users group on the Session Host.

Reset activations made earlier

Microsoft: "If a user already activated the Microsoft 365 Apps before shared computer activation was enabled, you have to reset the activation to allow shared computer activation to work." Disruptive step: the reset page says its purpose is "to remove their related licenses and cached Office account information", so the user must activate again. Note which account each profile shows before you start, and work on one profile before the rest. Back-out: there is none for the cleared state; the user signs in and activates again under the new setting.

The reset page lists the licensing folder for this licence type, %localappdata%\Microsoft\Office\16.0\Licensing, among the places to clear. That page is titled for Microsoft 365 Apps for enterprise; check on your own system that it applies to your plan before you use it. For one or a few devices, Microsoft's overview says "The UI version of the Microsoft Support and Recovery Assistant is recommended if you need to reset Office activation on a single device, or on a few individual devices." Download it from the link on the overview page. The enterprise command-line version of the assistant is the one the overview describes as supporting scripting for managing multiple devices.

Roaming the token (optional)

For pooled or non-persistent profiles, the overview describes licensing token roaming: set SCLCacheOverride to 1 and SCLCacheOverrideDirectory to a folder unique to each user that Office can write to. Microsoft warns that "Using a shared folder on the network might lead to network latency issues, adversely affecting the time it takes to open Office programs."

Confirm the fix

  • reg query shows SharedComputerLicensing with a data value of 1 after the restart.
  • A test user on a supported plan signs in, starts Word, and is activated without reduced functionality mode.
  • The user's %localappdata%\Microsoft\Office\16.0\Licensing folder contains the token.
  • A second user on the same server activates separately, which shows each user gets their own token.

What to watch afterwards

  • The 30-day token. Users who are away for a long period meet a new activation on return, and need the server to reach the internet.
  • New servers and images. Add SharedComputerLicensing to the build checklist so a rebuilt host is not left at 0.
  • Plan changes. A user moved from Business Premium to a plan without support loses the supported route; check that user's activation after the change.
  • The Windows Server support dates on Microsoft's RDS page.

Risks and limits

These commands have not been run or lab-tested.

  • Microsoft's page dated 2024-09-19 says Microsoft 365 Apps "is supported on Windows Server 2019 and Windows Server 2016 only until October 2025", and "Microsoft 365 Apps (Version 2302 or later) is supported on Windows Server 2022 only until October 2026". The October 2025 date has passed, and so has the October 2026 date, so check the current page for what applies to your server before you plan around it.
  • The overview links to Microsoft's troubleshooting page for the verification steps. That page gives two checks: File > Account > About shows "Shared Computer Activation" instead of a Product ID, and the registry value SharedComputerLicensing is 1. It also says that after activation succeeds there are text files in %localappdata%\Microsoft\Office\16.0\Licensing, and not to change them.
  • Licence entitlements and plan names change. Check the current Microsoft page and your own agreement before buying or reassigning licences.
  • Personal virtual desktops assigned to one user do not use shared computer activation, according to the RDS page.
  • Microsoft's troubleshooting page lists messages, not error numbers, for activation faults; no error numbers are listed here.

Sources