Network Printing

1
Network Printing for Windows v2

Connectivity Master Full Module
Ricoh Academy Europe

Created by: Ricoh Academy Europe Version:1.0.a Classification: Internal
See notes for version changes
Date of Version Description

change History
29-02-2012 1.0.a Initial version (no changes)
Created by: Ricoh Academy Europe Version: V1.0.a Classification: Internal 1

Objectives
 After finishing this module you should be able to: 2
 do an installation in a Windows-based environment.

 do basic troubleshooting in a Windows-based environment.
 advise customers on Windows-based network printing.
 Furthermore you should have a good understanding about
Windows-based networking and the used printing jargon/
terminology.
No additional notes

Requirements
 Networked printers/MFP’s 3
 Client PC’s running Windows XP/ Vista/ 7
 Supported Printer Drivers
 SmartDeviceMonitor for Client
 Windows 2003 server running Terminal Server Service
 Windows 2008 server running Terminal Server Service
No additional notes

Pre-requisites and Exam
 A+ 4
 Network+
 After this training, you can do the exam on WICE.
No additional notes

Module Overview
1. Introduction to Windows Printing 5
2. Printer Ports
3. Terminal Services
No additional notes

6
1. Introduction to Windows Printing

No additional notes

Chapter Overview
1. Windows Printing Introduction 7
2. Printing Architecture Windows XP

3. Printing Architecture Windows 7
4. Network Printing Architecture
No additional notes

8
1.1 Windows Printing Introduction

No additional notes

Windows Printing Introduction
 Printing and printer sharing are amongst the most 9
frequently used (network) services.

 Issues with printing, be it print server issues, driver issues,
or otherwise, are very common.
 This training module will provide you the necessary
information and tools to help you installing and
troubleshooting (networked) printers in a Windows
environment.
No additional notes

Local Printer and Network Printer
 The difference between a local printer and a network 10
printer is a bit obscure.

 Networked printers can still be regarded as local printers,
based on how you connect to these printers.
 The next few slides will show the difference.
Local printer and network

printer in Windows XP
No additional notes

Local Printing
 Local Printing is printing to a printer, connected to a local 11
port.
 This can be printers connected via USB or parallel cable, but
also networked printers using a local port.
 There are no intermediate servers (for instance print
servers), so there is direct communication between the PC
and the printer.
 Local printers can be added by starting the Add Printer
Wizard or using a setup program.
 Plug and Play compatible printers can start the Add Printer
Wizard automatically when they are connected.
 Some Plug and Play printers do require you to install the
drivers before connecting the printer, so always check the
printer’s installation guide.
No additional notes

Network Printing
 Network Printing is printing to a printer: 12
 that is attached to another computer/server, or

 that publishes itself as a network printer on the network, or
 using the Internet Printing Protocol (IPP).
No additional notes

Windows Printing Architecture
 Actually, there is no one common Windows Printing 13
Architecture.
 When looking at the most recent Windows versions,
basically there are two architectures:
 Printing architecture before Windows Vista.
 This includes Windows 2000, Windows XP, Windows 2003
Server.
 In this module, we will call this the Printing Architecture of
Windows XP.
 Printing architecture of Vista and later.
 This includes Windows Vista, Windows 7 and Windows 2008
Server.
 In this module, we will call this the Printing Architecture of
Windows 7.
 The next chapters will show the differences.
No additional notes

14
1.2 Printing Architecture Windows XP

No additional notes

GDI-Based Printing
 Windows XP uses a GDI-based printing architecture. 15
 Applications designed for Windows XP make GDI calls to

print their documents.
 Print data is stored in the spooler until the printer is ready
to print.
 The Print Monitor provides the common language for the
client and the printer to understand each other, so you can
configure the printer and monitor the printer status.
Application
GDI Printer Driver
Spooler
Print Monitor
GDI:
 The Graphics Device Interface (GDI) is a Microsoft Windows application
programming interface and core operating system component
responsible for representing graphical objects and transmitting them to
output devices such as monitors and printers.
 GDI includes user-mode and kernel-mode components.
 The user-mode component, Microsoft Win32 GDI, is used by Win32
applications that require graphics support.
 The kernel-mode component, the graphics engine, exports services
and functions that graphics device drivers can use.
Kernel Mode:
 Kernel-mode drivers are called version 2 drivers and run in a privileged
operating mode.
 An error in a kernel-mode driver can cause the entire server to stop
responding.
User Mode:
 User-mode drivers are called version 3 drivers and run at the same
system privilege level as an application.
 User-mode drivers are hosted in the spooler process.
 An error in a user-mode driver will only stop the spooler service which is
easily restarted.
There are two different types of print monitors:
 The Language Monitors provide a full-duplex communications path
between the print spooler and bi-directional printers.
 The Port Monitors are responsible for providing a communications path
between the user-mode print spooler and the kernel-mode port drivers
that access I/O port hardware.

Spooler
 The print spooler is an important part of the print process, 16
which consists of a set of Microsoft and vendor

components that perform the following tasks:
 Should a print job be handled locally or across a network?
 Accepting a data stream created by GDI, in conjunction with
a printer driver, for output on a particular printer type.
 Spooling the data to a file.
 Selecting the first available physical printer in a logical
printer queue.
 Converting a data stream from a spooled format such as
EMF to a format that can be sent to the printer hardware
(such as PCL).
 Sending a data stream to printer hardware.
 Maintaining the registry database for spooler components
and printer forms.
No additional notes

Spooler Location
 The default location for the spooler is c:\Windows\ 17
System32\spool\PRINTERS.
 The print spooler is controlled by the Print Spooler service.
Note
 This is not only true for Windows XP, but for other versions as well
(Windows 2003, Vista, 7, etc).

Spooler Crash
 Buggy drivers can result in a crashing Print Spooler 18
service, which in turn will result in the inability to print.

 In the Printer windows, all printers seem to be removed
from the system.
No additional notes

Start Spooler
 To restart the spooler: either locate the Print Spooler 19
services in “services” and select start or enter “net start

spooler” in the cmd.
No additional notes

Print Processor
 Print processors convert the spooled data from a print job 20
into a format that is understood by a print monitor.

 The print processor reads the file, performs the
conversion on the data stream and writes the converted
data to the spooler.
 Print processors are associated with printer drivers during
driver installation.
 The default Print Processor provided with the operating
system is winprint.dll, which is included in Localspl.dll.
 The Print Processors of Windows 2000, XP and Windows
2003 Server can handle the following input data types:
No additional notes

Input Data Types
 EMF: 21
 Enhanced Metafile (EMF) data consists of instructions to call

GDI functions.
 The print processor must call the GDI functions to render
printable images.
 EMF data is device independent and can be sent to a server
more quickly than RAW data.
 RAW:
 RAW data can be sent to a print monitor without further
processing.
 Postscript commands can be considered RAW data if the target
printer supports Postscript.
 TEXT:
 TEXT data consists solely of ANSI text. The print processor
calls GDI to draw characters using the print device's default
font, and sends the resulting RAW-formatted output to the
spooler.
No additional notes

Printer Drivers
 Printer drivers are basically pieces of software that converts the 22
data to be printed to the form specific to a printer.
 The purpose of printer drivers is to allow applications to do

printing without being aware of the technical details of each
printer model.
 On Windows 2000, 2003 Server and XP systems, printer drivers

