Licensing di Office in ambienti Remote Desktop services
Spesso agli eventi, nei forum circa al corretto licensing di Office in ambienti RDS, il licensig di questo tipo di scenario è approfondito in questo documento Licensing brief: Licensing of Microsoft desktop application software for use with Windows Server Remote Desktop Services.
Di seguito alcuni punti da tenere presenti quando ci si appresta a gestire il licensing di Office 2013 in scenari RDS.
Per utilizzare Office in ambiente RDS occorre usare licenze Volume License in quanto le licenze OEM e FPP non consentono l’utilizzo del prodotto in rete.
“Microsoft Office retail (full packaged product) and original equipment manufacturer (OEM) products released in 2007 or later do not permit network use.”
“Volume Licensing desktop application licenses give the customer the right to locally install the software and also to use the same software remotely from a network server using Windows Server Remote Desktop Services (or similar technology). Local installation is not a prerequisite for network use. In some cases, local installation may not be technically possible or desired.”
La licenza di Office dovrà essere conforme in termini di suite/edizione, componenti, lingua e versione all’Office installato sul server Session Host.
“Use of Microsoft desktop applications in a Remote Desktop Services environment requires that the suite/edition, components, language, and version of the license acquired for the desktops from which the desktop application is remotely accessed matches that of the copy of the application being accessed.”
Office è licenziato in modalità per Device quindi occorre avere una licenza per ogni computer che utilizzerà il prodotto tramite RDS indipendentemente dal fatto che l’utilizzo degli RDS sia gestito per utente o per device tramite le CAL di Windows Server e le RDS CAL. Il server session host invece non richiede una licenza di Office (a meno con venga utilizzato anche come workstation locale).
“Microsoft licenses its desktop applications on a per-device basis. Per-device licensing means a customer must obtain a license for each desktop on or from which the product is used or accessed. For example, when a desktop application is accessed remotely across an organization using Windows Server Remote Desktop Services, a separate desktop application license is required for each desktop from which the application is accessed.”
“Windows Server is licensed under a server/Client Access License (CAL) model. The server/CAL model provides both user and device licensing options. Customers with more devices than users can license users rather than devices. In contrast, Microsoft desktop applications are licensed under a device-based model. This means, while user CALs permit a particular user to access the server software from any device in a Remote Desktop Services environment, a Microsoft desktop application license permits that user to access the application only from the desktop to which the license is assigned.
Remote Desktop Services can be used by both Windows desktops and non-Windows desktops (e.g. Linux PCs or thin client devices). Microsoft desktop applications must be licensed for each and every desktop from which they are remotely accessed regardless of whether that desktop is a Windows desktop.”
“Every device that uses Windows Server Remote Desktop Services to remotely access Microsoft Office requires a Remote Desktop Services CAL, in addition to Windows Server CAL and a Microsoft Office license. Dedicate a Microsoft Office license for every desktop on or from which you plan to use or access Microsoft Office, even if that use is only occasional. Examples of desktops that might access Microsoft Office using Windows Server Remote Desktop Services functionality include Windows-based workstations, Macintosh computers, and UNIX workstations. The servers hosting the applications do not require Microsoft Office licenses.
Nel caso l’azienda voglia far utilizzare Office tramite RDS ai sui dipendenti dal computer di casa sarà necessario acquistare le Work At Home (WAH) Licenses oppure coprire le licenze di Offoce con la Software Assurance.
Scenario 7: Remote Access from a Home Device
Company employees remotely access a corporate network from home, using desktops that they own. While connected, the employees use Remote Desktop Services to access Microsoft Office on a corporate-owned server.
A Microsoft Office license for the version of Microsoft Office running on the server is required for the home desktop in this scenario. The company can enable this scenario by purchasing Work At Home (WAH) Licenses for the employees’ home desktops. Customers with active Software Assurance can also acquire Home Use Program (HUP) licenses for their employees’ home desktops. In addition, customers with active Software Assurance can also use their Roaming Use Rights to remotely access Microsoft Office software from qualified 3rd party devices. Please contact a Microsoft licensing specialist or Microsoft Volume Licensing Partner for more information about “Work at Home,” ”Home Use Program” and “Roaming Use Rights” options available for Microsoft Office.
Un’altra cosa da tenere presente è che non è possibile riassegnare una licenza prima di 90 giorni, considerazione da tenere presente nel caso venga dismesso un computer aziendale.
FAQ 8 I have installed Microsoft Office on a network server for access and use using Windows Server Remote Desktop Services. I have acquired Remote Desktop Services User Client Access Licenses for each of my employees. I want my employees to be able to access Microsoft Office from any company managed desktop. What licenses are needed to properly license Microsoft Office within this environment?
Since Microsoft Office is licensed through a device-based licensing model only, each desktop that is used to access Microsoft Office using Remote Desktop Services must have a separate Microsoft Office license dedicated to it. Licenses for Microsoft Office cannot be shared across desktops to support concurrent use. In addition, you may not reassign a license within 90 days of the last assignment. Furthermore, Microsoft Office retail (full packaged product) and original equipment manufacturer (OEM) products released in 2007 or later do not permit network use.
Se non è possibile stimare quanti saranno i device di terze parti che utilizzeranno Office tramite RDS è possibile utilizzare i benefici dei roaming rights disponibili se le Volume License di Office sono coperte Software Assurance. Ciò significa che sfruttando roaming rights è possibile licenziare di fatto Office in modalità per utente anzichè per device.
FAQ 9 I have installed Microsoft Office on a network server for access and use using Windows Server Remote Desktop Services. I want my employees to be able to access Microsoft Office from 3rd party devices. What licenses are needed to properly license Microsoft Office within this environment?
With active Software Assurance for Office in Volume Licensing, you can exercise your roaming rights benefit to enable users to remotely access the Office software on a qualified third-party device, regardless of the technology used to access the software. Roaming rights do not permit the Office software be installed and run locally on the third-party device. Roaming rights also apply only to the primary user of a licensed device with Software Assurance coverage, and are subject to the limitation on the number of users in the base license terms.
Se si è acquistato Office in modalità OEM è possibile dopo 90 giorni inserirlo nel proprio contratto Volume Licensing coprendo la licenza OEM con Software Assurance.
FAQ 10 I have just purchased several new desktops from an OEM with preinstalled licenses for Microsoft Office Professional 2010. Can I install the software on a network server and use these desktops to remotely access it? What if the copy running on the server is licensed under my Volume Licensing agreement—does that change the answer?
The answer is no in both cases. First, the OEM license does not permit access and use from a network server. Even if you are licensed under your Volume Licensing agreement to use the software on a network server from licensed desktops, your OEM Office licenses do not permit you to access the Volume Licensing software on the server. The OEM versions and Volume Licensing editions of Microsoft Office are not the same. However, within 90 days of purchase, you can acquire Software Assurance coverage for your OEM licenses under your Volume Licensing agreement. Doing so gives you rights to a Volume Licensing Office Standard edition (please refer to the Volume Licensing Product List for a more complete description of the rules related to purchasing Software Assurance for OEM software). You may use the software locally on those licensed desktops enrolled in Software Assurance or remotely from a network server (e.g., using Remote Desktop Services).
Se una licenza di Office è coperta da Sofware Assurance garantisce la possibilità di poter utilizzare tramite RDS anche una versione di prodotto diversa da quella della licenza.
FAQ11 I have Office Professional Plus 2013 installed on a network server. Can I access this copy of Microsoft Office using Remote Desktop Services from a desktop that has Office Professional Plus 2010 installed and is covered by Software Assurance?
Yes. To use Office Professional Plus 2013 in this scenario, you would need to be licensed for Office Professional Plus 2013. A desktop that is licensed for and has Office Professional Plus 2010 installed and is covered by active Software Assurance is considered to be licensed for Office Professional Plus 2013.
Concludendo per utilizzare Office in scenari RDS occorrono oltre licenze necessarie per l’utilizzo degli RDS (CAL + RDS CAL) una licenza di Office per ogni device che utilizzerà il prodotto. Per rendere più dinamiche le possibilità di utilizzo di Office tramite RDS conviene coprire le licenze con la Software Assurance.
Per quanto riguarda Office 365 dalla metà del 2014 è possibile utilizzarlo in ambiente RDS grazie alla Shared Activation Support, a riguardo si vedano i seguenti:
- RDS and shared computer support for Office 365 ProPlus coming soon!
- Office 365 shared computer activation
Per quanto riguarda invece l’installazione dell’Office sul server Session Host l’approccio più semplice è quello di installare una versione del prodotto scaricata dal sito Volume Licensing.
A riguardo si vedano i seguenti:
- KB2810023 “This copy of Microsoft Office 2013 cannot be used on a computer running Terminal Services” error when you try to open the Click-to-Run version of an Office 2013 program or suite on a terminal server.
- Deployment methods for Office 2013
- How to install and activate Office Professional Plus 2013 on a terminal server
- How to install the MSDN/TechNet copy of Microsoft Office 2013 on a Windows Server that is running Remote Desktop
Ciao,
ti chiedo un chiarimento su questa nota:
“Concludendo per utilizzare Office in scenari RDS occorrono oltre licenze necessarie per l’utilizzo degli RDS (CAL + RDS CAL) una licenza di Office per ogni device che utilizzerà il prodotto. Per rendere più dinamiche le possibilità di utilizzo di Office tramite RDS conviene coprire le licenze con la Software Assurance.”
Le CAL non vanno calcolate solo sugli utenti attivi in AD? Ricordo o a suo tempo ho capito male quanto mi era stato spiegato dal call-center di MS?
Grazie
Le CAL vanno calcolate in base a come si intende gestire il licensing ovvero per Device o per Utente o anche per situazioni miste.
Avevo discusso le varie possibilità di gestione delle CAL in questo post che sebbene sia data è ancora attuale
http://www.devadmin.it/2009/10/06/cal-client-access-licensing/
Nel caso di CAL per Utente occorre avere una CAL per ogni utente nominale che spesso coincidono con gli utenti AD ma non sempre, si pensi ad esempio agli utenti creati per l’esecuzione di un determinato servizio che rimangono esenti da CAL o a casi in cui un utente fisico accede con più di un utente AD a lui dedicati per gestire la sicurezza in scenari differenti (per esempio acceso locale e remoto tramite VPN)
Ciao Ermanno,
riprendo questo post che risale a 2 anni fa ma che trovo ancora attuale per chiederti se riesci a chiarirmi un dubbio a cui non trovo risposta pur avendo letto un sacco di forum e guide Microsoft al licensing.
Lo scenario è quello di 60 client Windows che hanno necessità di utilizzare Office sia sul client locale sia in desktop remoto su un server aziendale.
Dando per scontato la necessità di essere in regola con le cal server e le cal rds per quanto riguarda le licenze Office hanno bisogno di 60 licenze o di 120 licenze?
Secondo la mia interpretazione dovrebbero bastare 60 licenze di una versione Office che includa il Remote Use Rights (quindi Office a volume oppure 365 proplus) che dovrebbe coprire sia l’utilizzo in locale sia l’utilizzo in remote desktop tramite appunto il Remote Use Rights purchè sul server sia installata la medesima versione che è installata sul client.
Grazie
Ciao Diego,
i Remote Use Rights sono concessi in Microsoft Office software in Volume Licensing o in Microsoft Office 365 ProPlus Subscription Service in Volume Licensing e in effetti consento l’uso della stessa versione di Office su client o tramite server RDS
Dal seguente Licensing Microsoft Office software in Volume Licensing (https://download.microsoft.com/download/3/D/4/3D42BDC2-6725-4B29-B75A-A5B04179958B/Licensing_Microsoft_Office_Software.pdf):
“With Remote Use Rights, a company may install Microsoft Office on a single device such as a server and then allow users to access Microsoft Office remotely from licensed desktops (or as the primary user of the licensed device hosting the session) as if the desktop application was installed locally on their desktops. Remote Use Rights are granted under desktop application licenses for Microsoft Office acquired through Microsoft Volume Licensing.
When a copy of Microsoft Office software is installed on a server, users may remotely access and use the copy of Microsoft Office from any licensed device. When a copy of Microsoft Office is installed on a desktop, the primary user of the desktop may remotely access and use the software from any other device. Other users in the organization may also access and use the copy of software installed on a desktop from other separately licensed devices.
Examples of remote access technology used with Microsoft Office licensed as a desktop application include Remote Desktop Services (RDS) as part of Microsoft Virtual Desktop Infrastructure (VDI) solution. Using any component of this technology requires an RDS CAL license for each user or device used to access the server remotely.
Components of a Microsoft Office suite may vary per software product edition. Under Remote Use Rights, a customer may only access a copy of the same edition of Microsoft Office as its copy on their individual licensed device. For example, if a customer is using a device licensed for Microsoft Office Standard 2016, they may access Office Standard 2016 running on a server. The device may not use Remote Use Rights to use components of Office Professional Plus 2016.”
Dal seguente Licensing Microsoft Office 365 ProPlus Subscription Service in Volume Licensing (http://download.microsoft.com/download/3/D/4/3D42BDC2-6725-4B29-B75A-A5B04179958B/Licensing_Office365_ProPlus_in_Volume_Licensing.pdf):
“Virtualization with Remote Desktop Service (RDS)
Shared computer activation is another activation mode for Office365 ProPlus and integrates with RDS virtualization technologies. Examples of virtualization scenarios using RDS role enabled include Remote Desktop Session Host and Pooled VDI (using RDS). When Office 365 ProPlus is deployed on a network server with RDS role enabled, each Licensed User may sign in with their own subscription account to temporarily activate Office via shared computer activation*. Shared computer activation also enables use of Office 365 ProPlus on shared devices such as those on a factory floor or medical personnel in a hospital. Deploying Office 365 ProPlus using shared computer activation does not count against a user’s five desktop installations of Office 365 ProPlus.
*Additional licenses are required to enable virtualization deployments on a network server. Please consult a Volume Licensing Partner to determine your license needs.”
Quindi nello scenario che prospettavi tu servono 60 licenze di Office, inoltre vedi anche il seguente link per sapere quali versioni di Office supportano
la Desktop virtualization e la Shared computer activation
https://technet.microsoft.com/en-us/library/office-applications-service-description.aspx
Inoltre vedi anche la riposta data da Peter Zhang (Microsoft Support Engineer) nella discussione Offic 365 Business Plans and RDS Server
(https://partnersupport.microsoft.com/en-us/par_onlserv/forum/par_office365/offic-365-business-plans-and-rds-server/3ba3268a-216b-4d4e-b477-6bfaa54e03f4)
Ciao Ermanno,
ti ringrazio per la tempestiva e soprattutto esaustiva risposta a conferma della mia interpretazione.
Ho cercato conferma perché di solito tutti gli esempi che si trovano parlano di client senza Office installato in locale perché usato esclusivamente in remoto (zero client/ thin client) ma in questo caso è necessario che l’utente possa usare l’office anche in locale ed è molto positivo che non debba raddoppiare le licenze e di conseguenza i costi.
Grazie
Diego