
Some people, meaning only some users can’t print and some can. If some people
can’t print, the problem likely has to do with the permissions, application soft-
ware, or the network. Perform the following actions:

Check the network using a computer in the same subnet as the people
having the problem. See if you can ping the printer’s IP address. At the
command line, type ping PrinterIP, where PrinterIP is the IP address of the
printer. If you can’t ping the printer’s IP address from any system on the
subnet, a switch or routing between the user’s computer and the printer
might be bad or disconnected. This happens a lot if local switches/hubs are
under people’s desks.

Check the printer permissions and the permissions on the spool folder to
see if the groups of which the users are members have appropriate access. If
the permissions are set incorrectly, the spooling won’t work. See “Confi gur-
ing Print Spool, Logging, and Notifi cation Settings” on page 889 and the
Troubleshooting sidebar “Check permissions on the spool folder” on page
881.

Check the print processor. Windows 95, Windows 98, and Windows Me
clients can print only if the print processor uses the RAW data type. See
“Viewing the Print Processor and Default Data Type” on page 901.

Check the application being used for printing. The application might be
incorrectly confi gured or the default printer might not be what users think
it is.

Check the error message generated when printing. If the client gets an
error stating it must install a print driver when connecting to a printer,
this means the correct drivers are installed on the server but aren’t avail-

894. If the client gets an “Access Denied” error, this is a permissions issue.

Check the printer permissions and the permissions on the spool folder to
see if the user or groups of which the user is a member have appropriate
access. If the permissions are set incorrectly, the spooling won’t work. See
“Confi guring Print Spool, Logging, and Notifi cation Settings” on page 889
and the Troubleshooting sidebar “Check permissions on the spool folder”
on page 881.
Resolving Garbled or Incorrect Printing
If the printer prints garbled or incorrect pages, this can be a sign that the printer is
incorrectly confi gured. You should check the print driver and the print processor set-
tings. You might want to reinstall the print driver as discussed in “Viewing and Con-
fi guring Print Drivers” on page 887. You might want to change the print processor data
type to RAW or EMF to see if this clears up the problem. See “Viewing the Print Proces-
sor and Default Data Type” on page 901.
To resolve this problem, check the following:

Ensure that the complete document is transferred to the printer before printing
starts by selecting the Start Printing After Last Page Is Spooled option. See “Con-
fi guring Print Spooling” on page 900.

Try using the RAW data type or the EMF data type to see if this clears up the
problem. See “Viewing the Print Processor and Default Data Type” on page 901.

Try removing any separator page that is used, because this might be setting the
printer page description language incorrectly. See “Confi guring Separator Pages”
on page 902.

Try clearing the Enable Advanced Printing Features check box on the Advanced
tab. This disables metafi le spooling. Windows 95, Windows 98, and Windows Me

on the Microsoft Windows XP, Windows Vista, Windows Server 2003, and Windows
Server 2008 operating systems and is available for installation on other versions of
Windows as well. For details on the use and features of this client, see “Supporting
Remote Desktop Connection Clients” on page 613.
Using Terminal Services . . . . . . . . . . . . . . . . . . . . . . . . . 919
Designing the Terminal Services Infrastructure . . . . . . 927
Setting Up Terminal Services . . . . . . . . . . . . . . . . . . . . . 936
Using the Terminal Services Configuration Tool . . . . . . 957
Configuring RemoteApps . . . . . . . . . . . . . . . . . . . . . . . . 966
Using Terminal Services Manager . . . . . . . . . . . . . . . . . 975
Managing Terminal Services from the
Command Line. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 978
Other Useful Terminal Services Commands . . . . . . . . . 980
Configuring Terminal Services Per-User Settings . . . . . 981
CHAPTER 28
Deploying Terminal Services
919
Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.
By sending only the data required for I/O devices to and from the server, Terminal Ser-
vices signifi cantly reduces the amount of data transferred between a client and a server.
This reduces the amount of network bandwidth used, allowing Terminal Services to
operate in low-bandwidth environments. In addition, users are able to optimize per-
formance based on the speed of their connection. On a 28.8 Kbps modem, a user has
only the essential features to ensure the best overall performance possible. As a user
goes from a 28.8 Kbps modem connection to a LAN connection at 10 Mbps or higher,
Windows features are automatically added to enhance the user experience. Admin-
istrators can also confi gure Terminal Services to restrict the additional features. For
example, if hundreds of users are using a terminal server, you might need to restrict
enhancements to ensure the overall performance of the server. If you don’t do this and
the terminal server is overworked, it might fail.