make use of GDI (Unidrv or PScript-based).
 As of Windows Vista, printer drivers can also use XPS (XPSDrv),
but that will be explained later in this training.
 Programs then use the same standard API’s to draw text and
pictures both on screen and on paper.
 More in-depth information about drivers can be found in the

Basic Printer Driver module on WICE.
 Printers which use GDI natively are commonly referred to as Winprinters

and are considered incompatible with other operating systems.
 Win32 APIs also allow applications to send data directly to the spooler,
bypassing the printer driver; however, few applications actually use this
option.

23
1.3 Printing Architecture Windows 7

No additional notes

New Architecture
 The print architecture of Windows Vista, 7 and 2008 is 24
considerably different compared with older Windows version.
 It takes advantage of the new open XML paper Specification

(XPS).
 This provides better support for current and future printing

devices and operations.
 The print architecture is designed to address:

 The increasing demand for color laser printing.
 The increasing demand for color fidelity.
 The increasing use of advanced graphics and color.
 Although introduced by Windows Vista, the new features are

available on Windows 7 and 2008 as well.
No additional notes

XPS (1/2)
 The open XML Paper Specification is the foundation for 25
document and printing improvements the newer MS

Operating Systems.
 It consists of Extensible Markup Language (XML) markup

that defines the composition of a document and the visual
appearance of each page along with rendering rules for
displaying or printing the document.
 The XPS Document format serves as a document format,

a spool file format, and a page description language (PDL)
for printers.
No additional notes

XPS (2/2)
 Consistent use of XPS throughout the system greatly 26
improves print predictability and reliability.
 XPS Document processing eliminates the need for any

conversions between application and printer, which makes
it possible to deliver a WYSIWYG ("what-you-see-is-what-
you-get") experience.
 In essence you can compare this format with PDF.
No additional notes

Print Path
 The new print subsystem implements an XPS print path 27
that supports the new XPS spool file and the Windows
Presentation Foundation graphics engine.
 The GDI print path in Windows XP, which uses GDI-based

Version 3 print drivers (user-mode drivers), is also still
available.
 This allows Microsoft Win32® GDI-based applications to

print to XPS Document devices and allows Windows
Presentation Foundation applications to print to legacy
printers.
No additional notes

Print Subsystem
28
No additional notes

Color Printing
 Windows Vista, 7 and 2008 make full use of the Windows 29
Color System.
 The WCS introduces significant innovations to color

management to match color across different software
applications, imaging devices and imaging media.
 XPS natively supports:

 higher precision, higher dynamic range, and larger gamut
color spaces.
 the use of CMYK and supporting n-ink systems (more than
four colorants).
 named colors.
No additional notes

High-Fidelity Print Output
 The XPS print path reduces or eliminates image data 30
conversions and color space conversion.
 This enables high-fidelity output.
 It provides more faithful rendering of graphics attributes

such as transparency and gradients.
No additional notes

Improved End-user Experience
 XML Print Capabilities is a method of publishing 31
configurable device capabilities such as finishing options

and page layout options.
 Available options will automatically be set in the printer

driver.
 Truth be told: Even on older Windows versions features like
this were made possible by implementing an update function
in the driver.
No additional notes

Improved Spooling and Rendering
 Spooling efficiency is improved by spooling XPS 32
documents in a native spool format when printing to XPS

enabled drivers and printers.
 It eliminates the requirement to generate an intermediate

spool file, such as an EMF data file, before the document
is spooled.
 Through smaller spool file sizes, network traffic is reduced

and printing performance is improved.
No additional notes

Driver Store
 Windows Vista also introduced the driver store. 33
 This is a trusted cache of in-box and third-party drivers

that are stored on the local hard disk.
 When a third-party driver is installed on Vista, 7 or 2008,

setup automatically copies the driver package into the
driver store.
 Then the driver is installed from the driver package in the

driver store.
 You can add driver packages into the driver store for
installation at a later time (staging).
No additional notes

Supported Drivers
 Vista introduced a new printer driver type: XPSDRv. 34
 This driver is also a user-mode driver.
 Windows Vista, 7 and 2008 also support version 3 printer

drivers.
 Version 2 drivers (kernel-mode drivers) are not supported.
No additional notes

Client-side Rendering
 Client-side Rendering causes print driver rendering to 35
occur on the client machine by default when a

Windows Vista/7/2008 client is connected to a
Windows Vista/7/2008 print server.
 The goal of this feature is to increase server performance

and scalability while reducing printing issues that are
caused by a driver mismatch between the client and the
server.
 But before discussing print servers, lets first have a look at

how to connect networked printers.
No additional notes

36
1.4 Network Printing Architecture

No additional notes

Network Printing
 Network Printing can roughly be divided in 2 categories: 37
 Peer-to-peer:
 In a peer-to-peer network there are no dedicated servers or
hierarchy among the computers.
 Server-based:
 A server-based network consists of a group of user-oriented
PCs (Clients) that request and receive network services from
specialized computers (Servers).
No additional notes

Peer-to-peer Printing
 The Windows platform allows several peer-to-peer printing 38
possibilities
 Win9x/Me requires additional utilities.
 WinNT and later have built-in peer-to-peer printing protocols.
 No print server (computer) is required with peer-to-peer
printing.
 Peer-to-peer networks are designed for connecting a
small number of computers.
Workstations
Printe
r
Note:
 All of the computers on the network handle security and administration
for themselves, so users must make the decisions about who gets
access to what.

Server-based Printing
 In server-based printing, all clients connect to a print 39
server, which in turn is connected to one or more printers.

 This allows administrators to control access to printers.
 The next slides will show you an example of what the
printing process can look like if you print through a print
server.
 The example shows a Windows print server.
 If you use another type of server (Unix, Linux, Mac OSX,
Novell) then the process would be quite different.
Workstations
Printe
Print Server r
No additional notes

Remote Printing Process (1/3)
 The client computer delivers 40
the print job to the print

server.
 The client-side spooler
makes a remote procedure
call (RPC) to the server side
of the spooler, which uses
the print router to poll the
remote print provider on the
client side.
 The remote print provider
initiates another RPC to the
server spooler, which
receives the print job over
the network.
No additional notes

 The router on the server 41
passes the print job to the

local print provider on the
server (component of the
spooler), which spools the
print job (writes it to the
disk).
 The local print provider then
polls the print processor.
 The print processor
recognizes the job's data
type and receives the print
job.
 The print processor then
converts the print job
according to its data type.
No additional notes

 Control of the print job is 42
passed to the separator page

processor, which adds a
separator page, if specified.
 The job is de-spooled to the
print monitors.
 For bi-directional printers, a
language monitor handles the
two-way communication
between the sender and the
printer, and then it passes the
print job to a port monitor.
 If the printer is not bi-
directional, the print job goes
directly to the port monitor,
which sends it to the target
printer.
No additional notes

43
2. Printer Ports

No additional notes

Chapter Overview
1. LPR 44
2. Standard TCP/IP
3. IPP
4. Smart Device Monitor for Client
5. Point and Print
6. WSD
No additional notes

45
2.1 LPR

No additional notes

LPR
 Although called LPR, the correct term would be LPD/LPR 46
printing (Line Printer Daemon/ Line Printer Remote).

 It uses TCP/IP to establish connections between printers
and workstations on a network.
 It was originally developed for BSD Unix but soon adopted
by many other Operating Systems.
 The LPD software typically is stored in the printer or print
server and the LPR software must be installed in the client
device.
 The LPR client sends the print request to the IP address
of the LPD printer/server, which in turn queues the file and
prints it when the printer becomes available.
No additional notes

Advantages/ Disadvantages
 Advantages: 47
 Simple to implement.
 Platform independent.
 No special utilities needed for Windows NT and later.
 You may have to add the LPR/ LPD daemon first.
 Disadvantages:
 For Windows 9x/Me special utilities are needed to create an
LPR port.
 The LPR port is unidirectional.
 It lacks print job acknowledgment, so once the print data is
transmitted to the LPD, the host will consider the job done.
 No automatic update of installed accessories or paper tray
configuration.
No additional notes

LPR in Windows
 To configure an LPR port in Windows XP you have to 48
install the Print Services for Unix first.

 Select Add/Remove Programs  Add/Remove Windows
Components  Other Network File and Print Services.
 In Windows 7:
 Select Programs and Features  Turn Windows features on
or off  Print and Document Services  LPR Port Monitor
for LPR printing) and LPD Print Service (for using the PC as
an LPR print server).
Windows XP Windows 7
No additional notes

