This is the title slide

1
(No Transcript)
2
Windows Server 2003 Terminal Services Training
Guide

• What is it?
• How does it work?
• Advantages
• What about Installation Activation?
• Configuring a Terminal Server
• Activating Terminal Server Licensing
• Deciding on types of client access (CAL)
  licensing
• Installing Terminal Server CALs
• Making Sure That Your Terminal Server Can Detect
  the License Server
• Licensing
• Changes to Windows Server 2003 Licensing
• External Connectors
• Transition Plan End of Operating System
  Equivalency
• Usage Scenarios
• Common (Office, Citrix)
• Advanced (Roaming usage, Multiple domains)
• Conclusion
• QA

3
What is it?

• Terminal Services provides a multi-session
  environment that allows client devices to access
  a virtual Windows Professional desktop session
  and Windows-based programs running on the server,
  even for devices without an operating system.

4
How Does it Work?

• Uses RDP (Remote Desktop Protocol), relies on
  TCP/IP, and falls under the application layer of
  the ISO 7-layer model.
• RDP - is the client software used to communicate
  between device and terminal service, also
  available in browser form for remote internet
  usage (Advanced Client).
• A 128 bit, RC4 (stream cipher) bi-directional
  encryption method is used to secure the
  connection.

5
Advantages

• Terminal Services allow
• Sharing of applications and desktops over the
  network.
• Administrators to take control of, and manage, a
  computer from their desk.
• Centralisation and management of applications
  (constantly keeping them up to date).
• Thin client, not concurrency solution.

6
What about Installation Activation?
7
Activation

• Windows Server 2003 Terminal Server requires that
  you install a license server before the terminal
  server can function. A license server is a
  computer on which Terminal Server Licensing is
  installed.
• For small deployments, it is acceptable to
  install both the Terminal Server and the Terminal
  Server Licensing service on the same physical
  computer. However, for larger deployments suggest
  that Terminal Server Licensing be installed on a
  separate server.

8
Configuring a Terminal Server

• Open the configure your server wizard from
  Administrative Tools and in the select a role
  section, choose Terminal Server and click Next
  twice to confirm your actions. The wizard will
  then start to install the required files.
• The installation will continue for a few minutes
  before the machine is restarted. After the
  machine has booted and you logon, you are
  presented with a confirmation screen that states
  the computer is now a terminal server.

9
Activating Terminal Server Licensing

• A license server is not considered operational
  until it is activated.
• To activate Terminal Server Licensing
• 1. On the computer running Terminal Server
  License Server, click Start, Programs,
  Administrative Tools, Terminal Server Licensing.
• 2. If the License Server has not been activated,
  in the console tree, right-click the Terminal
  Server License Server you want to activate.
• 3. Click Activate Server to start the Activation
  Wizard.
• 4. In the Activation method list, select
  Automatic connection (recommended), and then
  click Next.
• 5. Follow the instructions in the wizard.

10
Deciding What Type of Client Access License (CAL)
to Purchase

• Windows Server 2003 Terminal Server can operate
  in two licensing modes Per Device (default
  factory setting) and Per User.
• A Per Device CAL gives each client computer or
  device the right to access a terminal server that
  is running Windows Server 2003. If you install
  Per Device CALs on your license server, you need
  to ensure that the licensing mode on Terminal
  Server is set to Per Device.
• Using Per User licensing, one user can access a
  terminal server from an unlimited number of
  devices and only one CAL is needed instead of a
  CAL for each device. If you purchase and install
  Per User CALs on your license server, you must
  set the licensing mode on to Per User.
• Note Per User Licensing is not monitored by
  Terminal Server. This means that when you install
  Per User CALs, do not expect the number of
  available Per User CALs to be monitored.

11
Installing Terminal Server CALs

• Terminal Server Licensing is of no value unless
  it has Terminal Server CAL tokensan electronic
  representation of a Terminal Server CALwhich it
  can issue to various terminal servers. The
  terminal servers, in turn, can pass the tokens to
  the client devices connected to those terminal
  servers. After you purchase the appropriate type
  and quantity of Terminal Server CALs, you need to
  install them on the computer running Terminal
  Server Licensing.
• To install CALs
• 1. On the computer running Terminal Server
  Licensing, click Start, Programs, Administrative
  Tools, Terminal Server Licensing.
• 2. Select the license server in the right pane,
  and then on the Action menu, Install, Licenses.
