Thin Client

Download file

Brief

Licensing Windows Client Operating Systems in Multiuser Scenarios March 2008

Corporate Academic • Open License• Open License Value • Select License • Academic Select • Enterprise Agreement

Summary
This licensing brief can help clarify Microsoft’s licensing policies for the Windows Vista® operating system when there is potential for multiuser scenarios. The Windows client operating system (OS) license terms do not permit multiple users to access or otherwise use one licensed copy of the software simultaneously. Windows Server operating systems are both designed and licensed for multiuse scenarios and should be used for all multiuser scenarios.

Under existing licensing policies, multiple users violate licensing terms when accessing programs hosted on a single PC, however no such violation exits when accessing programs hosted on a single server. Programs such as the Microsoft® Office System suite and/or individual Microsoft Office suite components require individual licenses for each device they operate on whether on a local device or a shared server OS.

What’s New in this Brief
• This brief replaces a previous version published in January 2008.
• Significant changes in this brief include:
• New section on the use of Windows Server
• Updated and expanded “Enabling Multiuser Scenarios” section and “Requirements for multiuse scenarios and clarifications of application licensing a Terminal Services Client Access License” section

Details
Windows desktop PC operating systems license terms do not permit multiple users to access or otherwise use one licensed copy of the software simultaneously. The following use models of multiple users simultaneously accessing a single licensed copy of the Windows XP or Windows Vista operating system are examples of mislicensed use of the product.

• There are no current migration paths based on these illustrated scenarios. Under current licensing terms each PC or access device must have one full license for Windows Vista or Windows XP purchased through the original equipment manufacturer (OEM) channel, the retail/full packaged product (FPP) channel or through Volume Licensing (upgrade). Currently no licensing terms exist that allow shared use of the OS. Each PC or device must have a unique license for an operating system using Windows Vista or Windows XP.
• The Microsoft Product Use Rights (PUR) indicates that Windows client operating systems can be licensed under the following terms:
o One license per device
o One user access at a time
o No use of the runtime for programs not installed in the device
o A device can access the OS and is appropriately licensed to run the software
o Or has an appropriate remote desktop PC license (RDL)

Multiuser systems with Windows Server
While it is not possible to provide a multiuser solution with the Windows client operating system, the Windows Server operating systems are designed to provide a multiuser solution using Terminal Services and / or other technologies.

Multiple users may access one license of Windows Server 2008 as long as every accessing user or device has a Terminal Services CAL.

The Windows Server End User License Agreement (EULA) and Product Use Rights (PUR) specify that a Terminal Services CAL (TS CAL) is required whenever a user is remotely connecting to a Windows Server for the purposes of displaying, accessing or using a graphical user interface (i.e. a desktop or application).

The TS CAL is required irrespective of the technology used to access the server remotely. This includes (but is not limited to) the use of Microsoft Terminal Services or other third party software that enables multiuser scenarios on Windows Server.

Both device and user variants of the TS CAL are available to allow customers to optimize their CAL purchase decisions based on their individual needs

NOTE: In addition to the TS CAL, every user or device that accesses a Windows Server needs to have an appropriate Windows Server CAL in addition to any other applicable software and server licenses that may be required.

Microsoft Desktop Application Licensing in a multiuser environment:
Enabling Multiuser Scenarios

Use of Microsoft desktop PC programs in a shared use environment requires that the license is acquired for every endpoint (desktop PC, thin client, etc.) that remotely accesses the desktop PC program installed on the multiuser system. This license must match the suite/edition, components, language, and version of the copy of the program being accessed.

For example:

• Product (or suite): Microsoft Office Standard 2007 and Microsoft Office Professional Plus 2007 are different products (or suites). A desktop PC licensed for Office Standard 2007 may not remotely access and use Office Professional Plus 2007.

• Components: A license for a suite (e.g. a Microsoft Office system suite) for the accessing endpoint (desktop PC, thin client, etc.) must have exactly the same components as the copy of the Microsoft Office suite being remotely accessed.

• Language: The English/multi-language version of the Microsoft Office suite may not be accessed remotely from a desktop PC, which is licensed for a single language version of the Microsoft Office suite. Likewise, remote access to a licensed copy of Microsoft Office Multi-Language Pack 2007 requires that the accessing desktop PC be licensed for the Office Multi-Language Pack 2007.

• Version: Microsoft Office System 2003 and the 2007 Microsoft Office system are different versions. You may not remotely access the 2007 Microsoft Office system from a desktop PC that is licensed for Microsoft Office System 2003.

Requirements for a Terminal Services Client Access License (TS CAL)
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 Terminal Services, a separate desktop application license is required for each desktop from which the application is accessed.

Use of Microsoft desktop applications in a Terminal Services environment requires that the license acquired for the desktops from which the desktop application is remotely accessed matches the suite/edition, components, language, and version of the copy of the application being accessed.
For example, with the release of the 2007 Microsoft Office system, generally only licenses obtained through the Microsoft Volume Licensing Program can be deployed to a network server for remote access. Most retail (full packaged product) and OEM licenses for products released in the 2007 release timeframe do not permit network use.

Frequently Asked Questions

What if a Volume Licensing customer purchases new devices that do not have an operating system preinstalled (“naked” PCs)?
Customers’ options for acquiring full licenses for the Windows operating system are through the OEM channel, the retail/FPP channel or through Volume Licensing (upgrade). If a customer purchases PCs without software, the customer needs to license the Windows operating system as FPP. Because of the cost of FPP, customers might prefer to request that their new devices come with a licensed desktop PC operating system preinstalled (e.g., the Windows Vista Business operating system, the Windows XP Professional operating system, etc.). Microsoft’s Volume Licensing programs are not a source for full licenses for the Windows operating system. These programs offer only upgrade licenses for the Windows desktop PC license. A customer using the Volume Licensing Windows desktop PC operating system media to install a full operating system is not legally licensed for desktop PC operating system software if they acquire a PC that does not have a licensed copy of the software preinstalled. The customer is also not legally licensed for the OS software if they acquire the Volume Licensing upgrade license without having a licensed copy of a qualifying desktop PC operating system installed on their device.

The Microsoft Volume Licensing Product Usage Rights (PUR) document says I can use desktop PC program software on a network device. What does this mean?
Under the network use provision, you may run the software on a network server for access and use on your licensed desktop PCs using Terminal Services (or similar functionality).

How can I provide my customers / users with a multiuser environment?
The appropriate solution to use is the Windows Server 2008 operating system which is designed for a multiuser environment.

Where can I learn more?
Additional information is available from the following:

Enabling Multiuser Scenarios: Presentation Virtualization Using Terminal Services
Download from: http://www.microsoft.com/windowsserver2008/en/us/presentation-terminal.aspx

Licensing of Microsoft Desktop Application Software for Use with Windows Server Terminal Services Download from: http://www.microsoft.com/licensing/resources/volbrief.mspx

Operating System License Requirements: Initial Operating System and Transfer of License
Download from: http://www.microsoft.com/licensing/resources/volbrief.mspx

2007 Microsoft Office System Components/Migrations/Step-Up License/Multilanguage/OEM Enrollment Download from: http://www.microsoft.com/licensing/resources/volbrief.mspx

Microsoft Product Use Rights: http://www.microsoftvolumelicensing.com/userights/PUR.aspx