Fix ‘Sorry, Office Can’t Be Activated’ on Remote Desktop

If you see the error “Sorry, Office can’t be activated because it doesn’t meet the requirements for running on Remote Desktop Services”, Office is installed on a Remote Desktop Services (RDS) server without Shared Computer Activation enabled. This blocks every user who connects via a remote desktop session from opening Word, Excel, or any other Office app.

This article walks you through the exact steps to enable Shared Computer Activation, verify it took effect, and clear stale licensing tokens that can keep the error alive even after the setting is corrected.

---

---

Why This Error Appears

Microsoft requires that Click-to-Run Office programs running on a server with Remote Desktop Services have Shared Computer Activation enabled. Without it, Office attempts a standard per-device activation, which RDS does not support. The error most commonly appears in two situations:

• Office was installed on the RDS/Terminal Server without Shared Computer Activation turned on.
• A new user connects and the server cannot issue a licensing token for that user’s session.

For firms that access QuickBooks, Sage, Drake, or other accounting software through a hosted cloud environment, Office often runs alongside those apps on the same remote session. Getting the activation setting right is essential for uninterrupted work.

---

---

Fix 1 — Enable Shared Computer Activation via Registry

This is the fastest method for a single server.

1. Press Windows + R, type regedit, and press Enter.
2. Navigate to HKLMSOFTWAREMicrosoftOfficeClickToRunConfiguration.
3. Look for the value SharedComputerLicensing.
4. If the value does not exist, right-click the Configuration key, select New > String Value, and name it SharedComputerLicensing.
5. Double-click SharedComputerLicensing and set the value data to 1.
6. Click OK and close Registry Editor.
7. Restart the server so the change takes effect.

---

---

Fix 2 — Enable Shared Computer Activation via Group Policy

Use this method when you manage multiple servers or want a policy-enforced setting.

1. Open the Group Policy Management Console on your domain controller.
2. Edit or create a GPO linked to the OU containing your RDS servers.
3. Navigate to Computer Configuration > Administrative Templates > Microsoft Office 2016 (Machine) > Licensing Settings.
4. Open the policy setting Use shared computer activation.
5. Set it to Enabled.
6. Click OK and close the editor.
7. Run gpupdate /force on the RDS server or wait for the next policy refresh cycle.
8. Restart the server.

> Note: The Administrative Templates for Office must already be loaded into your Group Policy store. Download the latest ADMX files from Microsoft if the path above does not appear. See Microsoft for Microsoft’s official guidance on this configuration.

---

---

Fix 3 — Reinstall Office with Shared Computer Activation

If the registry and policy fixes do not resolve the issue, the cleanest solution is to uninstall Office and reinstall it with the Shared Computer Activation flag set from the start.

1. Download the Office Deployment Tool (ODT) from Microsoft.
2. Create or edit your configuration.xml file.
3. Add the attribute SharedComputerLicensing="1" inside the element.
4. Run the ODT setup with your configuration file to install Office.
5. After installation, verify the setting using the method in the next section.

Microsoft recommends that customers with a Microsoft 365 Apps for enterprise license use this approach for all RDS deployments. If you are running a different Click-to-Run version that does not support Shared Computer Activation, Microsoft advises switching to an Office edition that uses a volume license key instead.

---

---

Verify Shared Computer Activation Is Active

After applying any of the fixes above:

1. Open Word in a remote desktop session.
2. Go to File > Account > About Word.
3. Look for the text Shared Computer Activation in the dialog.
4. If that text appears, activation is configured correctly.

If the text is absent, the setting has not taken effect. Confirm the registry value is set to 1 and that the server was restarted after the change.

---

---

Clear Stale Licensing Tokens

Even after enabling Shared Computer Activation, individual users may still see activation prompts if old, invalid tokens are cached on their profile.

1. Have the affected user sign out of all Office applications.
2. Press Windows + R and type %localappdata%MicrosoftOfficeLicensing.
3. Press Enter to open the folder.
4. Select all files (Ctrl + A) and delete them.
5. Have the user sign back in to Office with their Microsoft 365 account.
6. Open Word or Excel to confirm the error is gone.

---

---

Additional Troubleshooting Steps

If the error persists after completing the fixes above:

• Enable TLS 1.2. Microsoft’s guidance states that TLS 1.2 should be enabled on the server if activation issues continue, followed by a restart.
• Run Windows Update. Microsoft advises checking for and installing all pending Windows updates, then restarting the device, when Microsoft 365 activation problems do not resolve through other means.
• Check license assignment. Confirm in the Microsoft 365 admin center that the user account has an active license assigned. A missing or expired license prevents token issuance regardless of server settings.
• Review firewall rules. The RDS server must reach Microsoft’s activation endpoints over the internet. Outbound HTTPS on port 443 must be open.

If your team accesses accounting software through a managed cloud hosting environment, the hosting provider’s support team can typically assist with server-level settings like these. For Sagenext-hosted environments specifically, you can review how Office access is configured within your hosted session at.

---

---

Frequently Asked Questions

What causes the ‘Sorry, Office can’t be activated’ error on Remote Desktop?

The error appears when a Click-to-Run version of Office is installed on a Remote Desktop Services server without Shared Computer Activation enabled. Office attempts a per-device activation that RDS does not support. It can also occur when the server cannot issue a licensing token to a new user connecting for the first time. Enabling Shared Computer Activation and ensuring each user has a valid Microsoft 365 license assigned resolves the root cause.

Do I need a specific Office license to use Shared Computer Activation on RDS?

Microsoft recommends Microsoft 365 Apps for enterprise for RDS deployments with Shared Computer Activation. If you are running a Click-to-Run version that does not support Shared Computer Activation, Microsoft’s guidance is to install an Office edition that uses a volume license key instead. Check the license type before attempting the registry or Group Policy fixes to confirm your edition supports the feature.

How do I confirm Shared Computer Activation is working after I enable it?

Open Word in a remote desktop session, go to File > Account > About Word, and look for the text Shared Computer Activation in the product information dialog. If that text is present, the setting is active. If it is missing, verify the registry value SharedComputerLicensing under HKLMSOFTWAREMicrosoftOfficeClickToRunConfiguration is set to 1 and that the server was restarted after the change was made.

Why does the error keep coming back for certain users even after I fix the server setting?

Stale or corrupted licensing tokens cached in a user’s profile can cause the activation error to reappear even when the server is configured correctly. Have the affected user sign out of Office, delete all files in %localappdata%MicrosoftOfficeLicensing, and sign back in. This forces Office to request a fresh token from Microsoft’s licensing servers using the corrected Shared Computer Activation configuration.

Can this error affect QuickBooks or Sage software running on the same RDS server?

The activation error is specific to Microsoft Office apps such as Word, Excel, and Outlook. QuickBooks, Sage 50, Sage 100, and other accounting applications have their own separate licensing mechanisms and are not directly affected by Office’s Shared Computer Activation setting. However, if users rely on Excel for reporting or Outlook for email integration alongside their accounting software in the same remote session, resolving the Office activation error is necessary for those integrations to function. Learn more about how hosted accounting software sessions are managed at AI Accountant Vs Cloud Hosted Software Cpas Guide.

---

---

Summary

The “Sorry, Office can’t be activated” error on Remote Desktop is caused by a missing Shared Computer Activation configuration, not a problem with the user’s credentials or the accounting software running in the same session. Set SharedComputerLicensing to 1 in the registry or via Group Policy, restart the server, clear any cached tokens, and verify the setting inside Word’s About dialog. If TLS 1.2 is disabled or Windows updates are pending, address those as well — Microsoft identifies both as contributing factors when activation issues persist.