Home Applications How Microsoft Office Is Licensed In A Terminal Services Environment

How Microsoft Office Is Licensed In A Terminal Services Environment

0
43
0

Answer To A Question On How Microsoft Office Is Licensed In A Terminal Services Environment And Why OEM Office Doesn’t Cover It, In Plain English

 

The Microsoft Small Business Community Blog posted a great article on How Microsoft Office Is Licensed In A Terminal Services Environment due to an email from a Partner stating they found Microsoft licensing to be “confusing and convoluted” in regards to Microsoft Office in a Terminal Services environment.  This was posted in response to an earlier Blog post the Microsoft Small Business Community Blog had: “OEM Office for Terminal Services? You might want to check that EULA…”  To be fair, here is an exact quote from the Partner:

 

“Microsoft’s insanely confusing and convoluted licensing programs, and their incredibly unreasonable demands regarding the licensing of some products (especially concerning Office on a Terminal Server)”

 

The request made by the Partner was, and this again is a direct quote, “to get at least an explanation that could help us to rationalize such stupid licensing requirements to our clients?”   In addition, they added, “I am looking for someone who really knows their stuff, not someone who is reading a EULA to me from their screen in their call-center.”  As such, I thought I would share the explanation on Office licensing and Terminal Services “in plain English” I sent back to help address this:

 

1.      Microsoft Office is a desktop application. As such, you need (1) Microsoft Office license per desktop using the Microsoft Office software. Terminal Services does not change the number of devices accessing and using a software application, it merely provides another avenue to access the software through. So licensing Microsoft Office doesn’t change at all regardless if Terminal Services is used or not. You still need one license per device accessing and using the Microsoft Office application.

 

2.      When someone purchases a commercial software license (Microsoft or not), they are not purchasing the software itself. The software bits and bytes are owned by the software publisher. What you are buying is the rights to use the software under the terms and conditions of the license agreement you purchased. As such, when purchasing software, you should purchase the license that provides you with the rights you want.

 

a)      For instance, if you want to be able to run Microsoft Access, don’t buy a Microsoft Standard license because this does not give you the rights to run Access. Be sure to purchase an Office license that does provide you the rights to run Microsoft Access.
 
b)      If you want to be able to run Microsoft Publisher, don’t buy a Microsoft Standard license because this does not give you the rights to run Publisher. Be sure to purchase an Office license that does provide you the rights to run Microsoft Publisher.
 
c)      If you want the rights to be able to transfer your Office license from one machine to another one when you retire the original PC, be sure you buy a license that provides those rights. Don’t buy an OEM Office license since OEM licenses do not provide transfer rights. Volume Licensing and Retail Box Office licenses do provide transfer rights.
 
d)     If you want the rights to be able to install a prior version of Office instead of the version you purchased, be sure to purchase an Office license with downgrade rights. Don’t purchase an OEM or Retail Box of Office 2007 since those do not have downgrade rights. Purchase a Volume License of Office 2007 since it does have Downgrade Rights.
 
e)      If you want the rights to be able to access and run Office from a network device, be sure to purchase an Office license with Network Storage and Use Rights. Don’t purchase an OEM Office license since it does not provide Network Storage and Use rights. Purchase a Volume License of Office so that you have Network Storage and Use Rights.
 

f)       The statement that because you have an OEM Office license, you should be able to use it in a Terminal Services environment is the same as saying you have an Office Standard license so you should be able to run Access. Why? You did not purchase the rights to have Network Storage and Use rights just like you did not pay to have rights to run Access, so why should you be entitled to do so? Simply purchase a license that provides you with what you want.

 

 

 

 

More Resources:

DABCC DABCC.com, the world leader in sharing the finest Virtualization & Cloud news and support resources. #Citrix, #VMware, #Microsoft, #Mobility and much more! Brought to you by @douglasabrown & team!
| LATEST RESOURCES

White Papers

    Dell Customized VMware ESXi 6.5 Upgrade Scenarios White Paper

    VMware recently announced vSphere 6.5 release. Dell supports direct upgrade to Dell customized ESXi 6.5 from both ESXi 6.0 Update 2 and ESXi 5.5 Update 3 branches. This document talks about some of the best practices to be considered before upgrading to Dell customized ESXi 6.5 in terms of UEFI Secureboot. This white paper is relevant for all […]

    Downloads

      Free Tool! SPDocKit Pulse – Autodiscover SharePoint Farms and Servers

      Autodiscover SharePoint farms and the accompanying servers in your domain. Use the interactive dashboard to monitor Farm performance and track status per Server (RAM, CPU and disk data). Download Free Tool powered by SPDocKit: https://pulse.spdockit.com/

      On-Demand Webinars

        Office 365 Planning, Implementing, and Optimizing on Virtual Desktops – On-Demand Webinar

        In this webinar hosted by FSLogix CEO Kevin Goodman, and Solutions Architect Dave Young, they present the critical elements to get your Office 365 implementation optimized. They begin by detailing the challenges involved with Office 365 on virtual desktops, and cap it off with answers to some of the vital planning questions, such as: How […]

        Latest Videos

          Microsoft Video: Modern Windows 10 management strategies, using Configuration Manager and Microsoft Intune

          Lead engineer Mark Florida joins Simon May to demonstrate your options for managing Windows 10 devices using traditional management strategies with Configuration Manager and Cloud-based, modern management with Microsoft Intune. From the fine folks at Microsoft.

          Close