LPR Port
49
Windows 7
Windows XP
No additional notes

Queue Name
 The LPR port requires an IP address or hostname and a 50
so-called queue name.

 The queue name depends on the network card of the print
device.
 A few examples:
 Ricoh NIB’s: lp
 Osicom DPI NIB: PORT1
 Emulex: PASSTHRU
 Many Ricoh devices also allow users to create so-called

virtual printers.
 These are virtual queues with specific job parameters
assigned (duplex, staple, 10 copies etc.).
 The LPR queue name is then the virtual printer name.
No additional notes

Source and Destination Ports
 The Windows LPR port will default to the LPR RFC 51
Source and Destination ports (TCP:721-731, TCP:515)
 This means you can have only 11 simultaneous

connections from the print server to printers
 You might notice this as pausing between a large amount of
print jobs
 You can find a solution for this problem on the Microsoft

website:
 http://support.microsoft.com/kb/q179156/
 Note that enabling the LPD daemon on Windows Vista, 7

and 2008 will create an exception in the Windows Firewall.
No additional notes

52
Practical Work
Exercise 1

No additional notes

53
2.2 Standard TCP/IP

No additional notes

Standard TCP/IP
 The Standard TCP/IP port monitor is the successor of the 54
LPR port on Windows.

 It’s faster, more scalable and bi-directional.
 It uses the TCP/IP protocol for communication, but it also
uses the SNMP (Simple Network Management Protocol)
protocol to configure and monitor the printer status.
 It sends data to the printer using either the RAW or LPR
printing protocols.
No additional notes

RAW (1/2)
 The RAW protocol is the default for most printing devices. 55
 When sending a RAW-formatted job, the sending

computer will open a TCP stream to the printer’s network
interface (usually port 9100, but a manufacturer can
designate different ports).
 When the port is created, Windows uses SNMP to query

the device.
 When the device returns a value, Windows will use a system
file, tcpmon.ini, to choose the correct settings.
No additional notes

RAW (2/2)
1. IP Address of device 56
1 2. Protocol type
2 3. Port number
3
4. Community name for SNMP
(Read)
No additional notes

LPR (1/3)
 The standard TCP/IP port can be configured to comply 57
more closely to the LPR standard (RFC 1179).

 You can use the [Configure Port] button to enable LPR
printing.
No additional notes

LPR (2/3)
 You have to specify the correct queue name. 58
 Enabling byte counting is helpful if an LPD requires an

accurate byte count to be sent, which is compliant with the
RFC.
No additional notes

LPR (3/3)
 The standard TCP/IP port monitor deviates from the LPR 59
standard in two ways:
 The monitor does not conform to the RFC 1179 requirement

that the source TCP port lies between port 721 and 731.
 Instead, it can use ports from the general, unreserved pool of
ports (ports 1024 and above).
 The standard monitor spools the print job only once.

 LPR sends the job twice, once to determine the job size, and
once to send the actual job.
Note
 The LPR standard states that print jobs must include information about
the size of a print job.
 Sending a job with job size information requires that the port monitor
spools the job twice, once to determine the size, and once to send the job
to the spooler.
 Therefore, to improve performance the standard port monitor will send
the job without job size information.
 It will claim the job is a default size, regardless of the job’s actual
size.

LPR vs. Standard TCP/IP
 The table below compares the Standard TCP/IP port 60
monitor to the LPR port monitor.
LPR (RFC 1179 Compliant) Standard TCP/IP Port Monitor

Limited to 721–731 source ports Source ports from ephemeral ports (9100 default)
Four-minute timeout per port No source port timeout
Unidirectional—single error status reporting Uses SNMP for rich status and error reporting
Control file requires double spooling for accurate Single-file spooling enabled by default.
byte count (configurable through Port Properties)
Prints to destination port 515 Prints to destination port 515 in LPR mode
No additional notes

61
Practical Work
Exercise 2

No additional notes

62
2.3 IPP

No additional notes

What is IPP
 The Internet Printing Protocol (IPP) is a standard for 63
printing documents over the web.
 IPP defines basic handshaking and communication

methods, but does not enforce the format of the print data
stream.
 IPP was created by a consortium of printer manufacturers

and related industries.
 Basically, there are two main components to IPP:

 Web-based printer management.
 Internet printing.
No additional notes

Web-based Printer Management (1/2)
 Web-based printer management allows users to purge 64
print jobs, pause printers and so on using a web browser.

 The url is: http://servername or IP-address/printers.
No additional notes

Web-based Printer Management (2/2)
 Prerequisites: 65
 IIS must be installed and running on the print server.
 Users must have enough privileges in order to pause

printers, delete jobs and so on.
 When a printer is created it must be shared to make it

available for management trough a browser.
No additional notes

Internet Printing (1/3)
 Internet printing allows you to make printers accessible 66
over the internet or intranet by using the printer’s URL as

the name of the printer.
 Example: http://gaia/printer.
IPP
LAN
Firewall
Internet
Firewall
No additional notes

 HTTP printer connections can be established in two ways: 67
1. You can select “Connect” in the Web-based management

window.
 The client will then make a RPC connection to the print server
(like Point and Print).
 Note that the Internet Explorer’s security settings must be set to
medium-low or lower. Otherwise a true IPP port will be created.
Internet settings to medium-high:

IPP port is created
No additional notes

2. You can create a true IPP port which requires the 68
installation of a local printer queue.

 A local printer queue will be installed on the client PC.
 It is not as innovative as an RPC connection, but it may be the
preferred port for some situations, for instance when you want
to create an https port (secured by SSL).
No additional notes

Security
 As stated in the previous slide, a true IPP port can be 69
secured by using SSL (Secure Sockets Layer).
 SSL ensures that print data is encrypted and provides a

counter measure for wiretap and falsification.
 Note
 More information on SSL can be found in the GW Security
Features modules on WICE.
No additional notes

70
Practical Work
Exercise 3

No additional notes

71
2.4 Smart Device Monitor for Client

No additional notes

SDM Port
 The SmartDeviceMonitor for Client (SDM for C) is a Ricoh 72
printing solution.
 It provides additional useful features like:

 Bi-directional support.
 Support for TCP/IP, NetBEUI and IPP.
 Support for NetBEUI was discontinued in Windows XP and
