Title: Terminal Server Licensing
1Terminal Server Licensing
2How Many Feel Like This ?
3Or Perhaps This ?
4Or Maybe This ?
5The Importance of Licensing
6Lack of Understanding Can Lead To
7Or This Guy Coming for You
8Whats in a License?
9Whats in a License?
- Server Licenses
- One per server instance
- Client Access Licenses (CALs)
- File and Print
- Terminal Server
- Application Licenses
- Office, Adobe, etc.
- Add-on Licenses
- Citrix, RTO, Tricerat, etc.
10Terminal Server CALs
- Temporary Terminal Server (TS) CAL
- Windows Server 2008 Device TS CAL
- Windows Server 2008 User TS CAL
- Windows Server 2003 Device TS CAL
- Windows Server 2003 User TS CAL
- Windows Server 2003 External TS Connector
- Windows 2000 TS CAL
- Windows 2000 TS Internet Connector License
- Windows 2000 Built-in TS CAL
11Still Here ?
12Terminal Server CALs
- Temporary Terminal Server (TS) CAL
- Windows Server 2008 Device TS CAL
- Windows Server 2008 User TS CAL
- Windows Server 2003 Device TS CAL
- Windows Server 2003 User TS CAL
- Windows Server 2003 External TS Connector
- Windows 2000 TS CAL
- Windows 2000 TS Internet Connector License
- Windows 2000 Built-in TS CAL
13Terminal Server CALs
- Temporary Terminal Server (TS) CAL
- Windows Server Device TS CAL
- Windows Server User TS CAL
-
-
-
-
-
-
14Types of Terminal Server CALs
- Temporary CAL
- Per-Device CAL
- Per-User CAL
- First CAL issued
- Good for 90 days
- Only get one
15Types of Terminal Server CALs
- Temporary CAL
- Per-Device CAL
- Per-User CAL
- Licensed for every known device
- Expiring CAL (variable 52-89 days)
- Expired licenses returned to the pool every 24
hours
16Types of Terminal Server CALs
- Temporary CAL
- Per-Device CAL
- Per-User CAL
- Licensed for every known user
- Still not enforced
- Can be tracked
No concurrent use model!
17Per-Device or Per-User ?
- Per-User
- More devices than users
- Users that use different PCs
- Users that connect from multiple locations
- Per-Device
- More users than devices
- PCs shared by multiple users
- Swing shifts (help desk)
Whichever is Cheaper!
18Because its all about this guy
19Typical Licensing Requirements
- Windows Server 2008/2003
- Windows Server License per Terminal Server
- File and Print CAL for each client user/device
- Terminal Server CAL for each client user/device
- Application Licenses for each user/instance
20TS Licensing Infrastructure
Client
Microsoft Clearinghouse
TS License Server
Terminal Servers
21License Server Fun Facts
- At least one activated with TS CALs installed
- Lightweight no need for dedicated role
- Only active when in use
- lt 20 MB RAM
- 5 MB for every 6000 licenses issued
- Can reside on any server
22License Server Installation
- Install the TS Licensing Role on the server
- Activate the License Server with the Microsoft
Clearinghouse - Install per-user and/or per-device CALs on the
License Server - Configure your terminal servers to discover/use
the License Server
23License Server Installation
- WS08 Installed as a Role
- Choose a Discovery Scope
- Workgroup
- Domain or Forest
- Location of license database
- NOT on a compressed drive
24TS Licensing Tool
- Activate/deactivate license servers
- Install CAL packs
- Manage licenses
- Revoke CALs
25License Service Activation
- Activated by the Microsoft Clearinghouse
- Obtains certificates from Microsoft (X.509)
- Validates the identity of the license server
- Allows terminal servers to decode CALs
- Stored in HKLM\Software\Microsoft\
TermServLicensing\ Certificates
Microsoft Clearinghouse
TS License Server
26License Server Discovery
- Two ways to locate
- Automatically
- With a little help
27TS Licensing Grace Period
- 120 Days
- Terminal Servers accept connections during grace
period - Ends upon issuance of a permanent CAL
28Automatic Discovery
- Workgroup mode Same local subnet as the terminal
server - Domain mode Installed on a domain controller
- Forest mode (formerly known as Enterprise mode)
Same Active Directory site - License server and terminal server on same
computer
29Automatic Discovery
- Terminal Servers in a
- Workgroup Every 15 minutes
- Domain Every 60 seconds
- If all known license servers are unreachable
- First contact obtains certificates to check CALs
TS License Server
Terminal Servers
30Configuring Discovery
- During Terminal Services installation
- Afterwards in Terminal Server Configuration MMC
- Group Policy
- WMI
31Upon Successful Discovery
- Once found, added to the following key
- EnterpriseServerMulti (Forest mode)
- DomainLicenseServerMulti (Domain mode)
- In the following location
- WS03 HKLM\Software\Microsoft\MSLicensing\
Parameters\ - WS08 HKLM\System\CurrentControlSet\Control\
Terminal Server\RCM\ - Checked periodically
32Per-Device Discovery Flowchart
Available on MsTerminalServices.org
33Terminal Server Licensing Modes
- Per-Device
- Per-Device CALs issued only
- Strict enforcement
- All devices need one
- Per-User
- Per-User CALs
- Not enforced
- Configured in TS Configuration or GPO
34CAL Allocation Process
- Per-Device
- Client connects to TS
- TS requests license from LS
- License issued and passed to TS
- TS passed license to client
- Client stores license in registry
35CAL Allocation Process
- First logon
- Offers HW ID from registry
- HKLM\Software\Microsoft\MSLicensing\HardwareID
- Issued a temp CAL
- Upon successful logon, TS marks CAL validated
- Second logon
- Attempt upgrade to permanent CAL
- Subsequent logons
- Present permanent to terminal server
- Terminal server validates CAL
36CAL Allocation Process
- Per-User
- Client connects to TS
- TS checks license server availability
- If found, accepts the connection
37CAL Allocation Process
- No CAL assignment takes place
- Once grace period expires LS must be reachable
- Not enforced
38Per-Device Flowchart
Available on MsTerminalServices.org
39Controlling CAL Allocation
- By default, a license server can issue CALs to
any license server - Must enable the License Servers security group in
GPO - Populate the Terminal Services Computers group on
the license server
40Preventing CAL Upgrades
- Down-level client can be issued an up-level CAL
- WS03 client obtains a WS08 CAL
- Prevent this with GPO
- Computer Configuration\Administrative
Templates\Windows Components\Terminal
Services\Licensing - Enable Prevent License Upgrade
41Split Licensing Model
WS03
WS03 License Server
WS03 Terminal Servers
WS08
WS08 License Server
WS08 Terminal Servers
42CAL Revocation
- New for WS08!
- Per-Device CALs only
- Restricted to 20 of CALs
- Performed in TS Licensing Manager or WMI
43Backing up License Servers
- Cannot move a license server
- Backup the following
- License Server root (C\Windows\System32\Lserver)
- System State
- Repair directory
- Perform and ASR backup
TSLic.edb
44License Server Recovery
- Reinstall Windows Server
- Reinstall License Service
- Restore the backup
- Or perform ASR
45License Server Recovery
- Challenges
- Must be identical hardware
- Lengthy process
- May involve extended downtime
46A Better Way
- Consider image-based backup
- Acronis, Symantec, Ghost
- Virtual Machine
- Portable files for restoration
- Easy disaster recovery integration
47High Availability
- License Service is NOT cluster-aware
- Two or more license servers
48High Availability
49HA Considerations
- Only concerned with per-device situations
- Remember the terminal server checks CALs
- No CAL issued temp
- Temp CAL connect until expired
- Full CAL connect until expired
- Expired CAL denied connection
50License Issuance Matrix
51Are we at least here?
52Troubleshooting
- Common Issues
- No license server installed
- Terminal server cannot discover license server
- Out of per-device CALs
- Wrong licensing mode on license servers
53Troubleshooting
- Check the basics
- Event Viewer
- Event ID 1004 - The terminal server cannot issue
a client license - Event ID 1010 - The terminal services could not
locate a license server - Event ID 1009 - The terminal server licensing
grace period is about to expire on ltdategt and the
service has not registered with a license server
with installed licenses - Verify the license service is installed
- Verify the service is started
- Check name resolution/PING
54MSLicensing Registry Key
- Contains the HardwareID of the client
- HKLM\Software\Microsoft\MSLicensing\Store\
- Common issues
- Event ID 1003 invalid license
- Out of licenses
- Delete MSLicensing key entirely
- Client regenerates new random HardwareID key
55Why Discovery Fails
- Network Issues
- Failed to install a license server
- Wrong scope configuration
The key is discoverability!
56Checking Discovery
- New for WS08!
- Terminal Services Configuration MMC
- Licensing Diagnosis
- Previously LSVIEW from WS03 Reskit
57License Server Config Review
- New for WS08!
- Integrated into TS License Manager tool
- Change scope
58CAL Reporting
- Previously leveraged LSReport from the WS03
ResKit - Unsupported in WS08, but still works
- WS08 includes WMI providers for reporting
59WMI Providers
- http//msdn.microsoft.com/en-us/library/aa383481.a
spx
60Per-User CAL Usage Reporting
- New for WS08!
- License server registers CAL in AD user account
- terminalServer attribute
- Queries AD, not LS database
- Relies on membership in Terminal Server License
Servers group
61Per-User CAL Usage Reporting
- Performed through TS License Manager tool
- WMI Script
This information is pulled from AD, not the
license database
TS CAL Usage Report TS License Server,"W2K8-1" TS
CAL Type,"Per User" Report Date,"5/15/2008
41953 AM" Report Scope,"Domain" Installed TS
CALs,"0" TS CALs in Use,"1" TS CAL
Availability,"None" Issued to User,TS CAL
Version,Expires On Domain\Administrator,Windows
Server 2008,Thursday August 14 2008 021415
62Howre we doing?
63Rule 1
- Microsoft has NO concurrent user license model
64Rule 2
- Ensure a License Server is installed on your
infrastructure... - And activated!
65Rule 3
- Set your terminal servers in Per-User mode
66Rule 4
- Ensure your license servers are discoverable
- Set discovery via GPO
67Dont forget this guy
68For More Information
- Microsoft TS Licensing Step-by-Step Whitepaper
- www.brianmadden.com
- www.msterminalservices.org
- www.datadr.net
- www.eventid.net
69Thanks!
70(No Transcript)