Terminal Server Em Windows

download Terminal Server Em Windows

of 22

Transcript of Terminal Server Em Windows

  • 8/14/2019 Terminal Server Em Windows

    1/22

    Your independent source for application and desktop

    virtualization.

    Sign in |Join

    Topics

    Blogs

    Forums

    Videos

    Books

    Events

    Aout !s

    Blogs" #riginal Blogs on Brian$adden.com"Brian $adden"T%e !ltimate &uide to 'indo(s)**+ Terminal Server ,icensing

    $arketplace

    Object1

    Object2

    Object3

    http://www.brianmadden.com/login.aspx?ReturnUrl=%2Fblogs%2Fbrianmadden%2Farchive%2F2004%2F04%2F01%2Fthe-ultimate-guide-to-windows-2003-terminal-server-licensing.aspxhttp://www.brianmadden.com/user/CreateUser.aspx?ReturnUrl=http://www.brianmadden.com/user/CreateUser.aspx?ReturnUrl=http://www.brianmadden.com/topics/http://www.brianmadden.com/bloglist/http://www.brianmadden.com/forums/http://www.brianmadden.com/videoshttp://www.brianmadden.com/books/http://www.brianmadden.com/events/http://www.brianmadden.com/aboutus/http://www.brianmadden.com/bloglisthttp://www.brianmadden.com/blogs/default.aspx?GroupID=4http://www.brianmadden.com/blogs/brianmadden/default.aspxhttp://www.brianmadden.com/blogs/brianmadden/default.aspxhttp://www.brianmadden.com/blogs/brianmadden/archive/2004/04/01/the-ultimate-guide-to-windows-2003-terminal-server-licensing.aspxhttp://www.brianmadden.com/blogs/brianmadden/archive/2004/04/01/the-ultimate-guide-to-windows-2003-terminal-server-licensing.aspxhttp://www.brianmadden.com/blogs/brianmadden/archive/2004/04/01/the-ultimate-guide-to-windows-2003-terminal-server-licensing.aspxhttp://www.brianmadden.com/blogs/brianmadden/archive/2004/04/01/the-ultimate-guide-to-windows-2003-terminal-server-licensing.aspxhttp://ad.doubleclick.net/jump/bmad/;ptile=2;sz=125x125;ord=123456789?http://ad.doubleclick.net/jump/bmad/;ptile=3;sz=125x125;ord=123456789?http://ad.doubleclick.net/jump/bmad/;ptile=4;sz=125x125;ord=123456789?http://ad.doubleclick.net/jump/bmad/;ptile=4;sz=125x125;ord=123456789?http://ad.doubleclick.net/jump/bmad/;ptile=3;sz=125x125;ord=123456789?http://ad.doubleclick.net/jump/bmad/;ptile=2;sz=125x125;ord=123456789?http://www.brianmadden.com/http://www.brianmadden.com/user/CreateUser.aspx?ReturnUrl=http://www.brianmadden.com/topics/http://www.brianmadden.com/bloglist/http://www.brianmadden.com/forums/http://www.brianmadden.com/videoshttp://www.brianmadden.com/books/http://www.brianmadden.com/events/http://www.brianmadden.com/aboutus/http://www.brianmadden.com/bloglisthttp://www.brianmadden.com/blogs/default.aspx?GroupID=4http://www.brianmadden.com/blogs/brianmadden/default.aspxhttp://www.brianmadden.com/blogs/brianmadden/archive/2004/04/01/the-ultimate-guide-to-windows-2003-terminal-server-licensing.aspxhttp://www.brianmadden.com/blogs/brianmadden/archive/2004/04/01/the-ultimate-guide-to-windows-2003-terminal-server-licensing.aspxhttp://www.brianmadden.com/login.aspx?ReturnUrl=%2Fblogs%2Fbrianmadden%2Farchive%2F2004%2F04%2F01%2Fthe-ultimate-guide-to-windows-2003-terminal-server-licensing.aspx
  • 8/14/2019 Terminal Server Em Windows

    2/22

    Object4

    Object5

    Brian Madden's Blog

    Home

    http://ad.doubleclick.net/jump/bmad/;ptile=1;sz=728x90;subject=TS;ord=123456789?http://ad.doubleclick.net/jump/bmad/;ptile=1;sz=728x90;subject=TS;ord=123456789?http://www.brianmadden.com/blogs/brianmadden/default.aspxhttp://ad.doubleclick.net/jump/bmad/;ptile=1;sz=728x90;subject=TS;ord=123456789?http://ad.doubleclick.net/jump/bmad/;ptile=5;sz=120x600;subject=TS;ord=123456789?http://www.brianmadden.com/blogs/brianmadden/default.aspx
  • 8/14/2019 Terminal Server Em Windows

    3/22

    Object6

    http://ad.doubleclick.net/jump/bmad/;ptile=6;sz=310x950;subject=TS;ord=123456789?subject=TS
  • 8/14/2019 Terminal Server Em Windows

    4/22

    Syndication

    -SS for osts

    Atom

    -SS for /omments

    Recent Posts

    '%at0s t%e difference et(een t%e 12/A client31 t%e 14enApp lug5in31 and t%e 1/itri6

    -eceiver71 A guide to /itri60s client names and variants.

    /itri6 drops t%e (ord 84enApp9 from t%eir 2/A client. /ould t%is %int at pulis%ed appsfrom 4en:esktop7

    ;o( to use t(itter for real (ork purposes pervisor on a $ac running $ac #S 4 in a V$?

    Tags

    Application Streaming

    Brian$adden.com 2nformation

    BriForum

    BriForum articipant Blog Entries

    Business 2nformation

    /itri6

    /itri6 iForum

    /itri6 $etaFrame resentation Server +.*

    /lient Soft(are

    Editorials 2ndustr> Buzz

    ,icensing

    ,ong%orn Terminal Services

    $icrosoft Terminal Services

    erformance

    Securit>

    Server Virtualization

    Support

    Tec%nical Articles

    T%e Future

    T%in /lient ;ard(are

    T%ird art> Soft(are

    V:2

    Virtualization

    'e 2nterface

    Vie( more

    Archives

    $a> )**@

  • 8/14/2019 Terminal Server Em Windows

    5/22

    Feruar> )**@ )**@

  • 8/14/2019 Terminal Server Em Windows

    6/22

    Feruar> )** )**

  • 8/14/2019 Terminal Server Em Windows

    7/22

    functioning ecause t%e> (erenIt licensed properl>. Terminal Servers running on 'indo(s )***

    (ere t%e first to use $icrosoftIs ne( licensing enforcement tec%nolog>3 and 'indo(s )**+ uildson t%at.

    T%e onl> t%ing t%at c%anges faster t%an tec%nolog> is t%e licensing of tec%nolog>. For t%at reason3

    itIs important to note t%at t%is licensing paper (as up5to5date (%en it (as (ritten. ;o(ever3 itIs

    possile t%at t%e details of $icrosoft licensing %ave c%anged since t%en. You can find current

    information on t%e (e at (((.microsoft.comlicensing or (((.rianmadden.com.

    T%is paper concludes (it% a look at %o( t%ird5part> applications are licensed in Terminal Server

    environments.

    Terminal Server !!" #icensing $verview

    Before addressing t%e tec%nical components t%at (ill make up >our licensing infrastructure3 letIs

    revie( $icrosoftIs licensing polic>. $icrosoft licenses can e divided into t(o groupsH

    ,icenses reKuired for eac% server.

    ,icenses reKuired for clients.

    Terminal Server implementation (ill reKuire ot% client and server licenses.#icenses Re%uired &or ach Terminal Server

    $icrosoft reKuires one license for eac% server in a Terminal Services environment. T%is license3

    kno(n as a 8server license39 is Lust t%e standard 'indo(s Server )**+ licenseM>ou donIt needan>t%ing special to run Terminal Server. 2t is t%e same license used for t%e ase server operating

    s>stem of an> 'indo(s )**+ serverM(%et%er t%at server is an E6c%ange Server3 a SN, Server3 ora file and print server. ;o(ever3 unlike some $icrosoft server applications t%at reKuire specific

    server licenses our server.

    Microso&t Terminal Server (lient Access #icenses

    Before >ou get too e6cited aout t%e fact t%at >ou donIt need a special server license to run

    Terminal Services3 rememer t%at >ouIll need a client license for ever>one t%at connects to a

    'indo(s )**+ Terminal Server.

    rior to 'indo(s Server )**+3 a Terminal Server /lient Access ,icense computer device t%at connected to a Terminal Server. T%is licensing s>stem is kno(n as 8per

    device9 licensing. $icrosoft defined one 8device9 as a uniKue piece of %ard(are used to access a

    server. 2f >ou %ad t(o computers and >ou accessed t%e same server from eac% of t%em3 >ou %ad t(o

    different devices and needed a separate 8per device9 license for eac%. Suc% (as t%e case even if >ounever used ot% devices at t%e same time. Daturall> t%is met%od of licensing elicited numerouscomplaints.

    2n 'indo(s Server )**+3 $icrosoft added a second TS /A, option. T%is 8per user9 client licensing

    option allo(s >ou to purc%ase one license for eac% user account. A user can t%en access a Terminal

    Server from multiple client devices using one license. 8er user9 TS /A,s are associated (it% useraccounts3 so t(o users cannot s%are a license even if t%e> never log on at t%e same time. 2f t(o users

    s%are t%e same p%>sical computer3 t%en it mig%t e preferale to emplo> t%e 8per device9 licenseoption discussed in t%e previous paragrap%.

    $icrosoft also offers an 8e6ternal connector9 Terminal Server client access license t%at >ou u> for

    a server and lets >ou connect an unlimited numer of non5emplo>ees to t%e server.,etIs look at t%e t%ree different Terminal Server client license options.

    $)tion *+ Terminal Server ,-evice. (lient Access #icense

    http://www.microsoft.com/licensinghttp://www.microsoft.com/licensinghttp://www.brianmadden.com/http://www.microsoft.com/licensinghttp://www.brianmadden.com/
  • 8/14/2019 Terminal Server Em Windows

    8/22

    Terminal Services licensing %as traditionall> een %andled > t%e Terminal Server device /lient

    Access ,icense ees of t%e compan> t%at

    oug%t t%e license3 (%at %appens if a compan> (ants to e6tend its Terminal Server environment tousiness partners (%ere t%e names of users and client devices (ouldnIt e kno(n7 '%at %appens if

    a compan> (ants to e6tend an application via a Terminal Server to t%e 2nternet7 Tec%nicall>follo(ing t%e $icrosoft terms3 >ou (ould need to u> a license for eac% uniKue user or computer

    t%at connected to >our server.

    /learl> t%is is not feasile. To address t%is c%allenge3 $icrosoft introduced t%e E6ternal /onnector

    ,icense stems are e6tended to e6ternal parties3 includingusiness partners and t%e pulic.

    E/,s are availale for all ne( $icrosoft products account for unlimited users and client devices=.

    2n Terminal Server )**+ environments3 E/,s provide a simple (a> to u> 8concurrent9 userlicenses for t%ose (%o need to connect to >our server. 2f >ou (anted to open up a server to trading

    partners3 >ou (ould u> a Terminal Server E/,.

    At t%is point >ou mig%t e (ondering (%> >ou canIt Lust u> E/,s and forget all t%is per5user andper5device garage. $icrosoft %as strict rules governing t%e use of E/,s3 and users of t%e TS E/,s

    cannot e emplo>ees of t%e organization t%at oug%t t%e license.

    Microso&t Windows Server (lient Access #icenses

    Do( t%at >ou understand t%e difference et(een t%e t%ree Terminal Server5specific /A,s3 >ou need

    to kno( t%at eac% client device also needs a standard 'indo(s Server )**+ /A,. To legall> accessa 'indo(s )**+ Terminal Server3 eac% client seat reKuires eac% of t%e follo(ing licensesH

    'indo(s Server )**+ /lient Access ,icense.

    'indo(s Server )**+ Terminal Server /lient Access ,icense.

    #icense *+ Windows Server (lient Access #icense 0Server (A#1

    An> user needs t%is 'indo(s Server /A, to access a 'indo(s )**+ server. T%is license providest%e 8asic9 access rig%ts t%at allo( users to store files3 print3 and e part of an Active :irector>. 2f

    >ou %ave a unified Active :irector> (it% *** users3 t%en >ouIll %ave *** 'indo(s Server /A,s.

    #icense + Windows Server !!" Terminal Server (lient Access #icense 0TS (A#1

    'e discussed t%e TS /A,

  • 8/14/2019 Terminal Server Em Windows

    9/22

    access a 8remote control9 session on a Terminal Server.

    2f >ou %ave a ***5user Active :irector> environment (it% a fe( Terminal Servers t%at provide

    applications for +** users3 t%en >ouIll need *** 'indo(s Server /A,s and +** Terminal Server/A,s.

    S)ecial #icensing Scenarios

    rior to 'indo(s Server )**+3 t%ere (ere special license rules for specific situations. $icrosoft %asc%anged t%e (a> t%ese situations are %andled (it% t%e introduction of 'indo(s Server )**+.

    TS (A# Re%uirements when (onnecting to a Terminal Server &rom Windows 2P

    rior to 'indo(s Server )**+3 client (orkstations t%at ran 'indo(s DT3 )***3 or 4 rofessional

    %ad t%e rig%t to otain a 8free9 TS /A,. T%e onl> reKuirement (as to purc%ase a TS /A, for client

    devices t%at ran an operating s>stem lo(er t%an t%e Terminal Server operating s>stem. For e6ample3'indo(s )*** rofessional (orkstations did not reKuire purc%ase of a TS /A, to connect to a

    'indo(s )*** Terminal Server since 'indo(s )*** client devices %ad t%e rig%t to otain a free'indo(s )*** TS /A,. Also3 since t%ese licenses (ere ack(ards compatile3 t%e 'indo(s )***

    TS /A, (ould also appl> if >ou (ere using a 'indo(s 4 rofessional client to connect to a

    'indo(s )*** Terminal Server.

    Since 'indo(s 4 (as released over a >ear efore 'indo(s Server )**+3 man> people oug%t'indo(s 4 rofessional (it% t%e assumption t%at it (ould include a 8free9 'indo(s Server )**+

    TS /A,. ;o(ever3 (it% t%e release of 'indo(s )**+3 $icrosoft removed t%e 8free9 TS /A,license t%at (as uilt5in to 'indo(s 4 rofessional. !nfortunatel>3 t%is announcement came (ell

    after man> organizations oug%t multiple copies of 'indo(s 4 assuming t%at its free TS /A,

    (ould (ork (it% 'indo(s )**+ Terminal Servers.

    Degative response to t%is announcement prompted $icrosoft grant a free 'indo(s )**+ TS /A,to an>one (%o o(ned a 'indo(s 4 rofessional license on April )+3 )**+ efore t%e

    release of 'indo(s Server )**+.:oes >our cop> of 'indo(s 4 come (it% a free 'indo(s Server

    )**+ TS /A,7 2f >ou oug%t it efore April )G3 )**+3 t%en it does. 2f >ou oug%t if after t%at it doesnot3 and >ouIll %ave to u> a 'indo(s )**+ TS /A,. ou %ad TS /A,s t%at (ere enrolled in

    $icrosoft Enterprise Agreements or Soft(are Assurance3 t%en >ou automaticall> Kualified for t%e'indo(s )**+ TS /A, upgrade.=

    2nterestingl>3 t%e added TS /A, costs of Terminal Server on 'indo(s Server )**+ %as upset some

    companies so muc% t%at t%e> are claiming it as t%e sole reason t%at t%e> (ill keep t%eir Terminal

    Servers running on 'indo(s )***.

    The Wor34at4Home TS (A#

    $icrosoft licensing agreements also used to provide 8(ork5at5%ome9 licenses for Terminal Servers.

    T%ese (ere additional3 c%eap TS /A,s for users t%at used an office computer to access TerminalServers and t%en (ent %ome and accessed Terminal Servers from a %ome /. 'it% t%e advent of

    'indo(s )**+Is ne( per5user TS /A,3 t%e (ork5at5%ome license is no longer an option.

    Similar to TS /A,s3 an> prior (ork5at5%ome licenses t%at are enrolled in an Enterprise Agreementor Soft(are Assurance ma> e upgraded to current licenses.

    Windows !!" Terminal Server #icensing (om)onents

    'indo(s DT Server G.* Terminal Server Edition used t%e 8%onor s>stem9 for tracking licenses.

    '%ile >ou (ere legall> supposed to purc%ase t%e correct licenses3 t%ere (as not%ing tec%nicall>

    stopping >ou from connecting more users t%an >ou paid for. '%ile t%e %onor s>stem (orked (ellfor s>stem administrators and t%ieves3 it %as not (orked as (ell for $icrosoft s%are%olders.

    As alluded to in t%e opening sentences of t%is paper3 t%is s>stem c%anged (%en 'indo(s )*** (as

    released. 2n Terminal Services for 'indo(s )***3 a $icrosoft 8Terminal Services ,icensing

  • 8/14/2019 Terminal Server Em Windows

    10/22

    Service9 is reKuired to run on one or more servers on >our net(ork. T%is Terminal Services

    licensing service is responsile for monitoring3 distriuting3 and enforcing TS /A, usage.$icrosoft implemented t%is licensing service as a 8service to t%eir customers9 (%o (ere 8deepl>

    concerned t%at t%e> mig%t accidentall> forget to pa> for a license or t(o3 ever> once in a(%ile.9 2n

    Terminal Server environments running on 'indo(s )*** platforms3 t%is licensing serviceinfrastructure guarantees t%at t%ere e no 8accidentall> forgetting9 to purc%ase all t%e needed

    licenses.'indo(s )**+ Terminal Servers also make use of licensing serversMalt%oug% t%e e6act mannerdepends upon for (%ic% of t%ree licensing options a server is configured ou enale Terminal Services3 t%e server immediatel> egins tr>ing to locate a licensing server. 2tt%en communicates (it% t%e licensing server to ensure t%at client devices are licensed properl>.

    Eac% Terminal Server must e configured to use per5user3 per5device3 or e6ternal connector licenses.

    #icenses

    T%e license service t%at runs on a 'indo(s )**+ server keeps track of seven different t>pes of

    licenses. T%ese include four t>pes of licenses for 'indo(s )**+ Terminal Servers and t%ree t>pes= for 'indo(s )*** Terminal Servers. T%e seven t>pes of 'indo(s)**+ client licenses includeH

  • 8/14/2019 Terminal Server Em Windows

    11/22

    'indo(s Server )**+ TS :evice /A,s. T%is license is t%e per5device /A, t%at is issued to

    uniKue client %ard(are devices. 2t allo(s t%e client device to access 'indo(s )*** and)**+ Terminal Servers.

    'indo(s Server )**+ TS !ser /A,s. T%is is t%e per user /A, t%atIs assigned to uniKue

    user accounts. T%is license allo(s a user to access 'indo(s )*** and )**+ Terminal

    Servers. 2f t%e client device %as a valid TS :evice /A,3 t%en t%is TS !ser /A, is not

    needed3 and vice versa. 'indo(s Server )**+ TS E6ternal /onnector ,icenses. '%en assigned to a Terminal

    Server3 t%is E/, license allo(s unlimited non5emplo>ee connections. '%en t%is E/, is

    used3 TS :evice /A,s and TS !ser /A,s are not needed.

    'indo(s )*** TS /A,s. T%ese are per5device licenses for devices connecting to Terminal

    Servers running 'indo(s )***.

    'indo(s )*** TS 2nternet /onnector ,icenses. T%ese licenses are essentiall> t%e 'indo(s

    )*** version of t%e 'indo(s )**+ TS E/,. '%en assigned to a 'indo(s )*** Terminal

    Server3 t%is license allo(s )** simultaneous connections. T%ese connections must e made> non5emplo>ees3 across t%e 2nternet3 via anon>mous user accounts.

    'indo(s )*** Built5in ,icenses. T%ese uilt5in licenses are used for 'indo(s )*** and'indo(s 4 (orkstations t%at are connecting to 'indo(s )***5ased Terminal Servers.-ememer from t%e previous section t%at 'indo(s )**+ Terminal Servers do not support

    t%e use of uilt5in licenses. for 8free9 'indo(s )**+ TS /A,s3 >ou %ave to otain TS :evices /A,s from $icrosoftM

    t%e>Ire not automaticall> uilt in.=

    Temporar> ,icenses. 2f a licensing server ever runs out of activated licenses3 it (ill issuetemporar> licenses to an> client devices reKuesting per5device TS /A,s

    comple6. 2tIs proal> also fairl> ovious t%at t%e licensing service pla>s a central role. 2n 'indo(s

    )**+3 t%is service uilds on t%e licensing functionalit> t%at (as availale in 'indo(s )***.

    TS #icensing Service 5nstallation (onsiderations

    T%e TS licensing service is separate from t%e actual Terminal Server components t%at allo( users torun remote sessions.

    2n 'indo(s )**+ Terminal Server environments3 t%e TS licensing service must e installed on a

    'indo(s )**+ server. T%at server can e an> server in >our environment t%at %as a trust pat% to

    >our Terminal Servers. time after t%at via t%e /ontrol anel affecting performance. 2t adds ver> little /! or memor>

    over%ead3 and its %ard disk reKuirements are negligile. T%e average memor> usage is less t%an

    *$B (%en active3 and t%e license dataase (ill gro( in increments of onl> $B for ever> 3***license tokens issued. T%e license server does not reKuire 2nternet access.

  • 8/14/2019 Terminal Server Em Windows

    12/22

    TS #icensing Service Sco)e

    As part of t%e licensing service setup3 t%e installation routine asks if >ou (ant to set up t%e license

    server for >our 8Enterprise9 or 8:omain or 'orkgroup.9 T%e option c%osen %ere our Terminal Servers and lets >ou

    control (%ic% Terminal Servers can receive licenses from >our licensing server. You can configure

    >our license server so t%at it provides licenses for eit%erH

    An entire Active :irector> site. our licensing server (ill respond to a licensereKuest from an> Terminal Server in t%e same Active :irector> site. 2f Terminal Servers from

    multiple domains e6ist in t%at Active :irector> site3 t%e license server (ill provide licenses for all

    of t%em.

    T%is option reKuires t%at >our Terminal Servers e part of an Active :irector> domain. '%en t%elicensing service starts3 it registers itself (it% a domain controller and creates a 8TS5,icensing9

    oLect in t%e director>3 allo(ing Terminal Servers from an> domain to Kuer> a domain controller to

    locate t%e license server.

    -omain 6 Wor3grou) Sco)e

    /%oosing t%e 8Your domain or (orkgroup9 option causes t%e license server to e%ave differentl>3depending on (%et%er itIs part of an Active :irector> domain.

    2n A: environments3 t%is c%oice causes >our licensing servers to onl> respond to license reKuests

    from Terminal Servers in t%e same Active :irector> domain. 2f an Active :irector> domain crosses

    multiple Active :irector> sites3 t%e licensing server (ill fulfill reKuests from multiple sites. T%isoption is useful in situations (%ere t%ere are multiple usiness units partitioned into different

    domains on t%e same net(ork. A license server from one domain (onIt give licenses to clientsconnecting to Terminal Servers from a different domain.

    2n non5A: environments3 c%oosing t%is option means t%at >our license server (ill not attempt toregister itself (it% a domain controller3 and >our Terminal Servers (ill %ave to find >our license

    servers on t%eir o(n. t%e $icrosoftclearing%ouse via t%e Terminal Services ,icensing tool. T%is activation gives t%e license server t%e

    digital certificate it (ill use to accept and activate TS /A,s.

    T%e license server activation is fairl> straig%tfor(ard via t%e 2nternet or via a (e page3 fa63 or telep%one call. 2f >ou run t%e licensing tool on a

    computer ot%er t%an t%e license server3 t%e computer t%at >ou are using must %ave access to t%e

    2nternetMnot t%e license server.

    You must install a TS licensing server (it%in )* da>s of using Terminal Services on a 'indo(s)**+ server. s (it% 'indo(s )***.= 2f a 'indo(s )**+ Terminal

    Server canIt find a license server after itIs een used for )* da>s3 t%e Terminal Server (ill refuseconnections to clients (it%out valid TS /A,s.

    How Terminal Servers &ind #icensing Servers

    Since >ou can install t%e licensing service on an> 'indo(s )**+ server in >our environment3 t%ereal fun egins (%en >ou tr> to get >our Terminal Servers to talk to >our license server

    installing a license server on >our net(ork does not necessaril> mean t%at >our Terminal Servers

  • 8/14/2019 Terminal Server Em Windows

    13/22

    (ill e ale to find it.

    ,icense server 8discover>9 is t%e tec%nical term for t%e process > (%ic% Terminal Servers locate

    and connect to licensing servers. As soon as t%e Terminal Server role is added to a 'indo(s )**+server3 t%e server immediatel> egins t%e discover> process. ,icense server discover> can %appen in

    a numer of (a>s3 depending on (%ic% of t%e follo(ing environments t%e Terminal Server finds

    itself inH

    Do domain

  • 8/14/2019 Terminal Server Em Windows

    14/22

    DT G domain or(orkgroup

    )* min min

    :omain $ode )* min min

    Enterprise $ode * min * min

    -iscovery in Active -irectory nvironments'%en a Terminal Server is a memer of an Active :irector> domain3 t%e license server discover>

    process is entirel> different.

    . First3 t%e Terminal Server attempts to contact t%e license server ke>. 2f a license server is discovered at an> point t%roug% t%isprocess3 t%e remainder of t%e discover> process is aorted.

    ). 2f t%at attempt fails3 t%e server ne6t looks for an enterprise scope licensing server >performing an ,:A Kuer> for t%e follo(ing oLect in its Active :irector> siteH

    ,:AH/DRTS5Enterprise5,icense5Server3/DR3

    /DRsites3/DRconfiguration3:/R3:/Rcom

    +. 2f t%at attempt also fails3 t%e Terminal Server egins Kuer>ing ever> domain controller in t%esite3 looking for 8enterprise scope9 licensing servers.G. 2f t%e Terminal Server still %as not found a license server3 it (ill Kuer> ever> ot%er domain

    controller are configured as a domain scope license server.

    #ne t%ing t%at >ou mig%t %ave noticed aout t%is discover> process is t%at domain scopelicense servers must e installed on domain controllers in order for >our Terminal Servers to

    discover t%em. :omain scope license servers do not register t%emselves (it% ot%er domaincontrollers and Terminal Servers onl> Kuer> domain controllers to see if t%e> are license

    servers.

    T%ereIs not%ing (rong (it% installing a domain scope license server on a non5domain controller.

    Just e a(are t%an >ouIll need to manuall> configure t%e registries of >our Terminal Servers to find

    t%ose license servers. Enterprise scope license servers are not affected3 since t%e> registert%emselves (it% t%e domain controllers3 even (%en not installed on a domain controller.

    2f a Terminal Server does not find a license server via t%is discover> process3 t%e (%ole process is

    started over once ever> %our.

    2f license servers are found3 t%e Terminal Server keeps a list of t%em in its registr>. Enterprise li5censing servers are stored in t%e ;P,$QSoft(areQ$icrosoftQ$S,icensingQarameters

    QEnterpriseServer$ulti registr> location3 and domain licensing servers are stored in t%e

    ;P,$QSoft(areQ$icrosoftQ$S,icensingQarametersQ:omain,icenseServer$ulti registr> location.B> storing t%ese server names in t%e registr>3 a Terminal Server is ale to Kuickl> pick a ne( license

    server if its primar> c%oice is not availale. #nce a license server is found3 t%e Terminal Server (ill

    onl> start t%e discover> process over again if it canIt connect to an> of t%e servers in t%e registr>.

    Trou9leshooting #icense Server -iscoveryYou are likel> to run into situations in (%ic% one of >our Terminal Servers cannot find a license

    server and t%e reason is not apparent. Fortunatel>3 t%e 'indo(s Server )**+ -esource Pit in5cludesa Terminal Server ,icense Server vie(er tool3 ,SV2E'.E4E. ,SV2E' is a &!25ased tool t%at is

    run on a Terminal Server. 2t provides >ou (it% t%e names and t>pes of eac% license server t%at it candiscover.

    Figure 3. Microsoft license server discovery process

    The Terminal Server !!" #icensing Process,etIs take a look no( at %o( t%e entire licensing process (orks. T%e e6act process t%at takes place

  • 8/14/2019 Terminal Server Em Windows

    15/22

    is different depending on (%et%er t%e Terminal Server is configured to use device5ased or user5

    ased TS /A,s.

    Terminal Servers (on&igured &or -evice4Based TS (A#s'%en a Terminal Server is configured to use TS :evice /A,s TS

    /A,.

    C. T%e Terminal Server passes t%is certificate do(n to t%e client.@. T%e userIs credentials are validated. 2f t%e user successfull> aut%enticates3 t%e Terminal

    Server contacts t%e license server a second time. T%is time around3 t%e Terminal Serverinforms t%e license server t%at t%e TS /A, t%at (as sent to t%e client s%ould e marked as

    8valid.9 2f t%e user did not successfull> aut%enticate3 temporar> TS /A, to t%e

    Terminal Server..T%e Terminal Server contacts t%e license server. Since t%e licensing server marked t%e /A,

    as valid t%e first time t%e user aut%enticated3 t%e client deviceIs temporar> /A, is up5gradedto a full /A,. 2f3 for some reason3 all of t%e license servers %ave depleted t%eir in5ventories

    of TS /A,s3 t%e client device keeps its temporar> @*5da> TS /A, certificate. As long as t%e@*5da> certificate %as not e6pired3 t%e client device can still connect3 even (it% no availale

    licenses on an> license servers.

    An unlicensed client device (ill al(a>s e granted a temporar> @*5da> TS /A, at t%e time of its

    first connection. #nl> after successful aut%entication and a second logon is t%e temporar> TS /A,upgraded to a full TS /A,. T%is t(oOstage licensing process is used to ensure t%at TS /A,s are

    onl> assigned to aut%enticated users. reviousl> ou %ave a )*5da> 8grace period9 during (%ic% a Terminal Server (ill function even ifit cannot contact a license server. ;o(ever3 ) da>s after >ou install Terminal Services onto a

  • 8/14/2019 Terminal Server Em Windows

    16/22

    'indo(s )**+ server3 t%at server must e ale to contact a licensing server or no ne( users (ill e

    ale to connect. All of t%is action takes place a soon as t%e connection is madeMefore t%e usereven aut%enticates?

    TS (A# #icense (erti&icate Storage on (lient -evicesAs mentioned earlier3 (%en a client device receives a TS :evice /A, from a Terminal Server3 it

    receives it in t%e form of a digital certificate from a license server. For t%is reason >ou must acti5

    vate t%e license server (it% t%e $icrosoft clearing%ouse =. T%edigital certificate is an actual certificate copied to t%e client device at

    ;P,$QSoft(areQ$icrosoftQ$S,icensingQStoreQ,icense**6.

    An>one (%o %as een in t%e computer industr> for more t%an five minutes can proal> spot apotential fla( in t%is plan. /lient devices tend to reak. 'indo(s5ased terminals %ave t%eir -#$s

    reflas%ed. #perating s>stems are reinstalled on (orkstations. /s are reimaged. '%enever t%is%appens3 t%e TS /A, digital certificate stored on t%e client device is lost forever. T%e TS /A,

    doesnIt e6ist on t%e license server after itIs transferred to a client device. '%en t%at client connects

    ack to a Terminal Server3 it %as no digital certificate to present. T%e server t%inks t%at it %as nolicense3 and instructs t%e license server to issue a ne( TS /A, in t%e form of a ne( digital

    certificate. 2n effect3 t%at one client device ends up consuming t(o TS /A,sMt%e old one t%at (aslost and t%e ne( one t%at (as Lust issued. 2f t%e client device (ere reset again3 a t%ird TS /A,

    (ould e used.

    2n 'indo(s )**+

  • 8/14/2019 Terminal Server Em Windows

    17/22

    /A, certificate t%at (as selected to e6pire at t%e C@ da> ma6imum. '%en it

    passes do(n t%e certificate3 t%e license server decrements its total TS /A, license count > one3also noting t%at particular certificateIs e6piration date. Do(3 assume t%at a catastrop%ic event oc5

    curs at t%e client3 causing its local operating s>stem to e reinstalled and its local TS /A, certifi5

    cate to e lost. '%en t%at client aut%enticates to a Terminal Server3 t%e Terminal Server (ill reKuesta ne( TS /A, certificate from t%e license server and t%e license server > one. At t%is point t%ere %ave een t(o TS /A, licenses given out to t%at oneclient3 ut t%e first one (ill never e rene(ed ecause t%e certificate (as lost (%en t%e client (as

    reuilt. After C@ da>s selected duration of t%e first certificate=3 t%e first TS /A, is

    returned to t%e pool > t%e license server.

    T%e administrator in t%is situation proal> oug%t Lust enoug% TS /A,s to cover t%e e6act numerof client devices. ;e did not u> e6tras to cover t%e ) O C@ da> period during (%ic% one client

    device %ad t(o /A,s assigned. B> purc%asing t%e e6act amount of TS /A,s3 t%e li5cense server(ould not %ave an> more TS /A,s to give out (%en t%e client device asked for t%e ne( TS /A,

    certificate after t%e first (as lost. 2n t%is case3 t%e license server (ould grant a tem5porar> @*5da>

    TS /A, certificate to t%e client device ecause t%e client device appears to t%e server as a rand

    ne( mac%ine.Because t%e temporar> TS /A, certificate is al(a>s valid at least one da> longer t%en t%e full /A,

    certificate s versus a ma6imum of C@ da>s=3 t%e old3 lost full TS /A, (ill al(a>s e

    returned to t%e inventor> on t%e license server at least one da> efore t%e temporar> TS /A, cer5tificate (ould e6pire. For e6ample3 after da> CC3 t%e client deviceIs temporar> TS /A, certificate

    (ill e6pire in ) da>s3 ut t%e license server is tracking t%e e6piration of t%e full TS /A, t%at (asoriginall> granted for C@ da>s. T%at full TS /A, onl> %as da> left efore it e6pires. T%e follo(ing

    da>3 (%en t%e client deviceIs temporar> TS /A, certificate %as onl> da> remaining3 t%e license

    server (ill add t%e original TS /A, ack in its inventor> pool3 making it availale to grant to t%eclient as a permanent license for anot%er random period of ) O C@ da>s.

    True geeks (ill enLo> tracing t%e entire licensing flo( in 'indo(s )**+ Terminal Server envi5ronments in Figure G.

    Multi)le #icense Time&rames /)lainedT%roug%out t%is license distriution and acKuisition process3 (e %ave discussed t(o different li5

    cense timeframes. '%ile ot% are related to 'indo(s )**+ Terminal Services licensing3 t%e> are

    actuall> completel> different.

    A 'indo(s )**+ Terminal Server (ill (ork (it%out a license server for )* da>s.

    2f a license server runs out of TS /A,s temporar> ones.

    T%e first item relates to t%e presence of a license server. 2f a Terminal Server cannot locate a li5censeserver3 it (ill still allo( unlicensed client devices to log on. T%e Terminal Server itself does not

    grant @*5da> temporar> licenses if it cannot find a license server. 2nstead3 if a license server cannot

    e located3 t%e Terminal Server simpl> 8looks t%e ot%er (a>9 for )* da>s. After t%e grace periodends3 unlicensed client device connections are refused. T%is )*5da> countdo(n egins t%e first

    time a Terminal Services client device connects to t%e server.

    From a legal standpoint3 >ou must %ave a valid TS /A, for eac% client device t%at connects to aTerminal Server3 even during t%e first )* da>s. T%e )*5da> t%res%old is not a free evaluation

    period. -at%er3 it gives >ou a c%ance to set up >our Terminal Server environment and get t%e ugs(orked out efore >ou activate >our license server.

    T%e second item relates to t%e license server itself. 2f3 over t%e course of usiness3 a TS licensing

    server runs out of licenses3 it (ill egin to grant @*5da> temporar> license certificates to client

    devices. !nlike 'indo(s )***3 'indo(s )**+ license servers do not %ave to e activated to %andout @*5da> temporar> TS /A,s.

    Figure 4. The Terminal Server 2003 Device!ased TS "#$ $icensing %rocess

  • 8/14/2019 Terminal Server Em Windows

    18/22

    T%ese temporar> licenses can onl> e replaced > full TS /A, licensesMt%e> cannot e replaced

    > additional temporar> licenses. T%ere is no limit to t%e numer of temporar> licenses t%at a li5cense server can grant. Also3 t%e @*5da> timer for t%e e6piration of t%e TS /A,s is client specific3

    meaning t%at different temporar> licenses can e6pire on different da>sMeven if t%e> (ere all

    granted > t%e same license server.

    Terminal Servers con&igured &or User4Based (A#sEver>t%ing discussed in t%e previous section is applicale onl> (%en Terminal Servers are config5

    ured in 8per device9 licensing mode. '%en a user connects to a Terminal Server configured in 8peruser9 licensing mode3 a different process takes place.

    . '%en Terminal Services is installed on a 'indo(s )**+ server3 t%e server verifies t%at it can

    find process outlined previousl>= a license server.

    ). T%ere is no Step T(o.

    T%atIs rig%t. All t%is TS /A, digital certificate3 temp license3 transfer mumo5Lumo onl> applies

    (%en Terminal Servers are configured for 8per device9 licenses. 'it% per user licenses3 all >ou %aveto do is make sure t%at t%e Terminal Server can find a license server. verif>ing t%at it e6ists3 t%ereIs no com5munication et(een a 8per user9 configured Terminal Server and a license server.

    ;o( did t%is come to e7 '%en 'indo(s )**+ (as in eta testing3 $icrosoft (as planning to offera 8per processor9 licensing model. At t%e last minute prolem (as t%at it (as so late in t%e game t%at $icrosoftdidnIt %ave time to uild t%e 8per user9 tec%nical license compliance infrastructure ou

    can et (eIll see it in future versions of 'indo(s=.

    -esigning your #icensing Server nvironmentDo( t%at (eIve revie(ed t%e details of %o( licensing (orks3 letIs look at some of t%e issues affectt%e design of >our TS licensing servers.

    Selecting (%ic% Terminal Servers can access (%ic% license servers.

    ,icensing Terminal Servers in mi6ed 'indo(s )*** and 'indo(s )**+ environments.

    n&orcing which Terminal Servers are Authori:ed to Receive #icensesA ne( feature of 'indo(s )**+ allo(s >ou to specif> securit> permissions for >our license servers.T%at is3 >ou can specif> (%ic% Terminal Servers are aut%orized to pass out licenses from a specific

    license server.

    T%is feature is useful to organizations t%at manage licensing > usiness unit or specific users

    groups3 since it can prevent one department from 8stealing9 anot%er departmentIs licenses.You must first enale t%is securit> feature via a polic> applied to t%e license server is enaled on a license server t%atIs also a domain controller3 t%e group t%atIscreated is a domain local group ou reall> plan on managing >our licenses > department3 itIs proal> not t%e est idea to install

    t%e licensing service on a domain controller.

    2f >ou (ant to manage licenses > usiness unit3 itIs usuall> easiest to install t%e license server in8domain or (orkgroup mode9 onto a server t%atIs 8o(ned9 > t%at usiness unit. T%en3 activate t%e

    ,icense Server Securit> via &roup olic>. #nce t%is polic> is applied3 add t%e Business !nitIs

  • 8/14/2019 Terminal Server Em Windows

    19/22

    Terminal Servers into t%e local ,icense Server Securit> &roup3 ensuring t%at onl> aut%orized

    Terminal Servers can receive Terminal Service /A,s. T%is is also a good (a> to prevent ot%er de5partments or even rogue Terminal Servers from accessing >our license service and using up /A,s.

    #icensing in Mi/ed Windows !!! 6 !!" nvironments

    2f >ouIre migrating from 'indo(s )*** or if >ouIre running a )***)**+ mi6ed environment3 t%ere

    are a fe( licensing issues to consider (%en planning >our design.Preventing TS (A# #icense U)gradesSince itIs possile for a single 'indo(s )**+5ased license server to distriute ot% 'indo(s )***and 'indo(s )**+ TS /A,s3 >ou need to give some special t%oug%t to environments (%ere ot%

    are used.

    Your 'indo(s )*** Terminal Servers communicates (it% >our 'indo(s )**+ license server and

    reKuest licenses from it3 and >our 'indo(s )**+ license server mimics a 'indo(s )*** licenseserver.

    Because $icrosoft licenses are ack(ards5compatile3 t%e 'indo(s )**+ license server can

    tec%nicall> issue eit%er a 'indo(s )*** or )**+ TS /A, for clients (anting to connect to a

    'indo(s )*** Terminal Server.

    T%e license server (ill al(a>s tr> to provide t%e e6act matc% for t%e version of t%e license. But (%at%appens (%en a client device reKuires a TS /A, to connect to a 'indo(s )*** Terminal Server

    and t%e license server onl> %ad )**+ TS /A,s availale7 S%ould t%e license server 8(aste9 a )**+/A, on t%e 'indo(s )*** server3 or s%ould it provide a @*5da> temporar> )**+ license7 2f t%e

    client alread> %ad a temporar> /A,3 s%ould t%e server 8upgrade9 it to a )**+ permanent TS /A,3

    or s%ould it den> t%e userIs connection7

    T%e desired outcome of t%is situation depends upon >our usiness environment. You can specif>(%ic% e%avior >ou (ant >our licensing server to follo(. T%is functionalit> is controlled via t%e

    8revent ,icense !pgrade9 polic> | /omputer /onfiguration | Administrative

    Templates | 'indo(s /omponents | Terminal Services | ,icensing=.

    As t%e name implies3 enaling t%is polic> pro%iits a licensing server from ever using a 'indo(s)**+ TS /A, for a 'indo(s )*** environment. /%apter in out ook Terminal Services for

    'indo(s Server )**+H Advanced Tec%nical :esign &uide e6plains %o( policies are used andimplemented in Terminal Server environments.

    U)grading a Windows !!! #icensing Server2f >ou %ave an e6isting 'indo(s )*** license server3 itIs possile to upgrade it to 'indo(s )**+

    (%ile preserving t%e e6isting license dataase. :uring t%e upgrade from )*** to )**+3 t%e licenseservice t%at (as installed (ill e upgraded and t%e dataase content (ill e migrated into t%e ne(

    license dataase. After t%e upgrade to 'indo(s )**+3 >ouIll need to reactivate >our license server3Lust as if >ou %ad installed a ne( license server. T%is can e accomplis%ed > using t%e 8-eactivate

    Server9 option from t%e action menu in t%e Terminal Services ,icensing $anager.

    Managing your TS #icensing Servers

    #nce >our environment gro(s to ecome a Terminal Server po(er%ouse serving t%ousands of

    customers (it% %undreds of servers3 >ouIll need a fe( tools to ensure t%at ever>t%ing is goingaccording to plan (it% regards to licensing.

    $anaging 'indo(s )**+ Terminal Services license servers s%ould not take muc% of >our time.

    T%ere are onl> a fe( tasks >ouIll need to kno( aoutH

    Adding ne( licenses to t%e license pool.

    Administering t%e license server. -eporting on license usage.

    Troules%ooting client device license acKuisition.

  • 8/14/2019 Terminal Server Em Windows

    20/22

    Adding #icenses to a TS #icense ServerAll ne(l>Opurc%ased Terminal Server /lient Access ,icenses must e installed into a TS licenseserver dataase. Since 'indo(s Server )**+ also supports 'indo(s )*** licenses3 >ou can also

    install >our 'indo(s )*** TS /A,s onto a )**+ server. ou u> licenses

    t%roug% a volume license agreement suc% as Select or an Enterprise Agreement3 t%en >ouIll need to

    enter t%at agreement numer into t%e ,icensing 'izard (%en >ou add t%e licenses.

    After t%e licenses %ave een installed3 >ou must activate t%em. ,icenses are activated via t%e samet%ree met%ods >ou use to activate t%e license server to e distriuted to client devices. /lients t%at previousl> received t%e @*5da>

    temporar> licenses (ill e upgraded to full licenses t%e ne6t time t%e> connect.

    2n some situations3 adding or removing licenses to a license server (ill cause t%at server to notif>ot%er license servers.

    A domain scope license server (ill notif> ot%er license servers (it%in t%e same domain.

    An enterprise scope license server (ill notif> ot%er license servers in its Active :irector>

    site.

    An enterprise scope license server (ill notif> ot%er license servers in its domain.

    2n all of t%ese cases3 adding or removing licenses to a 'indo(s )*** or 'indo(s )**+ licenseserver (ill cause t%e server to notif> t%e appropriate 'indo(s )**+ license servers as mentioned. A

    'indo(s )**+ license server (ill not notif> a 'indo(s )*** license server.As outlined earlier in t%is paper3 t%is notification allo(s t%e license servers to redirect client

    reKuests to ot%er license servers s%ould t%e first server run out of licenses.Remotely Administering #icense ServersT%e TS licensing service is mainl> a 8set it and forget it9 kind of service. T%eoreticall>3 it onl>needs to e administered (%en ne( licenses are purc%ased or old licenses are removed.

    ;o(ever3 t%ere are times (%en it (ould e convenient to administer TS licensing servers remotel>.

    For tec%nical reasons3 t%e TS ,icensing Tool cannot e run via a remote Terminal Services session.;o(ever3 t%is tool can e e6ecuted locall> on an> 'indo(s )**+ computer and used to connect

    ack to one or more TS license servers. To do t%is3 cop> t%e licmgr.e6e and t%e lr(izdll.dll filesfrom t%e Qs>stem+)Q director> of t%e TS licensing server to t%e Qs>stem+)Q director> of t%e computer

    >ou (ould like to use. -un licmgr.e6e to use t%e tool.

    As (as mentioned previousl>3 running t%e tool in t%is manner can e %elpful (%en activating TSlicensing servers or TS /A, packs. :uring t%e activation3 t%e mac%ine running t%e TS ,icensing

    Tool needs access to t%e 2nternetMnot t%e actual license server itself. T%is met%od (orks (ell inscenarios in (%ic% t%e Terminal Servers are not connected to t%e 2nternet ut t%ere are certain

    administrator (orkstations connected to t%e 2nternet and t%e internal net(ork.

    $aintaining TS license servers is simple. #ne TS licensing console can connect to all of t%e licenseservers in >our environment3 facilitating centralized administration.

    Re)orting on #icense UsageT%e Terminal Server ,icense -eporting tool3 lsreport.e6e3 from t%e 'indo(s Server )**+ -esourcePit can e used to vie( and anal>ze t%e data contained (it%in t%e licensing server dataase. T%is

    tool outputs t%e information in t%e dataase into a ta5delimited format t%at allo(s >ou to create

    reports of (%o is using >our licenses. -un 8lsreport 79 from a command prompt for a list ofoptions.

    Uncovering (lient -evice TS (A# -etails

  • 8/14/2019 Terminal Server Em Windows

    21/22

    T%e Terminal Server /lient ,icense Test tool3 TS/TST.E4E3 is a command5line client5side tool t%at

    displa>s information aout a client deviceIs local TS /A,. Also included in t%e 'indo(s Server)**+ -esource Pit3 it provides t%e follo(ing information aout a licenseH

    2ssuer

    Scope

    2ssued to computer 2ssued to user

    ,icense 2:

    T>pe and Version

    Valid From

    E6piration date

    B> using t%e 8A9 s(itc%3 t%e follo(ing additional information is displa>edH

    Server certificate version

    ,icensed product version

    ;ard(are 2:

    /lient platform 2:

    /ompan> name

    T%is tool is used from t%e command line of a client device. 2tIs useful (%en >ou need to locate

    information aout t%e TS /A, certificate t%atIs stored locall> on t%at device.

    A))lication #icensing

    All t%is (ork on t%e Terminal Server licensing mig%t almost make >ou forget t%at >ou %ave toproperl> license >our applications as (ell. '%ile t%e purpose of t%is ook is to focus on Terminal

    Server3 t%ere are some common t%reads (ort% pointing out regarding application licensing.

    Because t%ere are so man> different (a>s t%at applications can e licensed3 itIs impossile go into

    specifics %ere. ;o(ever3 in almost all cases3 t%e application usage license is tied in some (a> to t%enumer of users or client devices. $ost application licenses are not linked to t%e numer of timest%e application is installed ecause t%e application vendors donIt (ant >ou to u> one cop> of t%e

    application for eac% Terminal Server t%at >ou %ave and t%en make t%at application availale to

    %undreds of users per server. $ost applications toda> %ave licensing agreements t%at fall into one oft(o categoriesH

    er Damed !ser. #ne license for eac% user t%at could e6ecute t%e application.

    er /oncurrent !ser. #ne license for eac% concurrent cop> of t%e application t%at is

    e6ecuted.

    n&orcing 7amed User A))lication #icensesApplications t%at are licensed 8per named user9 reKuire t%at >ou %ave a license for eac% user t%atcould access t%e application. 2f >ou %ave ** users (it% access to an application ut no more t%an

    * ever connect at t%e same time3 >ou still need to purc%ase ** application licenses. $ost$icrosoft applications are licensed t%is (a>3 in addition to man> e6pensive line5of5usiness

    applications.

    T%e ke> to properl> enforcing per named user application licenses is permitting or preventing users

    from eing ale to access t%e applications. An eas> (a> to do t%is is to create a domain group (it%all t%e user accounts of t%e users t%at (ill need to access t%e application. T%en3 add t%ese users to

    t%e -emote :esktop users group on t%e Terminal Server %osting t%e application so t%at onl>memers of t%at domain group can use it. T%is can also e done > setting DTFS permissions on t%e

    e6ecutale if users t%at donIt use t%is application connect to t%e same Terminal Server.

    Anot%er option is to create a Soft(are -estriction olic> to restrict t%at application to onl> a certain

    group of users. T%is polic> could e applied in t%e &roup olic> at t%e #! level for a large numer

  • 8/14/2019 Terminal Server Em Windows

    22/22

    of Terminal Servers.

    B> restricting access to t%e application itself3 >ou guarantee t%at onl> appropriate users (ill ever use

    t%e application. '%en it comes time to pa> for >our application licenses3 all >ou %ave to do is countt%e numer of users t%at are in >our application group and u> t%at numer of licenses.

    n&orcing (oncurrent User A))lication #icenses

    Applications (%ose licenses are ased on t%e numer of concurrent users onl> reKuire t%at anapplication license is purc%ased for eac% concurrent connection. 2f >ou %ave ** users t%at %aveaccess to an application ut no more t%an * ever connect at t%e same time3 >ou onl> need to

    purc%ase * licenses. Your compan>Is accountants (ill appreciate applications t%at are ased on

    concurrenc>. You (ill proal> not appreciate t%em ecause t%e> are %arder to enforce from atec%nical standpoint. 'it%in Terminal Server3 t%ere are t(o (a>s to enforce concurrent usersH

    ,imit t%e numer of connections on t%e Terminal Server %osting t%e application. T%is can e

    done in t%e Terminal Server /onfiguration utilit> > editing t%e -: connection properties.

    /reate a atc% file t%at (rites to a flag file efore an application is launc%ed. T%at atc% filecan e configured to c%eck t%e flag file to see %o( man> ot%er instances of t%e application

    are running. For environments in (%ic% applications are e6ecuted across more t%an oneserver3 t%e flag file can e stored on a net(ork drive. '%en users Kuit t%e application3 t%eflag file is updated to reflect t%e user c%ange. T%e onl> prolem (it% t%is of (riting t%e scripts in t%e first place= is t%at t%e flag file is not updated if usersdo not e6it t%e application properl>.

    Hardware -ongles in Terminal Server nvironments

    T%e onl> additional item (ort% mentioning aout application licensing relates to applications t%atreKuire a %ard(are ke>. 2f >ou %ave an application t%at reKuires a %ard(are ke>3 or 8dongle39 it

    proal> (onIt (ork on a Terminal Server. $icrosoft %as intentionall> disaled t%is functionalit>ecause t%e sole purpose of a %ard(are ke> is to prevent multiple users from using an application3

    and Terminal ServicesI sole purpose is to allo( multiple users to use an application.2f >our %ard(are ke> vendor did not use t%e standard $icrosoft A2s (%en (riting t%e application3

    t%e %ard(are ke> ma> (ork on a Terminal Server. 2f t%is is t%e case for >our application >ou mustensure t%at its use in a Terminal Server environment is acceptale from a licensing standpoint