Terminal Services installations, as follows:

One or more installations that’ll be used internally only with standard options,
such as the RDC client and RemoteApps. For ease of reference throughout this
Chapter 28
920 Chapter 28 Deploying Terminal Services
Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.
chapter, I will refer to servers with this type of installation as standard terminal
servers when I need to differentiate between the two types of installations.

One or more installations that’ll be used for Internet-based or intranet-based
access with TS Gateway and TS Web Access. For ease of reference throughout
this chapter, I will refer to servers with this type of installation as Web access or
gateway terminal servers when I need to differentiate between the two types of
installations.
In this way, you ensure that there are separate environments with separate require-
ments and separate procedures.
Terminal Services Servers
It’s very easy to set up a standard terminal server. What isn’t so easy is getting the
infrastructure right before you do so and maintaining the installation after it’s in place.
Before you install Terminal Services, it is essential to plan the environment and to
deploy Terminal Services before you install applications on the terminal server. After
you deploy Terminal Services, you will confi gure the environment, install applications,
and make those applications available to remote users.
The features for the Remote Desktop Connection client were discussed in “Supporting
Remote Desktop Connection Clients” on page 613. For Windows Server 2008, there are
many standard features and enhancements as well. The administration tools for Termi-
nal Services include the following:

Terminal Services Manager

Protocol (RDP) are what allow users to establish remote connections to a terminal
server. Server settings also enable you to easily set terminal server policy. A key
policy is the single session policy, which, when activated, limits a user to a single
session, whether the session is active or not.

TS RemoteApp Manager
TS RemoteApp Manager, shown in the following screen,
confi gures RemoteApps as well as deployment settings that apply to RemoteApps.
After you’ve confi gure a terminal server, you can copy the list of RemoteApp
Chapter 28
922 Chapter 28 Deploying Terminal Services
Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.
programs and deployment settings from that server to another using export and
import tasks.

TS Gateway Manager
TS Gateway Manager, shown in the following screen, is
used to confi gure authorization policies that control access to network resources
according to group membership. You use Terminal Services connection authori-
zation policies (TS CAPs) to specify who can connect to a TS Gateway server, and
Terminal Services resource authorization policies (TS RAPs) to specify the inter-
nal network resources to which users can connect through a TS Gateway server.

TS Web Access Administration
TS Web Access Administration, shown in the
following screen, provides access to the IIS server hosting the Web applications
required for Web access to Terminal Services, including a primary TS application
and two RPC proxy applications. Similar to what a user sees, you can view the list
of available RemoteApp programs or connect to remote desktops to which you
have access.

tion of the Terminal Services Easy Print driver and a Group Policy setting that enables
you to redirect only the default client printer. The Terminal Services Easy Print driver
allows users to reliably print from a RemoteApp program or from a terminal server
desktop session to the correct printer confi gured for use on their client computers. It
Chapter 28
924 Chapter 28 Deploying Terminal Services
Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.
also enables users to have a much more consistent printing experience between local
and remote sessions.
The Redirect Only The Default Client Printer setting in Group Policy allows you to
specify whether the default client printer is the only printer that is redirected in Termi-
nal Services sessions, which helps to limit the number of printers that the spooler must
enumerate, therefore improving terminal server scalability.
Note
To use the Terminal Services Easy Print driver, clients must be running Remote Desktop
Connection (RDC) client version 6.1 or later and have Microsoft .NET Framework 3.0
Service Pack 1 (SP1) installed. Note also that the terminal server fallback printer driver is
not included with Windows Server 2008. Although the Specify Terminal Server Fallback
Printer Driver Behavior setting still exists in Group Policy, it cannot be used with terminal
servers running Windows Server 2008.
Terminal Services Licensing
A Terminal Services license server is required to set up Terminal Services (see Figure
28-1). The license server, responsible for issuing licenses and tracking their usage,
maintains a pool of all available licenses. The assigned licenses are also tracked so that
they can be validated. Terminal Services requires that you get offi cial licenses from
Microsoft and activate them through the Microsoft Clearinghouse.
Terminal Services
license server
Microsoft
Clearinghouse