later.
 Support for monitoring and controlling network devices.
 This chapter will describe some printer specific features of

SDM.
 For more information about SDM, please check the
SmartDeviceMonitor 2004 module on the WICE website.
No additional notes

NETBEUI
 Microsoft has discontinued the support for the NetBEUI 73
protocol in Windows XP and later.

 This means that this protocol will be grayed-out in SDM for
Client.
No additional notes

IPP with SDM
 SDM allows you to use IPP even when the operating 74
system does not support IPP (Windows 9x/Me, NT4.0).
 SDM allows IPP user authentication.
 SDM is faster then using a Windows IPP port.
 In the print queue window, you can get more information

with SDM then when using a Windows IPP port.
No additional notes

IPP Port
 Start the Add Printer Wizard and select local port. 75
 In the dropdown box, select SmartDeviceMonitor.

 Enter the Printer URL (see screenshot).
 Additionally, you can enter the IPP Port Name (Friendly
name)
No additional notes

IPP Authentication in SDM
 Most Ricoh devices support 76
IPP Authentication.
 Administrators can enter up
to 10 usernames and
passwords into the device
using WebImageMonitor.
 Users can only print when
they supply one of those
usernames/ passwords.
No additional notes

Authentication Method
 IPP Authentication has 3 settings: 77
 Disable.
 Authentication is disabled.
 Everybody is allowed to print.
 Basic.
 Authentication is enabled.
 Users have to supply a username and password.
 These credentials are send over the network in plain text.
 Digest.
 Authentication is enabled.
 Users have to supply a username and password.
 The hash of the password is send over the network.
No additional notes

IPP Authentication
 The Windows IPP port does 78
not allow authentication.
 But SDM allows users to

enter their credentials.
 They can also enter a proxy

IP address in case they print
via a proxy server.
No additional notes

79
Practical Work
Exercise 4

No additional notes

80
2.5 Point and Print

No additional notes

What is Point and Print?
 Point and Print is the Windows feature that automatically 81
downloads and installs a printer driver when a user

connects to a shared printer.
 Point and Print also updates the printer driver on the client
computer when the driver configuration is updated on the
print server.
No additional notes

Driver Installation
 When you install a printer on a print server, you must 82
install the printer driver for the server’s native processor

architecture.
 Because Point and Print downloads printer drivers that are

installed on the print server, Point and Print can download
the print server’s native printer driver to client computers
that have the same processor architecture as the print
server and use the same printer driver type.
 For Point and Print to support client computers with other

processor architectures or that require another printer
driver type, you must install the corresponding printer
drivers on the print server.
No additional notes

Connection Methods
 Point and Print supports various ways for a client 83
computer to establish a connection to a shared printer that

is hosted on a Windows print server:
 UNC.
 Add Printer Wizard.
 Drag and drop.
 Double-click.
No additional notes

UNC
 UNC stands for Universal Naming Convention. 84
 From the Start menu, choose Run (Start Search box in

Windows Vista, 7 and 2008), type the Universal Naming
Convention (UNC) pathname of the remote printer, for
example, \\PrintServer\Printer, and then click OK.
Note
 You probably have to manually browse to the printer installation files to
install the printer driver.

Add Printer Wizard
 From the Start menu, open the Printers and Faxes folder 85
(Devices and Printers in Windows Vista, 7 and 2008).

 Click Add a Printer, click Next, select Network printer in
the Add Printer Wizard and then specify the UNC path to
the shared printer.
No additional notes

Drag and Drop or Double-click
 From the Start menu, choose Run, type the name of the 86
print server, for example \\PrintServer, and then click OK

to view the shared printers on the print server.
 Drag the desired printer icon into the Printers & Faxes
folder of the local client computer to install the printer, or
just double-click on the printer icon.
No additional notes

87
Practical Work
Exercise 5

No additional notes

88
2.6 WSD

No additional notes

What is WSD
 WS-Device is a newly-supported standard function for 89
Windows Vista and later.

 Ricoh calls this WS-MFP.
 It supports the connection of devices such as printers and
scanners in the Windows environment.
Windows
Vista
Note: “WS” stands for Web Services.
No additional notes

Plug and Play
 The WS-MFP feature is similar to UPnP which is supported on 90
05S and later products.
 WS-MFP includes the features provided by UPnP and also

provides a driver auto installation function and some other print
and scan services as well.
 Once a network connection is established, you can use the

Network Explorer to browse content on connected computers,
MFP’s, printers and scanners.
 The next slides will show how to install a driver using WSD.
 Note that this chapter shows the main points about WSD.
 Check the GW Connectivity training on WICE for more

extensive information.
No additional notes

Network Explorer
 Network Explorer presents a view of all computers, 91
devices, printers and scanners on a network.
No additional notes

Specifications
 WS-MFP provides the following 2 services: 92
 Printer service.
 Supported on 07A models and later.
 Scanner service.
 Supported on 08A models and later.
 Supported Operating Systems:
 Windows Vista or later.
 Supported communication protocols:
 TCP/IP (IPv4/IPv6).
 SNMP daemon (snmpd).
 Supported models:
 07A or later models MFP/LP.
 Supported I/F:
 Ethernet and Wireless LAN.
No additional notes

Requirements
 Both the machine and computer must be on the same 93
network segment, and Network Discovery must be

enabled.
No additional notes

Configuration of MFP
 WS-Device and WS-Printer can be enabled from the Web 94
Image Monitor menu.

 TCP/IP (IPv4/IPv6):
 WSD (Device) (Active/Inactive)
 WSD (Printer) (Active/Inactive)
 WSD (Scanner) (Active/Inactive)
 WS-Printer/IPP Timeout (Default: 900 seconds)
IPv4/ IPv6 Settings in Web Image Monitor
 You can also use telnet:

 > set [param]
 Enable/Disable the following functions:
Wsdev (WS-Device IPv4)
Wsdev6 (WS-Device IPv6)
Wsprn (WS-Printer)

Auto Installation/ Configuration
 Once the device is found on the network, a user can install its 95
printer driver by using the auto installation function that is

supported with Windows Vista and later.
 When a user installs the driver from Network Explorer, an

appropriate printer driver is automatically selected and installed
using the WSDMON Port Monitor (WSD port is automatically
created).
 Although the printer port is created automatically, device

accessories may have to be configured manually from the driver
menu, depending on the controller version.
 07A – 08S models:
 Bidirectional communication via WSD not supported.
 Accessory settings must be configured manually.
 08A or later:
 Bidirectional communication via WSD supported.
 Accessory settings configured automatically.
Note:
 An appropriate printer driver can only be automatically selected when the
driver is available in the driver store.
WSDMON Port Monitor
 The WSDMON port monitor is a printer port monitor that supports printing
to network printers that comply with the Web Services for Devices (WSD)
technology. The WSDMON port monitor listens for WSD events and
updates the printer status accordingly. This port monitor is new for
Windows Vista.
 The WSDMON port monitor can:
 Discover network printers and install them.
 Send jobs to WSD printers.
 Monitor the status and configuration of the WSD printers and update
the printer object status accordingly.

Icons in Network Explorer
 07A Controller: 96
 WSD-Printer Only.
 Right-click or double-click to
install.
 08S or later:
 WSD-Printer and Scanner.
 Right-click or double-click to
install.
 Click to view Web Image

Monitor.
No additional notes

Installation
 In Network Explorer, select the device whose driver you 97
