Installing Office 365 Apps with Remote Desktop Service (RDS)

In your organization Remote Desktop Services (RDS) If you are using Microsoft 365 applications on and users “Sorry, Office can't be activated because it doesn't meet the requirements for running on Remote Desktop Services.” error, this issue is usually caused by Office not being properly installed and licensed for RDS.

Office 365 Error on Remote Desktop Services

Actually, there is no problem until this installation and configuration process. When your users connect to RDS servers and run office applications (Word, Excel, etc.) “Sorry, Office can't be activated because it doesn't meet the requirements for running on Remote Desktop Services.” They may encounter a warning.

Required Licensing for Office 365 in Remote Desktop Services

To use Office 365 on RDS, you must have one of the following licenses:

  • Microsoft 365 Business Premium
  • Microsoft 365 Apps for Enterprise
  • Office 365 E3
  • Microsoft 365 E5
  • Academic Plans Office 365 E3 and Microsoft 365 E5
  • Not for Profit Office 365 E3 and Office 365 E5

These licenses provide the features and support necessary to run Office applications in multi-session environments, especially over RDS.

Distribution process Office Deployment Tool(ODT) You need to do this using . Unless you meet these requirements, your users connected via RDP will not be able to run Office applications.

Deploying Office 365 on Remote Desktop Services (RDS)

To successfully deploy Office 365 applications on RDS, the Office Deployment Tool (ODT) must be used. ODT, allows you to do a customized Office installation and includes the necessary configurations for special scenarios, such as RDS.

Office Deployment Tool From Microsoft's official website download.

  • Within the ODT configuration.xml file, RDS Edit it to make it suitable for your computer. This file contains which Office applications will be installed, language options, and other important installation settings.
  • The following example shows a simple configuration.xml file
<Configuration>
  <Add OfficeClientEdition="64" Channel="Monthly">
    <Product ID="O365ProPlusRetail">
      <Language ID="en-us" />
    </Product>
  </Add>
  <Display Level="None" AcceptEULA="TRUE" />
  <Property Name="SharedComputerLicensing" Value="1" />
</Configuration>
SharedComputerLicensing feature 1 This setting is required so that Office can be used by multiple users in an RDS environment.

Configuration.xml After preparing the file, you can start the Office installation using ODT.

After installation process RDS You need to restart the server. After these operations Remote Desktop Services (RDS) Each logged in user has their own office can activate the application.

Configuring SharedComputerLicensing Using Group Policy

On RDS servers SharedComputerLicensing, Office 365 Apps (formerly Office 365 ProPlus) RDS (Remote Desktop Services) or other shared environments. This feature allows multiple users to use the same machine Office 365 It ensures that you do not experience licensing issues while using your applications.

Download the latest Administrative Template files (ADMX/ADML) for Office from Microsoft's official website.

  • Open the Group Policy Management Console (gpedit.msc).
  • Create a new GPO (Group Policy Object) or edit an existing GPO.
  • Computer Configuration\Policies\Administrative Templates\Microsoft Office 2016 (Machine)\Licensing Settings follow the steps.
  • Use shared computer activation "“Enabled” set it up.

Configuring SharedComputerLicensing Using Regedit

  • Open the Registry Editor by typing “regedit” in the Start menu.
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration follow the path.
  • Right click, select “New” -> “Reg_SZ”.
  • As string name SharedComputerLicensing enter.
  • In terms of value 1 set.

Comment