stop serving unlicensed clients.
Provided that the server has a license, it will give the license to the terminal server,
which in turn issues it to the client. Client access licenses provided by Terminal Ser-
vices are issued per device or per user, so the way licensing works depends on the
licensing confi guration—which can be mixed and matched as necessary. With per-
device licensing, the license is valid only for a particular computer and will be validated
in the future to the globally unique identifi er (GUID) of the machine on which the cli-
ent is running. With per-user licensing, the license is valid only for that user and will be
validated in the future to the GUID of the user’s account.
Note
Terminal Services client access licenses are issued per device or per user only. They are
not available in per-server mode because Windows sessions are not allowed in per-server
mode.
An issued license is valid for a period of 52 to 89 days; the interval is assigned ran-
domly. When the client later disconnects or logs off the terminal server, the license is
not returned to the pool. The expiration date serves to return unused licenses to the
license pool. Each time a client connects to a terminal server, the expiration date of its
license is checked. If the current date is within seven days of the expiration date, the
license server renews the license for another 52 to 89 days. If a client doesn’t log back
on to the terminal server before its license expires, the license is returned to the license
pool, which makes it available to other clients.
TS Licensing for Windows Server 2008 now includes the ability to track the issuance of
TS Per User CALs in TS Licensing Manager. If the terminal server is in Per User licens-
ing mode, the user connecting to it must have a TS Per User CAL. If the user does not
have the required TS Per User CAL, the terminal server will contact the license server
to get the CAL for the user. After the license server issues a TS Per User CAL to the user,
you can track the issuance of the CAL in TS Licensing Manager.
Note
For the fi rst 120 days after deployment, clients can be granted a temporary license if an
activated license server is not available. After this grace period, Terminal Services will

could access a Windows 2000 terminal server without needing a Terminal Services client
access license. With the release of Windows Server 2003 and Windows Server 2008, all
clients are required to have a Terminal Services client access license.
Designing the Terminal Services Infrastructure
Terminal Services can be deployed in single-server and multi-server environments. The
fi rst thing to plan is Terminal Services capacity. Capacity planning can help you deter-
mine the actual number of users that a specifi c Terminal Services confi guration can
support.
Capacity Planning for Terminal Services
It is important to note that Windows Server 2008 has signifi cant scalability advan-
tages over its predecessors. Primarily this is because the Windows Server 2008 kernel
provides better use of the 32-bit virtual address space. Because a terminal server must
allocate virtual resources for all users who are logged on, whether they are active or in
a disconnected state, the improved memory handling in Windows Server 2008 gives it
signifi cant advantages over Windows 2000 Server and some advantage over Windows
SIDE OUT
Terminal Services licensing changes
Anyone who wants to use Terminal Services must have a client access license. This
remains true whether a user connects to the terminal server using Remote Desktop
Protocol (RDP), RDP over HTTPS, or another vendor’s protocol. You can purchase client
access licenses using the licensing programs discussed in “Selecting a Software Licensing
Program” on page 63. This means that small companies can purchase licenses in packs of
5, 20, or more, while bigger companies can purchase licenses under programs such as the
Microsoft Open License.
When you purchase licenses in packs, you’ll receive a product activation code that can be
used one time to activate the number of licenses purchased. When you use Open License
or other programs, you purchase a set number of licenses. With Open License, you are
then issued an Open License Authorization and a set of license numbers that you can use
to activate licenses. Under Select and Enterprise licensing agreements, you provide your
Enrollment Agreement Number to activate licenses.

