How to Install Office 2016 on Windows Server 2016 for Remote Desktop Users
Question details
The user needs to install Office 2016 on a Windows Server 2016 environment for multiple users connecting via Remote Desktop Services, but only has product keys and no installation media.

- Product
- Microsoft Office 2016
- Device & OS
- Windows Server 2016
- Scenario
- Deploying Office applications for a shared Remote Desktop Services (RDS) environment.
- Observed behavior
- The user requires the correct installation media and the proper licensing methodology to ensure Office 2016 functions correctly in a multi-user RDS environment.
Verify your Office 2016 license type before proceeding. Retail and Original Equipment Manufacturer (OEM) licenses generally do not support Remote Desktop Services; you will need an Office Professional Plus volume license.
Install using the Volume Licensing Service Center (VLSC)
Use this method to obtain the correct installation media and deploy Office 2016 using a Volume License, which is strictly required for RDS environments.
To run Microsoft Office on a server with the Remote Desktop Session Host role enabled, a Volume License edition (like Office Professional Plus) is mandatory. Retail or OEM keys will result in a 'cannot be used on Terminal Services' error.
Confirm that your product keys are for a Volume License edition of Office 2016 (such as Office Professional Plus).
Log in to the Microsoft Volume Licensing Service Center (VLSC) website using your organizational credentials and download the Office 2016 installation ISO file.
Mount the downloaded ISO on your Windows Server 2016. Use the Office Deployment Tool or your preferred management software to run the setup for the RDS environment.
Install the latest Windows Server and Office patches. Finally, activate Office using your Key Management Service (KMS) or Multiple Activation Key (MAK).

Deploying Retail or OEM Licenses Locally
If you discover that your keys are Retail or OEM, you cannot install them on the shared Windows Server.
Try WPS Office for a Lightweight, Compatible Experience
If navigating complex volume licensing and RDS deployment restrictions is holding up your workflow, consider WPS Office. It provides a highly compatible, cost-effective alternative to Microsoft Office with a straightforward deployment process.
- 1. Download the Installer: Visit the official WPS Office website and download the free installation package.
- 2. Install on Devices: Run the installer on your workstations for a fast, straightforward setup.
- 3. Open Existing Documents: Immediately open and edit your existing .docx, .xlsx, and .pptx files with full compatibility.

Frequently Asked Questions
Why do I get an error saying this copy of Office cannot be used on Terminal Services?
This error occurs because you are trying to install a Retail or OEM version of Office on a server running Remote Desktop Services. Microsoft requires a Volume License edition for shared RDS environments.
Can I use Office 365 or Microsoft 365 on Windows Server 2016 RDS?
Yes, but you must have a specific enterprise subscription (such as Microsoft 365 Apps for enterprise) that includes Shared Computer Activation (SCA). Standard business plans do not support RDS installation.
Where can I download the Office Deployment Tool (ODT)?
The Office Deployment Tool can be downloaded for free from the official Microsoft Download Center. It is required if you are configuring Click-to-Run versions of Office for shared environments.
Do I need to put the RDS server into install mode before installing Office?
Yes, when installing applications on a Windows Server with the RDS role, you should switch the server to Install Mode (using the 'change user /install' command) to ensure registry keys and settings are properly applied for all users.