want to install, and then click “Install”.

 When the appropriate driver is in the driver store of the
OS, the installation process will automatically install the
drivers for the device (Otherwise locate and install the
driver manually).
No additional notes

Event Notification
 Users can check the device status from the Printer View. 98
 Device events such as paper jam or low toner will be

displayed here when they occur.
 Device Events (ex.):

 Door Open.
 Paper End.
 Paper Jam.
 Offline (Printer).
 Low or no toner.
No additional notes

99
Practical Work
Exercise 6

No additional notes

100
3. Remote Desktop Services

No additional notes
Chapter Overview
1. Introduction 101
2. Terminal Server History

3. Printing
4. Port Redirection
5. Accessories
6. Easy Print
7. Citrix
No additional notes
102
3.1 Introduction

No additional notes
Remote Desktop Services
 Remote Desktop Services in Windows Server 2008 R2, 103
formerly known as Terminal Services in Windows Server

2008 and previous versions, is one of the components of
Microsoft Windows (both server and client versions) that
allows a user to access applications and data on a remote
computer over a network, using the Remote Desktop
Protocol (RDP).
 Terminal Services is Microsoft's implementation of thin-
client terminal server computing, where Windows
applications, or even the entire desktop of the computer
running Terminal Services, are made accessible to a
remote client machine.
 The client can either be a fully-fledged computer, running
any operating system as long as the terminal services
protocol is supported, or a bare bone machine powerful
enough to support the protocol.
No additional notes
Remote Desktop Connection
 Microsoft also provides the client software: Remote 104
Desktop Connection (formerly called Terminal Services

Client).
 When an RDP client connects to the server (using TCP
port 3389), it is tagged with a unique Session ID and
associated with a freshly spawned console session
(session 0, keyboard and mouse only).
 After entering the user credentials, the GUI is presented.
 Any input is redirected over the network to the server,
where all application execution takes place.
 Any installed printer on the client-side should also be
redirected, so users can print from their Remote Desktop
session.
 These redirected printers are called session printers.
No additional notes
Printers and Remote Desktop Services
 Getting users to print on printers via Remote Desktop, be 105
it local printers or networked printers, can be a challenge.

 When we just stick to Microsoft, there are so many
different server versions (NT4.0, 2000, 2003, 2008),
clients (2000, XP, Vista, 7 and earlier of course),
architectures (32 bit or 64 bit), printer drivers (RPCS,
PCL5, PCL 6, Postscript, mini drivers, universal drivers)
that you are bound to get a headache when you run into
problems.
 To make matters worse, instead of using the Microsoft
terminal services, many companies use Citrix Terminal
Server (Citrix Presentation Server/ XenApp) or other 3rd
party solutions like ThinPrint or Screwdrivers.
No additional notes
Supported Drivers
 On www.ricoh-support.com you can find a compatibility list 106
of Ricoh printer drivers.

 Make sure to check this list, before attempting to use
these drivers in a terminal server environment.
No additional notes
107
3.2 Terminal Server Overview

No additional notes
Terminal Server History
 The Terminal Server history dates from the 1990’s. 108
 The original MultiWin architecture was designed by Citrix, who

licensed the Windows NT 3.51 source code from Microsoft to
create multi-user Windows.
 Citrix created its own product called WinFrame, which was a
multi-user version of Windows NT 3.51 and totally separate from
the operating system that Microsoft produced.
 Microsoft licensed MultiWin back from Citrix in 1995 and
plugged this multi-user core into the base operating system to
make a new product: Windows Server with multi-user
capabilities.
 The end result was Windows NT4.0, Terminal Server Edition.
 Citrix no longer provided a standalone product but released
MetaFrame, which ran on top of Terminal Server Edition in
much the same way that Citrix Presentation Server runs on
Windows Server now.
No additional notes
Starting Point
 Terminal Server Edition was very much a starting point. 109
 The operating system was pretty basic, to put it mildly.

 Almost every installation of Terminal Server Edition ran
MetaFrame on top of it because the base product did little
more than provide a multi-user operating system.
 That Terminal Server Edition and the core operating
system were different products wasn't great for either
Microsoft or its customers.
 Microsoft had to deal with two sets of operating system
service packs, while customers had to purchase a
separate product to test server-based computing and
juggle two different service packs that were not released
at the same time.
No additional notes
Windows 2000 Server
 The first real breakthrough in Microsoft Terminal Services 110
was in Windows 2000 Server.

 For the first time, Terminal Services was a server role in
the base server operating system, not a separate product.
 Windows 2000 Server introduced Remote Administration
as an optional component, allowing server administrators
to remotely manage servers.
 RDP in Windows 2000 Server added some basic
functionality such as client printer redirection and a shared
clipboard between local and remote sessions.
No additional notes
Windows 2003 Server
 The next big step was Windows Server 2003, which took 111
some of the decisions made in the Windows 2000 Server

time frame to the next logical conclusion.
 It enabled Remote Administration for all Windows server
roles and make it an option for the client.
 It also enabled drive mapping, full color, sound and other
features previously only possible with third-party products
to make the remote experience a lot more like the local
desktop experience.
 Windows Server 2003 introduced some Group Policy
settings for configuring and managing terminal servers,
and Terminal Server Manager supported management of
remote servers.
 Windows 2000 terminal servers could be configured
remotely, but not collectively.
No additional notes
Windows 2008 Server
 The latest edition (at the time of writing this module) is 112
Windows 2008 Server.

 The features included in Windows Server 2008 assume
the following:
 Many end users access the corporate LAN from the Internet
at least some of the time.
 End users don't always log on from domain-joined
computers.
 End users are more likely to run a full desktop (with some
locally installed applications) than a terminal device.
 End users may work from a branch office but still are
connected to the domain.
 Administrators need more application-serving capacity than
a single server - they must be able to add some redundancy.
No additional notes
113
3.3 Printing

No additional notes
Terminal Server Printing
 As already mentioned, printing via a terminal server 114
session can be quite a challenge.

 Depending on the Terminal Server in use, printer drivers
sometimes have to be installed on both the client PCs and
Terminal Servers.
 These drivers must be Terminal Server suitable, since faulty
(or incompatible) drivers can crash the system.
 The drivers on both the servers and clients have to be of the
same version, otherwise printing may not be possible.
 Especially challenging when you have a mixed bunch of
Operating Systems in the network.
 Thankfully, much of the printing pain goes away with
Windows 2008 Server’s Easy Print.
 But before looking at Easy Print, let’s first discuss
Windows 2000 and 2003 Server printing, because it is
used a lot in the field.
No additional notes
Scenario's 2000 and 2003 Server
 There are in general 4 methods of installing printer drivers 115
in a Windows 2000 or 2003 Terminal Server (TS)

environment:
A. The printer (driver) is installed directly on the terminal
server.
B. The printer (driver) is installed on the terminal server with
point and print by browsing (while in a terminal session) to
a shared printer on the local client pc.
C. The printer is installed on the server and client. The
session is auto-created/ auto-redirected when the user logs
into a terminal session (w2k option).
D. The printer is installed on the client and the administrator
manually creates/ redirects a printer on the server to the
client (w2k option).
 The next slides will explain these scenario’s in detail.
No additional notes
Scenario A
 The printer (driver) is installed directly on the terminal 116
server.
Network LPT/USB/COM
connection connection
Terminal
Terminal Printe
Server
Server r
Client
 Disadvantage:
 Terminal Server needs to be in the same physical location