Data entry workers provide data input. They typically perform
data entry, transcription, order entry, or clerical work. Data entry workers typi-
cally have low impact on a server on a per-user basis. This means a server used
primarily by data entry workers could scale to a larger number of users than a
server used by other types of workers.

Knowledge worker
Knowledge workers perform day-to-day tasks using business
applications. Rather than providing strictly data input, knowledge workers create
documents, spreadsheets, presentations, and reports. Knowledge workers typi-
cally have moderate impact on a server on a per-user basis. This means a server
being used primarily by knowledge workers would not scale as well as a server
being used by data entry workers.

Productivity worker
Productivity workers are the high-performance workers in
the business environment. Their daily tasks include specialized applications for
graphic design, CAD, 3D animation, and applications that perform complex cal-
culations or require a high amount of processing. Productivity workers typically
have high impact on a server on a per-user basis. This means a server being used
primarily by productivity workers would scale to a lower number of users than a
server used by the other types of workers.
The impact of these types of users can best be illustrated graphically. Consider the sce-
nario in Figure 28-2. The chart shows the number of different types of users that can be
supported on three different server confi gurations.

Server A is a four-processor system with high-end processors and 4 GB RAM.

Server B is a two-processor system with high-end processors and 4 GB RAM.


tions being used, it doesn’t take into account the way users work. The way users work
can also have a signifi cant impact on Terminal Services. You should also consider these
factors:

Users’ typing speed

Users’ work habits

Experience settings on the client
Believe it or not, typing speed can affect performance. Many users who type very
quickly will make more updates and require more processing than a group of users
who type slowly. You don’t want to tell users to type more slowly, but you do want to
take their typing skills into account.
Designing the Terminal Services Infrastructure 929
Chapter 28
Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.
Users with poor work habits can have a signifi cant impact on performance. Consider
the case of a user who exits applications rather than switching among them: The user
starts Microsoft Outlook to check his mail, exits Outlook, starts Microsoft Word to type
a document, exits Word, starts Outlook again to check his e-mail, exits Outlook, and so
on—and does this all day long. Starting and exiting applications requires more process-
ing and resources than simply switching among applications as you use them.
The experience settings on the client can have a signifi cant impact on performance as
well. If users have optimized their experience settings for LAN connections of 10 Mbps
or higher, they will have desktop backgrounds, themes, menu and window animation,
and other extras that require a lot more processing on the server. The only experience
setting that actually improves performance is bitmap caching, which ensures that cach-
ing is used as much as possible to reduce the amount of data that has to be passed to
the client. Client display settings also affect server performance. The default display set-
ting is for High Color (16 bit). An additional option is available for True Color (24 bit).

930 Chapter 28 Deploying Terminal Services
Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.
Also consider network bandwidth and disk confi guration in capacity planning. A
network running at 100 megabits per second (Mbps) can handle hundreds of Termi-
nal Services users. A network running at 1,000 Mbps (Gigabit Ethernet) can handle
thousands of Terminal Services users. Consider existing traffi c on the network before
Terminal Services is deployed as a limiting factor. For capacity planning, you can test
the average amount of bandwidth a client uses when working with a terminal server by
monitoring the Bytes Total/Sec counter of the Network Interface performance object.
If a client uses 1,250 bytes per second on average, this is 10,000 bits per second. In
theory, a network running at 100 Mbps could handle 10,000 of these clients. Reduce
this by 50 percent to shift from the theoretical to what is probably possible, and then
subtract current bandwidth usage to come up with a working number.
Disk subsystem performance can also have a substantial impact on overall perfor-
mance, especially on a server that makes moderate to heavy use of the paging fi le.
Because the number and frequency of standard read/write operations for fi les affects
the design of the disk subsystem, these operations will also affect overall performance.
Ideally, the disk subsystem on a terminal server will be confi gured with hardware RAID
and multiple RAID controllers rather than software RAID. When multiple SCSI/RAID
controllers are used, disks should be confi gured to distribute the load. When you
install applications that will be used with Terminal Services, you can help spread the
load by installing and confi guring applications to use different disk sets on different
SCSI/RAID controllers.
Planning Organizational Structure for Terminal Services
When you are deploying Terminal Services, your planning should include deciding
where in the organizational structure your terminal servers should be located. As dis-
cussed in Chapter 19, “Using Remote Desktop for Administration,” servers running
in Terminal Server mode should be clearly separated from servers running in Remote
Desktop for Administration mode. This ensures that administrators and support per-
sonnel can use Remote Desktop for Administration throughout the organization and

