Avatar of Patrick Doman
Patrick Doman
Flag for United States of America asked on

Guidance for Installing Office 2016 Pro Plus on a Terminal Server

I need to be able to install Office 2016 Pro Plus on a Windows Server 2008 R2 Terminal Server, well, 2 actually.
Is there any good guidance on this for someone who hasn't done this before? Currently there is 2010 on the server. I am going to be moving the customer to Office 365, then will migrate the organization to their own private cloud. But for now, I think we need to get them licensed properly and on the updated Office platform.  This looks like a streaming install vs a MSI on the Office 365 E3 license. Will that be a problem?
Microsoft OfficeInstallationMicrosoft 365Windows OS

Avatar of undefined
Last Comment

8/22/2022 - Mon

The install for Office 365 using a click to run methodology.  This is done by the user logging into O365 and installing from the click to run. To install on TS you cannot install this method. You will need to use the ODT ( Office Deployment Tool) to download and install this properly on a Terminal Server.


Office 2016 standard perpetual gets installed just like any other application.

Once installed you can advertise the app.

For licensing of Office on TS it will depend on the type of license your client owns or leases
Office 2016 PP is a perpetual license where O365 E3 is a subscription.  

That being said there is a category that comes up with Terminal Server. Remote User Rights

This will help explain perpetual

Office 365 is subscription and you get up to 5 devices per subscription you don't want to commit a license when not in use so when installing you need to make sure it's install properly.

With the above covered, in the TS session, you gave to change mode from exec in which the TS commonly operates to install mode.
change user /install

Is there a necessity, requirement for office2016 to be on a TS?
Office 2010 functions just as well.

The deployment of 2016 to the workstations or are all employees remote; thus the need/use for TS?

Are the TSs function as a farm for redundancy?

Test locally on a system where 2010 exists to make sure the settings of the install do not remove 2010 if you plan to gave them coexist.

The other, do the users use outlook on the TS?
Patrick Doman

The 2010 isn't licensed properly from what I can tell. It was installed 2 IT people ago.
I am going through and upgrading them to Office 365 E3 licensing.  As I do this, I read that there is a configuration.xml file I need to setup which will outline the silent installation method that can be used. I did use the change user /install mode the other day, I remember that from older OS's.

Not sure if that still works.
I saw in an article that I can use a command in the xml file that tells the system not to prompt for activation.

<Display Level="None" AcceptEULA="True" />
<Property Name="SharedComputerLicensing" Value="1" />

Display Level = None and SharedComputerLicensing

I don't have an example xml file though as I have not done this before.

I am looking through articles Microsoft gave me but I don't see one specifically for Office 365 non retail versions. Most of the configuration.xml files are all for retail versions of the software.
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.

you have to download the tool
then retrieve the install packages.

Then the install package is setup in a share with the config file that specifies that meets your needs.


Check with the vendor from/through or when you run the package, see what options it has......
Patrick Doman

Ok I did that and now I have the configs

<Product ID="O365ProPlusRetail">
      <Language ID="en-us" />

My confusion is what to type in since the config files appear to. Be written for retail packages in all of the examples

I have 71 people running on windows servers that I need to push the install to tonight

Does the change user /install also need to be run on the 2008 R2 servers ?

From what I have seen I need to make sure the users aren’t prompted to login if I can avoid that.
I don’t see configurations examples for the office 365 example.

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
Log in to continue reading
Log In
Sign up - Free for 7 days
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
Patrick Doman

Thank you for both of your comments, I wouldn't have found the resolution to this as fast without your input.
One question I have is the Shared Computer Activation. It has a Allow the licensing token to roam. If I have 2 servers, remote desktop servers, in the same network that are going to be running the Office 2016, do I need to do something with this?
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
Patrick Doman


From what I read about the TS the install does not really take a permanent license.  Office 365 E3 entitles you to 5 devices to activate. If you did not enable the SharedComputerLicensing each time a user connected and activated Office. Once you hit 5 activation you will not be able to activate anymore until the admin can manually remove the devices.

With TS the license is just barrowed for the session technically.
Patrick Doman

Correct. But I see that the users have a home directory. So I need to enable that location as a storage area for the Activation Token. So it follows them if they login to server 1 or Server 2.

I downloaded the Admin Template Files but not quite sure what to do with those yet.
Group Policy on the DC doesn't have an Office 2016 folder under Group Policy to point out the users home directory.

See note: Licensing token roaming Starting with Version 1704 of Office 365 ProPlus, you can configure the licensing token to roam with the user's profile or be located on a shared folder on the network. Previously, the licensing token was always saved to a specific folder on the local computer and was associated with that specific computer. In those cases, if the user signed in to a different computer, the user would be prompted to activate Office on that computer in order to get a new licensing token. The ability to roam the licensing token is especially helpful for non-persistent VDI scenarios.

To configure licensing token roaming, you can use either the Office Deployment Tool or Group Policy, or you can use Registry Editor to edit the registry. Whichever method you choose, you need to provide a folder location that is unique to the user. The folder location can either be part of the user's roaming profile or a shared folder on the network. Office needs to be able to write to that folder location. If you're using a shared folder on the network, be aware that network latency problems can adversely impact the time it takes to open Office.

If you're using Group Policy, download the most current Administrative Template files (ADMX/ADML) for Office and enable the "Specify the location to save the licensing token used by shared computer activation" policy setting. This policy setting is found under Computer Configuration\Policies\Administrative Templates\Microsoft Office 2016 (Machine)\Licensing Settings.

If you're using the Office Deployment Tool, include the SCLCacheOverride and SCLCacheOverrideDirectory in the Property element of your configuration.xml file. For more information, see Configuration options for the Office Deployment Tool.

To edit the registry, go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration, add a string value of SCLCacheOverride, and set the value to 1. Also, add a string value of SCLCacheOverrideDirectory and set the value to the path of the folder to save the licensing token.


If you're using Microsoft Application Virtualization (App-V) to deploy Office 365 ProPlus, the registry location is HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\16.0\Common\Licensing.
Your help has saved me hundreds of hours of internet surfing.
Patrick Doman

I ran the setup, and it removed the older version of office from the terminal server but it won't install the new one. When I run setup.exe /configure configuration.xml    it just goes back to the prompt after a few seconds. There doesn't appear to be an error log.

Did you download the entire deployment package before trying to install?

Deals with it is a large amount of data.
The install us in the background.

Often when a removal is done, a restart might be required, in such a case a subsequent install attempt without restart might not go forward as it may still see ref to prior version that it can not uninstall as it has already been, awaiting a restart.

The download directive one for 32bit version, and one for 64 bit.

The other part you are using setup.exe with a local config versus using a shared reference for both that has the catalog/packages.

IMHO, never remove what exists unless/until what you plan to add will be accepted and work.
Local prior testing assures if a test environment does not exist, using virtualization helps.....
Patrick Doman

Yes, on one system since the install was silent, I had to go in and change that.
When I did I saw Office 2007 Sharepoint Designer was still installed
I removed that and its installing now.
On the other server I get an error about free disk space but the server has 47GB free on the c: drive. So not sure what's up with that yet.
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.

There must be a minimum requirement for Office to be installed.
I would clean up the TS server. The area I would look first is the User's profile cache %systemdrive%\Users
You may have way to many profiles on this machine.