as the client.
 Before Windows 2000 (WinNT) there were 2 common terminal server-

printing methods:
 1. The printer (driver) is installed directly on the terminal server.
In this case, an administrator installs the driver directly on the
terminal server.
The driver becomes available to all terminal server clients.
 2. The printer (driver) is installed on the terminal server via point and
print by browsing to a shared printer on the client.
In this case, the driver is installed via point and print from the
client while the client is in a terminal session.
The driver gets installed on the terminal server and will be
available to the client only.
Note:
 The administrator can also install the printer on the server via point and
print and make it available to all users.
 As from Windows 2000 Terminal Services, you have two additional types
of printing.
 3. The printer is installed on the server and client. The session is
auto-created / auto-redirected when the user logs into a terminal
session.
 4. The printer is installed on the client and the administrator
manually creates/ redirects a printer on the server to the client.
Scenario A: Printing Process
 The client connects to the 117
Terminal Server creating a

TS with printer
Terminal Session. installed
 The user launches an
application from within their
terminal session (application
is launched on the server) Terminal
Server
and selects File  Print. Client
 The file gets rendered and
spooled on the server and is
then sent to the printing
device. Spooler
 The data is printed on the

printing device.
Printe
r
Scenario A - Printer installed on the server/ print device local to the server
 In this scenario we are running a Terminal Server or Remote Desktop

Server and the printer is “local” to the Terminal Server. This is a very
basic setup and does not require a large amount of focus on
configurations in order to implement. All you should to do is install the
printer on the Terminal Server and direct the port to the locally attached
print device. This would mean that the printer driver on the server is uses
an LPT port, LPR port or TCP/IP port. that connects directly to the print
device.
 When any client connects to the Terminal Server through a terminal
session, all printers installed on the server will be available to this client.
They can startup an application and print to the servers locally attached
printer just as if they were sitting at the console of the server. In this
scenario, the print job is rendered and spooled only on the terminal
server and then sent directly to the printing device.
 This scenario works well in an environment where the printer and the
terminal client user are both located at the same physical location and the
client does not need access to a locally attached printer on the client
terminal / PC. Because users will only have access to the print devices
that are locally attached to the server, they should be able to physically
walk to the print device that is providing their output.
Scenario B
 The printer (driver) is installed on the terminal server with 118
point and print by browsing (while in a terminal session) to

a shared printer on the local client pc.
LPT/USB/COM Network
Terminal Server
Printe TS with printer
Client with printer
r installed
installed
 Disadvantages:
 Client needs rights to install printer drivers on the server.
 Not ideal for connections made through the internet.
No additional notes
Scenario B: Installation Process
1. The client connects to the TS with printer 119
Terminal Server installed

terminal server creating a
Client
terminal session.
2. The user opens network 1
neighborhood from within

the terminal session and
browses to the installed/
shared printer on the client 2
PC. 3
3. The user connects to the
shared printer on the client
Network
machine, which results in
the driver being installed on
the server (point and print).
Printe
r
Scenario B - Printer installed via point and print / print device is local to the
client
 In this scenario, the terminal client will have a shared printer installed on
the local machine and will be directing its output to its locally attached
print device via LPT, LPR, etc. You will then connect to the terminal
server via a terminal session and install the printer on the server via point
and print. This will create a network printer on the terminal server that is
pointing to the shared printer on the terminal client. When the terminal
client user connects to the terminal server, they will then be able to print
to their locally attached print device. In this case, the terminal client / PC
is acting as the print server.
 In this scenario the terminal client user will launch an application from
within a terminal session. They will then select file/print and the job will be
rendered and spooled on the printer installed on the server. Because the
printer was installed on the server as networked printer that is pointing to
the shared printer on the client, the output will be sent to the terminal
client / PC and get spooled on the shared printer. Because the shared
printer on the client is configured to communicate directly to the printing
the device, the print data stream is then sent directly to the printing
device.
 This scenario is beneficial in an environment where the terminal client
user needs to be able to print to a locally attached printer. Because of the
way “point and print” works, this scenario is not ideal over a
WAN/Internet. This situation is ideal when the terminal client user is
located within the same network infrastructure as the Terminal Server
and needs access to a local printer connected to its workstation while in a
terminal session.
Scenario B: Printing Process
1. The terminal client user TS with printer 120
Terminal Server installed

connects to the terminal
Client
server with the terminal
server client.
2. The user launches an
application from within the
terminal session and prints.
3. The job is rendered and
spooled on the server and
sent to the clients shared
Spooler
printer.
4. The job is spooled on the
client and then sent to the
print device. Spooler
5. The job is printed on the
Printe
printing device. r
No additional notes
Scenario C
 The printer is installed on the server and client. 121
 The session is auto-created / auto-redirected when the

user logs into a terminal session (w2k option).
LPT/USB/COM Network
TS with printer
installed
Internet
Terminal Server
Printe
Client with printer
r
installed
 Advantage:
 Works good over the internet.
 Disadvantage:
 Works only with Terminal Server supported drivers.
Scenario C - Windows 2000 or later Auto-create / Automatic Printer

Redirection
 Windows 2000 (or later) Terminal Services provides automatic queue

creation / automatic printer redirection. The queue creation / printer
redirection is an automated process providing that the terminal client / PC
has the same print driver installed locally as the Windows 2000 Terminal
Server. Any printer that is attached to the client via LPT, COM, or USB
will be automatically detected as long as the same print driver installed on
the terminal client is installed on the Terminal Server that it is connecting
to. When the client logs in, a printer / queue will be automatically created
for that users terminal session. This auto-created queue will automatically
redirect its output to the locally attached (LPT, COM, USB) printer on the
client. When the client disconnects or ends the session, the printer queue
is automatically deleted and all pending print jobs are terminated.
 In this scenario the terminal client user will launch an application from
within a terminal session. They will then select file/print and the job will be
rendered and spooled on the server using the auto-created / auto-
redirected print queue. The spooled file will then be sent to the locally
attached LPT, COM, or USB printer installed on the terminal client. From
there, the data-stream will be spooled and sent to the printing device that
is attached to the client. This scenario is getting more popular in
situations where the client is remotely connected to the terminal server
through the Internet / WAN and wants to print to a printer that is local to
the client.
Note:
 Citrix MetaFrame by default supports auto printer creation / auto printer
redirection for all printers that are local to the client regardless of the port
configuration.
Scenario C: Installation Process
 The printer is installed on the server and client. 122
 The session is auto-created / auto-redirected when the

user logs into a terminal session.
 Automatic Printer redirection is supported on all Win32 client
platforms.
 Print administrators can see all redirected printers, both on
the server and those redirected from their session while
normal users can see normal printers on the server and only
their own redirected printers.
 Redirected printers appear in the Printers folder in Control
Panel on the server.
 If a printer driver is not found on the server, an event is
logged and the client printer is not created. To make the
printer available, the driver must be manually installed on the
server.
No additional notes
Scenario C: Printing Process
1. The user connects to the TS TS with printer 123
with the TS client, creating a Terminal Server installed

terminal session. The printer Client
queue is auto-created / auto-
redirected.
2. The user launches an
application from within the
terminal session and selects
File  Print.
3. The file is spooled on the
server and the job is then Spooler
redirected to the client PC.
4. The job is spooled on the Shared
LPT printer that is installed Printer
on the client and printed*
5. The job is spooled on the
shared network printer Spooler
(installed on the client) and Spooler
then directed to and printed
on the printing device.
Printe
r
Note:
 If the print device is not attached with a LPT, COM, or USB port on the