ity or a self-signed certifi cate

Defi ne authorization policies that control connections and resource access on ter-
minal servers

Confi gure network policy and access services that control connections from
remote locations

Confi gure IIS to provide the necessary Web hosting services for Terminal
Services
Not only must you develop plans to confi gure these servers, but you must also develop
maintenance plans that include regular monitoring and periodic optimization of the
environment.
Deploying Single-Server Environments
Deploying Terminal Services in a single-server environment is much easier than
deploying Terminal Services in a multi-server environment. In a single-server deploy-
ment, a group of clients always connects to the same server, so that although your
organization might have three terminal servers, Group A always uses Server 1, Group B
always uses Server 2, and Group C always uses Server 3, as shown in Figure 28-3.
A single-server confi guration is the easiest to set up, as you need to perform only the
following steps:
1. Install the operating system on your designated server and confi gure the server
so it is optimized as appropriate for its intended use.
2. Install the required Terminal Services roles using the Add Roles Wizard to make
Terminal Services available to clients.
3. Install applications to be used by clients using the Install Application On
Terminal Server tool under Programs in Control Panel, which ensures that the
applications are set up using Install mode for Terminal Services rather than
Execute mode.
4. Install a Terminal Services license server and confi gure licenses for use.

Services
Sessions
Client 1
Client Group C
Client 2
Client 3
Client N
...
Figure 28-3 Terminal Services in a single-server environment.
Deploying Multi-Server Environments
Deploying Terminal Services in a multi-server environment requires a lot of planning
and an advanced setup. In a multi-server environment, you use load balancing to create
a farm of terminal servers whose incoming connections are distributed across mul-
tiple servers. Clients see the load-balanced terminal server farm as a single server. The
farm has a single virtual IP address, and client requests are directed to this virtual IP
address, allowing for seamless use of multiple servers.
Multi-server Terminal Services environments can be implemented using load balanc-
ing. A variety of techniques is possible, including using TS Session Broker Load Bal-
ancing with DNS round robin, TS Session Broker Load Balancing with routing tokens,
Designing the Terminal Services Infrastructure 933
Chapter 28
Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.
Microsoft Network Load Balancing, and hardware load balancers. A client that connects
to a load-balanced terminal server is said to be in a virtual session. If that session is dis-
connected, processing continues in a disconnected state and the client can be confi g-
ured to automatically try to reconnect the session. In a load-balanced farm, you always
want a client to connect to the server it was originally working with. This enables users
to continue where they left off without loss of data and without having to restart their
applications, open documents, and so on.
For multi-server Terminal Services environments, session information is managed

installs and starts the Terminal Services Session Broker service and creates a
local Session Directory Computers group.
Chapter 28
934 Chapter 28 Deploying Terminal Services
Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.
Client 1
...
TS Session
Broker server
Sessions
Session
Client 2 Client 3
Client N
Server
farm
address
Terminal
Server 1
Terminal
Server 2
Terminal
Server 3
Figure 28-4 A multi-server Terminal Services deployment.
5. Add each terminal server in the farm to the local Session Directory Computers
group on the TS Session Broker server.
6. Confi gure a terminal server to join a farm in TS Session Broker and to participate
in TS Session Broker Load Balancing (or your desired load balancing technique).
7. Install a Terminal Services license server and confi gure licenses for use.
8. Install terminal clients and confi gure them to use the Remote Desktop
Connection client or RDC over HTTP. Alternatively, confi gure applications to run