• 3. Follow the steps in the wizard for a
  successful installation of the CALs.

12
Making Sure That Your Terminal Server Can Detect
the License Server

• It is essential that a Windows Server 2003
  Terminal Server is able to detect a computer
  running Terminal Server Licensing on Windows
  Server 2003 for correct operation within your
  computing network.
• A Microsoft Windows 2000 license server cannot
  provide licenses to a Windows Server 2003
  Terminal Server. However, a Windows Server 2003
  license server can provide licenses to both
  Windows Server 2003 and Windows 2000 Terminal
  Server and, therefore, can support a mixed
  environment consisting of both Windows 2000
  Terminal Server and Windows Server 2003 Terminal
  Server.
• Although Terminal Server attempts to detect a
  license server automatically, you may want to
  explicitly specify the license server your
  Terminal Server connects to.

13
Licensing
14
Changes to Windows Server 2003 Terminal Services
Licensing

• The licensing of Terminal Server in Windows
  Server 2003 has changed from previous versions
  (Windows 2000 Server and NT 4.0).
• Three primary changes were made to the licensing
  of Terminal Server in Windows Server 2003
• User based licensing has been added to the
  historical Per-Device model. Customers will be
  able to purchase a TS CAL for a specific Device
  or a single User that accesses TS.
• All devices or users will be required to be
  assigned a TS CAL, regardless of the OS running
  on the client access device. With previous
  versions of Terminal Server, devices that were
  running the most current version of the Windows
  Professional Client OS were granted access to
  Terminal Servers without TS CALs (Windows 2000
  and Windows XP Pro).
• The TS Internet Connector has been replaced by
  the TS External Connector. This license allows
  for an unlimited number of External Users to
  access a single server (copy of the OS) and use
  TS.

15
User CAL Satisfying Roaming Use

• The addition of the User CAL for Terminal Server
  solves many of the problems with the current
  Terminal Server licensing model. Many customers
  wanted to give their users the flexibility to use
  TS from multiple devices, including devices that
  the company did not own or control, such as home
  PCs, PDAs or kiosks in airports or hotels.
• With Device based licensing, the customer was
  required to purchase a TS CAL for each device
  that a user connected to a terminal server from.
  This became cost prohibitive or was impossible if
  the company did not know how to track devices
  that it did not own.
• The User CAL will alleviate these problems
  because now a company only has to purchase a User
  CAL for each user and it is then licensed for any
  number of devices that he/she might connect to a
  Terminal Server with.

16
Transition Plan End of Operating System
Equivalency