client, we will install an additional shared printer and use the Net Use
command to redirect lpt1 on the client to the shared printer that is also
installed on the client.
Scenario D
 The printer is installed on the client and the administrator 124
manually creates/ redirects a printer on the server to the

client (w2k and later option).
LPT/USB/COM Network
TS with printer
installed
Internet
Terminal Server
Printe
Client with printer
r
installed
 Advantage:
 Works good over the internet including all types of locally
installed drivers (for example RPCS*).
 Disadvantage:
 Need to install drivers with help of the administrator.
Note:
 RPCS drivers are not supported on a Terminal Server.
Scenario D: Installation Process
 The user connects to the TS 125
with the TS client, creating a Termina

terminal session. The user l Server
then calls the Network
Administrator so that he can
manually install/ redirect a
printer for the user’s session
 The Network Administrator
manually installs and/ or
redirects a printer to the Add
user’s session using “Add printer
Printer” or editing the
properties of an existing Terminal Server
printer. Client with LPT
 The printer is created and printer installed
will redirect its output to the Spooler
LPT printer installed on the
client.
Scenario D - Windows 2000 and later Manual Printer Redirection
 This scenario (Specific to Windows 2000 Terminal Server Services or

later) is ideal when you have a remote user who wants print to their local
printer while in a terminal session, but they are not using a driver that is
compatible with the Terminal Server. For example, let’s say when you are
at home you use the RPCS driver to print to your CL7000 that is
connected to a LPT port. When you connect to the terminal server at the
office, you want to be able to print to your locally attached CL7000.
However, when you connect to the Windows 2000 Terminal Server at the
office with the Terminal Services Client, you never get a printer auto-
created. After doing some research, you realize that the RPCS driver is
not supported on Windows Terminal Servers and therefore the Network
administrator at the corporate office is not going to install it on the server.
 The way that you could get around this situation is by having the
administrator manually create/ redirect a printer for your session. For
example, the Network Administrator at the corporate office can install a
generic print driver on the server and have it redirect its output to your
local RPCS printer, which will in turn send the output to the print device.
 In this case, the printer is manually installed / redirected using the Add
Printers wizard. The client computer name is used to select the printer
port from the list of available ports. After the initial manual redirection,
printers are automatically redirected during subsequent logon sessions.
Note:
 Terminal Server Services does not support manual redirection of printers
connected through USB ports (only LPT and COM).
To Sum Up:
 Without Easy Print, IT administrators have to deal with the 126
following:
 Kernel-mode drivers:
 A buggy driver can - and often will - crash the terminal server. For
this reason, the use of kernel-mode drivers is blocked by default
since Windows Server 2003.
 Driver name mapping:
 When client and server are not running on the same kernel (e.g.,
clients running Windows 98 and the server running Windows 2000
Server), the drivers often do not have the same name. You have to
manually map them in an INF file to make printing to a redirected
printer work at all.
 Driver distribution:
 You have to test drivers before installing them on the terminal
server, and after they are tested, distribute them to all the other
terminal servers.
 Bandwidth usage:
 Printing can take up a lot of bandwidth, which can slow the user
session during print jobs.
No additional notes
127
Practical Work
Exercise 7

No additional notes
128
3.4 Port Redirection

No additional notes
Port redirection
 If a print device is not attached with a LPT, COM, or USB 129
port on the client, you can install an additional shared

printer and use the Net Use command to redirect lpt1 on
the client to the shared printer that is also installed on the
client.
 LPT-port redirection;
 Install local printer (not shared).
 Install printer (pointing to the final output device), share this
printer and remember the share name.
 Check client computer name.
 Perform LPT-port redirection.
 NOTE:
 The use of spaces in the printer share name is NOT
recommended.
No additional notes
LPT-port redirection (1/2)
130
A. Install local printer (not shared)
B. Install printer (shared)
No additional notes
LPT-port redirection (2/2)
C. Check client computer name 131
 Click on Start  Control

Panel  System
 Select the Network
Identification tab and
remember the full computer
name
D. Perform LPT-port redirection
 Start a command prompt
 Start  Programs 
Accessories  Command
Prompt
 Map the lpt1 port to your
shared printer using the “net
use” command syntax: net
use {port} \\{client computer
name}\{printer share name}
Notes:
 If you want to make sure that you have correctly mapped your lpt port on
the client to the network shared printer, you can print a test page from the
first (lpt) printer that was installed on the client. The output for the test
page should print on the networked printing device.
 To remember the connection, you may have to use the following

command: net use lpt1 \\computername\printer /persistent:yes
 For Windows 95, Windows 98, and Windows ME perform the following:
 right-click on the network printer in the printers folder and click
properties. From the details tab in the Printer Properties box, click
Capture Printer Port. This will enable you to select the LPT port that
you want to map to this network path.
 Because you are using a UNC (Universal Naming Convention) path to

the share, you may be required to have a NetBIOS compatible protocol
running on the client. On a windows PC, you can run NetBEUI, enable
NetBIOS over TCP/IP or use a WINS server.
 If you ever want to remove the mapping that you just created with the
“net use” command, you can enter the following command from a
command prompt: net use lpt1: /delete
132
3.5 Accessories

No additional notes
Accessories
 Something that users have to consider is the fact that 133
when a printer is auto-created, it will not always show the

installed accessories, nor will it always remember the
settings when the users logs off and on.
 This seems to be the case with many printer drivers, while

others seem to be working just fine.
 When it doesn’t work properly, users will have to configure

the driver every time a session-based printer is created.
No additional notes
134
3.6 Easy Print

No additional notes
What is Easy Print
 Terminal Services printing has been enhanced in Windows 135
Server 2008 by the addition of the Terminal Services Easy Print

printer driver and a Group Policy setting that enables you to
redirect only the default client printer.
 The Terminal Services Easy Print driver is a feature in Windows

Server 2008 that enables users to reliably print from a Terminal
Services RemoteApp program or from a terminal server desktop
session to the correct printer on their client computer. It also
enables users to have a much more consistent printing
experience between local and remote sessions.
 The “Redirect only the default client printer” policy setting allows
you to specify whether the default client printer is the only printer
that is redirected in Terminal Services sessions. This helps to
limit the number of printers that the spooler must enumerate,
therefore improving terminal server scalability.
 RemoteApp programs are programs that are accessed remotely through

Terminal Services and appear as if they are running on the end user's
local computer.
XPS
 Like legacy printing, Easy Print must render data into a 136
WYSIWYG format and pass that data from the terminal

server to the client where the printer is located.
 Where Easy Print differs is in the rendering and spooling

process.
 Windows Vista, 7 and Windows Server 2008 use XPS, which
supports true WYSIWYG, greater color depth, and faster
printing than GDI.
 When you print to XPS, you create an XML file that, like an
EMF file, explains exactly what the desired output should
look like.
 One major difference is that a native XPS file can be
processed by an XPS-capable driver without being
converted to the RAW format.
 Most of the time, an XPS spool file is smaller than an EMF
one.
No additional notes
Easy Print Printing Process
 Basically, Easy Print takes a print job request and does 137
only enough processing on the terminal server to get the

