This post has an update here: Further to Licensing Office in a Terminal Services Environment.
This one is a bit of a brain buster to figure out, though Eric Ligman has done a great job of clarifying the way to properly license Microsoft Office in a Terminal Services environment:
- 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
- Office is licensed per _
desktop_ _device_ accessing the application no matter where the application is installed.
- Open Licensing provides the rights to run Office in a Terminal Services environment.
So, we have a client that we are setting up that has a combined total 22 users in their Active Directory with 11 physical machines on the network and 11 users connecting remotely via TS Gateway on SBS to their internal Windows Server 2008 R2 Standard Terminal Server.
Office and their Line of Business application will be delivered via TS RemoteApps as well as Remote Desktop Services for certain users that require a desktop to work from.
All 11 systems will have Office and all 11 TS users will be accessing Office on the Terminal Server so we will be providing them with a sum total of 22 Open Value based licenses.
A couple of key Office Open Value part numbers:
- Office 2007/2010 Open Value 3 Year Agreement with 3 Payments
- 021-07257: Office 2007/2010 Standard
- 269-09046: Office 2007/2010 Professional Plus
The Microsoft License Advisor site:
There are three physical servers on this particular network with SBS 2008 Premium and Windows Server 2008 R2 being licensed with an Open Value Agreement.
UPDATE: Eric kindly e-mailed us with some clarifications based on our client situation mentioned in this post. His thoughts are developed with some examples in our post Further to Licensing Office in a Terminal Services Environment.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book