Windows Terminal Server Software Licensing Control

White Paper
®Windows Terminal Server Software Licensing
Control with AppSense Application Manager Application Manager® Windows Terminal Server Software Licensing Control with AppSense Application Manager
®Windows Terminal Server Software Licensing Control
with AppSense Application Manager
Contents
Overview 3 Background on Microsoft product licensing 3 ®Common mistakes with licensing on Windows Terminal Servers 3 How does AppSense Application Manager control licensing? 4 Conclusion 5 Appendix 6 ®Licensing Microsoft OfficeT in a Windows Terminal Server Environment 6 ®Do's and Don'ts of using OfficeT on a Windows Terminal Server 7
© AppSense 2005 Page 2 of 9 ® Windows Terminal Server Software Licensing Control with AppSense Application Manager
Overview
By preventing users from running unauthorized applications, AppSense Application Manager is already known to guarantee application integrity across Personal Computers, laptops and servers delivering improved security, reduced downtime and lower support costs. But a key question we are often asked is, "Can AppSense Application Manager be used to provide ®effective and efficient software license management in a Windows Terminal Server environment?". The answer is 'yes', and this document explains how. Additionally, we've included an appendix (provided by Microsoft) which highlights common questions around licensing Microsoft OfficeT in a ®Windows Terminal Server environment.
Background on Microsoft product licensing
Microsoft licenses many of it's applications on a per device basis. This means that a license is required for each device that accesses the software. A device is a Personal Computer, a laptop computer, PDA, workstation, terminal, or other digital electronic or analogue devices that allows access to the application.
®Common mistakes with licensing on Windows Terminal Servers ®A common mistake that many customers make when licensing their Windows Terminal Server system is to assume that 'publishing' applications to a limited user group means they are compliant with the Microsoft license agreement. With many Microsoft products this is not a valid approach to license restriction, as users within the group can potentially access the application from any device that ®connects to the Windows Terminal Server. In this case a license is required for each client device.
© AppSense 2005 Page 3 of 9 ® Windows Terminal Server Software Licensing Control with AppSense Application Manager
How does AppSense Application Manager control licensing?
AppSense Application Manager operates via a kernel level filter driver in the operating system (similar to a virus scanning filter). This filter intercepts all file execution requests to determine if the request is authorized or not. Any unauthorized requests are blocked and the user receives a message, configurable by the administrator, stating that execution has been denied. A key benefit derived from this fine level of control is the ability to define rules that the Administrator can use to restrict access to applications by user, group, client name or IP address. It is this ability to restrict application access by client name or IP address that allows AppSense Application Manager to ®effectively control and manage licensing in a Windows Terminal Server environment. Consider an organization which requires Microsoft Project to run on a limited number of devices ®where Microsoft Project is installed on a Windows Terminal Server. Without AppSense Application Manager, the organization must license Microsoft Project for each and every device that may connect ®to the Windows Terminal Server. ®By installing and configuring AppSense Application Manager on the Windows Terminal Server, the organization is able to define which devices can run Microsoft Project, therefore minimizing the number of licenses required (Figure 1). If more users require access to Microsoft Project in the future, their client devices can be added to the AppSense Application Manager configuration once additional Microsoft Project licenses have been purchased.

Figure 1 Using client names and IP addresses to control access and licensing of MSProject.exe
© AppSense 2005 Page 4 of 9 ® Windows Terminal Server Software Licensing Control with AppSense Application Manager
Conclusion
... [download for more]