print job to the client.
1. The user launches a print job from an application running in
the remote session.
2. The print job is converted to an XPS file, whether from a
Win32 application requiring initial conversion to GDI or
directly from a Windows Presentation Foundation (WPF)
application.
3. The XPS file is sent to the Easy Print plug-in in the Remote
Desktop Connection client 6.1.
4. Unconverted XPS files go straight to the print driver as
XPS spool files.
5. XPS files destined for a GDI printer are converted to EMF
spool files.
6. The print job goes to the printer.
No additional notes
Benefits of Easy Print
 You don't have to install printer drivers on the terminal 138
server.
 TS Easy Print uses a proxy driver on the server to pass
print jobs to the client for printing.
 Because of this, all client printers are available in the TS
client session.
 By using TS Easy Print, you no longer have to match
drivers on the terminal server with drivers on the client,
and there is no risk of server crashes due to crashing
kernel-mode print drivers.
 Furthermore, the printing preferences you get when you
print from a Terminal Services session are the same
preferences you get when printing from a client computer.
No additional notes
Easy Print in Practice
 Easy Print in practice: Just login into the Server 2008 139
Terminal Server.
Client Computer
Terminal Server
No additional notes
140
Practical Work
Exercise 8

No additional notes
141
3.7 Citrix

No additional notes
What is Citrix
 We couldn’t talk about Terminal Services without 142
mentioning Citrix.
 Citrix Systems, Inc. is a multinational corporation, founded
in 1989, that provides server and desktop virtualization,
networking, software-as-a-service (SaaS) and cloud
computing technologies including Xen open source
products.
 Citrix and Microsoft have a strong relationship, which
ensures a tight integration of both the MS Operating
System and the Citrix software.
 Popular Citrix applications include Citrix MetaFrame
(discontinued), Citrix Presentation Server and Citrix
XenApp (formerly Presentation Server).
 You can download a list of compatible print devices from
www.ricoh-support.com.
No additional notes
Citrix Products
143
No additional notes
ICA
 Citrix uses the ICA protocol, or Independent Computing 144
Architecture (similar to RDP on Windows TS).
 With the latest additional of Citrix, connection to a Citrix

server is done through a web-based client called Web
Interface for XenApp.
 Can be downloaded for free from the Citrix website.
No additional notes
Device Options/ Accessories
 The older versions of Citrix (MetaFrame, MetaFrame XP) 145
suffered from the same limitation as Windows Terminal

Server (prior to Easy Print): accessory settings of session-
based printers are not remembered.
No additional notes
DeviceOption Utility for MetaFrame (1/2)
 The DeviceOption Utility for MetaFrame is a Ricoh 146
solution for this problem, specifically designed for Citrix

MetaFrame.
 It allows administrators to configure printing devices in

such a way that session-based printers will show all the
installed accessories.
 You can download this utility from the Ricoh website:

www.ricoh-support.com.
No additional notes
DeviceOption Utility for MetaFrame (2/2)
 Pre-define accessory settings of printer driver such as 147
duplex unit, additional tray, HDD and finisher.
Printer driver is not configured by Printer driver is configured by DeviceOption Utility

DeviceOption Utility
MetaFrame Server MetaFrame Server Staple
HDD/Memory
Duplex
Punching
Additional Tray
Auto created printers reset the

option settings to default every Auto created printers can keep the
time a client logs on. option settings of client printer devices.
No additional notes
Requirements
 The DeviceOption Utility for MetaFrame does have 148
requirements regarding MetaFrame version, printer

drivers and printer models.
 You can check www.ricoh-support.com for a current list of
requirements.
No additional notes
Universal Print Driver
 Citrix introduced the Citrix Universal Printer in 149
Presentation Server 4.0.
 It provides basically the same features as the Universal

Printer in Windows Server 2008.
 The Universal Printer Driver is automatically installed on

all Presentation Servers where it acts like a proxy for
printer drivers operating on the Windows client.
No additional notes
150
Basic Network Printing for Windows

END

No additional notes

Network Printing

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Network Printing

Uploaded by

Copyright:

Available Formats

1

Network Printing for Windows v2

Ricoh Academy Europe

See notes for version changes

Date of Version Description

29-02-2012 1.0.a Initial version (no changes)

Created by: Ricoh Academy Europe Version: V1.0.a Classification: Internal 1

 do an installation in a Windows-based environment.

Created by: Ricoh Academy Europe Version: V1.0.a Classification: Internal 2

 Client PC’s running Windows XP/ Vista/ 7

 Supported Printer Drivers

 SmartDeviceMonitor for Client

 Windows 2003 server running Terminal Server Service

 Windows 2008 server running Terminal Server Service

Created by: Ricoh Academy Europe Version: V1.0.a Classification: Internal 3

 After this training, you can do the exam on WICE.

Created by: Ricoh Academy Europe Version: V1.0.a Classification: Internal 4

Created by: Ricoh Academy Europe Version: V1.0.a Classification: Internal 5

1. Introduction to Windows Printing

Ricoh Academy Europe

Created by: Ricoh Academy Europe Version: V1.0.a Classification: Internal 6

2. Printing Architecture Windows XP

Created by: Ricoh Academy Europe Version: V1.0.a Classification: Internal 7

1.1 Windows Printing Introduction

Ricoh Academy Europe

Created by: Ricoh Academy Europe Version: V1.0.a Classification: Internal 8

frequently used (network) services.

Created by: Ricoh Academy Europe Version: V1.0.a Classification: Internal 9

printer is a bit obscure.

Local printer and network

Created by: Ricoh Academy Europe Version: V1.0.a Classification: Internal 10

Created by: Ricoh Academy Europe Version: V1.0.a Classification: Internal 11

 that is attached to another computer/server, or

Created by: Ricoh Academy Europe Version: V1.0.a Classification: Internal 12

Created by: Ricoh Academy Europe Version: V1.0.a Classification: Internal 13

1.2 Printing Architecture Windows XP

Ricoh Academy Europe

Created by: Ricoh Academy Europe Version: V1.0.a Classification: Internal 14

 Applications designed for Windows XP make GDI calls to

GDI Printer Driver

Created by: Ricoh Academy Europe Version: V1.0.a Classification: Internal 15

which consists of a set of Microsoft and vendor

Created by: Ricoh Academy Europe Version: V1.0.a Classification: Internal 16

Created by: Ricoh Academy Europe Version: V1.0.a Classification: Internal 17

service, which in turn will result in the inability to print.

Created by: Ricoh Academy Europe Version: V1.0.a Classification: Internal 18

services in “services” and select start or enter “net start

Created by: Ricoh Academy Europe Version: V1.0.a Classification: Internal 19

into a format that is understood by a print monitor.

Created by: Ricoh Academy Europe Version: V1.0.a Classification: Internal 20

 Enhanced Metafile (EMF) data consists of instructions to call

Created by: Ricoh Academy Europe Version: V1.0.a Classification: Internal 21

data to be printed to the form specific to a printer.

 The purpose of printer drivers is to allow applications to do

 On Windows 2000, 2003 Server and XP systems, printer drivers

 More in-depth information about drivers can be found in the

 Printers which use GDI natively are commonly referred to as Winprinters

Created by: Ricoh Academy Europe Version: V1.0.a Classification: Internal 22

1.3 Printing Architecture Windows 7

Ricoh Academy Europe

Created by: Ricoh Academy Europe Version: V1.0.a Classification: Internal 23

considerably different compared with older Windows version.