• All devices or users will be required to be
  assigned a TS CAL, regardless of the OS running
  on the client access device. With previous
  versions of Terminal Server, devices that were
  running the most current version of the Windows
  Professional Client OS were granted access to
  Terminal Servers without TS CALs (Windows 2000
  and Windows XP Pro.
• Microsoft realizes that the removal of operating
  system equivalency will affect customers and is
  committed to accommodating existing Microsoft
  customers who would like to take advantage of
  Windows Server 2003 features.
• Every Windows XP Professional desktop license
  that a customer owned on the date of the public
  launch of Windows Server 2003 (April 24 2003)
  will be eligible for a complimentary Windows
  Server 2003 TS CAL.

17
Transition Plan Scenarios

• One of following scenarios will apply
• Customers with either platform or operating
  system component Enterprise Agreements (EAs), or
  Upgrade Advantage (UA) or Software Assurance (SA)
  coverage for their Windows desktop computers,
  will be eligible for a Windows Server 2003 TS
  CALplus SA coverage on that TS CAL for each
  covered desktop owned at the time of the Windows
  2003 launch.
• Customers who own Windows XP Professional
  licenses, without upgrade rightsno SA/EA/UAwill
  be eligible for a Windows 2003 TS CAL for each
  licensed desktop owned at the time of the Windows
  Server 2003 launch, but will not get upgrade
  rights on the TS CAL.

18
TS External Connector License

• A company has 2 choices when licensing Windows
  Server 2003 for external use
• Obtain TS CALs for each external user or device
  that will connect to a Terminal Server.
• Obtain a TS External Connector for each copy of
  Windows Server 2003 that will be used by external
  users.
• Customers will make their purchasing decision
  based on economics and ease of management.
  Customers with a small number of external users
  may elect to purchase TS CALs for those users or
  devices. Customers with a large number of
  external Users or has users that are difficult to
  track may choose to purchase the External
  Connector.

19
Definition of External Usage

• Definition of External User
• Any person other than a person that performs work
  for the company as an employee, independent
  contractor, agent, or service provider i.e., a
  business partner or customer
• Examples
• Vendors
• Customers
• Alumni

• Users who DO NOT qualify as External Users
• Any person that performs work for the company as
  an employee, independent contractor, agent, or
  service provider
• Examples
• Employees
• Independent contractors
• Consultants
• Agents
• Faculty
• Staff
• Currently enrolled students

20
Usage Scenarios
21
Use of Third-Party Products (Multiplexing)

• E.g. Customer using Citrix to provide access to
  Terminal Services.
• Use of third party products such as Citrix do not
  change the Microsoft licensing requirements
  (PUR).
• These are still desktops accessing TS and will
  need a Windows Server 2003 CAL TS CAL.

22
Application Licensing (e.g. Office in a Terminal
Services Environment)

• When a user runs Office 2003 through Windows
  Terminal Services, all of the application
  execution takes place on the server only the
  keyboard, mouse, and display information are
  transmitted over the network to the client
  computer.
• If you elect to deploy Office 2003 as a client on
  a Windows Terminal Servicesenabled computer, you
  will need to acquire one license for each client
  computer that makes use of the Microsoft Office
  System.

23
Separate Domains

• Scenario 1 WIDGETS Inc employee - majority of
  time at Segway Pty Ltd
• Contracted to do work on behalf of Segway
• Uses WIDGETS owned laptop running Segway SOE
• Accesses WIDGETS resources using Terminal
  Services (from the same machine)
• (Assumes Windows XP Pro is the desktop OS)
• Licensing
• Software (except OS which comes with device) must
  be licensed by Segway (even though machine is
  owned by WIDGETS)
• Segway requires TS CAL, Server CAL and desktop
  licenses (e.g., Office)
• If this employee needs to access Widget software
  via Terminal Services they can do so under the
  following circumstances
• WIDGETS must provide a separate TS CAL and
  Windows Server CAL for this machine
• Must be using the same machine
• Machine must be licensed for the same software
  (or a higher version)
• Usage must be internal to WIDGETS (i.e., not for
  another WIDGETS customer)
• If this employee moves onto another project then
  the desktop software on this machine needs to be
  re-licensed by WIDGETS (or the new customer)

24
Separate Domains part 2

• Scenario 2 - WIDGET employee - small percentage
  of time working for Segway from WIDGET premises
• Uses WIDGET owned machine running WIDGET SOE to
  access WIDGET resources
• Logs on to Segway network using TS session
• Licensing
• Must be licensed by WIDGET
• Require TS CAL, Server CAL and desktop licenses
  (e.g., Office)
• If this employee needs to access Segway software
  via Terminal Services they can do so under the
  following circumstances
• Segway must provide a separate TS CAL and Windows
  Server CAL for this machine
• Must be using the same machine
• Machine must be licensed for the same software
  (or a higher version)

25
Separate Domains part 3

• Scenario 3 - WIDGET employee - small percentage
  of time working for Segway from Segaway premises
• Uses Segway owned machine to access Segways
  resources
• Accesses WIDGET resources through Terminal
  Services from Segway machine
• Licensing
• Machine must be licensed by Segway
• WIDGET needs to provide separate TS and Server
  CALs for the Segway machine that is accessing
  WIDGET resources

26
Roaming Usage

• Scenario 4 - WIDGET employee working from home
  using home PC (owned by employee)
• Licensing
• Employee can access WIDGET resources using
  Terminal Services under the following
  circumstances
• Employee has a USER CAL for multiple device use
• Or separate DEVICE CALs for home and work PC

27
Concluding Remarks

• Terminal Services is a thin client not a
  concurrency solution
• Every device needs a license for Windows TS (no
  more OS equivalency)
• Every application needs a license
• Intervening 3rd party software or hardware layers
  dont eliminate need for TS CAL
• For roaming users best to acquire USER CALs

28
More Information

• Windows Server 2003 Terminal Server Licensing
  whitepaper
• http//www.microsoft.com/windowsserver2003/techinf
  o/overview/termservlic.mspx

29
What is it?

• Terminal Services provides a multi-session
  environment that allows client devices to access
  a virtual Windows Professional desktop session
  and Windows-based programs running on the server,
  even for devices without an operating system
• Thin client, not concurrency solution

30
How does it work?

• Uses RDP (Remote Desktop Protocol), relies on
  TCP/IP, and falls under the application layer of
  the ISO 7-layer model.
• A 128 bit, RC4 bi-directional encryption method
  is used to secure the connection.

31
Advantages

• Terminal Services allow
• Sharing of applications and desktops over the
  network
• Administrators to take control of, and manage, a
  computer from their desk
• Centralisation and management of applications
  (constantly keeping them up to date)

32
What about Installation Activation?
33
What about activation?

• Windows Server 2003 Terminal Server requires that
  you install a license server before the terminal
  server can function. A license server is a
  computer on which Terminal Server Licensing is
  installed.
• For small deployments, it is acceptable to
  install both the Terminal Server and the Terminal
  Server Licensing service on the same physical
  computer. However, for larger deployments suggest
  that Terminal Server Licensing be installed on a
  separate server.

34
Configuring a Terminal Server

• Open the configure your server wizard from
  Administrative Tools and in the select a role
  section, choose Terminal Server and click Next
  twice to confirm your actions. The wizard will
  then start to install the required files.
• The installation will continue for a few minutes
  before the machine is restarted. After the
  machine has booted and you logon, you are
  presented with a confirmation screen that states
  the computer is now a terminal server.

35
Activating Terminal Server Licensing

• A license server is not considered operational
  until it is activated.
• To activate Terminal Server Licensing
• 1. On the computer running Terminal Server
  License Server, click Start, Programs,
  Administrative Tools, Terminal Server Licensing.
• 2. If the License Server has not been activated,
  in the console tree, right-click the Terminal
  Server License Server you want to activate.
• 3. Click Activate Server to start the Activation
  Wizard.
• 4. In the Activation method list, select
  Automatic connection (recommended), and then
  click Next.
• 5. Follow the instructions in the wizard.

36
Deciding What Type of Client Access License (CAL)
to Purchase

• When you have completed all the preceding tasks,
  Windows Server 2003 Terminal Server can operate
  in two licensing modes Per Device (default
  factory setting) and Per User. By default,
  Terminal Server Licensing is configured in Per
  Device mode.
• A Per Device CAL gives each client computer or
  device the right to access a terminal server that
  is running Windows Server 2003. If you install
  Per Device CALs on your license server, you need
  to ensure that the licensing mode on Terminal
  Server is set to Per Device.
• Using Per User licensing, one user can access a
  terminal server from an unlimited number of
  devices and only one CAL is needed instead of a
  CAL for each device. If you purchase and install
  Per User CALs on your license server, you must
  set the licensing mode on to Per User.
• Note Per User Licensing is not monitored by
  Terminal Server. This means that when you install
  Per User CALs, do not expect the number of
  available Per User CALs to be monitored.

37
Installing Terminal Server CALs

• Terminal Server Licensing is of no value unless
  it has Terminal Server CAL tokensan electronic
  representation of a Terminal Server CALwhich it
  can issue to various terminal servers. The
  terminal servers, in turn, can pass the tokens to
  the client devices connected to those terminal
  servers. After you purchase the appropriate type
  and quantity of Terminal Server CALs, you need to
  install them on the computer running Terminal
  Server Licensing.
• To install CALs
• 1. On the computer running Terminal Server
  Licensing, click Start, Programs, Administrative
  Tools, Terminal Server Licensing.
• 2. Select the license server in the right pane,
  and then on the Action menu, Install, Licenses.
• 3. Follow the steps in the wizard for a
  successful installation of the CALs.

38
Making Sure That Your Terminal Server Can Detect
the License Server

• It is essential that a Windows Server 2003
  Terminal Server is able to detect a computer
  running Terminal Server Licensing on Windows
  Server 2003 for correct operation within your
  computing network.
• A Microsoft Windows 2000 license server cannot
  provide licenses to a Windows Server 2003
  Terminal Server. However, a Windows Server 2003
  license server can provide licenses to both
  Windows Server 2003 and Windows 2000 Terminal
  Server and, therefore, can support a mixed
  environment consisting of both Windows 2000
  Terminal Server and Windows Server 2003 Terminal
  Server.
• Although Terminal Server attempts to detect a
  license server automatically, you may want to
  explicitly specify the license server your
  Terminal Server connects to.

39
Licensing
40
(No Transcript)