How To Install Office 2010 On Terminal Server 2008 R2

In this article, we will show how to gear up and install Role 365 on a last server with the Remote Desktop Services (RDS) role for simultaneous employ by multiple users. The Shared Computer Activation mode of Function 365 ProPlus is used in RDS, VDI, and scenarios where multiple users use a shared Windows host.

Past default, a Microsoft 365 Apps license allows a user to install and activate Part 365 on a maximum of 5 devices. Nevertheless, there are cases when a user doesn't have a personal estimator and they have to piece of work on different computers using their account (RDS, VDI hosts, shared computers, etc.). To ignore the limit on the number of Office 365 license activations, you can install Role 365 on such computers or RDS servers in the Shared Computer Activation mode.

This article describes general licensing rules and differences betwixt the archetype Office (2013, 2022, 2022) versions and Role 365 subscriptions.

Requirements:

• First of all, note that you can apply the following Role 365 licenses (subscriptions) with desktop virtualization support on your terminal (RDS) server: Microsoft 365 Apps for Enterprise (Office 365 ProPlus), Part 365 E3, or Office 365 E5;
• Users must authenticate on a shared computer (RDS server) using their accounts Microsoft 365 Apps licenses are jump to;
• The Remote Desktop Services role must be installed and configured on your server (it may exist a stand-alone server or a server in an RDS farm with the Connection Broker). The RDS host must be targeted to the RDS licensing server, and the licensing server must accept enough User or Device RDS CALs;
• All previous Microsoft Office versions must exist uninstalled before installing Office 365 ProPlus.

You must install Office 365 ProPlus on the RDS server in the Shared Computer Activation mode using a custom XML configuration file.

We have already told that to install mod MS Part (Office 365 and Role 2022) versions, the click-to-run (C2R) is used as an installation method instead of MSI installers. C2R Installer downloads installation files from the Web (from Microsoft CDN).

For a custom C2R installation of Role, you must use the Microsoft Office Deployment Tool (ODT) — https://www.microsoft.com/en-usa/download/details.aspx?id=49117.
Download and install officedeploymenttool.exe. In the installation directory, you will see sample XML files to configure Office 365 and Office 2022 Enterprise installation settings and a C2R installation file – setup.exe.

In the configuration file configuration-Office365-x64.xml, you can specify what Office 365 products y'all want to install. By default, all apps are installed, and you cannot install certain Office applications from the graphical Click2Run Installer (for more data encounter the article on How to Custom Install Only Specific Apps of Function 365/2019/2016?).

You tin can configure Office installation settings manually in the configuration-Office365-x64.xml. However, it is easier to generate an XML file with the installation settings you want using Microsoft's online service — https://config.office.com/ (Part Customization Tool). Open the spider web folio, select Office installation settings (architecture, language, apps, whether you need to install Visio and Projection, etc.). Remember to select Product activation –> Shared Computer in the Licensing and Activation section.

Save the XML file as office365proplus_shared_rds.xml and open up it with any text editor.

This XML file contains the installation settings for an Office 365 packet. Notation the following setting:

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

Use this option (Shared Calculator Activation) if your copy of Office 365 to exist used past multiple users (an RDS server, a VDI calculator, a shared computer, or a mutual Windows host with multiple RDP connections enabled). If you do not prepare it, you volition be able to activate Office 365 for a single user only.

Switch your RDS server to the app installation mode:

change user /install

To install Office 365 on the RDS host co-ordinate to the options specified in the configuration file, use the post-obit command:

setup /configure office365proplus_shared_rds.xml

Note that in our instance Office 365 C2R installer will download files from the Web. Even so, you can download Office 365 installation files to a shared network folder on your file server in advance and use information technology every bit a source of installation files. Then you lot tin can specify the installation source in your XML file.

Change the line:

<Add OfficeClientEdition="64" Channel="Current">

to

<Add SourcePath="\\mun-fs01\Install\Office365" OfficeClientEdition="64" Channel="Electric current">

Later the installation is over, change the RDS host manner to normal:

alter user /execute

How Office 365 user licenses are activated? Each user is prompted to sign in with their Office 365 credentials (electronic mail and password) when they start whatsoever Office app for the first time. If y'all have Azure Agile Directory (Microsoft 365) and on-premises Agile Directory synchronization configured and a user logs on to a estimator using the account with Office 365 license assigned, their license gets activated automatically.

The user volition receive a license token from Office Licensing Service activation servers on the Web with a validity menses of xxx days. After 30 days, Part 365 will try to automatically renew the license token.

It is obvious that in the case of using Office 365 on an RDS host you demand constant Internet access to validate and activate user licenses on Microsoft servers. There is cipher similar to the KMS host in a local network.

If y'all take installed Office 365 without the SharedComputerLicensing option in your XML file, yous can change Part 365 installation blazon in the registry instead of the unabridged packet reinstallation. To practice information technology, modify the value of the SharedComputerLicensing Reg_SZ parameter to i in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration.

Or enable the Apply shared computer activation option from Role Administrative GPO templates in Computer Configuration -> Administrative Templates -> Microsoft Office 2022 (Computer) –> License Settings.

If you don't do it, you will encounter the following error when the 2nd user tries to start Role 365 apps:

This re-create of Microsoft Office cannot be used on a computer running Terminal Services. To employ Function on a figurer running Terminal Services, you must utilize a Volume License of Office.

Source: http://woshub.com/deploy-office-365-rds-terminal-server/

Posted by: simonsdoetianighim.blogspot.com

Share this post