Escolar Documentos
Profissional Documentos
Cultura Documentos
Administrator’s Guide
For other guides in this document set, go to the Document Center
Contents
Chapter 1 Welcome
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
Go to Document Center
CHAPTER 1
Welcome
Important Before you install MetaFrame Presentation Server, read the Readme
file, located in the Documentation directory of the product CD. For information
about new and important features, see Getting Started with MetaFrame
Presentation Server.
Citrix provides a variety of information resources online, including a complete
product documentation library, documentation updates, and technical articles on the
Citrix Web site at http://www.citrix.com.
Important To view, search, and print the PDF documentation, you need Adobe
Acrobat Reader 5.0.5 or later with Search. You can download Adobe Reader for
free from the Adobe Systems Web site at http://www.adobe.com/.
If you prefer to access the guides without using the Document Center, you can
navigate to the component PDF files using Windows Explorer. If you prefer to use
printed documentation, you can also print each guide from Adobe Reader.
More information about Citrix documentation, and details about how to obtain
further information and support, is included in Getting Started with MetaFrame
Presentation Server.
Go to Document Center
CHAPTER 2
Read this chapter to understand how server farms are structured and how you
should design farms to provide users with easy access to applications and resources.
This chapter discusses the following topics you should consider when designing a
farm:
• Overview of server farms. Farms are the central unit through which to
organize and manage MetaFrame Presentation Server.
• Centralizing or distributing servers. How you organize server location is
largely driven by the location of your users, the location of users’ applications
and data, and your network environment. There are advantages to either
centralizing servers at one site or distributing them among multiple sites.
• Deciding how many farms to deploy. Although most deployments use a single
farm, you can consider deploying separate farms for remote sites or
environments with tight firewall security between sites.
• Planning zones in farms. You can use zones to group servers by subnet or
location, control communication, enhance performance, or discourage
bottlenecks between groups of servers within the farm. Servers in a zone can
communicate directly with one another.
• Server farm deployment scenarios. You can review and draw from these six
common farm configurations when designing your deployment. The scenarios
range from a small single-zone farm centralized in one location to a large multi-
zone farm with regional sites.
For information about configuring the most appropriate licensing deployment for
your farm, see the MetaFrame Access Suite Licensing Guide.
16 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
The ICA protocol transports an application’s screens from the server it is running
on to the user’s client device, and returns the user’s input to the application on the
server. As an application runs on a server, MetaFrame Presentation Server
intercepts the application’s display data and uses the ICA protocol to send this data
(on standard network protocols) to the client software running on the user’s client
device.
When the user types on the keyboard or moves and clicks the mouse, the client
software sends this data to the application on the server. ICA requires minimal
client workstation capabilities and includes error detection and recovery,
encryption, and data compression.
For more information about client software, see “Deploying Client Software to
Users” on page 219.
A server farm is a grouping of servers running MetaFrame Presentation Server that
you can manage as a unit, similar in principle to a network domain. When designing
server farms, keep in mind the goal of providing users with the fastest possible
application access while achieving the degree of centralized administration and
network security that you need.
For enterprises with geographically dispersed sites, there are trade-offs to consider
between centralizing servers or scattering them with the applications or data
centers. The following table outlines some of these trade-offs.
In MetaFrame Presentation Server you use farms and zones to organize the
application environment and administer servers. The next two sections discuss
planning for farms and zones.
Go to Document Center Chapter 2 Designing Server Farms 19
Deploying a Single Farm. In general, a single farm meets the needs of most
deployments. For very large deployments with, for example, thousands of servers,
breaking the environment into multiple farms can increase performance. A
significant benefit to deploying a single farm is needing only one data store
database. For more information about data stores, see “Choosing a Database for the
Data Store” on page 40.
Deploying Multiple Farms. You typically consider using multiple farms when you
have geographically dispersed data centers that can support their own data store
database or you do not want communication between servers within the farm to
cross a firewall or WAN.
20 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
The following table compares how single and multiple farm deployments relate to a
few of the important factors you must consider when planning the server
environment:
You can use zones to organize servers within a farm. The next section provides
information about setting up zones.
Go to Document Center Chapter 2 Designing Server Farms 21
Important If you change a server’s zone membership (move the server to another
zone), incorrect information can appear in the Presentation Server Console until the
server sends updates to the zone data collector. To ensure data synchronization,
restart a server after you move it to another zone.
This diagram shows a server farm with two zones connected by a WAN link. Only the
zone data collector in each zone communicates over the WAN link. Individual servers
communicate over LANs primarily with their zone data collector.
When resolving a user’s application request to the least-loaded server in the farm, a
zone data collector queries the other zone data collectors for the information it
needs to identify the server with the lightest load.
Only zone data collectors send messages between zones, reducing communication
traffic in the farm because every server does not need to communicate with every
other server. If you have a large or geographically diverse farm, you may be able to
enhance performance by organizing servers into zones.
Note Beginning with MetaFrame Presentation Server 3.0, zone data collectors no
longer automatically send updates about server loads in their zone to other zone
data collectors. This change in communication is designed to reduce network traffic
between zones.
Zone data collectors no longer maintain load information for all servers in the farm
as they did in earlier releases. The zone data collector now maintains load
information only for the servers in its own zone. This behavior is especially
beneficial in large farms.
To ensure users are efficiently routed to the least loaded server in the server farm,
you can set farm properties to share load information across zones.
Exchanging server load information should be limited to the following conditions:
• The bandwidth capacity between zones is not limited
• The Zone preference and failover policy rule is not a consideration
Go to Document Center Chapter 2 Designing Server Farms 23
Tip To reduce network traffic in large farms with multiple zones, Citrix
recommends that you use the Zone Preference and Failover policy rule to direct
users’ requests for applications to preferred zones within the farm. For more
information about Zone Preference and Failover, see “Directing User Connections
to Preferred Zones” on page 27.
Citrix recommends that you maintain all servers in a farm at the most recent release
level of MetaFrame Presentation Server. If you find that you need to run different
release levels of MetaFrame Presentation Server in your server farm on a temporary
basis, configure a server running the latest release as the zone’s data collector.
Sizing Zones
Design zones to enhance farm performance when enumerating or opening
applications for users. The number of servers you can place in one zone depends
largely on the hardware of the zone data collector and the amount of farm activity.
Factors that can influence zone size include:
• How many users connect to the farm
• How many users log on simultaneously
24 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
• How long the average user stays logged on to a session (a single daily session or
repeated short sessions)
• How many published applications are load-balanced among servers
Routinely monitor the CPU and memory usage on the zone data collector to ensure
that it is not being overloaded with requests, especially after adding new
applications or additional users to the farm.
For most deployments, limit a zone to a group of servers that are located in a single
data center and connected by low latency links.
Important Citrix recommends that you maintain as few zones as possible while
still being able to complete application enumeration requests and resolutions in a
timely manner. Creating too many zones can decrease performance in a farm,
resulting in high network bandwidth consumption and decreased performance of
the zone data collectors.
Zones can typically support more than 500 servers. When sizing zones, start with
500 servers per zone and then monitor the IMA Work Item Queue Ready Count
counter on the zone data collector to determine how much activity it can support.
Tip To find out if a zone data collector is overloaded, you can monitor the server
for the number of work items that are ready for execution. As a zone data collector
becomes overloaded, work items on the server begin to pile up and stand in queue
for execution. You can check the Work Item Queue Ready Count counter from the
Citrix MetaFrame performance object in Windows Performance Monitor. If this
counter rises above zero for a steady length of time, you should be concerned about
the load on the data collector. For more information about monitoring performance,
see “Monitoring Performance of Sessions and Servers” on page 308.
If users experience delays when their available applications are being enumerated
or when they open an application, or if reports are being generated slowly, the zone
data collector may be overloaded. Consider taking the following actions to reduce
the load on the zone data collector:
• Increase the CPU power of the zone data collector
• Dedicate the zone data collector to handling zone information and users’
requests for applications, but not running published applications
• As a last resort, divide the current zone into two zones
Go to Document Center Chapter 2 Designing Server Farms 25
CAUTION Using Registry Editor incorrectly can cause serious problems that can
require you to reinstall the operating system. Citrix cannot guarantee that problems
resulting from incorrect use of Registry Editor can be solved. Use Registry Editor at
your own risk. Make sure you back up the registry before making changes to it.
Tip To ensure the most efficient use of network traffic between zone data
collectors, do not place zones at the same connection order if they have a high
latency link between them. The data collector queries all zones in the same
connection order simultaneously. Assign a different connection order to zones at
each remote site.
If you do not enable Zone Preference and Failover, users are directed by default to
the server in the farm with the lightest load, even if that server is in another zone
across a WAN link.
Go to Document Center Chapter 2 Designing Server Farms 29
To use Zone Preference and Failover in an environment with servers running earlier
releases of MetaFrame Presentation Server:
• Make sure that the zone data collector is a server running MetaFrame
Presentation Server 4.0 or later
• Run the Citrix XML Service on servers with MetaFrame Presentation Server
4.0 or later
• Make sure that the Web Interface is configured to communicate with the servers
in the farm that are running MetaFrame Presentation Server 4.0
• Use only the most recent version of the Presentation Server Console to create,
rename, or remove zones
30 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
Servers 1-100
Zone(s) 1
Physical Sites 1
Data Store Microsoft Access, MSDE, Microsoft SQL Server, IBM DB2, or Oracle
Connectivity 10 Mbps or higher (LAN)
This diagram shows a small farm in a central location. The farm contains a data store, a
single zone, one data collector for the zone, and multiple farm member servers.
Go to Document Center Chapter 2 Designing Server Farms 31
Servers 100+
Zone(s) 1 zone per 300+ servers
Physical Sites 1
Data Store Microsoft SQL Server, Oracle, or IBM DB2
Connectivity 10Mbps or higher (switched 100Mbps is recommended)
32 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
This diagram shows a large farm in a central location. The farm contains a data store
and four zones. Each zone consists of a data collector and multiple farm member
servers.
Citrix recommends the following for large farms in a central location:
• Dedicate a data collector for zones with more than 50 servers.
• With extremely large farms, using replicated Microsoft SQL Server databases,
replicated Oracle databases, or Oracle RAC can improve performance and
prevent a bottleneck at the data store. If replication is used with IBM DB2
databases, you must configure it for read-only and all changes must be made on
the master database.
• Scale zones to maximum capacity before introducing more zones.
Go to Document Center Chapter 2 Designing Server Farms 33
This diagram shows a small farm with distributed server locations. The farm consists of a
single zone distributed across four locations. Location 1 includes the data store, data
collector, and multiple farm member servers. Each of the other locations contain farm
member servers.
Citrix recommends the following for small farms in distributed sites:
34 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
• Use a single zone if all distributed sites have a connection to a central site, the
frequency of users connecting is limited, and the remote sites are in a single
zone and each have fewer than twenty-five servers.
If you are using multiple zones, provide all sites hosting a zone with a direct link
to all other zone sites. Otherwise, all locations need connectivity to a central site
where the zone data collector is located.
• Restart servers only when WAN links are at low utilization.
• If the majority of the servers in the farm reside at one location and the remote
sites have very few servers, use a single zone.
This diagram shows a single zone with remote sites and a central office. The data store
and data collector are located at the central office.
Go to Document Center Chapter 2 Designing Server Farms 35
Citrix recommends the following in for small farms with remote sites:
• Provide a central site with a dedicated connection to each remote site
• Consider centralizing servers at one site and have users connect from clients at
remote sites so that communication between servers does not cross a WAN link,
allowing the ICA protocol to enhance performance for users across the WAN
• Consider using Virtual Private Network (VPN) technology for remote sites
• Restart servers only when WAN links are at low utilization
Servers 200+
Zone(s) 2-4
Physical Sites 2
Data Store Microsoft SQL Server or Oracle (replicated to speed server start time
and minimize WAN queries)
Connectivity High speed (T1 or higher)
This diagram shows a farm with two data centers, each with its own zone. Zone 1
contains the data store master, a data collector, and multiple farm member servers. Zone
2 contains a data store replica, a data collector, and multiple farm member servers.
Citrix recommends the following for large farms with multiple data centers:
• Tune database replication intervals to reduce WAN utilization. Be aware that
changes made at the central site can take a few minutes to disseminate to
replicas.
36 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
• The IBM DB2 database does not support updateable replicas and should,
therefore, not be used in this scenario.
This diagram shows four regional sites with remote access. Each site is a zone and
includes a data collector for the zone, multiple local farm member servers, and multiple
remote farm member servers. The data store master is located in Zone 1 and a data
store replica is located in each of the other zones.
Go to Document Center Chapter 2 Designing Server Farms 37
Citrix recommends the following for large farms with regional sites:
• Consider using Virtual Private Network (VPN) technology for remote sites.
• Consider centralizing servers at one site and have users connect from clients at
remote sites so that communication between servers does not cross a WAN link,
allowing the ICA protocol to enhance performance for users across the WAN.
• Tune database replication intervals to reduce WAN utilization. Be aware that
changes made at the central site can take a few minutes to disseminate to
replicas.
The IBM DB2 database does not support updateable replicas and should,
therefore, not be used in replicated scenarios.
38 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
Go to Document Center
CHAPTER 3
The data store provides a repository of persistent information about the farm that
each server can reference, including the following:
• Farm configuration information
• Published application configurations
• Server configurations
• MetaFrame administrator accounts
• Printer configurations
• Trust relationships
CAUTION Ensure that the data store is properly backed up on a regular basis. If the
data store database is lost, you must recreate the farm. You cannot recreate the data
store from an existing farm.
When servers in a farm come online, they query the data store for configuration
information.
CAUTION Do not directly edit any data in the data store database with utilities or
tools provided by any product other than the MetaFrame Access Suite. For
example, do not use IBM DB2, Microsoft SQL Server, or Oracle utilities to edit the
data store. Doing so corrupts the data store database and destabilizes the farm.
You should consider many factors before deciding which database product to use
for the data store, including but not limited to:
• The number of servers you currently plan to have in the farm and whether you
plan to expand that number
• Whether or not you have a database administrator on staff with the expertise to
configure and manage a data store running on SQL Server, Oracle, or DB2
• Whether or not you foresee the enterprise expanding, therefore expanding the
number and type of published applications
• Whether or not the database can sustain an increase in the number of users and
connections
• Whether a server has the appropriate hardware configuration to also run an
Access or MSDE database or whether you require that the database be located
on a server that is not also running MetaFrame Presentation Server
• Any database maintenance requirements you may have, such as backup,
redundancy, and replication
Important Microsoft SQL, Oracle, and IBM DB2 servers require significant
expertise to install and maintain. If you do not have expertise with these products,
attempting to use them in a production environment is not recommended. See the
documentation included with your database product for important details such as
performance tuning and database backup procedures.
For information about supported database and ODBC driver versions, see “Data
Store Database Requirements” on page 47.
42 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
The following are general recommendations for the farm’s data store database:
• Microsoft Access and MSDE are suitable for all small and many medium-sized
environments that are located in one physical location.
• Microsoft SQL, Oracle, and IBM DB2 are suitable for any size environment
and are especially recommended for all large and enterprise environments.
When deploying large farms across a WAN, you can obtain considerable
performance advantage by replicating the data store and distributing the load
over multiple database servers. Microsoft SQL, Oracle, and IBM DB2 are
suitable for large farms and support replication. For more information about
replicating data stores, see “Using Replicated Data Store Databases” on page
46.
The response time of other events occurring in the farm—such as starting the IMA
Service on a single server, recreating the local host cache, or replicating printer
drivers to all servers in the farm—is affected more by the size of the farm than by
the response time of the data store.
Citrix testing shows that adding processors to the server hosting the data store can
dramatically improve response time when multiple simultaneous queries are being
executed. If the environment includes large numbers of servers coming online
simultaneously and at frequent intervals, the additional processors can service
requests faster.
The actual performance of a farm’s data store can vary depending upon which
database engine is used and the level of performance tuning that can be achieved.
Depending on the characteristics of a server farm, the CPU speed and CPU quantity
can vary widely.
In the chart below, five sample farm configurations are displayed and referred to as
scenarios A through E. Each scenario lists measurements of various metrics in the
farm.
The second chart shows, for each corresponding scenario, which hardware
configurations are suggested for the server hosting the data store.
Scenario A B C D E
Number of servers in farm 80 160 250 350 500
Number of applications published to all servers 50 50 50 50 50
Number of user policies 25 25 25 25 25
Printers per server 5 5 5 5 5
Printer drivers installed per server 25 25 25 25 25
Network print servers with printers 5 5 5 5 5
Number of Load Manager load evaluators 10 10 10 10 10
Number of Resource Manager applications 10 10 10 10 10
Number of Installation Manager groups 5 5 5 5 5
Number of Installation Manager packages 5 5 5 5 5
Number of application folders in Presentation 10 10 10 10 10
Server Console
Number of server folders in Presentation Server 8 16 25 35 50
Console
44 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
Scenario A B C D E
Number of Resource Manager metrics per 25 25 25 25 25
server
Number of MetaFrame administrators 10 10 10 10 10
Size of data store database in megabytes 32 51 76 101 125
Scenario A B C D E
Dual Pentium 3/700MHz with 1GB RAM X X
Dual Pentium 4/1.6GHz with 4GB RAM X X X
Quad Pentium 4/1.6GHz with 4GB RAM X X X X X
8-way Pentium 3/700MHz with 8GB RAM X X X X X
Direct access. To make a direct connection to the data store, a server must have the
appropriate ODBC drivers installed and configured properly. The server then
connects directly to the server on which the database is running.
By default, indirect access uses TCP port 2512 for communication between servers
in the farm and the intermediary server that connects to the data store. If the servers
are in different subnets divided by a firewall, be sure this port is open on the
firewall.
Go to Document Center Chapter 3 The Farm Data Store 45
RAID 0 RAID 0 has no redundancy. It is “striped,” which means that data is divided into
blocks spanning multiple disks. RAID 0 has multiple actuators (read/write
mechanisms) because of the multiple disk use. More actuators improve read and
write performance.
Citrix does not recommend the use of RAID 0 for critical data, such as a server
farm’s data store. The savings realized from purchasing fewer disks does not
typically make up for the costs resulting from downtime and support.
RAID 1 RAID 1 uses fully redundant disk mirroring. With disk mirroring, a complete copy of
one drive is maintained on another drive. RAID 1 provides high fault tolerance and
can improve read performance.
However, RAID 1 writes the data twice, which can degrade write performance in
single disk/controller environments. In addition, this type of redundancy requires
twice the disk space.
RAID 5 Like RAID 0, RAID 5 is striped. However, because RAID 5 adds parity to the data
striping, it includes fault tolerance. If one disk in a RAID 5 group fails, the logical disk
continues to function. The parity information is used to recreate data on a
replacement disk. The loss of two disks in a group at one time cannot be sustained.
RAID 5 uses multiple disk actuators that provide improved read and write
performance.
RAID 10 RAID 10 combines RAID 1 and RAID 0. It is a striped and fully mirrored set of disks.
It is the best configuration for both redundancy and performance. Because of this, it
is the most expensive storage option.
46 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
Tip You might experience poor performance if you use a local Presentation Server
Console to perform farm maintenance on a remote site that has high latency. Such a
situation requires communication between the console and the data store to cross
the high latency link. You can publish the Presentation Server Console as an
application on a server at the remote site and use a MetaFrame Presentation Server
Client to access the published console.
• Microsoft Access Jet Engine 4.0, Service Pack 1 through Service Pack 8
• Microsoft SQL Server Desktop Engine (MSDE) 8.00.760 for Windows 2000,
Service Pack 3 or later
• Microsoft SQL Server 7.0 with Service Pack 2
• Microsoft SQL Server 2000
• Oracle Server 7 (7.3.4) for NT
• Oracle Server 8 (8.0.6) for NT
• Oracle Server 8i (8.1.5, 8.1.6, 8.1.7) for NT and UNIX
• Oracle Server 9i (9.0.1) for NT
• Oracle 9i R2 for NT and Solaris
• IBM DB2 Version 7.2 with FixPak 5-13
• IBM DB2 Version 8.1 with FixPak 1-7a
Microsoft SQL Server, Oracle, and IBM DB2 databases require an ODBC database
client driver installed on each server that connects directly to them. Servers that
connect to the data store database indirectly (that is, through another server running
MetaFrame Presentation Server) do not require an ODBC client driver.
48 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
The following table lists the drivers required for supported ODBC database clients:
CAUTION The Oracle Client Version 8.1.5 is not supported. If you are using this
version, upgrade to 8.1.55.
Microsoft Access
Choosing Use a local database on this server and selecting the Access Database
entry from the list of possible databases during MetaFrame Presentation Server
Setup creates a Microsoft Access database on the first server in the new farm. This
database acts as the farm’s data store.
The Microsoft Access database engine and ODBC drivers are default components
of Windows servers. The ODBC connection to Access uses the Microsoft Jet
Engine. To use the database engine, you do not have to install any drivers or
perform any database configuration prior to installation of MetaFrame Presentation
Server.
Minimum Requirements
The server that hosts the Access database should meet the following minimum
requirements:
• Approximately 50MB of disk space for every 100 servers. Increase disk space if
there are a large number of published applications in the farm.
• 32MB of additional RAM if the server also hosts connections.
Important Be sure to back up the Access database using the Dsmaint command
(dsmaint backup) before changing the password used to access the database.
For more information about dsmaint and other commands, see “MetaFrame
Presentation Server Commands” on page 333.
Some backups occur automatically—each time the Citrix IMA Service is stopped
or a server is restarted, the existing Mf20.mdb file is backed up, compacted, and
copied as Mf20.unk. Each time the IMA Service starts, it deletes Mf20.bak if it
exists and renames the Mf20.unk file to Mf20.bak. This process helps ensure that
the Mf20.bak file is a valid farm database.
CAUTION If the server runs out of disk space on the drive where the Mf20.mdb
file is stored, automatic backups stop. Ensure that the amount of free disk space is at
least three times the size of the Mf20.mdb file.
The Mf20.mdb file and all automatic backup files are located by default in the
%ProgramFiles%\Citrix\Independent Management Architecture folder.
CAUTION Do not try to recover the data store with the dsmaint recover command
without first verifying that the Mf20.bak file exists because this command removes
the existing Mf20.mdb file from the server. If the Mf20.bak file does not exist, run
dsmaint backup.
Important If you install MSDE and specify an instance name different from
the default “CITRIX_METAFRAME,” you must install MetaFrame
Presentation Server using a manual installation method so that you can set the
MetaFrame Presentation Server Setup property
CTX_MF_MSDE_INSTANCE_NAME to the new instance name. See
“Customizing Setup” on page 389 for more information about Setup properties.
Important Citrix strongly recommends that you use the version of MSDE (MSDE
2000, Release A) included on the server installation CD for MetaFrame
Presentation Server.
After you install MSDE, choose Use a local database on this server and select the
SQL Server Desktop (MSDE) Database entry from the list of possible databases
during MetaFrame Presentation Server Setup.
Minimum Requirements
The server hosting the MSDE database should meet the following minimum
requirements:
• Approximately 50MB of disk space for every 100 servers and 25 applications in
the farm
• 32MB of additional RAM if the server also hosts connections
• 70MB of disk space for the MSDE database
Important If you intend to use MSDE to host your farm’s data store, do not use
double-byte characters in the name of the server on which the MSDE database will
be stored.
Migrating to MSDE
You can migrate only a data store using Microsoft Access to MSDE. To migrate
from Access to MSDE, run the MigrateToMsde utility located in the
Support\MSDE directory on the MetaFrame Presentation Server CD.
For more information about the MigrateToMsde utility, see “MetaFrame
Presentation Server Commands” on page 333.
Microsoft SQL Server 7. Microsoft SQL Server 7 with Service Pack 2 or Service
Pack 3 is supported on Windows 2000 Server and Windows Server 2003 families.
Version 3.70.08.20 or greater of the Microsoft SQL ODBC driver must be installed
on each server that directly accesses the SQL server.
• On Windows 2000 servers, the necessary drivers are installed with the operating
system.
• On Windows NT 4.0 Server, install Microsoft Data Access Components
(MDAC) Version 2.6 with Service Pack 1, which can be downloaded for free
from Microsoft’s download site. Do not use MDAC 2.6 without Service Pack 1.
Microsoft SQL Server 2000. Microsoft SQL Server 2000 is supported on Windows
2000 Server and Windows Server 2003 families.
On Windows NT 4.0 Server, Windows NT Service Pack 5 (SP 5) or later must be
installed for all SQL Server 2000 editions.
The following configurations have been verified by Citrix testing:
• MDAC 2.5, Windows 2000 Server, SQL Server 2000
• MDAC 2.51, Windows 2000 Server with SP1 or SP2, SQL Server 2000
• MDAC 2.51, Windows 2000 Server with SP1 or SP2, SQL Server 2000 with
SP1
• MDAC 2.6 SP1, Windows 2000 Server with SP1 or SP2, SQL Server 2000 with
SP1
54 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
Important MDAC 2.6 without SP1 is not supported because of an issue with
the driver.
Minimum Requirements
The practices outlined in this section are suggested practices for using Microsoft
SQL Server as the data store. Be sure to read the Microsoft SQL Server
documentation before you install and configure Microsoft SQL Server.
The server hosting the SQL Server database should meet the following minimum
requirements:
• There should be approximately 100MB of disk space for every 250 servers and
50 published applications in the farm. The required disk space increases if a
large number of published applications are in the farm.
• Set the “temp” database to automatically grow on a partition with at least 1GB
of free disk space. Citrix recommends 4GB if the farm is large and includes
multiple print drivers.
Note Make sure that enough disk space exists on the server to support growth
of both the temporary database (temp) and the data store database.
• When you finish installing the database with database owner rights, set the user
permissions to read/write only. Doing this increases the security of the database.
Important If you change the rights from database owner to read/write, be sure
to change the rights back to database owner before you attempt to install service
packs or feature releases. Installation of service packs or feature releases can fail
if the user account you use to authenticate to the data store during Setup does
not have database owner rights.
The following procedures explain how to configure the connection to use TCP/IP
sockets.
Failover
For fault tolerance with Microsoft SQL Server, use Microsoft clustering, which
provides failover and failback for clustered systems. If failover of the SQL Server
database occurs in a clustered environment, the failover of the database is
transparent to MetaFrame Presentation Server.
A Microsoft Cluster Services (MSCS) cluster group is a collection of resources,
such as disk drives, that are owned by one of the failover cluster nodes. You can
transfer the ownership of the group from one node to another, but each group can be
owned by only one node at a time.
The database files for an instance of Microsoft SQL Server 2000 are placed in a
single MSCS cluster group owned by the node on which the instance is installed. If
a node running an instance of Microsoft SQL Server fails, MSCS switches the
cluster group containing the data files for that instance to another node. Because the
new node already has the executable files and registry information for that instance
of Microsoft SQL Server on its local disk drive, it can start up an instance of
Microsoft SQL Server and start accepting connection requests for that instance.
Note MSCS clustering does not support load balancing among clustered servers
because it functions in active/passive mode only.
Go to Document Center Chapter 3 The Farm Data Store 57
Distributed Databases
MetaFrame Presentation Server supports distributed databases. Distributed
databases are useful when too many read requests to the data store create a
processing bottleneck. Microsoft SQL Server uses replication to create the
distributed database environment.
MetaFrame Presentation Server requires data to be coherent across multiple
databases. Coherent data is the same across the databases and synchronized for
updating. A two-phase commit algorithm is required to maintain data coherency
when there are writes to the database.
When configuring Microsoft SQL Server for a two-phase commit, you must use the
Immediate Updating Subscriber model. See your Microsoft SQL Server
documentation for information about setting up replication with the Immediate
Updating Subscriber model.
CAUTION Do not use merged replication. Using merged replication corrupts the
data store.
Oracle
MetaFrame Presentation Server supports the following Oracle databases for the
farm’s data store:
• Oracle 7, Version 7.3.4
• Oracle 8, Version 8.0.6
• Oracle8i, Version 8.1.6 and 8.1.7
• Oracle9i, Enterprise Edition Database Release 1
If you are using Oracle 8, install the Oracle Net8 client Version 8.1.5.5 and ODBC
drivers provided by Oracle on each server that will directly access the database
server. The farm’s data store is stored as an object (schema) assigned to a user. You
do not need a separate database for each data store.
During install, you can either run the Net8 Easy Config, or cancel the installation at
that point and copy the Tnsnames.ora and Sqlnet.ora files from the Oracle server to
%Oracle home directory%\Network\Admin on each server in the farm.
Go to Document Center Chapter 3 The Farm Data Store 59
Important Restart the system after you install the Oracle client and before you
install MetaFrame Presentation Server.
In some cases, you need to configure the DNS entry within the Oracle Net8
Assistant. To do this, click Profile and then select the Oracle Names tab. Enter the
DNS suffix that the network is using. You can use the command IPCONFIG /ALL
to gather the DNS suffix that must be used.
If you do not restart the server after you install the Oracle client, or if the client
requires the DNS suffix to be specified, Setup reports the following error: “The
procedure entry point OCIUnicodeToCharSet could not be located in the dynamic
link library OCI.dll.”
If you are using Oracle9i, install the Oracle9i Administrator client to obtain the
Oracle ODBC driver Version 9.0.1.0.1. The Oracle9i Run-time client does not have
ODBC driver support, which is required on each server directly accessing the
database server.
Minimum Requirements
The practices outlined below are suggested practices for using an Oracle database
for the farm’s data store. Be sure to read the Oracle documentation before you
install and configure Oracle databases.
The server hosting the Oracle database should meet the following minimum
requirements. Guidelines given here apply to supported versions of Oracle7, 8, 8i,
and 9i except as noted otherwise.
• There should be approximately 100MB of disk space for every 250 servers and
50 published applications in the farm. The required disk space increases if a
large number of published applications are in the farm.
• The Oracle Client (Version 8.1.55 or later) must be installed on the server before
you install MetaFrame Presentation Server. The 8.1.5 client is not supported
with MetaFrame Presentation Server.
• The Oracle user account must be the same for every server in the farm because
all servers running MetaFrame Presentation Server share a common schema.
• If you are using one database to hold information for multiple farms, each farm
represented in the database must have a different user account because the data
store information is stored in the Oracle user account’s schema.
• The account used to connect to the data store database must have the following
Oracle permissions:
• Connect
• Resource
• Unlimited Tablespace (optional)
Note If you are using the same Oracle database for multiple server farms, Citrix
recommends that you create a unique tablespace with its own user name and
password for added security for each farm. Do not use the default system account
within Oracle.
Migrating to Oracle
Migration of a farm data store to an Oracle database is supported for the database
versions listed in the following table. For information about data store migration,
see the Dsmaint command on page 368.
Note If you migrate from an Access database to an Oracle 8.1.7 database, the
Citrix IMA Service fails to start because the Oracle 8.1.7.0 driver alters the logon
authentication method. To avoid this problem, disable the Oracle NT Security
feature in the Oracle Advanced Security settings before migrating an Access
database to Oracle 8.1.7.
Client Configuration
If you use the Oracle 8.1.7 client to access the data store, you must disable the
Oracle NT Security feature for the client to work with MetaFrame Presentation
Server. The Oracle 8.1.7.0 driver installs a security feature, called NT Security, that
uses Windows NT credentials to authenticate to the Oracle server. Because the
Citrix IMA Service is configured to use the system account to access the data store,
the service fails to connect to the Oracle server when the NT Security feature is
enabled.
You can disable the use of NT Security on the Authentication tab of the Oracle
Advanced Security settings. Consult your Oracle documentation for more
information.
Failover
With Oracle, you can maintain a standby database for quick disaster recovery. A
standby database maintains a copy of the production database in a permanent state
of recovery.
Citrix recommends the use of standby databases. With Oracle8i and 9i, the
management of standby databases is fully automatic. See the Oracle documentation
for instructions about setting up a standby database.
Distributed Databases
MetaFrame Presentation Server supports distributed databases. Distributed
databases are useful when too many read requests to the data store create a
processing bottleneck. Oracle uses replication to create the distributed database
environment. Important items concerning distributed databases are listed below.
• To reduce the load on a single database server, install read/write replicas and
distribute the farm servers evenly across the master and replicas.
• MetaFrame Presentation Server requires data coherency across multiple
databases. Therefore, a two-phase commit algorithm is required for writes to the
database.
Using Oracle as a distributed database solution requires the following:
• All participating databases must be running Oracle
Go to Document Center Chapter 3 The Farm Data Store 63
Tip If the performance at the replicated database site is significantly slower, verify
that all the indexes for the user’s schema are successfully replicated.
Note Because of the hardware configuration required for Oracle Parallel Server,
this product was not tested in the Citrix test labs. Oracle Parallel Server is designed
to allow multiple database servers to access the same back-end database. In theory,
this provides good scalability in centrally located farms with hundreds of servers.
IBM DB2
MetaFrame Presentation Server supports IBM DB2 Universal Database Enterprise
Edition Version 7.2 for Windows 2000 with FixPak 5 or later for the farm’s data
store.
Install the IBM DB2 Run-Time Client and apply FixPak 5 on each server accessing
the database server. If you have multiple farms, create a separate database/
tablespace for each farm data store.
Important Restart the system after you install the IBM DB2 Run-Time client and
FixPak5 and before you install MetaFrame Presentation Server. You may also need
to restart after you install the Run-Time client and before you install FixPak 5. See
the DB2 documentation for more information.
Minimum Requirements
The practices outlined below are suggested practices for using an IBM DB2
database for the farm’s data store. Be sure to read the DB2 documentation before
you install and configure DB2 databases.
The server hosting the DB2 database should meet the following minimum
requirements:
• There should be approximately 100MB of disk space for every 250 servers and
50 published applications in the farm. The required disk space increases if a
large number of published applications are in the farm.
• Citrix labs tested the IBM DB2 environment with the following permissions
assigned to the user: connect database, create tables, register functions to
execute to database manager’s process, and create schemas implicitly.
• If you create a data source name (DSN) for use with an unattended installation
of IBM DB2, Citrix recommends that you create the DSN using the Microsoft
ODBC Data Source Administration screen. Doing so ensures that the DSN is
populated according to server requirements for proper connectivity to the DB2
database or tablespace.
• Give the DB2 user account that is used for the farm the following permissions:
• Connect database
Go to Document Center Chapter 3 The Farm Data Store 65
• Create tables
• Register functions to execute to database manager’s process
• Create schemas implicitly
System administrator (DB2Admin) account permissions are not needed for data
store access.
• Consult DB2 documentation for tuning database performance. The following
settings can help optimize performance in large farms:
Distributed Databases
MetaFrame Presentation Server supports distributed databases. Distributed
databases are useful when too many read requests to the data store create a
processing bottleneck. You can use a distributed database to distribute the load of
read requests. IBM DB2 uses replication to create the distributed database
environment.
66 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
Important MetaFrame Presentation Server uses the data type of binary large object
(BLOB) to store information in an IBM DB2 database. IBM DB2 does not support
the use of BLOB data types in an updateable replication scenario. Therefore, if your
farm needs to have updateable replicas, use Microsoft SQL Server or Oracle for the
farm’s data store instead of IBM DB2.
The migration of an existing farm data store to IBM DB2 is completed as a single
transaction for roll-back purposes. Before migrating the database to DB2, verify
that enough log space exists on the target DB2 server to support the migration. If
the DB2 server runs out of log space, the migration fails and rolls back.
Go to Document Center Chapter 3 The Farm Data Store 67
CAUTION Using Registry Editor incorrectly can cause serious problems that can
require you to reinstall the operating system. Citrix cannot guarantee that problems
resulting from incorrect use of Registry Editor can be solved. Use Registry Editor at
your own risk. Make sure you back up the registry before you edit it.
You can adjust the interval by which member servers query the farm’s data store for
missed changes. The default interval is 30 minutes. You can configure the interval
using the following registry key on each server you want to adjust, with the value
expressed in hexadecimal notation:
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\IMA\
DCNChangePollingInterval (DWORD)
Value: 0x1B7740 (default 1,800,000 milliseconds)
You must restart the IMA Service for this setting to take effect.
Most changes made through the Presentation Server Console are written to the data
store. When you open the console, it connects to a specified server. The Citrix IMA
Service running on this server performs all reads and writes to the data store for the
console.
If the data store is experiencing high CPU usage when there should not be
significant read or writes to the data store, it is possible that the data store is not
powerful enough to manage a query interval of 30 minutes. To determine whether
or not the data store query interval is causing the high CPU usage on the data store,
you can set the query interval to a very large number and test CPU usage. If the
CPU usage returns to normal after you set a large query interval, the data store
query interval is probably the cause of the high CPU usage. You can adjust the
query interval by trial and error.
68 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
To test the query interval, set the interval to 60 minutes and then restart all the
servers in the farm. If the data store is still experiencing constant high CPU usage,
increase the query interval further. If the CPU usage returns to normal, you can try a
smaller value. Continue these adjustments until data store CPU usage is normal.
Important Do not set the data store query interval higher than necessary. This
interval serves as an important safeguard against lost updates. Setting the interval
higher than necessary can cause delays in updating the local host cache of the
farm’s member servers.
The next section tells you how to force the local host cache to refresh.
This chapter includes background information about decisions you need to make
before you deploy MetaFrame Presentation Server. Be sure to read this chapter
before you install MetaFrame Presentation Server.
System Requirements
This section describes minimum configurations and recommendations for installing
MetaFrame Presentation Server. For information about system requirements for
client devices, see the Client Administrator’s Guide for each client platform.
Important You must install the Terminal Services component before you
install MetaFrame Presentation Server. Terminal Services is not installed with
Windows by default; you can install it with Add/Remove Programs in the
Control Panel. Install Terminal Services in Application Server mode.
70 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
Windows 2000 Server and Windows Server 2003 operating systems can address up
to 4GB of memory, usually 2GB for kernel and 2GB for processes. Using the /3GB
switch in the Boot.ini file changes memory allocation to 1GB for kernel and 3GB
for processes. Due to the large number of applications and processes running on a
MetaFrame Presentation Server and Terminal Services, kernel memory space is
heavily used, so using the /3GB switch causes a decrease in scalability.
The /3GB switch is useful for systems with a few processes that consume a large
amount of memory such as with Microsoft SQL Server and Microsoft Exchange
Server. However, if the applications hosted on MetaFrame Presentation Server are
not written to utilize the /3GB switch, you cannot take advantage of the extra
memory and may instead encounter instability.
The ICA Client Creator utility is not supported. If you want to create installation
floppy diskettes for supported client software, you must manually create them.
“Restrict each user to one session” feature is enabled by default. When this setting is
enabled, the server disconnects an active session and reconnects the new connection
request from the same user to the disconnected session. Enabling this feature
conserves resources and simplifies reconnecting to disconnected sessions.
You can disable this setting in the Server Settings node of Terminal Services
Configuration.
Go to Document Center Chapter 4 Planning for Deployment 71
Users must be members of the Remote Desktop Users group to connect through
Terminal Services. By default, there are no users in the Remote Desktop Users
group, so users are blocked from connecting remotely. MetaFrame Presentation
Server Setup allows you to add the members of the local Users group to the Remote
Desktop Users group. If you skip the step of adding users to the Remote Desktop
Users group, you must add users to this group after Setup completes.
All servers running MetaFrame Presentation Server must have graphics capabilities
of a minimum of VGA 640 x 480 pixels.
Set the displays for computers running the Presentation Server Console to a least
800 x 600 pixels.
Important You cannot configure a modem or serial port as both a RAS service port
and an ICA asynchronous connection port.
Most companies find that their users can be categorized as typical users or power
users.
Go to Document Center Chapter 4 Planning for Deployment 73
Typical user. A typical user generally uses one or two applications but normally
only one at a time. Little actual program data is transferred between the client and
server, and the users rarely use Object Linking and Embedding (OLE).
Power user. A more sophisticated user who uses three or more applications, often
with several active at the same time. Data is often cut and pasted between local and
remote applications, and OLE is used heavily.
Power users consume more resources than typical users. A good rule of thumb is
that one power user is equivalent to two typical users in processor utilization and
RAM requirements.
Tip The configuration examples in this section are based on numbers of typical
users. Adjust the numbers for power users.
Hard Drives
The hard drive subsystem in a server is an important factor in system throughput.
Small Computer System Interface (SCSI) disk drives and adapters, especially Fast
Narrow SCSI (SCSI-2), Fast Wide SCSI, Wide Ultra SCSI, and Wide Ultra2 SCSI
devices, have significantly better throughput than ST-506, Integrated Device
Electronics (IDE), or Enhanced Small Device Interface (ESDI) disk drives and
adapters.
For the highest performance, consider using a SCSI-based Redundant Array of
Independent Disks (RAID) controller. RAID controllers automatically place data
on multiple disk drives and can increase performance and improve data reliability.
Use NTFS for all disk partitions on your servers. NTFS allows security
configuration, better performance, and more fault tolerance.
Network Interfaces
The ICA protocol is highly compressed and causes negligible loading on a network,
but because the server handles all network requests, Citrix recommends a high-
performance network interface card (NIC).
If a multiport asynchronous communications adapter is installed for supporting
serial ICA connections, be sure to use an intelligent (microprocessor-based) adapter
to reduce interrupt overhead and increase throughput.
Use Windows 2000 Server or Windows Server 2003. Install MetaFrame Presentation
Server exclusively on Windows 2000 or Windows Server 2003 servers. Native
support for Active Directory is included in these versions of Windows, so you do
not need to install additional services.
Use a single forest. Install all servers in the server farm so they reside in one Active
Directory forest. See “Using Active Directory Forests” on page 76.
76 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
After you select users, changing the list of host servers can change the trust
intersection, which can make the application unavailable to users who are no longer
in the servers’ trust intersection. If the trust intersection changes, the console
informs you and removes users who are no longer eligible to use the resource from
the authorized users list.
A published application is available only to users who can access every server that
hosts the application. When multiple servers host the same application, you cannot
predict to which servers users will connect when they launch the application.
Therefore, if a user is authorized to access only some servers, you cannot ensure
that the user will always be able to use the application.
To prevent unpredictable access, MetaFrame Presentation Server removes users
from the authorized users of a published application or printer if the accounts are
not in the trust intersection for all the host servers.
Trust-Based Routing
Trust-based routing allows servers to be members of a server farm even if the
servers belong to domains that do not trust each other. In trust-based routing, a
request to enumerate users or authenticate a user is routed to a server that has the
required domain trust relationship if the originating server does not.
During a trust query cycle, a server registers its trusted domains with the farm’s data
store. This operation occurs during every service startup and approximately every
six hours while the service is executing. Therefore, the data store is a central
repository of all trust data for the servers in the server farm.
When a server needs to perform an operation (as defined below) on a domain that it
does not trust, the server determines from the data store which servers can perform
the operation and then routes the request to the most accessible server.
Trust-based routing applies to the following operations:
• Authenticating a MetaFrame administrator to the Presentation Server Console
• Refreshing the display or launching an application in Program Neighborhood
• Enumerating users and groups in the console
• Resolving users and groups into distinguished account names when you add
users or groups to a published application, add users to a printer autocreation
list, or define new MetaFrame administrators
This section describes the Active Directory security groups and gives
recommendations for using Active Directory security groups in a server farm.
Domain local groups. In the Active Directory model, domain local groups can
contain groups from other domains, but the domain local group can be assigned to
resources only in the domain in which it exists.
Universal groups. Universal groups can contain groups from other domains.
Universal groups are stored in the Active Directory global catalog. Universal
groups can be used for assigning permissions to resources in any domain.
Domain global groups. Global groups contain groups within the same domain and
can be assigned to resources in any domain. Citrix recommends that you use
domain global groups for user access to published applications and network
printers.
Note Domain global groups are equivalent to non-Active Directory global groups.
Domain local groups and universal groups are available only in Active Directory
domains that are operating in native mode.
If you plan to use universal groups or domain local groups, Citrix recommends that
you follow the deployment guidelines in this section regarding domain
configuration and use of groups to reduce administrative complexity.
For in-depth technical information about user access issues and configuration
issues, see “User Permission Scenarios with Active Directory” on page 78.
If you change the servers that host a published application, the trust intersection
with individual user accounts and with domain local groups can change.
For example, if all servers hosting an application or a printer reside in a common
domain, D1, you can select domain local groups from D1 to grant access to the
resource. If you then configure additional servers to host the resource and these
servers do not reside in D1, the Presentation Server Console detects the change and
removes the D1 domain local group from the configured accounts for the resource.
For more information about domains, establishing trust relationships among
domains, and configuring user accounts in domains or Active Directory, see your
Windows documentation.
The following table lists NDS terms and their meanings used in this section:
Term Meaning
Tree A set of objects set up hierarchically in a tree structure. The root object of
the NDS tree is at the top of the tree.
Container object The tree may or may not branch to these NDS Container objects:
Country (a country location for this part of the organization)
Organization (a company, university, or departmental unit)
Organizational Unit (a business unit, division, or project team)
Common Name The name for a leaf object on the tree. Examples of leaf objects are: users,
groups, servers, and printers.
Context An object’s position in the tree. One way to represent context is by a string
of the Common Names of the objects in the path from the leaf or container
object to the root.
Distinguished A combination of an object’s common name and its context that makes up
Name a complete NDS path for an object. A full Distinguished Name (DN) starts
with a period, for the root, and has a period between each object name.
Important If you install the Novell Client on a server before installing MetaFrame
Presentation Server, set the following value in the [386Enh] section of the
System.Ini file before you install MetaFrame Presentation Server:
FileSysChange=off
82 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
Make this change in the System.ini file for all users. If this parameter is not set
correctly, MetaFrame Presentation Server Setup reports that the FileSysChange
parameter is not valid.
Novell technical document 10058117 refers to this issue. See the Novell
knowledgebase on the Web at http://support.novell.com/search/kb_index.jsp for
more information.
CAUTION Using Registry Editor incorrectly can cause serious problems that can
require you to reinstall the operating system. Citrix cannot guarantee that problems
resulting from incorrect use of Registry Editor can be solved. Use Registry Editor at
your own risk. Make sure you back up the registry before you edit it.
1. Type a Distinguished Name in the User Name field. A full Distinguished Name
starts with a period and has a period between each object name.
For example, user JoeX, within two container objects (the Admin organization
unit within the PNQ organization) would type the following Distinguished
Name in the User Name box:
.JoeX.Admin.PNQ
2. Type the password in the Password box.
3. Type the NDS tree name in the Domain box.
The user management subsystem updates its domain trust information every six
hours (and during service startup). Therefore, it might take as long as six hours for
all servers in the server farm to recognize a new trust relationship.
You can avoid a delay in detection of network trust changes by restarting the IMA
Service on all servers affected by the change. For example, if you change a trust
relationship to allow DomainX to trust DomainY, restart all servers that belong to
DomainX. With Active Directory, if you add a new domain to an Active Directory
forest, for example, restart the IMA Service on all servers that belong to a domain
in the forest that is affected by the change.
If you are unsure which servers are affected by a trust relationship change, you can
restart the IMA Service on all servers in the farm to ensure that the change is
recognized. Citrix recommends that you restart the IMA Service only during off-
peak hours when the load on the servers is very low.
To give other user accounts access to the console, a MetaFrame administrator with
full administration rights logs on to the console and creates other MetaFrame
administrator accounts. The level of permission for various areas of farm
management depends on the specific business function of the administrator. For
example, your system or network administrators may need complete access to all
areas of farm and server management, while help desk personnel may need only
view access to most areas.
To give administrators of your server farm access to the Presentation Server
Console, you add their network user accounts to the MetaFrame administrators
group. The console uses standard Windows network logon and user account
authentication mechanisms. Click the MetaFrame Administrator node in the left
pane of the console to view all MetaFrame administrators.
When you create a MetaFrame administrator account for a user, you can grant or
deny access to specific farm management tasks, such as disconnecting users, or to
an entire area of server farm management, such as managing sessions. You can
create specialized MetaFrame administrators with the permission level to carry out
specific tasks without granting these administrators full access to all areas of farm
management.
For more information about delegating administration rights to MetaFrame
administrators, see “Creating MetaFrame Administrator Accounts” on page 159.
Note One MetaFrame administrator account with full administration rights must
always exist in the server farm. MetaFrame Presentation Server prevents you from
deleting the last MetaFrame administrator account with full administration rights.
However, if no administrator accounts exist in the farm data store database, a local
administrator account can log on to the Presentation Server Console to set up
MetaFrame administrator accounts. If the data store database contains at least one
MetaFrame administrator account, a local administrator account cannot log on to
the Presentation Server Console.
Note Features described in this section, including ICA browsing and published
applications, are not available to all MetaFrame Presentation Server Clients. This
section focuses on the features available with Clients for Win32, Version 6.0 or
later.
This diagram shows a client performing ICA browsing when requesting an application
from a server. To run an application, a client initiates an ICA session with the server.
ICA Browsing
ICA browsing is a process in which a client transmits data to locate servers on the
network and get information about the server farm’s published applications.
For ICA browsing, clients communicate with the Citrix XML Service or the ICA
browser, depending on the browsing protocol selected in the client. These options
are described under “Configuring ICA Browsing” on page 90.
ICA browsing occurs when:
• Users launch published applications. The client sends a request to locate the
application on a server. If you are using Load Manager, a component of
MetaFrame Presentation Server for Windows, Advanced Edition and Enterprise
Edition, the client gets the address of the server with the lightest load.
• Program Neighborhood users display the Application Set list in the Find New
Application Set wizard.
Go to Document Center Chapter 4 Planning for Deployment 89
This screenshot shows how ICA browsing produces the Server and Published
Application lists for a custom ICA connection in the Client for 32-bit Windows.
ICA Sessions
An ICA session is the communications link between clients and servers that users
establish to run applications. In an ICA session, a server transmits an application’s
screen display to the client and the client sends the user’s keystrokes, mouse
actions, and local data to the application running on the server.
The default port on servers for ICA sessions is 1494. This port must be open on
firewalls for inbound communication if clients are outside the firewall. The
outbound port used on the client for the ICA session is configured dynamically
when the session is established.
In addition to computers running MetaFrame Presentation Server, other
components, such as computers running the Web Interface, proxy servers, and Web
browsers can be involved in establishing ICA sessions. In all cases, the basic
communications link for an ICA session is between the client and the server.
90 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
Important MetaFrame Presentation Server does not support multiple farms on the
same subnet configured to respond to master browser requests.
This screen capture shows Server Location options: Network Protocol, Server Group,
and Address List.
Note Some MetaFrame Presentation Server Clients do not use ICA browsing and
connect only to specified servers. The options described in this section apply to
MetaFrame Presentation Server Clients for Win32. For information about other
server location options, see the Administrator’s Guide for each client you plan to
deploy.
Tip You can configure the clients’ DNS server to use round-robin DNS to map the
name “ica” to a set of servers that can service the XML requests. This is a
convenient method to use to avoid individual configuration of server location
addresses on clients.
92 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
To locate the Citrix XML Service, the MetaFrame Presentation Server Client makes
an HTTP connection to port 80 on the server. If the user is launching a published
application, for example, the XML Service then sends to the client the address of a
server that has the application published.
When you configure the client to use TCP/IP+HTTP, communication between the
client and XML Service consists of XML-formatted data in HTTP packets.
Citrix recommends using TCP/IP+HTTP protocol for ICA browsing because it
provides several advantages for most server farms:
• TCP/IP+HTTP uses XML data encapsulated in HTTP packets that the client
sends to port 80 by default. Most firewalls are configured so port 80 is open for
HTTP communication.
• TCP/IP+HTTP does not use UDP (User Datagram Protocol) or broadcasts to
locate servers in the server farm.
• Routers pass TCP/IP packets between subnets, which allows clients to locate
servers that are not on the same subnet.
You can set the server farm, or individual servers, to respond to client broadcasts for
compatibility with deployed clients.
Because UDP broadcast packets do not traverse subnets, using broadcasts for ICA
browsing works only if a server that responds to broadcasts is in the same subnet as
the clients. After the client locates a server, it communicates using directed (not
broadcast) UDP to port 1604.
Because of broadcast limitations, you might prefer to enter one or more IP
addresses or DNS names of servers in the Address List box. You must do this if the
client is not on the same subnet as a data collector.
In summary, using the TCP/IP setting and auto-location for ICA browsing is less
efficient than using TCP/IP+HTTP because it relies on UDP and UDP broadcasts.
Important All servers in the farm must use the same port for the Citrix XML
Service.
The XML Service default communication port is 80. Port 80 is open on most
firewalls to allow inbound communication to Web servers. If your servers,
including your Web servers, are behind a firewall, this port is probably open,
allowing clients to communicate with servers and allowing Web browsers to
communicate with servers running the Web Interface.
If you intend to send data over a secure HTTP connection using secure socket layer
(SSL), be sure that the XML Service is set to share its port with IIS and that IIS is
configured to support HTTPS.
Note Port 80 is the default port for HTTP communication with Web servers. The
Citrix XML Service includes an Internet Server Application Programming Interface
(ISAPI) extension that you can plug into Internet Information Services (IIS). The
extension allows IIS and the XML Service to share port 80. This is necessary only if
IIS is installed on servers running MetaFrame Presentation Server. IIS is required to
run the Web Interface.
For information about configuring the XML Service port number, see “Configuring
the Citrix XML Service Port” on page 134. For information about configuring the
port that the Web Interface uses, see the Web Interface Administrator’s Guide.
Go to Document Center Chapter 4 Planning for Deployment 95
Important If you change the port used by the Citrix XML Service, you must set
the correct port in the client. You can specify a port number when you add a server
to the Address List under Server Location in the client. If you also use the Web
Interface, be sure it uses the correct port for XML Service communication. For
more information, see the Web Interface documentation. See the client’s
Administrator’s Guide or online help for instructions about configuring the clients.
This diagram shows communication with servers running the Web Interface. In a
network configuration with Web servers in a demilitarized zone between firewalls, users’
Web browsers send application requests to servers running the Web Interface. Web
servers send secure (HTTPS) requests to the SSL Relay and XML Service in the server
farm. Clients establish ICA sessions with servers on port 1494. The port used on the
clients is configured dynamically.
As with the basic configuration, Citrix recommends that clients use the
TCP/IP+HTTP protocol to communicate through a firewall. When the user
launches an application from a Web page, the client establishes an ICA session
through the firewall to port 1494 on the server.
The diagram below illustrates communication between clients and servers when
SSL encryption is used.
Go to Document Center Chapter 4 Planning for Deployment 99
This diagram shows client-to-server communication with SSL. For SSL communication,
port 443 is open for inbound communication to the Citrix SSL Relay. The client
communicates with the SSL Relay for server location and ICA session communication.
The process of running the application begins with ICA browsing for server
location. In this scenario, SSL+HTTPS protocol and server IP addresses are
specified for server location in the client.
1. The client sends an encrypted request to the Citrix SSL Relay on port 443 on a
specified server using HTTPS.
2. The SSL Relay decrypts the request and sends it to the Citrix XML Service on
port 80.
3. The Citrix XML Service sends the address of a server that has the requested
application to the SSL Relay.
4. The SSL Relay encrypts and sends the address of the server to the client.
5. The client establishes an SSL-encrypted ICA session with the server specified
by the Citrix XML Service. ICA packets travel from the client to port 443 on the
server and are then decrypted and passed to port 1494. SSL-encrypted ICA
packets travel from the server to the client.
100 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
To make drive access more familiar for users, you can change the server drives to
use letters that are not likely to be used by client devices. Doing so ensures that
client drives retain their original drive letters. The following table shows an
example of drive letters used if you change the drive letters of a server.
If you intend to change a server’s drive letters, do so before you install MetaFrame
Presentation Server. If you change server drive letters after you install MetaFrame
Presentation Server, you must do it before installing any applications.
If you change the server’s drive letters, MetaFrame Presentation Server searches the
following registry keys and changes all drive references to reflect the new drive
letters:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\*
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\*
HKEY_LOCAL_MACHINE\SOFTWARE\Equinox\eqn\CurrentVersion
\NetRules
HKEY_LOCAL_MACHINE\SYSTEM\*
HKEY_CLASSES_ROOT\*
HKEY_USERS\*
MetaFrame Presentation Server also updates the pagefile entry and the following
shortcut files:
%SystemRoot%\Profiles\Default User\*.lnk
%SystemRoot%\Profiles\Administrator\*.lnk
%SystemRoot%\Profiles\All Users\*.lnk
The first time a user logs on to a server after you change the drive letters, references
to the old drive letters in the user’s profile are updated.
Run Driveremap.exe to change the server’s drive letters. For more information
about this utility, see “DRIVEREMAP” on page 362.
Go to Document Center Chapter 4 Planning for Deployment 103
Note MetaFrame Presentation Server does not support RSA Security Inc.’s PKCS
(Public-Key Cryptography Standard) #11 functional specification for personal
cryptographic tokens.
104 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
You can also use smart cards with the Web Interface for MetaFrame Presentation
Server. For details about configuring the Web Interface for smart card support, see
the Web Interface Administrator’s Guide, available from the Document Center.
Software Requirements
The following section presents the basic guidelines for using smart cards with
MetaFrame Presentation Server. Consult your smart card vendor or integrator to
determine detailed configuration requirements for your specific smart card
implementation.
The following components are required on the server:
• PC/SC software
• Cryptographic Service Provider (CSP) software
These components are required on the device running the supported MetaFrame
Presentation Server Client:
• PC/SC software
• Smart card reader software drivers
• Smart card reader
Your Windows server and client operating systems may come with PC/SC, CSP, or
smart card reader drivers already present. See your smart card vendor for
information about whether these software components are supported or must be
replaced with vendor-specific software.
If you are using pass-through authentication to pass credentials from your Windows
2000 or Windows XP client device to the smart card server session, CSP software
must be present on the client device.
You do not need to attach the smart card reader to your server during CSP software
installation if you can install the smart card reader driver portion separately from
the CSP portion.
To enable support for smart card usage within an application, run the Scconfig.exe
command-line utility on each server that hosts the application. This utility is used to
specify the applications (for example, Outlook.exe) that you want to configure to
have smart card transactions redirected from the server on which they execute to the
client device that hosts the smart card reader. This utility may be executed remotely
by specifying a target server according to the syntax below.
SCCONFIG /?
SCCONFIG ([/SERVER:servername] | [/FARM]) ([/QUERY] |
[/Q])
SCCONFIG ([/SERVER:servername] | [/FARM]) [/LOGON:on|off]
[/ENABLE_PROCESS: processname] [/
DISABLE_PROCESS:processname]
SCCONFIG [/SERVER:servername] [/INHERIT:on|off]
The parameters used in this utility are explained below.
• The /? option returns on-screen help for this utility.
• The /SERVER:servername option specifies the target server to configure.
• The /FARM option is used to set a farm-wide setting but does not configure any
servers. When the farm-wide setting is set, servers are configured according to
the state of the /INHERIT option. When MetaFrame Presentation Server is
installed on the server, “on” is the default state for /INHERIT.
• If neither the /SERVER or /FARM option is specified, the local server is
assumed.
• The /QUERY or /Q option can be used with the /SERVER or /FARM option to
display currently configured settings.
• The /LOGON option is used to turn on or off support for smart card
authentication during logon to MetaFrame Presentation Server. Upon
MetaFrame Presentation Server installation, “on” is the default state for /
LOGON.
• The /ENABLE_PROCESS and /DISABLE_PROCESS options are used to
enable or disable support for applications that can take advantage of smart card
functionality when run as published applications. For example, to enable
support for Microsoft Outlook, the processname would be OUTLOOK.EXE.
• Smart-card removal policy. This is a computer policy that has three possible
settings to determine the client device behavior when the user removes the
smart card from the smart card reader:
• None (no effect)
• Lock Workstation (disconnects all user sessions)
• Force Logoff (logs off all user sessions)
This chapter gives you guidelines and step-by-step instructions for the following
tasks:
• Creating a new server farm
• Migrating to MetaFrame Presentation Server
• Overview of upgrading an existing server farm
• Installing or upgrading individual servers
• Choosing options during Setup
• Installing client software on the server
• Unattended Setup of MetaFrame Presentation Server
• Cloning servers
• Uninstalling MetaFrame Presentation Server
If you are deploying MetaFrame Presentation Server for the first time, before you
install this product, read “Planning for Deployment” on page 69.
108 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
- Or -
• From either installation CD for MetaFrame Presentation Server, open
Documentation\docs\checklist.html
3. Remap server drives.
4. Install database software and create the farm data store.
The data store contains persistent configuration information about all servers in
the farm. All servers must be able to reference this configuration information.
Before installing MetaFrame Presentation Server, you choose and install a
database product to serve as your farm data store.
For information about using various database products for the farm data store,
see “Choosing a Database for the Data Store” on page 40.
5. Install the MetaFrame Access Suite license server.
For information about installing the license server, see the MetaFrame Access
Suite Licensing Guide.
6. Create your farm by installing your first data collector and server.
For information about installing individual servers, see “Installing or Upgrading
Individual Servers” on page 116.
Go to Document Center Chapter 5 Deploying MetaFrame Presentation Server 109
7. Install the Access Suite Console, the Presentation Server Console, and the
Document Center.
For information about installing individual servers, see “Installing or Upgrading
Individual Servers” on page 116.
8. Install the Web Interface.
For information about installing individual servers, see “Installing or Upgrading
Individual Servers” on page 116.
9. After installation, restart servers.
The installation of MetaFrame Presentation Server performs the following:
• Updates the computer with a new Gina DLL
• Registers modules to be loaded as part of Windows Terminal Services
For any newly installed server running MetaFrame Presentation Server, for the
new Gina DLL to take effect and allow users to log on and to enable Windows
Terminal Services, you must restart the computer.
If you are upgrading from an earlier release, Setup migrates and retains the server
drive mappings in place from the previous configuration.
By changing the server to use drive letters that are higher, such as M, N, or O, the
original lower drive letters become available for assignment to the drives on client
devices. This can make the use of drives on client devices less confusing for users,
because they see their drives identified by typical drive letters.
To access the drive remap utility, select Product installations on the initial Autorun
screen, and then select Remap drives. For more information about the
DriveRemap utility, see “DRIVEREMAP” on page 362.
3. Create a local user account called “MPSADMIN” and then use the following
DB2 SQL script to grant this account use of the tablespace:
GRANT USE OF TABLESPACE CTXSDB TO USER MPSADMIN
WITH GRANT OPTION
GRANT USE OF TABLESPACE CTXSDB TO PUBLIC WITH GRANT
OPTION
In the example above, the tablespace is named CTXSDB and saved in
C:\CTXSDB\MPS4\sqltag.nam. The user is named MPSADMIN.
For instructions about how to migrate a farm with servers running MetaFrame 1.0,
MetaFrame 1.8, and versions of MetaFrame XP prior to Feature Release 3, see the
MetaFrame Presentation Server Migration and Upgrade Guide, which is available
for download from the Support area of the Citrix Web site:
http://support.citrix.com/
7. Deploy the new package to client desktops using Active Directory group policy,
Microsoft Systems Management Server (SMS), or other third party deployment
product. This deployment method requires no user input.
8. Decommission the farm running MetaFrame 1.0 or 1.8.
You can use the Web Interface for MetaFrame Presentation Server 4.0 to
aggregate the published applications from the MetaFrame 1.8 farm alongside
the MetaFrame Presentation Server 4.0. This is useful if the transition from
MetaFrame 1.8 to MetaFrame Presentation Server 4.0 takes place over a period
of weeks or months.
When using Web Interface with MetaFrame 1.8, you must ensure that ICA
authentication tickets are disabled for the MetaFrame 1.8 farm configuration.
If ICA authentication tickets are not disabled, the following message is
displayed in the browser of the Web Interface client:
Error: An error has occurred while connecting to the requested
resource.
You also see the following event in the application log of the Web Interface
server:
Event Type: Error
Event Source: Web Interface at <Site_Path>
Event Category: None
Event ID: 0
Description:
The farm <Farm_Name> has been configured to use MetaFrame Pre-
sentation Server ticketing, but no ticket tag was received.
Check that the farm supports ticketing. [Log ID: a561610e]
MetaFrame XP, Feature Release 3 for MetaFrame Presentation Server 4.0 for Windows
Windows 2000 Server 2000 Server with Service Pack 4
MetaFrame XP, Feature Release 3 for MetaFrame Presentation Server 4.0 for Windows
Windows Server 2003 Server 2003
MetaFrame Presentation Server 3.0 for MetaFrame Presentation Server 4.0 for Windows
Windows 2000 Server 2000 Server with Service Pack 4
Go to Document Center Chapter 5 Deploying MetaFrame Presentation Server 115
MetaFrame Presentation Server 3.0 for MetaFrame Presentation Server 4.0 for Windows
Windows Server 2003 Server 2003
Citrix recommends that you maintain all servers in a farm at the most recent release
level of MetaFrame Presentation Server. If you find that you need to run different
release levels of MetaFrame Presentation Server in your server farm on a temporary
basis, configure a server running the latest release as the zone’s data collector. See
“Configuring Zones and Data Collectors” on page 21 for more information.
Note When you upgrade the Access Suite Console, or if you are sharing My
Views between systems running different versions of the Access Suite Console,
there are certain restrictions on how the upgraded console recognizes previously
saved My Views. Specifically, this restriction applies if you are using the consoles
included with MetaFrame Presentation Server 3.0 and MetaFrame Presentation
Server 4.0.
If, after upgrading, you are asked whether or not you want to upgrade your .msc
configuration file, choose one of the following options:
• If you choose to Upgrade your file, you cannot use an older version of the
console to access the My Views stored in the file, but you can save My Views in
your new version of the console.
• If you choose Don’t Upgrade, the file is not upgraded. You can continue to use
either version of the console to access the My Views stored in the file, but you
can save only My Views to this file using the older version of the console.
CAUTION Using Registry Editor incorrectly can cause serious problems that can
require you to reinstall the operating system. Citrix cannot guarantee that problems
resulting from incorrect use of Registry Editor can be solved. Use Registry Editor at
your own risk. Make sure you back up the registry before making changes to it.
Key: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\
Windows\Installer
Type: REG_SZ
Name: Logging
Value data: iwearucmopv
A log file is created in the %Tmp% directory for each operation.
• Use Active Directory’s Group Policy Editor to configure logging properties for
an Active Directory group.
To edit the Logging policy, open Group Policy Editor and select Computer
Configuration > Administrative Templates > Windows Components >
Windows Installer.
Using Autorun
Autorun consists of multiple screens from which you select tasks you want to
perform, such as installing MetaFrame Presentation Server or viewing the
installation checklist. If you select an installation task, a Setup wizard opens and
guides you through the installation process. For information about choosing options
during Setup, see “Choosing Options during Setup” on page 120.
118 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
View installation checklist. Make sure you view the installation checklist and
prepare the product installation as outlined in the checklist. You can print a copy of
the checklist for easy reference.
Product installations and updates. Select this option to go to the next Autorun
screen and to select the components of MetaFrame Presentation Server you want to
install.
Install Document Center. Select this option to install the Citrix Document Center on
the server. The Document Center gives you a single point of access to all
Administrator’s Guides to the MetaFrame Access Suite. After installing the
Document Center, you can browse the table of contents for information about a task
you want to accomplish and get point-and-click access to all pertinent sections
across the guides. For more information, see “Installing the Document Center” on
page 138.
Install MetaFrame Access Suite licensing. Select this option to install the license
server.
For more information about installing the license server, see the MetaFrame Access
Suite Licensing Guide.
Install MetaFrame Presentation Server 4.0 and its components. Select this option to
install or upgrade to MetaFrame Presentation Server or its components.
When you select this option, the MetaFrame Presentation Server components Setup
wizard appears. Use the Select Components screen of the wizard to select the
components you want to install. By default, all components except the license
server are selected for installation.
When you click Next, you start a sequence of separate Setup wizards, each of
which guides you through the installation of a particular component of MetaFrame
Presentation Server.
Go to Document Center Chapter 5 Deploying MetaFrame Presentation Server 119
Apply Service Pack 2005.04 to MetaFrame Presentation Server 3.0. Select this option
to apply all service packs for MetaFrame Presentation Server 3.0. This option does
not update your server to the feature set for MetaFrame Presentation Server 4.0.
This option fixes only problems solved since the last full release of MetaFrame
Presentation Server 3.0.
Install management consoles. Select this option to install the Access Suite Console
and the Management Console for MetaFrame Presentation Server only. You can
install both consoles on computers other than those running MetaFrame
Presentation Server, such as workstations and laptops.
Option Syntax
Install or configure a product msiexec /i {package|ProductCode}
Uninstall a product msiexec /x {package|ProductCode}
Set a logging level msiexec /L [i][w][e][a][r][u][c][m][p][v][+][!] LogFile
(use with Install or Uninstall option) To include the v option in a log file using the wildcard flag,
type /L*v at a command prompt.
The Windows Installer log file options can also be used
with the uninstall process.
Install a transform msiexec /i package TRANSFORMS=TransformList
(use with Install or Uninstall option) If you are applying multiple transforms, separate each
transform file with a semicolon.
Set the user interface level msiexec /q {n|b|r|f}
(use with Install or Uninstall option)
The following section describes the various options you configure during Setup.
The options are presented in the order they appear if you select the Install
MetaFrame Presentation Server and its components option on the Product
installations screen of Autorun. Depending on the components you choose to
install, you may not encounter all configuration options described in this section, or
you may encounter them in different order.
To install MetaFrame Presentation Server and its components, your computer must
satisfy specific installation prerequisites for each component. To verify that your
computer satisfies installation prerequisites for each component you are installing,
review the installation checklist. To access the installation checklist, select View
installation checklist from the initial Autorun screen.
If you launch Setup from the Autorun screen, Setup automatically installs any
software prerequisites on the server except Windows components. Setup does not
install Windows components. If Setup detects a missing Windows component that
is required to run MetaFrame Presentation Server, you must install the Windows
component manually and then resume Setup.
You may choose to install software prerequisites yourself. To do so, run the Setup
files located in the Support folder of the MetaFrame Presentation Server CD-ROM
and then resume Setup. Consult your software vendor for installation guidelines and
available updates.
If you have questions about which edition to choose, contact your reseller or go to
the Product Information area of the Citrix Web site at http://www.citrix.com/
products. Based on the edition you select, Setup presents you with the components
that are available for installation.
To create a server farm using Access or MSDE for the data store
1. On the Create or Join a Server Farm Setup screen, select Create a new farm
and click Next.
2. On the Create a Server Farm Setup screen, enter the following information:
• Enter a name for the new server farm. Farm names can include spaces but
cannot be more than 32 characters in length.
• Select Use a local database on this server and select the database from the list.
Important To use SQL Server Desktop (MSDE) for your farm data store, you
must install MSDE on the server before you install MetaFrame Presentation
Server. For more information about installing MSDE, see “Microsoft SQL
Server 2000 Desktop Engine (MSDE)” on page 50.
• The default zone name is the mask for the subnet in which the server resides.
If you want to change the server farm zone name, clear the option Use
Default Zone Name and enter the new name.
3. Click Next and continue with Setup.
Important If your driver does not appear in the list, cancel Setup, install the
driver, and then restart Setup.
• The default zone name is the mask for the subnet in which the server resides.
If you want to change the server farm zone name, clear the option Use
Default Zone Name and enter the new name.
3. Click Next and continue with Setup.
4. Follow the procedure “To configure an ODBC driver for Microsoft SQL
Server” on page 127, “To configure the ODBC driver for Oracle” on page 130,
or “To configure the ODBC driver for IBM DB2” on page 131.
5. Follow the remaining instructions in Setup.
This completes data store configuration of the first server in a new farm.
Go to Document Center Chapter 5 Deploying MetaFrame Presentation Server 127
• In the Password text box, specify the password associated with login ID.
• Click Next.
If the ODBC manager is unable to verify the login ID and password, the ODBC
manager prompts you to reenter them.
This screen capture shows where to select SQL server authentication and specify
the login ID and password.
3. When prompted:
• Select Change the default database to.
• From the list, select the database you created for MetaFrame Presentation
Server.
• Click Next.
This screen capture shows where to change the default database and where to
select a database from the list.
4. Click Finish.
This screen capture shows the Finish button is located on the same pane where you
can change the language of SQL Server system messages.
5. Test the new data source name. Click Test Data Source. If the test completes
successfully, click OK twice to complete the data source name configuration.
After creating your new data source, follow the steps in the procedure, “To create a
server farm with a SQL, Oracle, or DB2 data store” on page 126, beginning with
Step 6.
130 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
This screen capture shows the Oracle8 ODBC Driver Connect dialog box with fields for
Service Name, User Name, and Password.
1. In the Service Name text box, type the service name used when you installed
the Oracle client. In the User Name and Password text boxes, type the user
name and password created on the Oracle server for the data store.
2. Click OK.
This completes the Oracle data store setup. You are now ready to proceed with
MetaFrame Presentation Server Setup. Follow the steps in the procedure “To create
a server farm with a SQL, Oracle, or DB2 data store” on page 126, beginning with
Step 6.
Go to Document Center Chapter 5 Deploying MetaFrame Presentation Server 131
This screen capture shows the Connect To DB2 Database dialog box with a drop-down
menu for selecting a Database alias, a button to add a Database alias, fields for entering
User ID and Password, Change password features, and Connection mode selection of
Share or Exclusive.
1. Set the connection mode to Share.
2. Click Add to launch the IBM DB2 Client Configuration Assistant. This wizard
walks you through configuring the ODBC connection to the DB2 database.
3. Follow the instructions in the Client Configuration Assistant. On the Protocol
page, be sure you select TCP/IP. Citrix recommends that you use this protocol
to connect to the data store.
4. Click Finish when you are done configuring the connection.
5. On a Windows 2003 Server, click Test Connection to make sure that the
connection to the database works.
6. Click Close.
7. Ensure that the connection mode is still set to Share.
8. Enter the User ID and Password.
9. Click OK.
132 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
This completes the DB2 data store setup. You are now ready to continue with Setup.
Follow the steps in the procedure “To create a server farm with a SQL, Oracle, or
DB2 data store” on page 126, beginning with Step 6.
Note One full authority administrator account must always exist in the server
farm. Therefore, MetaFrame Presentation Server prevents you from deleting the
last full authority administrator account. However, if the account no longer exists in
the network account authority, the console allows a local administrator to log on to
the console to set up administrator accounts.
Prohibit shadowing of user sessions on this server. Select this option to permanently
disable shadowing of user sessions on the server. If you disable shadowing during
Setup, you cannot enable it using other MetaFrame Presentation Server
configuration utilities or by creating connection policies.
Allow shadowing of user sessions on this server. Select this option to enable
shadowing of user sessions by the server. When you enable shadowing, you can
apply the following restrictions:
• Prohibit remote control. By default, authorized users can view a session they
are shadowing, and also use their keyboard and mouse to interact with it. Select
this option to allow authorized users to view sessions but not to have keyboard
and mouse input. Shadowing without keyboard and mouse input may conceal
from the user the fact that a session is being shadowed.
• Force a shadow acceptance popup. By default, users are notified by an
acceptance prompt when other users are attempting to shadow their sessions.
Select this option to deny users the ability to shadow sessions without sending
this acceptance prompt.
• Log all shadow connections. You can log events such as shadowing attempts,
successes, and failures in the Windows event log and examine them using Event
Viewer. Select this option to enable logging.
If you do not want the Citrix XML Service to share the TCP port with IIS, you can
use a separate port for the Citrix XML Service. On the Configure Citrix XML
Service Port Setup page, select Use a separate port and enter the new port
number. If you plan to change the port used by the Citrix XML Service on
MetaFrame Presentation Server, make sure the port you plan to use is not used by
any other application.
For a list of ports in use, type netstat -a at a command prompt. Make a note of the
port number you specify. If you use a port other than the default port 80, you must
configure servers running the Web Interface and any clients using TCP/IP + HTTP
server location to use the port you choose. See the Web Interface Administrator’s
Guide for instructions about configuring the Web Interface to use a different port.
See the Client Administrator’s Guides for instructions about configuring the clients
to use a different port.
Important All servers in the farm must use the same TCP port for the Citrix XML
Service. If farms are running in interoperability mode, this requirement includes all
servers running either MetaFrame 1.8, MetaFrame XP, or MetaFrame Presentation
Server.
Important Use this procedure only if you do not want to share the port used by IIS.
If you entered a port number other than the default “Share with IIS” during Setup,
you can change the port to another port number using the Presentation Server
Console. However, if you want to change the setting to share the port with IIS after
running Setup, you must follow the instructions for manually setting the Citrix
XML Service to share the TCP port with IIS.
1. Use the Services Control Panel to stop the Citrix XML Service.
2. At a command prompt, type ctxxmlss /u to unload the Citrix XML Service
from memory.
3. Type ctxxmlss /rnn, where nn is the number of the port you want to use. For
example, ctxxmlss /r88 forces the Citrix XML Service to use TCP/IP port 88.
4. Restart the Citrix XML Service in the Control Panel.
To manually configure Citrix XML Service to share the TCP port with IIS
1. Use the Services Control Panel to stop the Citrix XML Service.
2. At a command prompt, type ctxxmlss /u to unload the Citrix XML Service.
136 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
3. Copy Wpnbr.dll and Ctxxmlss.txt to the IIS scripts directory on your Web
server. These files are installed in \Program Files\Citrix\System32 during
MetaFrame Presentation Server installation. The default scripts directory is
\Inetpub\Scripts.
4. Use Internet Service Manager to give the files read and write access.
5. Stop and restart the Web server.
Note Windows Server 2003 supports ICA connections over TCP/IP only.
Accessing applications through the Program Neighborhood Agent. You do not need
to publish a Web page if you want users to access published applications through
the Program Neighborhood Agent. However, because this client leverages the
technology provided by the Web Interface, you must install the Web Interface to use
the Program Neighborhood Agent.
The Web Interface requires a server running both Microsoft Internet Information
Services (IIS) Version 5.0 or later and the Microsoft Java Virtual Machine (JVM).
For large-scale deployments, Citrix recommends that you run the Web Interface on
dedicated Web servers. For smaller deployments, you can run MetaFrame
Presentation Server and the Web Interface on the same server.
For more information about configuring the Web Interface, see the Web Interface
Administrator’s Guide.
You can install a standalone copy of the Document Center on any 32-bit Windows
computer without installing MetaFrame Presentation Server. To ensure you have
access to all relevant information when you need it, Citrix recommends that you
install the Document Center before you install or upgrade to MetaFrame
Presentation Server.
To view, search, and print the contents of the Document Center, install Adobe
Reader 5.0.5 or later with Search on the computer. You can download Adobe
Reader for free from Adobe Systems’ Web site at http://www.adobe.com/.
To install the Document Center, select Install Document Center from the initial
Autorun screen and then follow the instructions in the Setup wizard.
Create or update ICA Client images. The ICA Client Creator is a utility you use to
create installation disks for Windows and DOS client software. The ICA Client
Distribution wizard places copies of the client software in the database from which
this utility creates client disks.
Note The ICA Client Creator utility is not supported on Windows Server 2003.
Create or update the ICA Client Update Database. Client Auto Update is a feature
that enables you to schedule the download and installation of the latest client
software from MetaFrame Presentation Server to client devices. The ICA Client
Distribution wizard places copies of clients in the database on the MetaFrame
Presentation Server used by Client Auto Update.
140 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
Install or upgrade the pass-through client on the server. The pass-through client is
an instance of Program Neighborhood or Program Neighborhood Agent that runs as
a published application on the server. It gives users of non-Win32 clients, including
the Client for DOS, the Client for Java, and RDP clients, access to their application
sets from within the feature-rich interface of Program Neighborhood even if
Program Neighborhood is not installed on their client devices. Install Program
Neighborhood if you plan to deploy clients other than Program Neighborhood to
users.
The wizard includes typical and custom installation paths. A typical installation
does the following:
• Installs the Client Auto Update Database and copies client software into the
database
• Installs the ICA Client Creator database and copies each client into the database
• Installs the MetaFrame Presentation Server Clients on the server
When performing a custom installation, a dialog box gives you options for
installing clients.
If you select Create/Update Citrix ICA Client Images or Create/Update Citrix
ICA Client Update Database, dialog boxes let you select clients to install. For
example, if you choose to Create/Update Citrix ICA Client Images, a dialog box
lets you select clients to add to the ICA Client Creator’s database. Clear the check
boxes for clients you do not want to add to the database.
Applying Transforms
You can manipulate the installation process by applying Windows Installer
transforms (files with the .mst extension) to the installation database contained in a
Windows Installer package. A transform makes changes to elements of the
database. A transform file modifies the installation package when it is being
installed and dynamically affects the installation behavior.
When you create a transform to apply to the MetaFrame Presentation Server
Windows Installer package, you set your desired values for properties in the
package. When you then apply the transform to the installation package, the
“questions” you are asked during Setup are answered. Creating a transform allows
you to roll out MetaFrame Presentation Server in unattended mode.
Transforms that you create to customize a Windows Installer setup package remain
cached on your system. These files are applied to the base Windows Installer
package whenever the Installer needs to modify it. You can apply transforms only
when you initially install Windows Installer packages; you cannot apply transforms
to software that is already installed.
Citrix provides four sample transforms on the MetaFrame Presentation Server CD.
You can open these transforms and edit the properties in them using commercially
available Windows Installer editing tools. The sample transforms include sample
values for select properties, allowing you to determine which properties to edit to
achieve a certain configuration.
For more information about each sample transform and the properties you can set
for each configuration, see “Customizing Setup” on page 389.
Cloning Servers
If your organization uses system imaging utilities to clone standard server
configurations, with a few adjustments you can also clone servers running
MetaFrame Presentation Server.
For detailed information about cloning servers, see Advanced Concepts for
MetaFrame Presentation Server, available from the Support area of the Citrix Web
site at http://www.citrix.com.
Go to Document Center Chapter 5 Deploying MetaFrame Presentation Server 143
Important If you rename a server on your network, the new server name is added
to the list of servers in the farm. However, you must remove the old server name
because it is still listed as a member of the farm. Before you remove the server
name, be sure to update all references to the new server name, including data
collector ranking, published application references, and license assignments.
If you are planning to uninstall MetaFrame Presentation Server from the Resource
Manager metric farm server or database connection server for a summary database,
be sure to reassign the server before removing it from the farm. If you are using a
summary database, Citrix recommends that you update the database before
removing any servers from the farm. Be sure to also create any necessary billing
reports from the server before you remove it.
This chapter includes basic information about tools that you use to manage servers,
server farms, and published applications. More detailed information is available in
the online help for the tools.
Some tools are installed when you run MetaFrame Presentation Server Setup. For
more information, see “Deploying MetaFrame Presentation Server” on page 107.
Management Console for the MetaFrame Access Suite. Use the Access Suite
Console to manage multiple farms in your deployment. The console snaps into the
Microsoft Management Console (MMC) and enables you to manage items
administered through the MetaFrame Presentation Server, MetaFrame Secure
Access Manager, and MetaFrame Password Manager products.
For MetaFrame Presentation Server, you can use the Access Suite Console to
administer servers, server farms, published applications, and sessions. You can
create a variety of reports, configure application access (both through the Web
Interface and Program Neighborhood Agent), and support MetaFrame Conference
Manager guest attendee logons. In addition, you can use the console to troubleshoot
alerts and diagnose problems in your farms, and view hotfix information for your
Citrix products. For more information about using this tool, see “Management
Console for the MetaFrame Access Suite” on page 149.
License Management Console. Use this console to manage and track MetaFrame
Access Suite software licenses. For more information about licensing, see the
online help in the console and the MetaFrame Access Suite Licensing Guide.
Citrix Connection Configuration. Use this tool to configure the user connections that
link to servers. For information, refer to the online help in Citrix Connection
Configuration.
Citrix SSL Relay Configuration. Use this tool to secure communication between a
server running the Web Interface and your farm. For information, see “Setting up
Citrix SSL Relay” on page 175.
ICA Client Creator. Use this utility to create diskettes or disk images for installing
client software.
Note ICA Client Creator is not supported on servers running Windows Server
2003.
Go to Document Center Chapter 6 Managing Servers and Farms 147
ICA Client Update Configuration. Use this tool to manage the Client Update
Database on a computer running MetaFrame Presentation Server. The database
contains current client software for each supported client platform and can be used
to install clients when users log on to the server. For more information about
deploying client software to users, see “Deploying Client Software to Users” on
page 219.
Shadow Taskbar. Shadowing allows users to view and control other users’ sessions
remotely. You can use the Shadow taskbar to shadow sessions and to switch among
multiple shadowed sessions. You can also use the Presentation Server Console to
shadow ICA sessions. For more information about shadowing, see “Shadowing
Sessions” on page 304.
SpeedScreen Latency Reduction Manager. Use this tool to configure local text echo
and other features that improve the user experience on slow networks.
CAUTION Do not run the console in two sessions simultaneously on one computer
using the same account. Changes made on the console in one session can overwrite
changes made in the other.
150 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
Note The top-level node of the console tree provided with MetaFrame
Presentation Server 4.0 is called MetaFrame Presentation Server Administration. In
MetaFrame Presentation Server 3.0, this node is called Access Suite Console.
This screen capture shows the layout of the console before running discovery (see
“Finding Items in Your Deployment Using Discovery” on page 156). The left pane
contains the console tree. The task pane is in the middle. The details pane is on the right.
Go to Document Center Chapter 6 Managing Servers and Farms 151
The following nodes are available under the top-level node in the console tree:
• Alerts. Lists the alerts created by all the items in your deployment. Double-
click an alert to drill down to the affected item.
• Search Results. Displays the results of any search that you perform. Click
Search in the task pane to perform a standard or advanced search.
• My Views. Allows you to customize the information that you display in the
details pane. For instructions about creating My Views, see “Customizing Your
Displays Using My Views” on page 152.
In addition, nodes are also created by some Access Suite Console snap-ins when
they are installed. Some snap-ins are not visible as nodes in the console tree but
they add features, such as extra tasks, to other snap-ins.
Depending on your Access Suite Console installation, the following snap-ins are
available:
• Presentation Server. Allows the console to establish contact with your
deployment and displays the applications, servers, and zones in your farms.
Presentation Server is contained in the Suite Components node.
• Dashboard. Displays alerts, allows you to monitor server performance data,
and helps you to diagnose server problems. This snap-in does not appear as a
separate node in the console tree, but adds alerting and monitoring features to
the Presentation Server snap-in. For information about displaying performance
data, see the Dashboard online help.
• My Knowledge. Provides context-sensitive troubleshooting information about
alerts using knowledge based articles from Citrix and any that your organization
creates. This snap-in does not appear as a separate node in the console tree, but
adds troubleshooting features and some additional alerts to the Presentation
Server snap-in. For information about viewing and providing troubleshooting
information, see the My Knowledge online help.
• Report Center. Allows you to create reports describing various aspects of your
deployment. For more information, see the Report Center online help.
• Licensing. Launches the License Management Console that allows you to
manage licenses for your Citrix products. For information about the License
Management Console, see the MetaFrame Access Suite Licensing Guide.
• Diagnostic Facility. Creates trace logs and other system information to assist
Citrix Technical Support in diagnosing problems.
152 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
• Web Interface. Allows you to manage how users access applications through
Web Interface and Program Neighborhood Agent sites, and to administer
MetaFrame Conferencing Manager guest attendee logons. In earlier releases of
MetaFrame Presentation Server, application access was configured through the
Web Interface and Program Neighborhood Agent Consoles. These tasks are
now carried out in the Access Suite Console. Web Interface is located in the
console tree under Suite Components > Configuration Tools. For more
information, see the Web Interface Administrator’s Guide.
• Hotfix Management. Manages hotfixes for your Citrix products. Hotfix
Management is located in the console tree under Suite Components >
Configuration Tools.
To create a My View
1. In the console tree, select My Views.
2. In the task pane, click Create new My View.
3. Select the new My View in the console tree and click Add items to My View in
the task pane.
4. Add the items that you want to manage and click OK.
5. In the task pane, click Edit My View and give the My View a meaningful name
and description.
Tip Create a new My View quickly by basing it on an existing one. Select the
existing My View in the console tree and click Duplicate My View in the task
pane. Then add or remove items from the duplicate My View as required.
Note If the size of your farm means that this type of display may be very large, it
may be more practical to display sessions for a single server, application, or user.
154 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
Troubleshooting Alerts
You can get context-sensitive information about alerts in the Access Suite Console
using My Knowledge. Two types of information are available:
• Articles provided by Citrix
• Articles provided by your company
The Citrix articles are provided as a standard component. To provide users with
local knowledge, you set up a company knowledge database. After you do this,
administrators with the necessary permissions can add, edit, and delete articles.
When you set up a new company knowledge database, My Knowledge
automatically creates the required tables and stored procedures in the database. To
create these tables and stored procedures yourself, the necessary SQL files are
provided in the My Knowledge folder in the Component CD folder.
To see all the alerts that can be generated for a server farm, select the farm, then
select the Available Alerts display.
For configurable alerts, you can also quickly see the current configuration, which
may give you a better understanding of why the alert was raised. If necessary, you
can then move directly to reconfigure the alert, disable it, or delete it from your
console or all consoles.
Go to Document Center Chapter 6 Managing Servers and Farms 155
Creating Reports
Administrators often need to create reports that describe how various aspects of the
server farms are functioning. For example, quarterly data for server uptime, CPU
utilization, or application availability are commonly compared with agreed figures
in a service level agreement.
Report Center in the Access Suite Console extends the reporting capabilities in
Resource Manager for MetaFrame Presentation Server, and allows you to easily
generate reports from a variety of real-time and historical data sources. Wizards
help you select the type of report, the data to be displayed, and the schedule for
running the report. You can view the status of your scheduled reports and adjust the
report parameters.
Report Center contains several report types that describe:
• Application usage and availability
• Server usage and availability, including CPU and memory utilization reports
and a server snapshot report (that can also be created from a real-time metric
graph)
• The distribution of client types that connect to your servers
• Administration policies in place for the farm
• Session statistics over time, including active and disconnected sessions
For information about creating reports in the Access Suite Console, including
assistance with troubleshooting, see the Report Center online help.
To run the discovery process for more than one product or component
1. Select Suite Components in the console tree.
2. If you need to configure discovery for at least one product or component, click
Configure and run discovery. To just run discovery for the items used by the
components, click Run discovery.
For example, if a new server farm is created in your deployment, click
Configure and Run discovery to add that farm and its servers to the console
tree. If a new server is added to a farm that is already present in the console tree,
click Run discovery to add that server to the console tree.
If you run the console from devices that do not have MetaFrame Presentation
Server installed, such as workstations or laptops, make sure to upgrade those
devices to the latest version of the Presentation Server Console.
This chapter describes how to use MetaFrame administrator accounts to secure and
delegate administrative tasks and describes ways in which you can secure farm
communications.
Full authority administrators. Full administrators can manage all aspects of a server
farm. They can, for example, publish applications, manage printers, terminate user
sessions, and create other administrator accounts.
The authority level you grant an administrator depends on the specific business
function of the administrator. For example, your system or network administrators
may need complete access to all areas of farm management, while help desk
personnel may need view-only access to most areas.
Your need to have custom administrator accounts with varying levels of authority is
likely to increase along with the size of your organization. For a smaller scale
organization whose scope is limited to a single zone and a single geographic area,
having a single group of administrators, all of whom share the same, full level of
authority, may suffice to manage the entire farm.
However, for larger scale organizations that span multiple departments and perhaps
multiple administrative, geographic, and time zones, you may want to delegate
limited sets of tasks to individuals in particular departments or zones without giving
them access to other areas of farm management.
For example, if your finance department uses mission-critical applications and
routinely deals with sensitive data, you can let a qualified member of that
department manage those applications. To do this, you place the applications in a
custom Applications folder and then give the individual permissions to manage just
those applications. In this scenario, delegating a commensurate amount of authority
ensures that:
• A qualified individual oversees a familiar set of applications
• The individual does not have access to areas of farm management you do not
want to delegate
• The integrity of confidential data and applications is preserved
• You can focus on other areas of farm management that require your attention
If you set up multiple zones in a farm, you can delegate tasks based on zones. To do
this, create a folder for each zone under the Servers node, place your servers in the
appropriate folders, and then assign the tasks of managing the servers to select
administrators.
Important Citrix recommends that you do not mix different release versions of
MetaFrame Presentation Server in the same server farm. Upgrade MetaFrame
Presentation Server to the current version to ensure that custom administrator
settings apply properly.
Restricting access to areas of farm management may not prevent administrators
from running some command-line utilities available with MetaFrame Presentation
Server.
When you create a new administrator account, you must associate it with one of
three authority levels—full, view-only, or custom access to farm management. You
can modify an administrator’s authority level at any time. For an overview of
authority levels, see “Types of MetaFrame Administrator Accounts” on page 159.
For information about modifying authority levels of existing administrator
accounts, see “Delegating Tasks to Custom Administrators” on page 162.
To create administrator accounts with full or view-only authority, you select
individual or group accounts and associate them with full or view-only privileges.
Both full and view-only privileges apply farm wide.
To create administrator accounts with custom authority, you select individual or
group accounts, assign them custom privileges, and then permissions to perform
select tasks.
Note One full authority administrator account must always exist in the server
farm. Therefore, MetaFrame Presentation Server prevents you from deleting the
last full authority administrator account. Citrix recommends that you add your
standard network administrators group to your MetaFrame administrators group so
that network administrators have access to manage network resources including
print servers.
To create, delete, and configure MetaFrame administrator accounts, you must log
on to the Presentation Server Console as a full authority administrator.
Tip Instead of selecting names from the list, you can type them in a text box.
To do this, click Add List of Names and use semicolons (;) to separate names.
3. Click Next.
4. On the Privileges page, select the authority level you want to grant the selected
administrator accounts. Select among the following options:
• Select View Only to give the selected administrators view-only access to all
areas of farm management. Click Finish when you are done and proceed to
Step 5.
• Select Full Administration to give the selected administrators full access to
all areas of farm management. Click Finish when you are done and proceed
to Step 5.
• Select Custom to delegate specific, limited tasks to the selected
administrators. Click Next when you are done and proceed to Step 5.
5. On the Permissions page, in the Folders pane, select the folder or node for
which you want to delegate tasks to the selected administrators. The tasks you
can delegate for the selected node or folder appear in the Tasks pane.
6. In the Tasks pane, select the tasks you want to delegate. Click Finish when you
are done.
Tasks Description
FARM-RELATED TASKS
Farm Management Toggles on/off all subtasks. Allows full access to view and modify all areas of
farm management. To disable subtasks, clear the check boxes.
Edit All Other Farm Settings Allows administrators to edit all farm properties, with the exception of zones.
Go to Document Center Chapter 7 Securing Your Farms 163
Tasks Description
Edit Zone Settings Allows administrators to configure zones, move servers to zones, and set
election preferences.
View Farm Management Allows view-only access to the farm properties.
APPLICATION-RELATED TASKS
If you select a folder of applications, the assigned permissions affect only the applications in the specified folder.
Published Applications Toggles on/off all subtasks. Allows full access to view and modify all areas of
publishing applications in the specified folder. To publish applications in
isolation environments, administrators also must have the “View Isolation
Environments” permission. To disable subtasks, clear the check boxes.
Publish Applications and Edit Allows administrators to manage applications, including publishing and editing
Properties properties. To publish applications in isolation environments, administrators
also must have the “View Isolation Environments” permission. Automatically
selects and requires the View permission.
View Published Applications and Allows view-only access to published applications and content.
Content
Resource Manager Toggles on/off all subtasks. Allows full access to view and modify all areas of
resource management in the specified folder. To disable subtasks, clear the
check boxes.
Create RM Applications and Edit Allows administrators to add, remove, snooze, sleep, awaken, and edit the
Properties properties of metrics associated with Resource Manager applications and
published applications. When creating or editing Resource Manager
applications, the servers to which the administrator can assign the application
are controlled by the “Assign RM Applications to Servers” permission for the
server folder. Automatically selects and requires the View permission.
Receive SMS and Email If an application metric is configured to send out SMS or email notifications, this
Notifications permission allows administrators to receive SMS or email notifications related
to applications, using the contact information specified in the “Alert Contact
Details” section of their profile. Automatically selects and requires the View
permission.
Note: Administrators can be given permission to receive other types of SMS
and email notifications in the Resource-Related tasks or Server-Based tasks.
164 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
Tasks Description
View RM Applications and Allows administrators to view any Resource Manager applications, as well as
Content any metrics associated with the application. Administrators can also select the
metric and generate a real-time graph that displays the current metric count
and the metric error and warning thresholds.
If administrators also have the “View Published Applications and Content” or
“View Session Management” permissions for the same folder, they can view
metrics associated with published applications in the specified folder and
generate real-time graphs for these metrics.
The RM watcher is available to display application-related Resource Manager
alerts.
Note: Administrators can be given permission to view resource-related
Resource Manager alerts using “View Resource Management Configuration
and Alerts” and server-related Resource Manager alerts using “View RM
Information and Alerts.”
Sessions Toggles on/off all subtasks. Allows full access to view and modify all areas of
session management for the specified folder. To disable subtasks, clear the
check boxes.
Connect Sessions Allows administrators to connect to a session. Automatically selects and
requires the View permission.
Disconnect Users Allows administrators to disconnect one or more sessions. Automatically
selects and requires the View permission.
Log Off Users Allows administrators to log off one or more sessions. Automatically selects
and requires the View permission.
Reset Sessions Allows administrators to reset client and disconnected sessions. Automatically
selects and requires the View permission.
Send Messages Allows administrators to send desktop messages to one or more sessions.
Automatically selects and requires the View permission.
View Session Management Allows view-only access to sessions management.
ADMINISTRATOR-RELATED TASKS
MetaFrame Administrators Toggles on/off all subtasks. Allows administrators to open the MetaFrame
Presentation Server Console and Web Interface Console and to view the
properties of other administrators. To disable subtasks, clear the check boxes.
Log on to Presentation Server Allows administrators to open the MetaFrame Presentation Server Console.
Console
Log on to Web Interface Console Allows administrators to open the Web Interface Console.
View MetaFrame Administrators Allows administrators to view the properties of other administrators.
INSTALLATION-RELATED TASKS
Go to Document Center Chapter 7 Securing Your Farms 165
Tasks Description
Installation Manager Toggles on/off all subtasks. Allows full access to view and modify all areas of
installation management. To disable subtasks, clear the check boxes.
Edit Installation Manager Allows administrators to edit and/or install/uninstall packages, package groups,
server groups, and Installation Manager properties. Automatically selects and
requires the View permission.
View Installation Manager Allows view-only access to the Installation Manager node in the Presentation
Server Console, the Installation Manager properties, all of the available
packages and package groups, package and package group properties, and
installation information.
Administrators can view a server group only if they have the “Install and
Uninstall Packages” server folder permission for at least one server in the
group, and they can view only the individual servers in the group for which they
have this permission.
ISOLATION ENVIRONMENT TASKS
Isolation Environments Toggles on/off all subtasks. Allows full access to view and modify all areas of
isolation environments. To disable subtasks, clear the check boxes.
Manage Isolation Environments Allows administrators to create and modify isolation environments, as well as
publish applications in an isolation environment. To publish applications in an
isolation environment, administrators also need the “Publish Applications and
Edit Properties” permission. Automatically selects and requires the View
permission.
View Isolation Environments Allows view-only access to isolation environments and the applications
published in them.
LOAD MANAGER TASKS
Load Manager Toggles on/off all subtasks. Allows full access to view and modify all areas of
load management. To disable subtasks, clear the check boxes.
Assign Load Evaluators Allows administrators to assign load evaluators to servers and published
applications.
Edit Load Evaluators Allows administrators to edit load evaluation settings. Automatically selects and
requires the View permission.
View Load Evaluators Allows view-only access to load evaluator settings.
MONITORING AND ALERTING TASKS
The following tasks are related to the My Knowledge extension - Configuration and Alerts.
Monitoring and Alerting Toggles on/off all subtasks. Allows full access to view and modify all areas of
monitoring and alerting. To disable subtasks, clear the check boxes.
166 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
Tasks Description
Edit Alerts Configuration Allows administrators to modify the current configuration of alerts generated by
the My Knowledge extension (SMA alerts). This information includes
thresholds, polling intervals, and whether the alert is enabled or disabled.
Automatically selects and requires the “View Alerts Configuration” permission.
To apply the configuration of all the My Knowledge extension alerts of the
currently selected farm (the source farm) to other discovered farms that have
SMA enabled (the target farms), administrators must have the “View Alerts
Configuration” permission for the source farm and “Edit Alerts Configuration”
permission for the target farms.”
Edit My Knowledge Configuration Allows administrators to create a new configuration and edit or delete the
current company knowledge configuration for the farm. Automatically selects
and requires the “View My Knowledge Configuration” permission.
To copy the company knowledge database configuration from another
discovered farm that has its company knowledge database configured (the
source farm) to the currently selected farm, the administrator must also have
the “View My Knowledge Configuration” permission in the source farm.
View Alerts Configuration Allows view-only access to the current configuration of the current configuration
of alerts generated by the My Knowledge extension. This information includes
thresholds, polling intervals, and whether the alert is enabled or disabled.
View My Knowledge Allows view-only access to the current company knowledge configuration of
Configuration alerts generated by the My Knowledge extension.
POLICY-RELATED TASKS
User Policies Toggles on/off all subtasks. Allows full access to view and modify all areas of
user policies. To disable subtasks, clear the check boxes.
Edit User Policies Allows administrators to create and modify policies. Automatically selects and
requires the View permission.
View User Policies Allows view-only access to policies.
PRINTER-RELATED TASKS
Printers Toggles on/off all subtasks. Allows full access to view and modify all areas of
printer management. To disable subtasks, clear the check boxes.
Edit All Other Printer Settings Allows administrators to import network print servers, map drivers, and edit all
other printer settings, with the exception of editing printer drivers, editing
printers, and replicating printer drivers. Automatically selects and requires the
View permission.
Edit Printer Drivers Allows administrators to edit driver-related features. Automatically selects and
requires the View permission.
Edit Printers Allows administrators to add, edit, delete, or reset client printers. Automatically
selects and requires the View permission.
Go to Document Center Chapter 7 Securing Your Farms 167
Tasks Description
Replicate Printer Drivers Allows administrators to replicate printer drivers from one server to another and
to manage the auto-replication list. Automatically selects and requires the View
permission.
View Printers and Printer Drivers Allows view-only access to printers and printer drivers.
RESOURCE-RELATED TASKS
Resource Management Toggles on/off all subtasks. Allows full access to view and modify all areas of
managing resources for the farm. To disable subtasks, clear the check boxes.
Configure Resource Management Allows administrators to edit the configuration of all the areas described in the
“View Resource Management Configuration” permission. Automatically selects
and requires the View permission.
Generate Billing Reports Allows administrators to generate billing reports, manage cost centers, manage
fee profiles, and view saved reports. Saved reports can also be viewed using
any Web browser. Automatically selects and requires the View permission.
Generate Current and Summary Allows administrators to generate current and summary reports and view any
Reports saved reports. Saved reports can also be viewed using any Web browser.
Automatically selects and requires the View permission.
Receive SMS and Email If the Summary Database is configured to send out SMS or email notifications,
Notifications this permission allows administrators to receive the SMS or email notification
related to resource management tasks (those not related to applications or
servers), using the contact information specified in the “Alert Contact Details”
section of their profile. Automatically selects and requires the View permission.
Note: Administrators can be given permission to receive other types of SMS
and email notifications in the Application-Related tasks or Server-Based tasks.
View Resource Management Allows administrators to view the Resource Manager node in the MetaFrame
Configuration and Alerts Presentation Server Console, including the current configuration of the
following areas of Resource Manager:
- Summary Database configuration
- SMS servers, gateways, and the receivers of SMS alerts
- Community string used for sending SNMP alerts
- Configuration of the currently selected method for sending email alerts (SMTP
or MAPI), and the receivers of email alerts
- Primary and backup farm metric servers
The RM watcher is available to display any current Resource Manager alerts,
other than alerts related to applications or servers.
Note: Administrators can be given permission to view application-related
Resource Manager alerts using “View RM Applications and Content” and
server-related Resource Manager alerts using “View RM Information and
Alerts.”
SERVER-BASED TASKS
If you select a folder of servers, the assigned permissions affect only the servers in the specified folder.
168 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
Tasks Description
Installation Manager Toggles on/off all subtasks. Allows full access to install and uninstall packages
on servers in the specified folder. To disable subtasks, clear the check boxes.
Install and Uninstall Packages Allows administrators to install and uninstall packages on all the servers in the
specified folder. This permission also controls which servers and server groups
administrators can view in the “Server Groups” section of the Installation
Manager node for the farm. Administrators can view a server group only if they
have the “Install and Uninstall Packages” server folder permission for at least
one server in the group, and they can view only the individual servers for which
they have this permission.
Published Applications Allows full permissions for administering published applications on servers in
the specified folder. To disable subtasks, clear the check boxes.
Assign Applications to Server Allows administrators to publish applications from servers. To publish
applications from a server, administrators must also have the “Publish
Applications and Edit Properties” permission.
Resource Manager Toggles on/off all subtasks. Allows full access to Resource Manager for servers
in the specified folder. To disable subtasks, clear the check boxes.
Assign RM Applications to Allows administrators to assign the servers on which a Resource Manager
Servers application can be monitored. Servers for which administrators do not have this
permission will not be visible when the administrators assign servers to a
Resource Manager application.
Note: This permission does not have any effect on the servers that can be
assigned to published applications.
Edit RM Information Allows administrators to add, remove, snooze, sleep, awaken, and edit the
properties of metrics associated with servers. Administrators can also modify
the configuration of the following sections in the server properties:
- Ignored processes
- Metric summary schedule
- Restart schedule
- Resource Manager alert recipients
Automatically selects and requires the View permission.
Receive SMS and Email If a server metric is configured to send out SMS or email notifications, this
Notifications permission allows administrators to receive SMS or email notifications related
to servers, using the contact information specified in the “Alert Contact Details”
section of their profile. Automatically selects and requires the View permission.
Note: Administrators can be given permission to receive other types of SMS
and email notifications in the Resource-Related tasks or Application-Related
tasks.
Go to Document Center Chapter 7 Securing Your Farms 169
Tasks Description
View RM Information and Alerts Allows the administrators to view any metrics that have been added to the
servers in the specified folder. Administrators can also select a metric and
generate a real-time graph that displays the current metric count and the metric
error and warning thresholds. If administrators also have the “Generate Current
and Summary Reports” permission, they can generate reports directly from the
graph.
Administrators can view the Resource Manager server log and view the current
configuration of the following sections in the server properties dialog:
- Ignored processes
- Metric summary schedule
- Restart schedule
- Resource Manager alert recipients
The RM watcher is available to display server-related Resource Manager
alerts.
Note: Administrators can be given permission to view application-related
Resource Manager alerts using “View RM Applications and Content” and
resource-related Resource Manager alerts using “View Resource Management
Configuration and Alerts.”
Servers Toggles on/off all subtasks. Allows full access to view and modify all areas of
server administration in the specified folder. To disable subtasks, clear the
check boxes.
Edit License Server Settings Allows administrators to edit settings for the license server.
Edit Other Server Settings Allows administrators to edit all server settings, with the exception of SNMP
settings, moving and removing servers, terminating processes, and license
server settings.
Edit SNMP Settings Allows administrators to set up notifications of events by the SNMP agent.
Move and Remove Servers Allows administrators to move servers between server folders and remove
servers from the farm.
Terminate Processes Allows administrators to terminate processes.
View Server Information Allows view-only access to server information.
Sessions Toggles on/off all subtasks. Allows full access to view and modify all areas of
session administration. To disable subtasks, clear the check boxes.
Connect Sessions Allows administrators to connect to user sessions. Automatically selects and
requires the View permission.
Disconnect Users Allows administrators to disconnect user sessions. Automatically selects and
requires the View permission.
Logoff Users Allows administrators to log off users. Automatically selects and requires the
View permission.
170 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
Tasks Description
Reset Sessions Allows administrators to reset user sessions. Automatically selects and
requires the View permission.
Send Messages Allows administrators to send messages to users, such as broadcasting
information about an upgrade or a warning about a system shutdown.
Automatically selects and requires the View permission.
View Session Management Allows view-only access to session management.
Note To apply the same permissions to a new folder as to its parent folder, select
the Copy permissions from the parent folder option when you create the new
folder.
To create, delete, and configure MetaFrame administrator accounts, you must log
on to the Presentation Server Console as a full authority administrator.
ICA encryption (SecureICA). Use ICA encryption (Citrix SecureICA) to encrypt the
information sent between a server running MetaFrame Presentation Server and a
client. ICA encryption makes it virtually impossible for unauthorized users to open
an encrypted transmission and, in the unlikely event that such an attack succeeds,
ICA encryption ensures that the attacker sees only meaningless screen commands
and not sensitive information. ICA encryption provides confidentiality to guard
against the threat of eavesdropping.
Note ICA encryption is not recommended for use across public networks.
Citrix SSL Relay. Use Citrix SSL Relay to provide end-to-end Secure Sockets
Layer/Transport Layer Security (SSL/TLS) encryption between specific servers and
clients.
In general, you use SSL Relay when:
• You have a small number of servers to support (five or fewer)
• You do not need to secure access at a DMZ
• You do not need to hide server IP addresses or you are using Network Address
Translation (NAT)
• You do need end-to-end encryption of data between clients and servers
The Secure Gateway. Use the Secure Gateway to provide SSL/TLS encryption
between a secure Internet gateway server and an SSL-enabled client, combined
with encryption of the HTTP communication between the Web browser and the
Web server. Using the Secure Gateway makes firewall traversal easier and provides
heightened security by providing a single point of entry and secure access to your
server farms.
In general, you use the Secure Gateway when:
• You have a large number of servers to support
• You want to hide internal IP addresses
• You want to secure access from the DMZ
Go to Document Center Chapter 7 Securing Your Farms 173
• You need two-factor authentication (in conjunction with the Web Interface)
A Virtual Private Network Solution. Use a Virtual Private Network (VPN) solution
when you need to create secure tunnels between geographic locations.
In general, you use a VPN solution when:
• You need two-factor authentication
• You need to create a secure pipeline for full (beyond ICA) network access
• You want to secure the network from within the DMZ
• Users normally access the network from the same workstations
• You want to use IP Security (IPSEC)
Both the Secure Gateway and SSL Relay support SSL/TLS encryption. Selection is
largely a matter of deciding which deployment best meets the needs of the
organization’s security policies. Each approach has its own advantages.
Overviews of the SSL Relay, the Secure Gateway, and ICA encryption are included
in this chapter.
174 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
Requesting a Certificate
After you decide on your Certificate Authority, you generate a request for a
certificate using your Web server software. This generates information known as a
certificate signing request (CSR) that you send to the Certificate Authority for
signing.
Go to Document Center Chapter 7 Securing Your Farms 177
You submit the CSR to the Certificate Authority and receive your signed SSL
certificate and password in return. If your organization is a Certificate Authority,
you should have your own procedures for supplying signed certificates.
Important The common name for the certificate must be the fully qualified
domain name of the server.
You can use the Microsoft Web Server Certificate wizard in the IIS snap-in to
request and import a certificate. You can use the wizard to request a certificate if
you are using an external CA, or request and also install the certificate if you are
using the wizard and an online CA; for example, you have Microsoft Enterprise
Certificate Services set up.
To change the SSL port for Internet Information Services Version 5.0
1. Click Start > Programs > Administrative Tools > Internet Services
Manager.
2. In the Internet Information Services Console tree, select Default Web Site and
choose Properties from the Action menu. The Default Web Site Properties
dialog box appears.
3. From the Directory Security tab, click Server Certificate. The Welcome to the
Web Server Certificate wizard appears. Follow the instructions in the wizard to
create or import a certificate.
4. When your server certificate is installed, select the Web Site tab in the Default
Web Site Properties dialog box.
5. Change the SSL port number to something other than 443.
6. Click OK to close the Default Web Site Properties dialog box.
2. On the Connection tab, type the new port number in the Relay Listening Port
box.
3. Click OK.
See the Web Interface Administrator’s Guide for the procedure to reconfigure
servers running the Web Interface with the new port number.
Note When you install MetaFrame Presentation Server, members of the User
group are allowed to edit registry entries in the registry hive
HKEY_LOCAL_MACHINE\SOFTWARE\Secure\Citrix\Citrix SSL Relay.
You can use the Microsoft Security Configuration and Analysis tool to prevent
members of the User group from editing these registry entries.
Important If you change the default Citrix SSL Relay port, you must set
SSLProxyHost to the new port number in the MetaFrame Presentation Server
Client for Win32 Appsrv.ini file. For more information about client settings, see the
Client for 32-bit Windows Administrator’s Guide.
CAUTION Using Registry Editor incorrectly can cause serious problems that can
require you to reinstall the operating system. Citrix cannot guarantee that problems
resulting from incorrect use of Registry Editor can be solved. Use Registry Editor at
your own risk. Make sure you back up the registry before you edit it.
To disable Kerberos logon to a particular server, set the following registry key on
the server:
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\Logon\DisableSSPI = 1
You can configure the Client for 32-bit Windows to use Kerberos with or without
pass-through authentication. For more information about client configuration, see
the Client for 32-bit Windows Administrator’s Guide.
Important If you are securing communications between the Secure Gateway and
the STA, ensure you install a server certificate on the server running the STA.
5. Select the performance counters you want to monitor and click Add.
6. Click Close.
7. Use the Windows Performance Console controls that appear at the top of the
right pane to switch views, add counters, and so on.
Warning Messages
These messages are logged as a result of events caused by corrupted data requests
or data packets received, ticket time-outs, and so on. In general, these errors are
likely to occur when the data request originates from an unknown source:
Error Number Error Message Description
CSG1201 Request Data - Parsing failed, bad XML. Data request packet contains corrupt XML data and
cannot be parsed.
CSG1202 Request Data - No ticket or wrong ticket The request is not in the right format for the STA to
version in XML. resolve the ticket to its associated data. The request is
rejected.
CSG1203 Request Data - Ticket not found. The ticket requested is not found. This can occur if the
ticket times out.
CSG1204 Request Ticket - Parsing failed, bad XML. The ticket request failed because the STA encountered
unknown XML data. The ticket cannot be parsed.
CSG1205 Request Ticket - No data or wrong type in Data request packet received contains no data or
XML. incorrect XML data. Ticketing failed.
CSG1206 Request Ticket - No memory to save data. The system is low on memory and cannot save the ticket
request.
CSG1207 Request Ticket - Maximum reached, data The maximum active ticket limit is reached. Ticketing
NOT saved. failed. Increase the maximum ticket limit or reduce the
ticket lifetime.
Go to Document Center Chapter 7 Securing Your Farms 185
CSG1208 Request Ticket - Failed, data NOT saved. A system error occurred when trying to save this ticket.
CSG1209 Unused tickets still in IMDB at unload. The STA terminated abruptly. Unused tickets are still
present in the In-Memory Database (IMDB).
Status Messages
These status messages are logged as a result of normal STA operations.
Error Number Error Message Description
CSG1301 CtxSTA.dll Loaded. The STA is started.
CSG1302 CtxSTA.dll Unloaded. The STA is unloaded (stopped).
CSG1303 Ticket Timed Out. This ticket reached the maximum ticket lifetime and has
now expired.
CSG1304 Request Data - Successful. This ticket data request is successful.
CSG1305 Request Ticket - Successful. This ticket request is successful.
CSG1306 Log file index reset to 000 (from 999). 1000 log files were generated in a 24-hour period. The
STA now reuses the oldest log file, STAyyyymmdd-
000.log.
186 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
Go to Document Center
CHAPTER 8
Transport types. Terminal Services in Windows Server 2003 supports only the
TCP/IP protocol. Windows 2000 servers support TCP/IP, IPX, SPX, NetBIOS, and
asynchronous (modem or direct cable) connections.
Supported hardware. Network interface cards (NIC), serial ports, and modems.
This screen capture shows the New Connection dialog box with network transport
configuration options.
190 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
3. Type a name for the connection in the Name box. You can enter an optional
description in the Comment box.
4. From the Type list, select Citrix ICA 3.0.
5. From the Transport list, select the transport protocol.
6. Click OK to add the ICA connection. If a connection with these settings exists,
a message tells you that a connection cannot be created with the same settings.
This screen capture shows the New Connection dialog box with asynchronous
transport configuration options.
3. Type a name for the new connection.
4. From the Type list, select Citrix ICA 3.0.
5. From the Transport list, select async. Options for asynchronous connections
appear in the dialog box.
6. From the Device list, select the COM port for the connection. Standard COM
ports appear in the list. If a TAPI modem is installed on a COM port, the modem
type follows the COM port name in the list. If a modem is installed on a
particular COM port, you cannot select that COM port for a direct cable (null
modem).
• To install a modem, click Install Modem. Then, follow the instructions in
the Install New Modem wizard to install and configure the modem.
• To configure an existing modem, click Modem Properties.
7. Click OK to add the connection. If a connection with these settings exists, a
message tells you that a connection cannot be created with the same settings.
Per-connection settings. You can use the Citrix Connection Configuration utility to
configure settings for each ICA connection. These settings are referred to as per-
connection settings because they affect all ICA sessions that users establish through
the ICA connection.
192 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
You can click Advanced, ICA Settings, and Client Settings in the New
Connection or Edit Connection dialog box to configure per-connection settings.
For example, for a particular ICA connection, you can set a time-out value in the
Advanced Connection Settings dialog box. This time-out setting affects the
sessions of all users who link to the server through that ICA connection.
Procedures for configuring per-connection settings appear later in this chapter.
Per-user settings. User and group settings that you configure in Windows apply to
any ICA connection. These settings, which are based on individual user accounts,
include user names and group memberships, permissions, and dial-in settings.
For more information about per-user settings, refer to your Windows
documentation. See the Windows online help for Local Users and Groups, or
Active Directory Users and Computers.
Precedence of Settings
A setting you specify in the Citrix Connection Configuration utility takes
precedence over per-user and per-client settings. However, for some ICA
connection settings, you can select an option to apply settings from user accounts or
clients to the ICA connection.
• You can specify that an ICA connection use some settings from user accounts
by selecting Inherit User Config.
• You can specify that an ICA connection use some settings from MetaFrame
Presentation Server Clients by selecting Inherit Client Config.
If you select one of these check boxes, the associated ICA connection settings are
dimmed and cannot be edited. The setting specified by the Windows user account
or client takes precedence over the ICA connection setting.
If you clear the check box for these options, the original ICA connection settings
take effect.
Go to Document Center Chapter 8 Configuring ICA Connections 193
Important You can create policies to enable some connection settings for specific
users, clients, or servers. Policies override similar connection settings configured in
the Citrix Connection Configuration utility. However, if you disable functionality in
the Citrix Connection Configuration utility, you cannot enable the functionality by
creating policies. For more information about policies, see “Creating and Applying
Policies” on page 289.
This screen capture shows modem callback options from the Edit Connection dialog
box.
• Select the Inherit User Config check box to enable modem callback only for
users who have modem callback enabled in their Windows user accounts. When
this option is selected, the drop-down list is not available.
• From the drop-down list, choose To a fixed phone number or To a roving
phone number to enable modem callback for all users.
• Choose Disabled from the drop-down list to disable modem callback for all
users.
When you enable modem callback, you can specify one callback phone number for
all users. You might do this if all users dial in from one phone number at a branch
office, or you can use callback numbers from each user’s Windows account.
Another option is to let users enter callback numbers when they make connections.
This screen capture shows asynchronous transport configuration options from the New
Connection and Edit Connection dialog boxes.
With these options you can configure the following device and transmission
properties for the ICA connection:
196 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
Device. Specifies the serial port (COM port) to use for the connection. The
available COM ports on the server appear in the drop-down list.
Device Connect On. Specifies the signal type (CTS, DSR, RI, DCD, or First
Character) for the server to use to determine when a connection is established and
ready for user logon. You can select Always Connected to bypass connection
detection.
Baud. Sets the communication rate for the connection. You can select standard
baud rates from the drop-down list.
Set Defaults. Resets to default values the Device Connect On and Baud settings and
the settings in the Advanced Async Configuration dialog box.
Advanced. Opens the Advanced Async Configuration dialog box for configuring
additional serial port settings. These settings are described in the next section.
This screen capture shows the Async Test dialog box displaying received data.
The dialog box displays the name of the serial port and baud rate. A row of
indicator “lights” shows the status of the DTR, RTS, CTS, DSR, DCD, and RI
signals.
You can type text in the scrolling area to send ASCII data to a device that is
connected to the specified serial port. The text you type does not appear in the
dialog box unless a connected device echoes text that it receives.
If you transmit text from a terminal emulation program (such as HyperTerminal in
Windows) that is running on a connected client device, the text appears in the
Async Test dialog box if the connection is configured correctly.
Hardware Flow Control. If you select Hardware in the Flow Control area, the
options in the Hardware Flow Control area are available to specify signals used for
flow control. Hardware flow control is the default configuration.
198 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
From the first drop-down menu, select the hardware signal action that indicates the
receive buffer is full. From the second menu, select the hardware signal action that
indicates data transmission can proceed. The default settings are Turn off RTS
when receive buffer is full and Transmit data when CTS is on.
This screen capture shows the Advanced Async Configuration dialog box with the flow
control option Hardware (RTS/CTS) selected. Options available are hardware flow
control, DTR state, parity, and stop.
Software Flow Control. If you select Software in the Flow Control area, the options
in the Software Flow Control area are available to specify the start and stop
characters for data transmission.
Select Decimal or Hex to define character values, and then type decimal or hex
values in the text boxes to set the Xon and Xoff characters for software flow
control.
This screen capture shows the Advanced Async Configuration dialog box with the flow
control option Software (Xon/Xoff) selected. Options available are software flow control,
DTR state, RTS state, parity, and stop.
Go to Document Center Chapter 8 Configuring ICA Connections 199
DTR State. The DTR State options are available with any flow control option
unless you select Turn Off DTR for Hardware Flow Control.
Select On to specify that the Data Terminal Ready (DTR) signal is always on.
Select Off to specify that the signal is always off.
RTS State. These options are available with any flow control option unless you
select Turn Off RTS for Hardware Flow Control.
Select On to specify that the Request To Send (RTS) signal is always on. Select Off
to specify that the signal is always off.
Parity. Click an option to specify the parity type or click None to specify no parity
setting.
Byte. This setting for the configuration of transmitted data cannot be changed
because ICA protocol requires 8 bits per byte.
This screen capture shows the Advanced Connection Settings dialog box with options
for logon, time out, security, auto-logon, initialization, user profile overrides, and other
connection settings.
Term Meaning
Enabled Shadowing is possible for sessions on the ICA connection.
Disabled Sessions on the ICA connection cannot be shadowed.
Input Refers to using the keyboard and mouse for remote control of the
shadowed session.
On means that the input from the mouse and keyboard are accepted
for remote control from the device shadowing the session. Off means
that this input is not accepted.
Notify Refers to a notification message that MetaFrame Presentation Server
sends to a client user. The message asks the user to allow someone
to shadow the session. Users can accept or deny shadowing requests.
On means the server notifies users of all attempts to shadow
sessions. Off means the server does not notify users, so they cannot
deny permission or prevent shadowing.
Go to Document Center Chapter 8 Configuring ICA Connections 203
For example, one option in the Shadowing menu states: “is enabled, input off,
notify on.” This setting does the following: allows shadowing, prohibits remote
control with the keyboard and mouse during shadowing, and requires the
notification (and permission) of client users before anyone can shadow their
sessions.
Note If you disable input for remote control or user notification when you install
MetaFrame Presentation Server, options for these features are not available in the
Shadowing menu in the Citrix Connection Configuration utility. However, the
options still appear in Microsoft’s user properties dialog box, but choosing them
does not override the settings you select during MetaFrame Presentation Server
installation. In general, you can use individual client properties to disable
shadowing features on a per-user basis, but not to enable shadowing features that
you disable on a server.
Configuring Audio
MetaFrame Presentation Server offers you a variety of tools to manage and control
the availability of sound in client sessions, both in terms of quality and cost in
resources, including:
• Audio properties you configure for individual published applications
• Audio related policies and settings you configure for specific connection types
• Audio settings the user configures on the client device
For example, you can use audio related connection polices to control bandwidth
usage and server CPU utilization. You can configure a policy rule to enable audio
for connections where audio is essential, and configure another rule to disable audio
for connections where it is not essential.
From the Presentation Server Console, you control the availability of speakers and
microphones in client sessions with separate policy rules. On the client device, a
single setting controls both. To enable audio on the client device, the user selects an
audio quality level from the Settings dialog box (for Program Neighborhood) or
from the Properties dialog box (for Program Neighborhood Agent). The
connection policies you configure on the server determine what audio quality levels
are available to the user. Connection policies permitting, enabling audio on the
client device turns on speakers, microphones, or both.
204 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
Important This section covers aspects of enabling audio support on servers. To use
audio in client sessions, users must also enable audio on the client device. For more
information about enabling audio for clients, see the Administrator’s Guides for the
clients you want to configure.
You control the availability and quality of audio in client sessions by performing the
following two steps:
Note In earlier releases of MetaFrame, this option was called Enable audio.
Note The availability and quality of audio in client sessions is determined both by
Terminal Services Configuration settings and by policies you configure through the
Presentation Server Console. By default, Terminal Services settings are configured,
whereas Presentation Server policies are not. This means that Terminal Services
settings apply by default, making medium quality audio available in client sessions
until you configure Presentation Server policies that override the Terminal Services
settings. If configured, Presentation Server policies override Terminal Services
settings.
Low sound quality; best performance. This setting is recommended for low-
bandwidth connections. This setting causes any sounds sent to the client to be
compressed to a maximum of 16Kbps. This compression results in a significant
decrease in the quality of the sound. The CPU requirements and benefits of this
setting are similar to those of the Medium setting; however, the lower data rate
allows reasonable performance for a low-bandwidth connection.
Medium sound quality; good performance. This setting is recommended for most
LAN-based connections. This setting causes any sounds sent to the client to be
compressed to a maximum of 64Kbps. This compression results in a moderate
decrease in the quality of the sound played on the client device.
By default, when you enable this rule, the medium sound quality level is selected.
By default, when you configure this rule, audio input is enabled on client devices.
Users can override the policy and disable their microphones by selecting No in the
Client Audio Security dialog box.
Users of Program Neighborhood and Program Neighborhood Agent access this
dialog box from the Program Neighborhood Connection Center (for seamless
connections), or from either the Program Neighborhood Connection Center or the
client’s system menu (for non-seamless connections). Users of other MetaFrame
Presentation Server Clients are automatically presented with the same dialog box at
the beginning of their sessions.
SpeedScreen Latency Reduction Manager. Provides mouse click feedback and local
text echo, both of which reduce a user’s perception of latency when typing and
clicking.
SpeedScreen Multimedia Acceleration. Allows you to control and optimize the way
MetaFrame Presentation Server passes streaming audio and video to users.
SpeedScreen Flash Acceleration. Allows you to control and optimize the way
MetaFrame Presentation Server passes Macromedia Flash animations to users.
Mouse Click Feedback. Mouse click feedback, which is enabled by default, changes
the appearance of the pointer from idle to busy after the user clicks a link, indicating
that the system is processing the user’s request.
Local Text Echo. When a user types text, the keystrokes are sent to the server,
which renders the fonts and then returns the updated screen redraw to the client.
You can bridge the delay between keystroke and screen redraw by enabling local
text echo. Local text echo temporarily utilizes client fonts to immediately display
text a user types while the screen redraw from the server is in transit.
Go to Document Center Chapter 8 Configuring ICA Connections 209
By default, Mouse Click Feedback is enabled and Local Text Echo is not enabled.
You can enable and disable Mouse Click Feedback at the server level and Local
Text Echo both at the server and application level. You can also configure Local
Text Echo settings for individual input fields within an application. See the
application help for SpeedScreen Latency Reduction Manager for more
information.
Note Applications that use non-standard Windows APIs for displaying text may
not support Local Text Echo.
To launch SpeedScreen Latency Reduction Manager, click its button on the ICA
Administrator Toolbar or select SpeedScreen Latency Reduction Manager from
the Citrix program group in the Start menu.
Important Test all aspects of an application with Local Text Echo in a non-
production environment before enabling text echo for your users.
To further accelerate the accessibility of Web pages and email, you can enable
JPEG compression with SpeedScreen Browser Acceleration. JPEG compression
offers you a trade-off between the quality of JPEG files as they appear on client
devices and the amount of bandwidth the files consume on their way from server to
client. JPEG compression results in slightly lower image resolution and slightly
higher resource consumption on both server and client. It does not affect JPEG files
rendered by applications other than those mentioned above. For information about
improving the throughput of image files rendered by other applications, see
“Optimizing Throughput of Image Files” on page 212.
SpeedScreen Browser Acceleration requires Version 7.0 or later of the MetaFrame
Presentation Server Clients for Win32, Internet Explorer 5.5 or later, and High
Color (16 bit) or greater connection color depth.
By default, SpeedScreen Browser Acceleration is enabled at the server farm level.
You can customize the settings for this feature at the farm level and for individual
servers. To do this, select the corresponding farm or server Properties page in the
Presentation Server Console and modify the SpeedScreen Browser Acceleration
settings as appropriate.
Note There is a slight delay between the time a user logs on to a session and the
time policy rules, if configured, take effect. For the time immediately following a
user’s logon and before policy rules take effect, SpeedScreen Image Acceleration
defaults to low image compression. This behavior improves session performance
by slightly accelerating image throughput while decreasing image quality only
marginally.
Then, if a policy rule is configured for the user’s connection type, the policy rule
takes effect, overriding the default setting. If no policy rule is configured,
SpeedScreen Image Acceleration applies image compression as follows: Medium
compression for WAN and lower bandwidth connections, no compression for LAN
connections. Medium compression amounts to slightly better session performance
due to slightly lower image quality. Use policy rules to override the default
behavior as appropriate.
Default to main client printer. If this option is checked, the user’s default client
printer is configured as the default printer for the client session.
Inherit user config. If this option is selected, the per-user settings in User Manager
are used.
To automatically connect to only the printer configured as the default printer when
the user logs on, select the By default, connect only the client’s main printer
check box.
Default printers can be set on the client device. Users can override the default
printer mapping with ICA Client Printer Configuration. For more information about
ICA Client Printer Configuration, see the Administrator’s Guides for the clients you
plan to deploy.
Click Client Mapping Overrides to disable client device connections.
However, the same drive letters are often in use by the drives on the server. In this
case, client drives are mapped to different drive letters. The server starts at V and
searches in ascending order for unassigned drive letters.
You can turn off client drive mapping through policies you configure in MetaFrame
Presentation Server. You can turn off mapping to client floppy disk drives, hard
drives, CD-ROM drives, or remote drives. For more information about configuring
policies, see “Creating and Applying Policies” on page 289.
CAUTION Using Registry Editor incorrectly can cause serious problems that can
require you to reinstall the operating system. Citrix cannot guarantee that problems
resulting from incorrect use of Registry Editor can be solved. Use Registry Editor at
your own risk. Make sure you back up the registry before you edit it.
REG_SZ: InitialClientDrive. Defines the first drive letter to use for client drive
mapping. The system searches backward through the alphabet to assign drive letters
to client drives that could not be mapped to their “native” drive letters.
REG_SZ: InitialNetWareDrive. Defines the drive letter to use for the NetWare
SYS:LOGIN directory that is mapped to the preferred server during the initial
NetWare attachment. This setting is the equivalent of the DOS VLM Net.cfg setting
“First Network Drive.” If this value is not set, the first available drive letter starting
with C and ending with Z is used for this mapping.
For more information about client COM port mapping, see the Administrator’s
Guides for the clients you plan to deploy.
CAUTION Using Registry Editor incorrectly can cause serious problems that can
require you to reinstall the operating system. Citrix cannot guarantee that problems
resulting from incorrect use of Registry Editor can be solved. Use Registry Editor at
your own risk. Make sure you back up the registry before you edit it.
You can turn off client drive mapping through policies you configure in MetaFrame
Presentation Server. MetaFrame Presentation Server now fully applies client drive
access restrictions that you specify in policy rules that turn off mapping to client
drives. Releases earlier than MetaFrame Presentation Server 3.0 allowed
applications to access a restricted client drive through a UNC path even when a
policy rule turned off mapping to the client drive. Now, applications cannot access
client drives restricted through policy rules that turn off mapping to the client drive.
Go to Document Center
CHAPTER 9
This chapter addresses issues to help you plan and implement your deployment of
MetaFrame Presentation Server Client software to users.
Tip If you are updating the MetaFrame Presentation Server Clients, use the Client
Update Database to deploy the latest versions of the client software.
If you are a system administrator for a small company with users in one physical
location, installing the client software from floppy disks or from a network file
server presents few problems.
You can eliminate user involvement in the installation process by installing the
client software on each user’s machine using a set of floppy disks or the MetaFrame
Presentation Server Components CD. This method is useful if your users have
limited computer experience.
220 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
If your users have a moderate level of computer expertise, you can direct them to a
network share point containing the client software. You can send users an email
message that contains both a link to the installation files and instructions for
installing the software. Installation by users can eliminate the need for you to
manually install client software.
In a large enterprise or an application service provider (ASP) environment with
hundreds or thousands of users in multiple locations, manual installation methods
are not efficient. In these situations, Web delivery of client software or deploying
with Active Directory or Microsoft Systems Management Server are the best
choices.
The table below lists common computing environments and the appropriate
deployment methods to use in each scenario.
Important When you choose to install the Web Interface, a Web site is installed in
a Citrix folder under the Web document root of the server; for example,
c:\Inetpub\wwwroot\Citrix\MetaFrame.
This Web site contains logic that at runtime references the server’s document root
directory for the presence of client software. To use the client installation feature of
the Web Interface, copy the Icaweb folder on the MetaFrame Presentation Server
Components CD into the Citrix folder in the Web document folder; for example,
c:\Inetpub\wwwroot\Citrix\Icaweb.
You must copy the entire Icaweb folder to the Citrix folder to enable Web-based
Client installation from the Web Interface.
222 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
If you plan to use the Web Interface, see the Web Interface Administrator’s Guide
for more information. If you do not plan to use the Web Interface but want to deploy
client software over the Web, see “Deploying Client Software over the Web” on
page 229.
The clients you need to deploy. To determine which clients you need to deploy,
determine which client devices and operating systems you need to support.
A smaller organization with many similar client devices might need to deploy the
client on only one or two platforms. In this scenario, using installation diskettes or
copying the necessary files to a central network share point for download are the
most efficient deployment methods.
Heterogeneous computing environments and geographic separation of large
enterprises and ASPs can make it impossible to predetermine which client devices
need to be supported. In these scenarios, Web-based installation is the most efficient
deployment method.
Centralized control and configuration requirements. Determine what limits you need
to impose on users’ access to published applications. You can configure various
settings before you initially deploy the clients.
For information about preconfiguring clients, see the Administrator’s Guide for the
required client or the Support area of the Citrix Web site at http://support.citrix.com.
Note You cannot route remote desktop sessions through Secure Gateway.
See the following table for an overview of MetaFrame Presentation Server features
and their availability through remote desktop sessions.
MetaFrame Presentation Server Feature Availability for Users of the Remote Desktop
Connection ActiveX Control:
MetaFrame Presentation Server Feature Supported with Remote Desktop Connection Software
Content redirection from client to server no
Content redirection from server to client no
Digital Dictation Support no
Dynamic Session Reconfiguration yes
MetaFrame Presentation Server Client no
options (audio, encryption, printing
settings)
ICA Keep-Alive no
Improved User Logon partially*
Printer bandwidth no
Published application shortcuts on client no
desktop and Start menu
Session Reliability no
Go to Document Center Chapter 9 Deploying Client Software to Users 225
MetaFrame Presentation Server Feature Supported with Remote Desktop Connection Software
SpeedScreen Browser Acceleration no
SpeedScreen Flash Acceleration no
SpeedScreen Image Acceleration no
SpeedScreen Multimedia Acceleration no
SpeedScreen Latency Reduction Manager no
Workspace Control no
Zone Preference and Failover yes
Deploying Clients through the Web Interface. When a user logs on to the Web
Interface, a built-in client software installation feature checks the user’s device for
the presence of the Web Client and presents the client software for download if
necessary.
To use the built-in client installation feature, you must prepare the Web server’s
Web document root folder to contain the required client files.
Manufacturing Enterprise
The Best Paper Company employs approximately 30,000 people, located in shop-
floor sites and remote offices in several countries. The enterprise has many pockets
of MetaFrame Presentation Server installations, each owned and managed by a
different team. Published applications include PeopleSoft and Oracle
Manufacturing and Financials.
The networking environment includes the following:
• Ethernet LANs
• Frame Relay WAN
• Internet connections for remote users
• TCP/IP network protocol
• Thousands of 486 PCs running Windows 95
• Thousands of Pentium PCs running Windows 2000
The Best Paper Company is using the Web Interface for MetaFrame Presentation
Server to give users access to critical applications. The company’s existing farms
function as an application serving back-end. The server farm supplies application
set information and hosts published applications.
Application sets are delivered to groups or individual users, based on their role in
the company. A user launches a Web browser to connect to the logon page for the
Web Interface. When the user is authenticated to the server farm, the application set
assigned to the user is displayed within the browser. To start an application, the user
clicks a hyperlink on the Web Interface page.
The company uses the Web Interface’s built-in Web-based ICA Client Installation
feature to deploy the client software. When a user launches an application, the
user’s computer is checked for the presence of the client software. If the client is not
detected, the user’s platform is identified and the appropriate client software is
presented for download and setup.
The Web browser and the client software work together as viewer and engine. The
browser displays the user’s application sets and the client software launches
applications.
For more information about the Web Interface, see the Web Interface
Administrator’s Guide.
Go to Document Center Chapter 9 Deploying Client Software to Users 231
Insurance Company
Protection Insurance is a mid-sized company with 800 employees. Published
applications include PeopleSoft and customized applications for the insurance
industry from JDE and Prelude. The networking environment includes:
• Ethernet LAN, Internet, and dial-up connections
• TCP/IP network protocol
232 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
With MetaFrame Presentation Server, you can expand users’ access to information.
You make information available to users by publishing applications and files on
servers. You then decide whether users should open certain file types with these
published applications or with applications running locally on client devices.
You can publish the following types of resources:
• Applications installed on servers running MetaFrame Presentation Server.
When users access them, the published applications appear to be running locally
on client devices.
You can publish any application that can run on the Windows console (32-bit
Windows applications, 16-bit Windows applications, DOS applications, POSIX
applications, and OS/2 applications).
• The server’s desktop, so users can access all of the resources available on the
server.
• Data files such as Web pages, documents, sound files, spreadsheets, and URLs.
In MetaFrame Presentation Server, the combined total of data types you can
publish is referred to as content.
You can adjust server load calculations for individual servers with Load Manager.
For instructions about configuring load evaluators, see the Load Manager
Administrator’s Guide, available from the Document Center or the Documentation
folder on the product CD.
• Which users should access applications locally and which should access
applications published on servers?
To provide a smoother user experience, review your user base, client hardware,
and client operating systems to determine which users should open which types
of applications.
For example, you may publish a financial spreadsheet on a server for users in
your accounting department to access. For security reasons, you want these
users to open the published file with the associated application published on the
server. However, you also published an audio file of a keynote speech given by
the company president. To prevent the servers from becoming overloaded, you
want users to open this file with player applications on their local client devices.
Note For your users to access content published with a specified universal naming
convention (UNC) path and through the Web Interface, you must publish the
content with content redirection and redirect to a correctly published application.
User authentication. Instead of logging on to and logging off from multiple servers
to access applications, Program Neighborhood users can be authenticated once to
all servers in a server farm and get immediate access to all applications configured
for their user group or specific user names.
Publishing applications for the special Citrix Anonymous user group lets you
completely eliminate the need for user authentication for those applications you
want to provide to all users on your network. For more information, see
“Anonymous Users” on page 242.
Published applications are presented to users running the Win32 Program
Neighborhood Client as application sets. An application set is a user’s view of the
resources that the user is authorized to run.
Note Users running the Win32 Program Neighborhood Client open the Program
Neighborhood interface to connect to applications and content published in server
farms. The Program Neighborhood Client runs on Windows XP, Windows 2000,
Windows NT 4.0 Workstation, Windows 95, Windows 98, and Windows Me
platforms.
Publishing applications in your server farm benefits users of most clients. Although
the Clients for UNIX, Macintosh, DOS, and the Web Client do not support the
complete (server- and client-side) administrative configuration of the ICA
connection provided by Program Neighborhood, these clients do support
connections to published applications.
With the Clients for UNIX, Macintosh, and DOS, users benefit from application
publishing’s simplified addressing and desktop navigation when they configure
connections to published applications using their connection configuration
managers.
With the clients that work with Web browsers (which are available as an Internet
Explorer Active-X control, Netscape plug-in, or Java applet), you can create Web
access that lets users click a link in a Web page to start a published application. You
can use the Web Interface to achieve this.
Selected user access. You publish applications for specific users and user groups.
By definition, an application you publish for a specific user group is unavailable to
other groups.
Enabled and disabled applications. You can temporarily restrict all access to an
application by disabling it. You can enable the application later to return access to
users. This capability is useful when you want to take an application offline for
maintenance.
Note Load Manager is part of MetaFrame Presentation Server when you license
the Advanced or Enterprise Edition. Load Manager provides features for managing
server loads in server farms. For information about Load Manager, see the Load
Manager Administrator’s Guide, available from the Document Center or the
Documentation folder on the product CD.
Client users on UNIX, Macintosh, and DOS. Using connection managers, these users
can browse a list of all applications published on the network and select an
application to run.
240 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
Web access. Users who have the Win32 Web Client or the Client for Java can
access applications using their Web browsers. You can use the Web Interface to
present hyperlinks to published applications. When users click these links, the
published application or content is launched on the server.
The Client for Win32 Program Neighborhood Agent integrates hyperlinks to
published applications into the Windows desktop. You must use the Web Interface
to allow users to connect using the Program Neighborhood Agent. For more
information about using the Program Neighborhood Agent, the Client for Win32
Web Client, or the Program Neighborhood, see the Client for 32-bit Windows
Administrator’s Guide, available from the Document Center or the Documentation
folder on the product CD.
For information about configuring Web access with the Web Interface, see the Web
Interface Administrator’s Guide.
Publishing applications in server farms lets you set up two types of application
access: explicit user account access and anonymous access.
Note The total number of users, whether anonymous or explicit, who are logged
on to a server farm at the same time cannot exceed the total count of all the
connection licenses available from the license server.
Anonymous Users
During MetaFrame Presentation Server installation, Setup creates a special user
group named Anonymous. By default, this user group contains 15 user accounts
with account names in the form Anonx, where x is a three-digit number from 000 to
014. By default, anonymous users have guest permissions.
Explicit Users
An explicit user is any user who is not a member of the Anonymous group. Explicit
users have user accounts that you create, configure, and maintain with standard user
account management tools.
Explicit users who log on to a server farm to run applications have a persistent
existence: their desktop settings, security settings, and other information is retained
between client sessions in a specific user profile.
To publish an application
1. Open the Presentation Server Console.
2. Verify that the server you want to host the application is a member of the server
farm. You can find the intended host server or servers under the Servers node.
3. From the Actions menu, choose New > Published Application.
4. Follow the instructions in the Application Publishing wizard. Detailed help for
each step is available by clicking Help.
244 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
Tip If you want to publish an application on additional servers, you can drag the
application in the console tree and drop it on servers to publish the application on
the servers. The application must already be installed on the servers, and it inherits
its settings from the first server where you published the application.
Important If you install and then publish applications after installing MetaFrame
Presentation Server, you must update the file type associations in the server’s
Windows registry. For instructions for doing this, see “Updating File Type
Associations in the Server Farm” on page 247.
Go to Document Center Chapter 10 Publishing Applications, Content, and Desktops 245
When you associate published applications with file types and then assign the
applications to users, you automatically implement the following:
1. Users running the Program Neighborhood Agent open all files of the associated
type encountered in locally running applications with applications published on
the server.
For example, when users double-click email attachments encountered in an
application running locally, the attachment opens in an application that is
published on the server, associated with the corresponding file type, and
assigned to the user. This feature is named Content Redirection from client to
server.
If you do not want this to occur for any Program Neighborhood Agent users, do
not associate the published application with any file types. If you do not want
this to occur for specific Program Neighborhood Agent users, do not assign
those users to the published application associated with the file type.
For more information about Content Redirection, see “Configuring Content
Redirection” on page 260.
2. Users connecting through the Web Interface or using the Program
Neighborhood Agent open published content of the associated file type with the
application published on the server.
For example, you publish a document of the Microsoft Word for Windows type.
This feature is named content publishing. When you also publish the Microsoft
Word application, associate it with a list of file types (files with the .doc
extension, for example), and assign it to a group of users, the published content
is opened in the Microsoft Word application published on the server. This
occurs for users when they connect to the logon page for the Web Interface and
click the link to the published content (the document, in this case).
If you do not want this to occur for any users, do not associate the published
application with any file types. If you do not associate the published application
with any file types, users open the published content with local player or viewer
applications if they are installed on the client devices.
For more information about Content Publishing, see “Publishing Content” on
page 263.
You associate published applications with file types on the last page of the
Publishing wizard or on a published application’s Properties page.
246 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
Depending on how or if you want to redirect application launching, you may need
to publish the same application more than once. Follow the procedures below to
associate published applications with file types:
Note When you associate a file type with a published application, several file
extensions can be affected. For example, when you associate the Word
document file type, file extensions in addition to the .doc extension are
associated with the published application.
Note When you associate a file type with a published application, several file
extensions can be affected. For example, when you associate the Word
document file type, file extensions in addition to the .doc extension are
associated with the published application.
CAUTION Using Registry Editor incorrectly can cause serious problems that can
require you to reinstall the operating system. Citrix cannot guarantee that problems
resulting from incorrect use of Registry Editor can be solved. Use Registry Editor at
your own risk. Make sure you back up the registry before you edit it.
Note In the event more sessions are launched on a server than IP addresses are
available, the server displays the error: No virtual IP address is available for this
session, please contact your administrator. The inability of the server to assign a
virtual IP address to a session does not prevent the user from launching an
application that requires a virtual IP address within the session; however, the
application may not function correctly.
Go to Document Center Chapter 10 Publishing Applications, Content, and Desktops 251
To enable isolation environments on a single server, but not for a whole farm
1. Disable isolation environment for the farm.
2. Under the Servers node of the Presentation Server Console, select the server for
which you want to enable isolation environments.
3. From the Actions menu, choose Properties.
4. In the left pane of the server Properties dialog box, choose Isolation Settings.
5. Clear the checkbox Use farm setting to enable application isolation.
Go to Document Center Chapter 10 Publishing Applications, Content, and Desktops 255
Note You set isolation settings only at the farm level. To change isolation settings
when isolation environments are enabled on individual servers, but not for the farm,
temporarily enable isolation environments at the farm level.
Roots. Specifies the virtual directories and registry locations in which files
modified by users (user profile root) and applications (installation root) reside.
You can set root locations for the following:
• Farm level. You can configure root locations only at the farm level
• Server level. Root locations set at the farm level apply only to enabled servers
Associate an application with the isolation environment after you publish the
application on a server in the farm.
CAUTION Using Registry Editor incorrectly can cause serious problems that can
require you to reinstall the operating system. Citrix cannot guarantee that problems
resulting from incorrect use of Registry Editor can be solved. Use Registry Editor at
your own risk. Make sure you back up the registry before you edit it.
2. Use regedit to delete the registry entries under installation root (typically
HKLM\Software\Citrix\AIE\<aiename>).
3. Because the server does not automatically update published application links,
after you remove applications from a deleted isolation environment, use the
console to delete the published links for the uninstalled applications.
260 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
Because an application file system and registry are isolated, this procedure provides
a clean uninstall of the applications from the server.
Note Content Redirection from client to server is available only with MetaFrame
Presentation Server Advanced or Enterprise Editions.
If you have users who run applications such as email programs locally, you can use
the content redirection capability in conjunction with the Win32 Program
Neighborhood Agent to redirect application launching from the client device to the
server. When users double-click attachments encountered in an email application
running locally, the attachment opens in an application that is published on the
server, associated with the corresponding file type, and assigned to the user.
Important You must enable client drive mapping to use this feature. You can
enable client drive mapping for the entire server farm, for specific servers, or for
specific users with user policies. For more information about user policies, see
“Creating and Applying Policies” on page 289.
If you do not want this to occur for any Program Neighborhood Agent users, do not
associate the published application with any file types. If you do not want this to
occur for specific Program Neighborhood Agent users, do not assign those users to
the published application associated with the file type.
Follow the procedure below to configure Content Redirection from client to server.
To free servers from processing these types of requests, you can redirect application
launching for supported URLs from the server to the local client device.
Note If the client device fails to connect to a URL, the URL is redirected back to
the server.
The following URL types are opened locally on the Clients for Win32 and Linux
when this type of content redirection is enabled:
HTTP (Hypertext Transfer Protocol)
HTTPS (Secure Hypertext Transfer Protocol)
RTSP (Real Player and QuickTime)
RTSPU (Real Player and QuickTime)
PNM (Legacy Real Player)
MMS (Microsoft’s Media Format)
Note If Content Redirection from server to client is not working for some of the
HTTPS links, verify that the client device has an appropriate certificate installed. If
the appropriate certificate is not installed, the HTTP ping from the client device to
the URL fails and the URL is redirected back to the server.
Content Redirection from server to client requires Internet Explorer Version 5.5
with Service Pack 2 on systems running Windows 98.
Go to Document Center Chapter 10 Publishing Applications, Content, and Desktops 263
Follow the procedures below to enable Content Redirection from server to client.
Publishing Content
You can give users access to information, such as documents, Web sites, and video
presentations, by publishing content for users in the same way that you publish
applications in a server farm.
With content publishing, you can publish and manage various types of content and
present it to users with the applications they need. Published content and published
applications appear together through the Web Interface, Program Neighborhood,
and Program Neighborhood Agent interfaces.
You can configure MetaFrame Presentation Server to allow users to open published
content in local player or viewer applications running on client devices or in
applications published on servers.
2. Determine which users you want to open the published content with a published
application.
3. Publish the application that corresponds to the content file type. For example, if
you published a Microsoft Word for Windows document file named
“Quarterly_Sales.doc,” publish Microsoft Word on a server running MetaFrame
Presentation Server. For more information about publishing applications, see
the online Help for the Application Publishing wizard.
4. When you publish Word, associate the file type “Word document” with the
application.
Note When you associate a file type with a published application, several file
extensions can be affected. For example, when you associate the Word
document file type, file extensions in addition to the .doc extension are
associated with the published application.
5. Assign the published Word to the users you want to open the published
document with the published application.
Follow these basic steps for publishing content for users to access with applications
running locally on client devices.
1. Publish the data file you want users to access. For more detailed instructions for
publishing content, see “Publishing Content on Servers” on page 265.
2. If you publish the application that corresponds to the content file type, do not
associate it with any file types if you want all users to open the published
content with locally installed applications.
However, if you want some users to open the published content with the
published application, you can associate the published application with the
content file type, but only assign the application to those users. For more
information about publishing applications, see the online Help for the
Application Publishing wizard.
If you want users to open published content with local applications, the applications
must be associated with published content through Web browser MIME types or
Windows file associations on the client device. No other client-side configuration is
necessary after viewer applications are installed and associations are configured.
To publish content
1. In the Presentation Server Console, choose Actions > New > Published
Application to open the Publishing wizard.
2. Type a name for the content you are publishing in the Display Name box. This
text appears as the name of the icon that represents the published content.
3. For Application Type, select Content.
4. In the Content Address box, specify the location of the content by entering a
URL or UNC address. See “Specifying Locations for Publishing Content.”
below for more information.
5. After specifying the content address, continue using the wizard to specify other
settings and publish the content.
Important Specifying a UNC directory path does not correctly display the
specified directory to users of Netscape Navigator prior to Version 6.0. Earlier
versions of Navigator incorrectly interpret the path as relative to the Web server. To
publish a directory to such users, consider specifying an FTP directory or listable
Web server directory.
Go to Document Center Chapter 10 Publishing Applications, Content, and Desktops 267
Note The term published application in this section refers to applications and
server desktops that are published for users in the server farm. It does not refer to
published content such as documents and media files.
You can apply a CPU priority setting to each published application. Each instance
of the application that runs in the server farm is affected by the setting. When
multiple servers host the same published application, the setting applies to each
server in the server farm on which the application runs.
If you publish the same application more than once—for separate groups of users,
different host servers, or with different settings, for example—you create separate
published applications -- each can have its own CPU priority setting.
You can use this setting in any size server farm, independent of load management
features in MetaFrame Presentation Server Advanced Edition and Enterprise
Edition. Load management distributes connections to servers based on the servers’
loads. In contrast, the CPU priority setting applies to a published application that
runs on any server in the server farm.
268 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
Important High priority indicates a process that performs time-critical tasks. The
threads of a high-priority process preempt the threads of low- and normal-priority
processes. An example is the Task List, which must respond quickly when called by
the user, regardless of the load on the system. Use extreme care when using the
high-priority setting. A CPU-bound application assigned high priority can consume
nearly all available CPU cycles, which can cause unacceptable performance by
other applications running on the server.
The CPU priority option is in the Application Publishing wizard and on the
Application Limits page in the Properties sheet for each published application.
You can set the priority level when you first publish applications and set or change
the level for published applications using the Presentation Server Console.
This chapter describes how to manage users and their sessions in a server farm. It
includes information about using the Presentation Server Console to monitor users’
connections. This chapter also includes information about creating and applying
policies to control select settings for users or user groups.
You can use the Presentation Server Console to perform session-management
activities, including logging off, shadowing, disconnecting, and sending messages
to users.
Note You may not see some or all of the data described below if you have not
been granted permission to perform these tasks. See your primary MetaFrame
administrator for more information.
Note For servers running MetaFrame Presentation Server 3.0 or later, clearing
the Enable logons to this server check box is a persistent setting that remains
in effect after restarting the server. In earlier releases, the Enable logons to this
server setting defaults to being selected each time the server is started.
User policies and client drive mappings change appropriately when a user moves to
a new client device. Policies and mappings are applied according to the client
device where the user is currently logged on to the session. For example, if a health
care worker logs off from a client device in the emergency room of a hospital and
then logs on to a workstation in the hospital’s X-ray laboratory, the policies, printer
mappings, and client drive mappings appropriate for the session in the X-ray
laboratory go into effect for the session as soon as the user logs on to the client
device in the X-ray laboratory.
You can configure Workspace Control behavior in the Web Interface Console or the
Program Neighborhood Agent Console. For more information about enabling and
configuring Workspace Control for users, see the Web Interface Administrator's
Guide.
Note The seamless session option in the MetaFrame Presentation Server Client
enables session sharing, a mode in which more than one published application runs
with a single connection. If a user runs multiple applications with session sharing,
the session counts as one connection.
To conserve resources, you can limit the number of concurrent connections that
users are permitted to establish. The limit applies to each user who connects to the
server farm. A user’s active sessions and disconnected sessions are counted for the
user’s total number of concurrent connections.
For example, you can set a limit of three concurrent connections for users. If a user
has three concurrent connections and tries to establish a fourth, the limit you set
prevents the additional connection. A message tells the user that a new connection
is not allowed.
Limiting connections can help you maintain availability of connection license
counts as well as prevent over-consumption of server resources by a few users.
You can apply the concurrent connections limit to all users, including members of
the local administrators group. To set connection limits, select Connection Limits
in the left pane of the farm’s Properties page.
For example, you can publish Autodesk AutoCAD and set a limit of 30 concurrent
instances in the server farm. When 30 users are running AutoCAD at the same time,
no more users can launch the application because of the limit of 30 concurrent
instances.
You can use the concurrent instances limit to enforce an application’s licensing
requirement.
Another connection control option lets you prevent any user from running multiple
instances of a particular published application. With some applications, running
more than one instance in a single user context can cause errors on the server.
You can apply application limits independently to each published application. For
example, you can apply the limitations on total concurrent instances and multiple
instances by a single user to one published application. You can limit only the total
concurrent instances of another application. You can configure a third application to
limit launching of multiple instances by individual users.
Maximum connections per user. You can limit users to a maximum of five
connections, for example. If a user tries to launch a sixth connection, the server
denies the connection request and records the user’s name and the time in the
System log.
Application instances per user. You can configure a published application to allow
each user to run only one instance of the application. If a user tries to launch a
second instance of the application, the server denies the connection request and
records the user name, the time, and the name of the published application in the
System log.
Use Allow only one instance of application for each user in Application Limits
on the Properties page to limit each published application to one instance for a
user.
280 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
User. The name of the user account that initiates a session appears in the User
column for each session. In the case of anonymous connections, the user name is a
string with the letters “Anon” followed by a session number.
Server. The servers on which the selected application is running appear in this
column.
Session. The Session column identifies a session with a name that includes the
protocol that the session uses, usually ICA or RDP (Remote Desktop Protocol). The
name also includes the network protocol for the session, and a number that
distinguishes the session from other sessions that are running on the server.
Session ID. The Session ID is a unique number that begins with 0 for the first
connection to the console. Listener sessions are numbered from 65,537 and
numbered backward in sequence.
Type. The type of connection being used to connect to the server, ICA or RDP, for
example.
Client name. This column displays the name of the client device that is running the
session.
Application. The name of the published application running within this session.
Idle Time. The amount of time during which the user has not interacted with the
application.
In Presentation Server Console, use the Actions menu and the toolbar buttons to
choose session management commands. You can right-click a session in the
console and choose commands from the menu that appears.
Disconnecting Sessions
To disconnect a session, choose Disconnect. When you disconnect a session, you
close the connection between the client and the server. However, this does not log
off the user, and programs that were running in the session are still running on the
server. If the client user then connects to the server (by selecting a published
application or custom connection to the server), the disconnected session is
reconnected to the client.
Shadowing Sessions
If you enabled shadowing on the server when you installed MetaFrame Presentation
Server, you can shadow a user’s session. Shadowing allows you to view the user’s
actions and take remote control of the user’s keyboard and mouse. See “Using
Shadowing to Monitor ICA Sessions” on page 201 for more information about
shadowing.
When you finish typing the message, click OK to send the message to the selected
sessions.
Resetting Sessions
Resetting a session with the Reset command terminates all processes that are
running in that session. You can use the Reset command to remove remaining
processes in the case of a session error. However, resetting a session can cause
applications to close without saving data.
If you reset a disconnected session, the word Down appears in the State column for
the session. When you refresh the console display or when the next automatic
refresh occurs, the session no longer appears in the list of sessions.
Important Ending users’ sessions with the Logoff Selected Session command can
result in loss of data if users do not close their applications first. You can send a
message to warn users to exit all applications if you need to log off their sessions.
284 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
Note You can use Session Reliability in conjunction with SSL, but not in sessions
routed through the Secure Gateway.
Auto Client Reconnect is supported with the Clients for 32-bit Windows, Java, and
Windows CE. This feature does not work with sessions embedded in applications
using the ICA Client Object.
By default, Auto Client Reconnect is enabled at the server farm level, and user re-
authentication is not required. You can customize the settings for this feature at the
farm level and for individual servers. To do this, select ICA Settings on the
corresponding farm or server Properties page in the Presentation Server Console
and modify the Auto Client Reconnect settings as appropriate.
Tip For maximum protection of users’ credentials and ICA sessions, use SSL
encryption for all communication between clients and the server farm.
Policies contain rules that define the policy’s settings. A single policy can apply
multiple rules. You can create policies that:
• Direct users to connect to servers in a local zone and fail over to a specific
remote zone
• Set a required encryption level for a group of specific clients
• Control audio sound quality used by client devices
• Route print jobs from specific workstations directly from the server to the
printer rather than through the client device
• Control bandwidth limits for sessions
Policies are applied when users log on to the server farm and remain in effect for the
length of the user’s session. In general, policies override similar settings configured
for the entire server farm, for specific servers, or on the client. However, the highest
encryption setting and the most restrictive shadowing setting always override other
settings.
With policies, you can tailor MetaFrame Presentation Server to meet users’ needs
based on their job functions, geographic locations, or connection types (LAN,
WAN, or dial-up). For example, for security reasons you may need to place
restrictions on user groups who regularly work with highly sensitive data. You can
create a policy that requires a high level of encryption for client sessions and
prevents users from saving the sensitive files on their local client drives.
However, if some of the people in the user group do need access to their local
drives, you can create another policy for only those users. You then rank or
prioritize the two policies to control which one should take precedence.
Policy rules have three states: enabled, disabled, or not configured. By default, all
rules are not configured. All unconfigured rules are ignored when users log on to
the server, so the rules come into play only when the state is enabled or disabled.
Creating Policies
The basic steps for effectively creating and using policies are as follows. These
steps are explained in more detail below.
1. Decide the criteria on which to base your policies.
You may want to create policies based on user job function, connection type,
client device, or geographic location, or you may want to use the same criteria
that you use for your Windows Active Directory group policies.
2. Create the policy. Creating a policy involves the following steps:
• Naming the policy
• Assigning the policy to user accounts, client devices, or servers
Go to Document Center Chapter 11 Managing Users and Sessions 291
To create a policy
1. In the Presentation Server Console, select the Policies node in the left pane and
choose Actions > New > Policy or click the Create Policy button on the
console toolbar.
2. In the New Policy dialog box, enter the name and description of the policy, then
click OK.
Examples of policy names are “Accounting Department” or “Lender Laptops.”
The policy name is displayed in the right pane of the console.
After creating a policy, you must configure at least one filter that determines
sessions to which the policy applies.
The following tables presents rules you can configure within a policy.
Bandwidth
To limit bandwidth used for the following: Use this policy rule:
Desktop wallpaper Visual Effects > Turn off desktop wallpaper
Menu and window animations Visual Effects >Turn off menu animations
Window contents while a window is dragged Visual Effects >Turn off window contents
while dragging
Compression level for image acceleration Speed Screen > Image acceleration using
lossy compression
Client audio mapping Session Limits > Audio
Devices connected to a local COM port Session Limits > COM ports
Cut-and-paste using local clipboard Session Limits > Clipboard
Access in a session to local, client drives Session Limits > Drives
Printers connected to the client LPT port Session Limits > LPT Ports
Custom devices connected to the client through Session Limits > OEM Virtual Channels
OEM virtual channels
Client session Session Limits > Overall Session
Printing Session Limits > Printer
TWAIN device (such as a camera or scanner) Session Limits > TWAIN Redirection
Client Devices
Control whether or not to allow audio input from Resources > Audio > Microphones
client microphones
Control client audio quality Resources > Audio > Sound quality
Control audio mapping to client speakers Resources > Audio > Turn off speakers
Control whether or not client drives are Resources > Drives > Connections
connected when users log on to the server
Control how drives map from the client device Resources > Drives > Mappings
Improve the speed of writing and copying files to Resources > Drives > Optimize >
a client disk over a WAN Asynchronous writes
Prevent client devices attached to local COM Resources > Ports > Turn off COM ports
ports from being available in a session
Go to Document Center Chapter 11 Managing Users and Sessions 293
Prevent client printers attached to local LPT ports Resources > Ports > Turn off LPT ports
from being made available in a session
Allow use of USB-tethered, Windows CE-based, Resources > PDA Devices > Turn on
PDA devices automatic virtual COM port mapping
Configure resources for the use of TWAIN Resources > Other > Configure TWAIN
devices, such as scanners and cameras redirection
Prevent cut-and-paste data transfer between the Resources > Other > Turn off clipboard
server and the local clipboard mapping
Prevent use of custom devices, such as an Resources > Other > Turn off OEM virtual
electronic pen (stylus) channels
Disable auto client update for a group of users, Maintenance > Turn off auto client update
clients, or servers
Printing
Control creation of client printers on the client Client Printers > Auto-creation
device
Allow use of legacy printer names and preserve Client Printers > Legacy client printers
backwards compatibility with prior versions of the
server
Control the location where printer properties are Client Printers > Printer properties retention
stored
Control whether print requests are processed by Client Printers > Print job routing
the client or the server
Prevent users from using printers connected to Client Printers > Turn off client printer
their client devices mapping
Control installation of native Windows drivers Drivers > Native printer driver auto-install
when automatically creating client and network
printers
Control when to use the universal print driver Drivers > Universal driver
Choose a printer based on a roaming user’s Session printers
session information
294 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
User Workspace
Limit the number of sessions that a user can run Connections > Limit total concurrent
at the same time sessions
Direct connections to preferred zones and Connections > Zone preferences and
failover to backup zones failover
Control whether or not to use content redirection Content Redirection > Server to client
from the server to the client device
Control whether or not shadowing is allowed Shadowing > Configuration
Allow or deny permission for users to shadow Shadowing > Permissions
connections
Use the server’s time zone instead of the client’s Time Zones > Do not estimate local time for
estimated local time zone legacy clients
Use the server’s time zone instead of the client’s Time Zones > Do not use Clients’ local time
time zone
Identify which credential repository to use when MetaFrame Password Manager > Central
using MetaFrame Password Manager Credential Store
Prevent use of MetaFrame Password Manager MetaFrame Password Manager > Do not
use MetaFrame Password Manager
Security
Migrating Policies
If you upgrade from a previous release of MetaFrame, your existing policies and
their rules are maintained and all new rules are not configured. After migrating, you
can open the settings for an existing policy and enable new rules and filters that you
want to add to the policy.
In a server farm that has servers running a previous release of MetaFrame, new
filters and rules are ignored by the servers running earlier releases.
Go to Document Center Chapter 11 Managing Users and Sessions 295
Overriding Policies
Policies are applied when users log on and remain in effect for the length of the
session. In general, connection policies override similar MetaFrame settings
configured for the entire server farm, for specific servers, or on the client. However,
the highest encryption setting and the most restrictive shadowing setting always
override other settings.
Prioritizing Policies
You can prioritize policies by ranking the priority number. By default, new policies
are given the lowest priority. In cases of conflicting policy settings, a policy with a
higher priority will override a policy with a lower priority. A policy with the priority
number of 1 has the highest ranking priority. If you have five policies ranked 1
through 5, the policy ranked with priority number 5 has the lowest priority.
In the following procedure, the interwoven example assumes that you created a
policy for your “Accounting” user group. One of the rules enabled in this policy
prevents the user group from saving data to their local drives. However, two users
who are members of the Accounting group travel to remote offices to perform
audits and need to save data to their local drives.
The steps below describe creating a new policy for Accounting group members
Carol and Martin that will allow them access to their local drives while allowing the
other policy rules to work the same way for them as for all other members of the
Accounting group.
296 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
Applying a Policy
By default, newly created policies are not applied to any sessions. Before a policy
has an effect, you must create a filter for it so the server can apply it to matching
sessions. You can filter sessions and apply a policy to them based on a combination
of the following criteria:
• Access control through which a client is connecting to a session
• IP address of a client device connecting to a session
• Name of a client device connecting to a session
• Users or user groups associated with a session
• Server hosting a session
By applying both user group and client device filters, you can create one policy for
employees of a New York office when they connect from their office workstations,
and create another policy for the same New York employees that sets a higher
encryption level for sessions connecting from laptops they use in the field.
To apply a policy
1. In the left pane of the console, choose the Policies node.
2. In the Contents tab, choose the policy you want to apply.
3. From the Actions menu, choose Policy > Apply this policy to.
4. Use the Policy Filters dialog box to configure filters to apply the policy to a
session based on access control, client IP address, client name, server the
session connects to, or the user who is making the connection.
• To apply the policy according to the type of access control through which
the user is connecting, click Access Control in the left pane.
Using the Access Control filter, you can match any connection a client
makes through MetaFrame Secure Access Manager.
• To apply the policy to client IP addresses, click Client IP Address in the left
pane and select Filter based on client IP address. Click Add to configure
an individual address or range of addresses and then specify whether to
allow or deny the addresses for the policy.
• To apply the policy to client names, click Client Name in the left pane and
select Filter based on client name. Click Add to specify a client name to
which the policy applies.
• To apply the policy to servers, click Servers in the left pane and select Filter
based on servers. Select servers or folders of servers in the right pane and
choose to apply or not apply the policy to them.
298 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
• To apply the policy to users, click Users in the left pane and select Filter
based on users. Select the user group and/or users to whom you want to
assign the policy and then click Add.
By default, the policy is allowed for any users or user groups you add to the
configured accounts list. If there are members of the user group you do not
want assigned to this policy, you can add the individual members of the
group and then select Deny to prevent the policy from being applied to
them.
5. If a filter has an Allow/Deny setting, you must select Allow to enforce the
policy.
6. Click OK when you are finished applying the policy filters.
Note To assign policies to all users accessing applications through the Web
Interface, you can use the wildcard expression WI_* when specifying the client
name filter. Users accessing applications through the Web Interface receive a
random client name of WI_number, where number is random ASCII characters.
Because the assigned client name is random, you cannot anticipate the client name
to be assigned to individual client users.
You can use search to list policies that apply to a connection based on:
• Whether or not the connection is made through access control
• The IP address of the client device making the connection
• The name of the client device making the connection
• The user or group membership of the user making the connection
• The server to which the connection is being made
Go to Document Center Chapter 11 Managing Users and Sessions 299
Note If the PDA Devices policy rule is disabled (by default), or there is no PDA
attached to the client device, a session user might access a PDA physically
connected to the server.
300 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
In addition to enabling and disabling this feature for a farm, you can enable this
feature for individual servers within a farm. Memory utilization management is not
enabled by default.
You do not want to enable memory utilization management on farms or servers that
exclusively host signed or certified applications. MetaFrame Presentation Server
can detect only some published applications that are signed or certified.
• The optimization time. The time at which the server begins rebasing DLLs.
The value of optimization time is based on a twenty-four hour clock.
5. If you store application files on a file server or remote server that requires
special access permissions, such as a domain administrator, clear the checkbox
Use local system account and provide the account and password that has
permissions to access the remotely stored application files.
Shadowing Sessions
You can monitor the actions of users by shadowing their sessions. A shadowed
session is displayed in the session of the shadower, the user who establishes
shadowing.
Shadowing a session provides a powerful tool for you to assist and monitor users.
Shadowing is a useful option for your Help desk staff who can use it to aid users
who have trouble using an application. Help desk personnel can view a user’s
actions to troubleshoot problems and can demonstrate correct procedures. You can
also use shadowing for remote diagnosis and as a teaching tool.
You can create a user policy to enable user-to-user shadowing. When you create a
policy allowing user-to-user shadowing, users can shadow other users without
requiring administrator rights. Multiple users from different locations can view
presentations and training sessions, allowing one-to-many, many-to-one, and many-
to-many online collaboration. See “Configuring User-to-User Shadowing” on page
306 for more information about user-to-user shadowing.
Go to Document Center Chapter 11 Managing Users and Sessions 305
By default, the user who will be shadowed is asked to accept or deny the request to
shadow the session.
You can shadow multiple sessions using the Presentation Server Console or the
Shadow Taskbar.
Tip You can click the Shadow Taskbar button on the ICA Administrator toolbar
to launch the Shadow Taskbar.
306 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
When the Shadow Taskbar is running and no sessions are being shadowed, the
Shadow button appears alone on the taskbar. Click the Shadow button and the
Shadow Session dialog box appears.
Use the Shadow Session dialog box to select the sessions you want to shadow. You
can select sessions based on the server, the application, or the users who are
associated with the sessions. You can select multiple sessions in the dialog box to
begin shadowing several sessions at once. Click OK to begin shadowing the
selected sessions.
For more information about shadowing with the Shadow Taskbar, press F1 to view
online Help when the Shadow Taskbar is running.
The basic steps for configuring user-to-user shadowing are as follows. These steps
are explained in more detail later in this section.
1. Create a user policy that identifies the users who can shadow other users’
sessions.
2. Assign the policy to the users to be shadowed.
3. Publish the Citrix Shadow Taskbar and assign it to the users who will shadow.
4. Instruct these users how to initiate shadowing from their client devices.
Go to Document Center Chapter 11 Managing Users and Sessions 307
Note Instruct your users to refrain from launching the Shadow Taskbar in
seamless mode. The Shadow Taskbar cannot function in seamless mode.
9. The users and user groups you added to the Configured Accounts list are listed
in the right pane of the policy’s property sheet. By default, the shadowing
permission for each user or user group is set to Allow. You can deny shadowing
permissions by clicking Deny.
10. Click OK at the bottom of the policy’s property page when you are done
configuring the shadowing rules.
After you create the policy and configure the rules, you must assign the policy to
the users who you want to be shadowed.
Important The list of users permitted to shadow is exclusive for each user to
whom a policy is assigned. For example, if you create a policy that permits user
MichelleF to shadow user LorenaB, this policy allows only MichelleF to shadow
LorenaB, unless you add more users to the list of users who can shadow in the same
policy’s property sheet.
To allow users to shadow other users’ sessions, you can publish the Shadow
Taskbar utility to the users you want to be able to shadow. When users open this
published application, the Shadow Taskbar appears at the top of users’ screens.
For more information about using the Shadow Taskbar to shadow sessions, see
“Using the Shadow Taskbar” on page 305 and the Taskbar’s online Help.
Note The entire ICA counter list is exposed only on a server running the
Enterprise Edition of MetaFrame Presentation Server. On a server running the
Advanced or Standard Edition, only latency-related counters are available.
This screen capture shows the Performance dialog box with System Monitor
selected.
3. Click Add.
4. In the Add Counters dialog box, click the Performance object drop-down list
and select ICA Session. The ICA performance counters are listed under Select
counters from list.
310 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
This screen capture shows the Add Counters dialog box with computer-selection
drop-down list, Performance object drop-down list, and counters list.
5. Select All Counters to enable all available ICA counters or select Select
counters from list and then highlight the individual counters you need.
6. Select All Instances to enable all instances of the selected ICA counters or
select Select instances from list and highlight only the instances you need.
In Performance Monitor, the instance list contains all active ICA sessions,
which includes any session (shadower) that is shadowing an active ICA session
(shadowee). An active session is one that is logged on to successfully and is in
use; a shadowing session is one that initiated shadowing of another ICA session.
Note In a shadowing session, although you are able to select ICA counters to
monitor, you will see no performance data for that session until shadowing is
terminated.
Managing Printers
Users can print documents easily when they run applications on servers running
MetaFrame Presentation Server. For most users, printing when they use
applications in a client session is no different from printing from applications that
run on their own computers.
This chapter describes features for making printers available to users and managing
printers in server farms.
To find step-by-step instructions for using the features that are described in this
chapter, use the online Help in the Presentation Server Console.
For more information about printing configuration and options for MetaFrame
Presentation Server Clients, see the Administrator’s Guide for the clients you plan
to deploy.
Overview of Printing
When users run applications that are published on servers, they can print to the
following types of printers:
• Printers that are connected to ports on users’ Win16 and Win32 client devices,
Windows CE, DOS, and Macintosh OS platforms
• Virtual printers created for tasks such as printing from a PostScript driver to a
file on a Windows client device
• Shared printers that are connected to print servers on a Windows network
• Printers that are connected directly to servers running MetaFrame
Presentation Server
• Printers that change according to attributes of a session (session printers)
312 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
The printers that MetaFrame Presentation Server Clients use can be categorized by
connection types. You can set up three general types of printer connections in a
server farm: client connections, network connections, and local connections.
Therefore, this chapter refers to printers in a server farm as client printers, network
printers, and local printers, depending on the type of connection they have in the
farm.
Client printers. The definition of a client printer depends on the client platform.
• Simple ports: On DOS-based and Windows CE client devices, a client printer is
physically connected by a cable to a port on the client device. A PC or
PostScript printer connected to a serial port on a Macintosh OS system is also
considered a client printer.
• Print queues that manage printers: On 32-bit Windows platforms (Windows XP,
Windows 2000, Windows NT, or Windows 9x), any printer that is set up in
Windows (these printers appear in the Printers folder on the client device) is a
client printer. Locally connected printers, printers that are connected on a
network, and virtual printers are all client printers.
Note Some virtual printers, such as a fax/modem device that is set up in the
Printers folder, might not be available as a client printer in ICA sessions.
When a user shares a client printer through Windows printer sharing, the printer
appears as a network printer to other users.
Network printers. Printers that are connected to print servers and shared on a
Windows network are referred to as network printers. In Windows network
environments, users can set up a network printer on their computers if they have
permission to connect to the print server. When a network printer is set up for use
on an individual Windows computer, the printer is a client printer on the client
device.
Local printers. Printers that are connected directly to servers are local printers
within a particular server farm. This definition includes a printer that is connected
to the server that hosts a user’s session, as well as printers that are connected to
other servers running MetaFrame Presentation Server in the same server farm.
If a printer is connected to a server outside of a server farm (either the server is not
a member of a server farm or is a member of a different server farm), the server
farm considers the printer a network printer, not a local printer.
Go to Document Center Chapter 12 Managing Printers 313
In this type of environment, you can set up printers in the server farm by simply
installing printer drivers on a server and using the replication feature in the
Presentation Server Console to distribute the drivers to all the servers in the farm.
• The printers that users normally print to are available automatically when they
connect to a server, because MetaFrame Presentation Server creates each user’s
client printers for use during ICA sessions.
• Mapping is necessary when the printer drivers you install for Windows 9x client
computers and Windows servers have different names, or when you want to use
one driver instead of another.
• Unless an applied policy enforces the legacy printers rule, when users print from
applications running on a server, the installed client printers appear in Windows
in the following form:
printer_name on server_name (from client_name) in session_ID
Here is an example:
HP LaserJet 4000 on printsrv03 (from garybW2K) in session 3
• If a policy applies the legacy printers rule, the installed client printers appear in
Windows in the following form:
Client\user_name#name_on_remote
where name_on_remote is the actual printer name on the remote device.
Here is an example:
Client\garyb#HP LaserJet 1012
• When some users have Windows 9x client devices, you map client printer
drivers to the drivers you install on servers. This is necessary when driver names
for the same printer are different on client devices running Windows 9x than
they are on the Windows 2000 or Windows 2003 servers. Driver mapping is not
necessary for client devices running Windows 2000 or higher, because they use
the same printer drivers as the Windows 2000 or higher servers.
• You import network print servers into the server farm to make the shared
printers available to all users when they connect to servers in the farm.
• If some client printer drivers are not compatible with the server platforms in the
farm, use the Driver Compatibility feature to prevent incompatible printer
drivers from causing server errors.
• Unless an applied policy enforces the legacy printers rule, when users print from
applications running on a server, the installed client printers appear in Windows
in the following form:
printer_name on server_name (from client_name) in session_ID
Here is an example:
HP LaserJet 4000 on printsrv03 (from garybW2K) in session 3
• If a policy applies the legacy printers rule, the installed client printers appear in
Windows in the following form:
Client\user_name#name_on_remote
where name_on_remote is the actual printer name on the remote device.
Here is an example:
Client\garyb#HP LaserJet 1012
• When users print to the network printers in the server farm, they see the original
assigned network printer names in Windows dialog boxes.
After you launch the console and log on to a server in the farm, the left pane in the
console displays the tree view of the server farm management nodes. When you
select an item in the tree, the right pane displays one or more tabs.
Expand the Printer Management node or the Servers node or the objects under these
nodes to use the primary printer management features in the console.
This screen capture shows Printer Management and Servers nodes. The expanded
Printer Management node makes available Drivers and Printers objects.
Contents Tab
When you select Printer Management, the Contents tab displays objects labeled
Drivers and Printers. The same objects appear in the tree under Printer Management
when you expand the node.
Double-clicking an object on the Contents tab is the same as selecting the object in
the tree. Either action changes the right pane to display information about the object
you select and puts commands related to the object in the Actions > Printer
Management submenu and on the console toolbar.
Importing print servers. Use the Network Print Servers tab when you want to
import a network print server to make its printers available to the users of the server
farm. When you select the tab, you can choose Import Network Print Server
from the toolbar or the Actions menu. The command and toolbar button are not
available when other tabs are selected.
Tip Importing a network print server lets users in the server farm use a printer that
is not connected to their client device. Client printers are automatically made
available to users in their ICA sessions.
Updating server information. If you add printers to or remove them from a network
print server, update the print server information to be sure that the console displays
the available printers on the Printers tab. To do this, select a print server and use
the Update Network Print Server command from the toolbar or the Actions
menu. You must take this action because updating print server information does not
take place automatically.
Removing print servers. Removing a print server removes all of its printers from the
farm. This is the opposite of importing a network print server. If you remove
printers, users cannot print to them. If you want to do this, select the print server to
remove and then choose Discard Network Print Server from the console toolbar
or the Actions menu. After you confirm the command, the printer server no longer
appears on the Network Print Server tab and its printers do not appear on the
Printers tab.
Bandwidth Tab
When you select Printer Management in the console tree, the Bandwidth tab
displays the print stream bandwidth setting for each server in the farm.
Note While you can limit print stream bandwidth through server settings, the best
practice is to do so through policies. For more information about configuring a
policy to include a print stream bandwidth limit, see “Limiting Printing Bandwidth
through Policies” on page 330.
You can use this tab to set or remove print stream bandwidth limits on servers and
copy settings from one server to others. Limiting printing bandwidth can improve
application performance for clients when printing and application data must
compete for limited bandwidth.
When you select a server in the list on the Bandwidth tab, you use the Edit
command to change its bandwidth setting, or use the Copy command to copy its
bandwidth setting to one or more servers in the farm. You can use these commands
from the console toolbar or the Actions menu.
318 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
When you select the Servers node in the tree, the Printer Bandwidth tab provides
the same display and features as the Bandwidth tab when you select Printer
Management.
You can use ICA Printer Bandwidth in the left pane of a server’s Properties page
to edit the server’s print stream bandwidth setting.
For more information about limiting the bandwidth of print data streams, see
“Limiting Printing Bandwidth in Client Sessions” on page 330.
Drivers Tab
When you select Drivers in the tree, the Drivers tab in the right pane displays
information about printer drivers installed on servers running MetaFrame
Presentation Server. The driver information includes each driver’s name and
operating system platform. You select a specific server from the Server drop-down
menu to display the drivers installed on one server, or select (Any) to display all
drivers on all servers in the farm.
If not prevented through the Native printer driver auto-install rule, MetaFrame
Presentation Server installs the drivers needed for the autocreation of client or
network printers. MetaFrame Presentation Server installs these drivers from the
primary set of native printer drivers provided with the Windows operating system.
If a driver for a printer used by client users is not in this primary set, that printer can
be autocreated only after you obtain and install a driver on the server(s) to which
these users connect. After installing the driver on one or more servers, you can use
the Drivers tab to replicate the installed driver to other servers in the farm.
Use the Drivers tab to copy printer drivers to other servers in a server farm. If
printer drivers are not already installed, copy the drivers to each server where users
log on and need access to the driver for printing to client printers or network
printers.
To copy a driver, select the driver and then use the Replicate Drivers command
from the console toolbar or the Actions menu.
Note Two tabs in Presentation Server Console show printer driver information. To
display the drivers installed on a server, you can select the server from the Server
menu on the Drivers tab, or select the server in the console tree and look at the
Printer Drivers tab. You can use either tab to copy printer drivers to other servers
in a farm.
Go to Document Center Chapter 12 Managing Printers 319
Printers Tab
When you select Printers in the Presentation Server Console tree, the Printers tab
in the right pane lists all printers you can configure in the server farm. The list
includes the following printers:
• Local shared printers that you install and connect directly to servers in the farm
• Network printers that are installed and connected to network print servers when
you import the print servers into the farm
• Printers discovered and attached through the Session printers policy rule
The printer list shows the printer name, print server name, driver name, and server
operating system platform for each local printer. For network printers, the list shows
only the printer name and print server name.
You can select a local printer on the Printers tab and use the console to copy the
drivers to other servers. You cannot copy a driver of a network printer from this tab.
(Use the Drivers tab to copy drivers from a server to other servers.)
To assign users to a printer, you configure session printer policies. Session printer
policies make a printer available to the user of a session to which you applied the
policy.
Note To connect to a session printer, the end user must have the necessary
Windows user or group permissions.
Printers Tab
When you select a server in the console tree under the Servers node or on the
Contents tab, the Printers tab displays information about a server’s local printers.
The tab displays information about the printers that are connected directly to the
server if you select the Shared option when you install the printers. Printers that you
do not share do not appear on the tab.
320 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
This tab is similar to the Printers tab that appears when you select Printers in the
console tree. However, when you select one server, the Printers tab displays only
the server’s local printer information, not information about network printers in the
farm.
You can select a local printer on the Printers tab and use the console to replicate the
drivers and settings for the printer to other servers. You can also assign users to the
printer to make it available as an autocreated printer in the users’ ICA sessions. If
you want to assign the same users to another printer, select the printer and copy its
autocreation settings from this tab.
When you use the wizard to install drivers on a server, the actual printer is not
attached to the server. Select the Local option and select any local printer port that
does not have an actual printing device connected; you can add multiple printers to
one port.
Tip In server farms where it is practical to do so, install all driver files on one
server.
After you install drivers, to copy the driver files and registry settings to other
servers in the server farm, you can use the driver replication feature in the
Presentation Server Console. Use the replication feature to save time when you
install printer drivers and to ensure that all drivers are available on all servers where
clients need them, so that users can print to the client and network printers in the
farm.
Note When you designate a printer driver to be incompatible for printers in the
farm (see “Managing Drivers for Autocreated Printers” on page 324), you cannot
create a printer driver mapping with the same driver.
To monitor and configure printer autocreation for Clients for DOS and
Windows CE
1. Under the Printer Management node of the console, select Printers.
2. From the Actions menu, choose Printer Management > Client Printers.
You can view the status of printers for clients on DOS and Windows CE
platforms in the Client Printers dialog box. In the dialog box, the word
<downloaded> appears in the list when information for client printer setup is
sent from the server to the client device.
Use the Client Printers dialog box to add, remove, reset, edit, and delete the
configuration for the Clients for DOS and Windows CE printers.
These client printers are available to the individual client users only. A client printer
appears in applications running on the server only during the client user’s ICA
session.
Under Client Printers, you can then configure the following rules:
Legacy client printers. To choose the style of client printers that should be
autocreated, enable this rule.
After enabling this rule, choose the style of client printers to create:
• To create printers that are private to each user session and use standard
Windows Terminal Services naming conventions, choose Create dynamic
session-private client printers.
• To create printers that can be shared between sessions and use printer names
that are compatible with prior versions of MetaFrame, choose Create old-style
client printers.
Printer properties retention. To control where the server stores modified, client-
printer properties, enable this rule.
After enabling this rule, choose where you want to store printer properties:
• To store printer properties on the client or the user profile, choose Held in
profile only if not saved on client.
If the server cannot store printer properties on the client, it stores them in the
user profile. In performing the necessary system checking, there may be delays
in logon time and use of additional bandwidth.
Choose this option if your server farm requires backward compatibility with
prior versions of MetaFrame and its clients and is not constrained by bandwidth
or logon performance.
• If your server uses an unsaved mandatory or roaming profile, choose Saved on
client device only.
Only choose this option if all the servers in your farm are running this version of
MetaFrame Presentation Server and your users are using the most recent clients.
328 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
Print job routing. To allow to connect directly from the server to the print server of a
client printer (a shared network printer), enable this rule, then configure according
to the following:
• If the network print server is not across a WAN from the server, choose
Connect directly to network print server if possible.
• If the network print server is across a WAN from both the client device and the
server, choose Always connect the printer indirectly as a client printer.
Turn off client printer mapping. To have users employ only network printers or
printers connected directly to the server, enable this rule.
Native printer driver auto-install.. Use this rule to configure whether or not to install
native printer drivers automatically on servers.
You can greatly reduce printer administration by configuring native printer drivers
to be installed automatically on servers when printers are autocreated.
A specific client printer can be created on a server only when its native driver is also
installed on the server. A standard set of native printer drivers is provided with
Windows. MetaFrame Presentation Server can automatically install printer drivers
from the standard Windows drivers and automatically create both network and
client printers.
To automatically install native print drivers, enable this rule. Enabling the rule
automatically sets Install Windows native drivers as needed.
This option has the potential to create a large number of printer drivers. You can
limit which drivers are installed by using the driver compatibility list. For more
information about how to set up and use a driver compatibility list, see
“Maintaining Driver Compatibility Lists” on page 324
Third-party drivers that are not provided with the standard Windows drivers must
be manually installed on the server before you can configure MetaFrame
Presentation Server to automatically create the printers that use those drivers. You
can also replicate a third-party driver from another server in the farm.
To prevent drivers from being installed automatically, choose the option Do not
automatically install drivers.
Universal driver. To control the assignment of a universal printer driver for client
printers, configure this rule. When you configure the universal driver rule, you can
select the following options:
• Use universal driver only if requested driver is unavailable. Select this
option to use native drivers for client printers, if they are available. If the driver
is not available on the server, the client printer is automatically created with the
appropriate universal driver.
• Use only printer model specific drivers. Select this option if you do not want
to use the universal print driver.
• Use universal driver only. Select this option if you do not want to use native
drivers.
5. Use the Printer rule to enable and disable the printing bandwidth session limit.
When enabling the printing bandwidth session limit, provide a bandwidth limit
in kilobits per second.
6. Click OK.
After configuring a printing bandwidth limit in a policy, consequent sessions to
which it is applied adhere to the limit. You must apply a policy through a filter for
the policy to affect sessions.
Command Description
acrcfg Configure autoreconnect settings
aierun Run isolation environment. Primarily for use in scripting environments.
aiesetup Install or uninstall an application from an isolation environment
altaddr Specify server alternate IP address
app Run application execution shell
apputil Add servers to Configured Servers list for published applications
auditlog Generate server logon/logoff reports
change client Change client device mapping
chfarm Change the server farm membership of the server
cltprint Set the number of client printer pipes
ctxxmlss Change the XML Service port number
driveremap Remap the server’s drive letters
dscheck Validate the integrity of the server farm data store
dsmaint Configure the server farm’s data store
icaport Configure TCP/IP port number used by the ICA protocol on the server
imaport Change IMA ports
334 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
Command Description
migratetomsde Migrate the server farm’s data store from a Microsoft Access database
to an MSDE database
query View information about server farms, processes, servers, ICA sessions,
and users
twconfig Configure ICA display settings
Go to Document Center Appendix A MetaFrame Presentation Server Commands 335
ACRCFG
Use acrcfg to configure automatic client reconnection settings for a server or a
server farm.
Syntax
acrcfg [/server:servername | /farm] [/query | /q]
acrcfg [/server:servername | /farm] [/require:on | off] [/logging:on | off]
acrcfg [/server:servername] [/inherit:on | off] [/require:on | off]
[/logging:on | off]
acrcfg [/?]
Parameters
servername
The name of a server running MetaFrame Presentation Server.
Options
/query, /q
Query current settings.
/server
The server to be viewed or modified by the other command line options. The
server specified by servername must be in the same server farm as the server on
which the command is run. This option and the /farm option are mutually
exclusive. The local server is the default if neither /server nor /farm is indicated.
/farm
The options on the command line after /farm are applied to the entire server
farm.
/inherit:on | off
To use the auto client reconnect settings from the server farm set /inherit to on
for a server. To disregard the server farm auto client reconnect settings, set
/inherit to off. By default, /inherit is set to on for a server.
336 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
/require:on | off
If you want users to be prompted for credentials during automatic reconnection,
set /require to on. Servers inherit the server farm setting unless /inherit is off. To
allow users to automatically reconnect to disconnected sessions without
providing credentials, set /require to off. By default, /require is set to off for
both a server and a server farm.
/logging:on | off
You can enable logging of client reconnections in the Application Event Log on
a server. Logging can be set only when /required is set to off. Logging is set to
off for both servers and server farms by default.
/?
Displays the syntax for the utility and information about the utility’s options.
Remarks
Enabling automatic client reconnection allows users to resume working where they
were interrupted when an ICA connection was broken. Automatic reconnection
detects broken connections and then reconnects the users to their sessions.
However, automatic reconnection can result in a new ICA session being launched
(instead of reconnecting to an existing session) if a client’s cookie, containing the
key to the session ID and credentials, is not used. The cookie is not used if it has
expired, for example, because of a delay in reconnection, or if credentials must be
reentered because /require is set to on. Auto client reconnection is not triggered if
users intentionally disconnect.
The auto client reconnect feature is enabled by default and can be disabled using
Appsrv.ini or an ICA file only on the Client for Win32 or with the Web Interface for
MetaFrame Presentation Server.
The /require and /logging options are valid with either /server or /farm, but /inherit
is not used with /farm. If neither /server nor /farm is selected and the /inherit,
/require, or /logging options are used, they are applied to the local server. You can
set /require only when /inherit is set to off. You can set logging only when /require
and /inherit are set to off. When logging is not valid, it disappears from later
queries. A query shows the required setting whether or not it is on.
Settings and values are not case sensitive.
Go to Document Center Appendix A MetaFrame Presentation Server Commands 337
Examples
The following four commands result in the following configurations:
• Require users to enter credentials when they automatically reconnect to servers
configured to inherit farm-wide settings
• Show the results
• Allow users to be reauthenticated automatically to the local server and set the
server to log client reconnections
• Show the results
C:\>acrcfg /farm /require:on
Update successful
C:\>acrcfg /farm /q
Auto Client Reconnect Info for: Farm-wide Settings
REQUIRE: on
C:\>acrcfg /inherit:off /require:off /logging:on
Update successful
C:\>acrcfg /q
Auto Client Reconnect Info for: Local Server
INHERIT: off
REQUIRE: off
LOGGING: on
Security Restrictions
You must be a MetaFrame administrator to make changes.
338 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
AIERUN
Use aierun to launch an application into an isolation environment.
Syntax
aierun [/w] AIE_Name Application [application parameters]
aierun [/?]
Parameters
AIE_Name
The name of an isolation environment.
Application
The name of the application to launch in the named isolation environment. You
can also append application parameters, if any.
Options
/w
Waits for the application launched by aierun to exit before continuing. This
option is useful when aierun is used in a script or batch file.
/?
Displays the syntax for the command and information about the command
options.
Remarks
aierun is an internal launcher used by MetaFrame Presentation Server during
application launching.
Use of aierun from a desktop session is not supported.
Security Restrictions
None.
Go to Document Center Appendix A MetaFrame Presentation Server Commands 339
AIESETUP
Use aiesetup to install an application into an isolation environment.
Syntax
aiesetup [/d] [/n] [/q] [/w] AIE_Name Setup_application [application parameters]
aiesetup [/?]
Parameters
AIE_Name
The name of an isolation environment.
Setup_application
The name of an application installer, such as an .msi or .exe, to run. You can
also append any parameters that the installer is required to process at runtime.
When using aiesetup with an .msi file, use msiexec.exe with the /i option.
Options
/d
Disables the automatic application discovery process for the isolation
environment.
/n
Disables automatically setting the Windows server to install mode (through the
change user install command).
/q
Installs the application in quiet mode and does not require user intervention,
such as pressing Enter to begin discovery prompt. This is useful in automated
application deployments, such as when using Installation Manager.
/w
Waits for the application launched by aiesetup to exit before continuing. This
option is useful when aiesetup is used in a script or batch file.
/?
Displays the syntax for the command and information about the command
options.
340 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
Usage
aiesetup launches the specified application installer and forces the application to
install within the specified isolation environment.
At runtime, if you did not use the /d option, aiesetup displays the following message
at a command prompt:
Press <Enter> to start the application discovery process when
application installation completes.
Press Q to skip application discovery and quit.
When installation is complete, the silent application discovery process is invoked.
The application discovery process locates application shortcuts added by the
installer and adds the information to the data store. Data collected by the application
discovery process facilitates publishing of applications installed in an isolation
environment.
Press Q to omit the application discovery process if it is not already running and
return to a command prompt. Alternatively, you can use the /d option with aiesetup
to omit the application discovery process.
Remarks
Application isolation functionality includes the ability to install applications into an
isolation environment as well as uninstall applications installed into an isolation
environment. This is useful in cases when different versions of an application
cannot be installed on a single server.
To install an application into an isolation environment, follow the procedure
outlined below.
1. Create an isolation environment with isolation rules as appropriate. For
information about creating isolation environments, see “Creating an Isolation
Environment” on page 255. For information about configuring isolation
environment rules, see online help for the Presentation Server Console.
2. Ready a copy of the MSI or EXE file for the application to be installed into the
isolation environment.
Go to Document Center Appendix A MetaFrame Presentation Server Commands 341
Security Restrictions
To execute aiesetup, you must be a MetaFrame administrator with the permissions
to perform all of the following tasks:
• Manage isolation environments for the farm
• Publish applications and edit properties for the farm
Run the aiesetup command on the server where you are installing the application.
Citrix does not support installing an application into an isolation environment
through a connection made with Remote Desktop Connection.
342 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
ALTADDR
Use altaddr to query and set the alternate (external) IP address for a server running
MetaFrame Presentation Server. The alternate address is returned to clients that
request it and is used to access a server that is behind a firewall.
Syntax
altaddr [/server:servername] [/set alternateaddress ] [/v]
altaddr [/server:servername] [/set adapteraddress alternateaddress] [/v]
altaddr [/server:servername] [/delete] [/v]
altaddr [/server:servername] [/delete adapteraddress] [/v]
altaddr [/?]
Parameters
servername
The name of a server.
alternateaddress
The alternate IP address for a server.
adapteraddress
The local IP address to which an alternate address is assigned.
Options
/server:servername
Specifies the server on which to set an alternate address. Defaults to the current
server.
/set
Sets alternate TCP/IP addresses. If an adapteraddress is specified,
alternateaddress is assigned only to the network adapter with that IP address.
/delete
Deletes the default alternate address on the specified server. If an adapter
address is specified, the alternate address for that adapter is deleted.
/v (verbose)
Displays information about the actions being performed.
Go to Document Center Appendix A MetaFrame Presentation Server Commands 343
/?
Displays the syntax for the utility and information about the utility’s options.
Remarks
The server subsystem reads the altaddr settings for server external IP addresses at
startup only. If you use altaddr to change the IP address setting, you must restart the
IMA Service for the new setting to take effect.
If altaddr is run without any parameters, it displays the information for alternate
addresses configured on the current server.
Examples
Set the server’s alternate address to 1.1.1.1:
altaddr /set 1.1.1.1
Set the server’s alternate address to 2.2.2.2 on the network interface card whose
adapter address is 1.1.1.1:
altaddr /set 2.2.2.2 1.1.1.1
Security Restrictions
None.
344 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
APP
App is a script interpreter for secure application execution. Use App to read
execution scripts that copy standardized .ini type files to user directories before
starting an application, or to perform application-related cleanup after an
application terminates. The script commands are described below.
Syntax
app scriptfilename
Parameter
scriptfilename
The name of a script file containing app commands (see script commands
below).
Remarks
If no scriptfilename is specified, app displays an error message.
The Application Execution Shell reads commands from the script file and processes
them in sequential order. The script file must reside in the %SystemRoot%\Scripts
directory.
Script Commands
The script commands are:
copy sourcedirectory\filespec targetdirectory
Copies files from sourcedirectory to targetdirectory. Filespec specifies the files
to copy and can include wild cards (*,?).
delete directory\filespec
Deletes files owned by a user in the directory specified. Filespec specifies the
files to delete and can include wild cards (*,?). See the Examples section for
more information.
deleteall directory\filespec
Deletes all files in the directory specified.
execute
Executes the program specified by the path command using the working
directory specified by the workdir command.
Go to Document Center Appendix A MetaFrame Presentation Server Commands 345
path executablepath
Executablepath is the full path of the executable to be run.
workdir directory
Sets the default working directory to the path specified by directory.
Script Parameters
directory
A directory or directory path.
executablepath
The full path of the executable to be run.
filespec
Specifies the files to copy and can include wildcards (*,?).
sourcedirectory
The directory and path from which files are to be copied.
targetdirectory
The directory and path to which files are to be copied.
Examples
The following script file runs the program Sol.exe:
PATH C:\Wtsrv\System32\Sol.exe
WORKDIR C:\Temp
EXECUTE
The following script file runs the program Notepad.exe. When the program
terminates, the script deletes files in the Myapps\Data directory created for the user
who launched the application:
PATH C:\Myapps\notepad.exe
WORKDIR C:\Myapps\Data
EXECUTE
DELETE C:\Myapps\Data\*.*
The following script file copies all the .wri files from the directory C:\Write\Files,
executes Write.exe in directory C:\Temp.wri, and then removes all files from that
directory when the program terminates:
PATH C:\Wtsrv\System32\Write.exe
WORKDIR C:\Temp.wri
COPY C:\Write\Files\*.wri C:\Temp.wri
EXECUTE
346 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
DELETEALL C:\Temp.wri\*.*
The following example demonstrates using the script file to implement a front-end
registration utility before executing the application Coolapp.exe. You can use this
method to run several applications in succession:
PATH C:\Regutil\Reg.exe
WORKDIR C:\Regutil
EXECUTE
PATH C:\Coolstuff\Coolapp.exe
WORKDIR C:\Temp
EXECUTE
DELETEALL C:\Temp
Security Restrictions
None.
Go to Document Center Appendix A MetaFrame Presentation Server Commands 347
APPUTIL
Use apputil to add servers to the Configured Servers list for a published application,
and to install or uninstall Installation Manager packages or package groups on
specified servers.
Syntax
apputil [ /? ]
apputil [ /q ]
apputil [ /i applicationID servername ]
apputil [ /u applicationID servername ]
apputil [ /qj jobID]
apputil [ /qp ]
apputil [ /ip packageID servername [reboot] ]
apputil [ /up packageID servername [reboot] ]
Parameters
applicationID
The ID of a published application, as displayed by the /q option.
servername
For the /i and /u options, this is the name of the server to add to the Configured
Servers list for the published application. For the /ip and /up options, this is the
name of the server that the Installation Manager package or package group will
be installed on or uninstalled from.
jobID
The ID of job that installs or uninstalls an Installation Manager package or
package group.
packageID
The ID of an Installation Manager package or package group, as displayed by
the /qp option.
Options
/?
Display the syntax for the utility and information about the utility’s options.
348 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
/q
Queries a list of all available published applications, published desktops, and
published applications bundled into Installation Manager packages.
/i
Add a server to the Configured Servers list for a specified published application.
You can use the /i option with the following types of published resources:
• Standard published applications. Note that any server-specific overrides
you configure when you publish the application (such as overrides to the
command line and working directory entries) are not applied to the specified
server when it is added to the Configured Servers list. To use the /i option
with the published application, be sure that the target application is located
in the default location you specify when you published the application.
• Published server desktops.
• Installation Manager packages. When you run apputil for published
applications associated with Installation Manager packages, the packaged
application is scheduled for immediate installation on the target host, and the
server is added to the Configured Servers list for the published application.
/u
Remove a server from the Configured Servers list for a specified Published
Application. Note that if the application published an Installation Manager
package, that package is not uninstalled from the target host.
/qj
Query the status of a specified job. Typically, a job’s status progresses from
Pending to Started to Success.
/qp
Query a list of all available Installation Manager packages and package groups.
/ip
Schedule the installation of an Installation Manager package or package group
on a specified server. Use reboot to force the server to restart after the job
completes.
/up
Schedule the uninstall of an Installation Manager package or package group on
a specified server. Use reboot to force the server to restart after the job
completes.
Go to Document Center Appendix A MetaFrame Presentation Server Commands 349
Remarks
You must run this utility from a server running MetaFrame Presentation Server
Enterprise Edition and Installation Manager.
When you use the /i option with an Installation Manager package, an unnamed
Installation Manager job is created. When the job completes successfully,
connections to the published application are enabled on the server.
When you use the Presentation Server Console to manually add servers to the
Configured Servers list for Installation Manager packages, or install and uninstall
packages or package groups, you can schedule when this should occur. However,
when you use the apputil utility, these tasks are scheduled immediately.
If an error occurs during execution of the utility, the process exit code “1” is
returned. Apputil returns “0” on success.
Examples
The following examples display the correct syntax and usage for the apputil utility.
C:\>apputil /q
Available published applications: 3.
Application ID Type Description
2e0e-0009-000010a9 Application Word
2e0e-0009-000010ac Desktop Desktop
2e0e-0009-000010af Package Acrobat Reader
C:\>apputil /qp
There are 2 packages and package groups available.
Package ID Type Description
05d1-007a-00000301 Package Group Accounts Package Group
05d1-0037-00000300 Package Acrobat Reader
Security Restrictions
To run this utility, you must be a MetaFrame administrator with the permissions to
perform the following tasks:
• To use the /q option, you must at least have permission to view published
applications and content.
• To use the /i or /u options for published applications and published desktops,
you must have permission to view published applications, to publish
applications, and to edit a published application’s properties.
• To use the /i option for Installation Manager packaged applications, you must
have permission to edit Installation Manager, in addition to the permissions
described above.
• To use the /qp and /qj options, you must have View Installation Manager
permission.
To use the /ip and /up options for Installation Manager packages or package groups,
you must have Install and Uninstall Packages permission.
Go to Document Center Appendix A MetaFrame Presentation Server Commands 351
AUDITLOG
Auditlog generates reports of logon/logoff activity for a server based on the
Windows NT Server security event log. To use auditlog, you must first enable
logon/logoff accounting. You can direct the auditlog output to a file.
Syntax
auditlog [username | session] [/eventlog:filename] [/before:mm/dd/yy]
[/after:mm/dd/yy] [[/write:filename] | [/detail | /time] [/all]]
auditlog [username | session] [/eventlog:filename] [/before:mm/dd/yy]
[/after:mm/dd/yy] [[/write:filename] | [/detail] | [/fail ] | [ /all]]
auditlog [/clear:filename]
auditlog [/?]
Parameters
filename
The name of the eventlog output file.
session
Specifies the session ID for which to produce a logon/logoff report. Use this
parameter to examine the logon/logoff record for a particular session.
mm/dd/yy
The month, day, and year (in two-digit format) to limit logging.
username
Specifies a user name for which to produce a logon/logoff report. Use this
parameter to examine the logon/logoff record for a particular user.
Options
/eventlog:filename
Specifies the name of a backup event log to use as input to auditlog. You can
back up the current log from the Event Log Viewer by using
auditlog /clear:filename.
/before:mm/dd/yy
Reports on logon/logoff activity only before mm/dd/yy.
/after:mm/dd/yy
Reports on logon/logoff activity only after mm/dd/yy.
352 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
/write:filename
Specifies the name of an output file. Creates a comma-delimited file that can be
imported into an application, such as a spreadsheet, to produce custom reports
or statistics. It generates a report of logon/logoff activity for each user,
displaying logon/logoff times and total time logged on.
If filename exists, the data is appended to the file.
/time
Generates a report of logon/logoff activity for each user, displaying logon/logoff
times and total time logged on. Useful for gathering usage statistics by user.
/fail
Generates a report of all failed logon attempts.
/all
Generates a report of all logon/logoff activity.
/detail
Generates a detailed report of logon/logoff activity.
/clear:filename
Saves the current event log in filename and clears the event log. This command
does not work if filename already exists.
/?
Displays the syntax for the utility and information about the utility’s options.
Remarks
Auditlog provides logs you can use to verify system security and correct usage. The
information can be extracted as reports or as comma-delimited files that can be used
as input to other programs.
You must enable logon/logoff accounting on the local server to collect the
information used by auditlog. To enable logon/logoff accounting, log on as a local
administrator and enable logon/logoff accounting with the Audit Policy in
Microsoft Windows.
Security Restrictions
None.
Go to Document Center Appendix A MetaFrame Presentation Server Commands 353
CHANGE CLIENT
Change client changes the current disk drive, COM port and LPT port mapping
settings for a client device.
Syntax
change client [/view | /flush | /current]
change client [{/default | [/default_drives] | [/default_printers]} [/ascending]]
[/noremap] [/persistent] [/force_prt_todef]
change client [/delete host_device] [host_device client_device] [/?]
Parameters
host_device
The name of a device on the host server to be mapped to a client device.
client_device
The name of a device on the client to be mapped to host_device.
Options
/view
Displays a list of all available client devices.
/flush
Flushes the client drive mapping cache. This action forces the server and the
client to resynchronize all disk data. See Remarks for more information.
/current
Displays the current client device mappings.
/default
Resets host drive and printer mappings to defaults.
/default_drives
Resets host drive mappings to defaults.
/default_printers
Resets host printer mappings to defaults.
354 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
/ascending
Uses ascending, instead of descending, search order for available drives and
printers to map. This option can be used only with /default, /default_drives, or
/default_printer.
/noremap
If /noremap is specified, client drives that conflict with server drives are not
mapped.
/persistent
Saves the current client drive mappings in the client device user’s profile.
/force_prt_todef
Sets the default printer for the client session to the default printer on the client’s
Windows desktop.
/delete host_device
Deletes the client device mapping to host_device.
/? (help)
Displays the syntax for the utility and information about the utility’s options.
Remarks
Typing change client with no parameters displays the current client device
mappings; it is equivalent to typing change client /current.
Use change client host_device client_device to create a client drive mapping. This
maps the client_device drive letter to the letter specified by host_device; for
example, change client v: c: maps client drive C to drive V on the server.
The /view option displays the share name, the share type, and a comment describing
the mapped device. Sample output for change client /view follows:
C:>change client /view
Available Shares on client connection ICA-tcp#7
The /flush option flushes the client drive cache. This cache is used to speed access
to client disk drives by retaining a local copy of the data on the server running
MetaFrame Presentation Server. The time-out for hard drive cache entries is ten
minutes and the time-out for diskette data is five seconds. If the client device is
using a multitasking operating system and files are created or modified, the server
does not know about the changes.
Flushing the cache forces the data on the server to be synchronized with the client
data. The cache time-out for diskettes is set to five seconds because diskette data is
usually more volatile; that is, the diskette can be removed and another diskette
inserted.
The /default option maps the drives and printers on the client device to mapped
drives and printers on the server running MetaFrame Presentation Server. Drives A
and B are always mapped to drives A and B on the server. Hard drives are mapped
to their corresponding drive letters if those drive letters are available on the server.
If the corresponding drive letter is in use on the server, the default action is to map
the drive to the highest unused drive letter. For example, if both machines have
drives C and D, the client drives C and D are mapped to V and U respectively.
These default mappings can be modified by the /ascending and /noremap options.
The /default_printers option resets printer mappings to defaults. /default_printers
attempts a one-to-one mapping of all client printers; for example, the client’s LPT1
and LPT2 ports are mapped to the server’s LPT1 and LPT2 ports. If the /ascending
option is specified, the mapping is done in ascending order.
The /default_drives option resets host drive mappings to defaults. /default_drives
attempts a one-to-one mapping of all client drives; for example, client drives A and
B are mapped to server drives A and B. Hard drives are mapped to their
corresponding drive letters if those drive letters are available on the server. If the
corresponding drive letter is in use on the server, the default action is to map the
drive to the highest unused drive letter. For example, if both machines have drives
C and D, the client drives C and D are mapped to V and U respectively. If the
/ascending option is specified, the mapping is done in ascending order.
The /ascending option causes the mapping to occur in ascending drive letter order.
For example, if the first two available drive letters on the server are I and J, drives C
and D in the preceding example are mapped to I and J respectively.
The /noremap option causes the mapping to skip drive letters occupied on the
server. For example, if the server has a drive C but no drive D , the client’s drive C
is mapped to D on the server, but the client’s drive D is not mapped.
356 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
The /persistent option causes the current device mappings to be saved in the user’s
profile. Drive conflicts can occur if the /persistent option is in use and the user logs
on from a client device that has a different disk drive configuration, or logs on to a
server that has a different disk drive configuration.
The /force_prt_todef option sets the default printer for the ICA session to the
default printer on the client’s Windows desktop.
Security Restrictions
None.
Go to Document Center Appendix A MetaFrame Presentation Server Commands 357
CHFARM
Change farm is used to change the farm membership of a server.
Syntax
chfarm
Remarks
You can use chfarm when you want to move a server from its current server farm.
You can move the server to an existing IMA-based server farm or create a new
server farm at the same time that you move the server. Citrix recommends that you
back up your data store before running chfarm.
Important If the server you want to move provides information for a Resource
Manager summary database, update the summary database before using chfarm. If
you do not update the summary database, you will lose approximately 24 hours
worth of summary data stored on the server. To update the summary database, click
the Resource Manager node in the Presentation Server Console, select the
Summary Database tab, and click Update Now.
CAUTION Be sure that the Presentation Server Console is closed before you run
the chfarm command. Running chfarm while the console is open can result in loss
of data and functionality.
Chfarm stops the IMA service on the server. The data store configuration part of the
MetaFrame Presentation Server Setup wizard appears. On the first page, you can
select to join an existing server farm or create a new server farm.
The wizard continues and you specify an existing data store (to join an existing
server farm) or set up a new data store (if you create a new server farm). While
running chfarm, you are prompted for the user name and password of the user you
want to designate as the initial MetaFrame administrator for the farm. For
information about data store setup and server farm configuration, see “The Farm
Data Store” on page 39.
If chfarm reports any error, continuing the process can corrupt the data store. If you
cancel the data store configuration part of the MetaFrame Presentation Server Setup
wizard, the server you are switching rejoins the original farm.
After the farm membership is changed or a new farm is created, restart the server.
358 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
Do not remove a server that hosts a server farm’s data store from the server farm,
unless all other servers are removed first. Doing so renders the farm unstable.
Note You cannot migrate a database to the same named instance of MSDE that is
already in use. If you are already using MSDE and you want to migrate to a new
farm using MSDE, you must either migrate to another database (Access or a third
party database) and then back to MSDE, or install another named instance of
MSDE and then launch chfarm with the /instancename option.
To move a server to a new server farm using MSDE as the data store
1. Create a named instance of MSDE by installing MSDE on the first server in the
new farm.
2. Run chfarm on the server that you want to use to create the new farm using the
/instancename:<name> option, where <name> is the name of the instance of
MSDE you created in Step 1.
Go to Document Center Appendix A MetaFrame Presentation Server Commands 359
CLTPRINT
Use cltprint to set the number of printer pipes for the client print spooler.
Syntax
cltprint [/q] [/pipes:nn] [/?]
Options
/q
Displays the current number of printer pipes.
/pipes:nn
Sets the specified number of printer pipes. This number represented by nn must
be from 10 to 63.
/?
Displays the syntax for the utility and information about the utility’s options.
Remarks
Printer pipes are used to send data from applications to client print spoolers. The
number of pipes specifies the number of print jobs that can be sent to the spooler
simultaneously.
The default number of printer pipes is ten.
The Spooler service must be stopped and restarted after changing the number of
pipes. Print jobs already spooled continue printing.
Print jobs sent to the spooler trigger an error message while the service is stopped.
Make sure no users start printing during the time the Spooler service is stopped.
Security Restrictions
None.
Go to Document Center Appendix A MetaFrame Presentation Server Commands 361
CTXXMLSS
Use ctxxmlss to change the Citrix XML Service port number.
Syntax
ctxxmlss [/rnnn] [/u] [/knnn] [/?]
Options
/rnnn
Changes the port number for the Citrix XML Service to nnn.
/u
Unloads Citrix XML Service from memory.
/knnn
Keeps the connection alive for nnn seconds. The default is nine seconds.
/?
Displays the syntax for the utility and information about the utility’s options.
Remarks
For more information, see “Configuring the Citrix XML Service Port” on page 134.
Security Restrictions
None.
362 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
DRIVEREMAP
Use the driveremap utility to change the server’s drive letters. MetaFrame
Presentation Server Setup installs the driveremap utility in C:\Program
Files\Citrix\System32.
Syntax
driveremap /?
driveremap /dbscript:filename
driveremap /drive:M
driveremap /u
driveremap /noreboot
driveremap /IME
Options
The following parameters can be used with driveremap at a command line.
/?
Displays the syntax for the utility and information about the utility’s options.
Go to Document Center Appendix A MetaFrame Presentation Server Commands 363
/dbscript:filename
Sets the path to Fixsecuritydatabase.cmd to filename. For Windows Server
2003, the Fixsecuritydatabase utility is run to update drive information in the
Windows security database after you remap the system drive.
Fixsecuritydatabase in not needed for Windows 2000 Server.
If you run driveremap from a location other than the MetaFrame Presentation
Server CD, use the /dbscript switch to specify the path to
Fixsecuritydatabase.cmd. If you copy Fixsecuritydatabase.cmd to a folder with
the same relative location to Driveremap.exe as on the MetaFrame Presentation
Server CD (\Support\Install\Fixsecuritydatabase.cmd), you do not need to
specify a new path with the \dbscript switch.
After remapping drives on Windows Server 2003, ensure that you restart the
server and log on with an administrator account that has read access to the
Fixsecuritydatabase.cmd file specified by /dbscript.
/drive:M
Specifies the drive letter to use for the first remapped drive.
/u
Permits unattended or silent installation where no dialog boxes are displayed
and no user input is required. You must use this option in conjunction with the
/drive: option.
/noreboot
Surpresses the Restart Computer message and does not restart the system. Citrix
strongly recommends that you restart the system after running this utility.
/ime[filename]
Changes the drive letter specified in
Software\Microsoft\Windows\CurrentVersion\Ime\Japan\IMEJP\Dictionaries
for all of the loaded hives under HKEY_USERS.
Remarks
The Drive Remapping utility allows you to select the drive letters you want to map.
Before installation, you can run the Drive Remapping utility from the Autorun
screens of the MetaFrame Presentation Server CD. After installing MetaFrame
Presentation Server, you can open the utility by running Driveremap.exe with no
parameters.
364 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
CAUTION Do not run Driveremap within an ICA session or RDP session, for
example from a command prompt of a server desktop published as an application.
Running Driveremap in an ICA session or RDP session can cause the server to
become unstable.
Examples
The following command remaps the server’s drive letters. The first available drive
is changed to M. The command uses the noreboot option, which suppresses the
appearance of any dialog boxes.
driveremap /u /drive:M /noreboot
The following command returns the server’s drive letters to the drive letters that
start at C and then prompts you to restart the server.
driveremap /u /drive:M /drive:C
Known Issues
The following items are known issues you may encounter when running the
driveremap utility.
• When running driveremap with no parameters, the drive letter choices in the
drop-down list may be greyed out. This can occur if the server has non-
contiguous drive letters, for example, C, D, X. The mapped drive letters are
spread over the interval [a..z] and no reasonable interval shifting can be
performed. Network drives are also taken into account.
To work around this issue, change the drive letters to C, D, and E and then run
the driveremap utility.
• At a command prompt, if you remap to a letter that is in use, nothing happens
and you are returned to the prompt. Locate the server’s drive letters in Windows
Explorer to verify that the drive letters are changed.
• MetaFrame Presentation Server drive remapping is not supported on Windows
2000 Dynamic Disks.
• Installation of the Web Interface on a server running MetaFrame Presentation
Server may fail if you are upgrading a server with remapped drives. See article
CTX240747 in the online Citrix Knowledge Base at http://support.citrix.com
for more information.
• If you upgrade from MetaFrame 1.8 to MetaFrame Presentation Server on a
server with changed server drive letters, the Win32 Pass-Through Client is not
updated. To avoid this issue, be sure the server is operating in install mode
before running Setup.
Go to Document Center Appendix A MetaFrame Presentation Server Commands 365
Security Restrictions
Only MetaFrame administrators can execute this command.
366 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
DSCHECK
Use dscheck to validate the consistency of the database used to host the server
farm’s data store. You can then repair any inconsistencies found.
Syntax
dscheck [/clean] [/?]
Options
/clean
Attempts to fix any consistency error that is found.
/?
Displays the syntax for the utility and information about the utility’s options.
Remarks
Dscheck performs a variety of tests to validate the integrity of a server farm’s data
store. When run without parameters, only these tests are run. Run dscheck on a
server in the farm that has a direct connection to the data store.
When you run dscheck with the /clean option, the utility runs tests and removes
inconsistent data (typically servers and applications) from the data store. Because
removing this data can affect the farm’s operation, be sure to back up the data store
before using the /clean option. Contact Citrix Technical Support for assistance in
restoring a backed up data store.
When you run the utility with the /clean option, you may need to run the dsmaint
command with the recreatelhc parameter on each server in the farm to update the
local host caches. Running this command sets the PSRequired registry value to 1 in
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\IMA\Runtime.
Dscheck reports the results of the tests in several ways. First, dscheck sends any
errors found as well as a summary to the event log and to the command window.
You can also write the output produced by dscheck to a file.
Second, several performance monitor values are updated under the performance
object for Citrix MetaFrame Presentation Server. These values include a count of
server errors, a count of application errors, a count of group errors, and an overall
flag indicating that errors were detected. The performance monitor values can be
used with Resource Manager to detect when problems are present.
Third, dscheck returns an error code of 0 for a successful scan (no errors are found)
and an error code of 1 if any problems are encountered.
Go to Document Center Appendix A MetaFrame Presentation Server Commands 367
Dscheck looks primarily at three data store objects: servers, applications, and
groups. For each of these object types, dscheck performs a series of tests on each
object instance.
For example, for each server object in the data store, dscheck verifies that there is a
corresponding common server object and then further verifies that both objects
have matching host IDs and host names.
Examples
To run consistency checks only:
dscheck
To check consistency and fix errors:
dscheck /clean
Security Restrictions
To run this utility, you must have direct access to the data store.
368 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
DSMAINT
Use dsmaint to configure the IMA data store for a server farm.
When using this command, user names and passwords may be case-sensitive,
depending on the database product you are using and the operating system on which
it runs.
Syntax
dsmaint config [/user:username] [/pwd:password] [/dsn:filename]
dsmaint backup destination_path
dsmaint failover direct_server
dsmaint compactdb [/ds] [/lhc]
dsmaint migrate [{ /srcdsn:dsn1 /srcuser:user1 /srcpwd:pwd1}] [{/dstdsn:dsn2
/dstuser:user2 /dstpwd:pwd2}]
dsmaint publishsqlds {/user:username /pwd:password}
dsmaint recover
dsmaint recreatelhc
dsmaint verifylhc [/autorepair]
dsmaint [/?]
Parameters
destination_path
Path to the backup data store.
dsn1
The name of the source data store.
dsn2
The name of the destination data store
filename
The name of the data store.
direct_server
The name of the new direct server for IMA data store operations.
password
The password to connect to the data store.
Go to Document Center Appendix A MetaFrame Presentation Server Commands 369
pwd1
The source data store password.
pwd2
The destination data store password.
user1
The source data store user logon.
user2
The destination data store user logon.
username
The name of the user to use when connecting to the data store.
Options
config
Changes configuration parameters used by IMA to connect to the data store.
/user:username
The username to connect to a data store.
/pwd:password
The password to connect to a data store.
/dsn:filename
The filename of an IMA data store.
backup
Creates a backup copy of the Access database that is the farm’s data store. Run
this command on the server that hosts the data store. Requires a path or share
point to which the database file will be copied. The backup command cannot be
used to create backups for Oracle or SQL data stores.
failover
Switches the server to use a new direct server for IMA data store operations.
compactdb
Compacts the Access database file.
/ds
Specifies the database is to be compacted immediately. If the IMA service
is running, this can be executed from the direct server or an indirect server.
If the IMA service is not running, this can be executed only on the direct
server.
370 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
/lhc
Specifies the local host cache is to be compacted immediately.
migrate
Migrates data from one data store database to another. Use this command to
move a data store to another server, rename a data store in the event of a server
name change, or migrate the data store to an Oracle, SQL Server, or DB2
database.
/srcdsn:dsn1
The name of the data store from which to migrate data.
/srcuser:user1
The user name to use to connect to the data store from which the data is
migrating.
/srcpwd:pwd1
The password to use to connect to the date store from which the data is
migrating.
/dstdsn:dsn2
The name of the data store to which to migrate the data.
/dstuser:user2
The user name that allows you to connect to the data store to which you are
migrating the source data store.
/dstpwd:pwd2
The password that allows you to connect to the data store to which you are
migrating the source data store.
publishsqlds
Publishes a data store to allow replication.
recover
Restores an Access data store to its last known good state. This must be
executed on the direct server while the IMA service is not running.
recreatelhc
Recreates the local host cache database.
verifylhc
Verifies the integrity of a Microsoft Access local host cache. If the local host
cache is corrupt, you are prompted with the option to recreate it. With the
verifylhc /autorepair option, the local host cache is automatically recreated if it
is found to be corrupted.
/?
Displays the syntax for the utility and information about the utility’s options.
Go to Document Center Appendix A MetaFrame Presentation Server Commands 371
Remarks
compactdb
During database compaction, the database is temporarily unavailable for both
reading and writing. The compaction time can vary from a few seconds to a few
minutes, depending on the size of the database and the usage.
config
For Access databases, this command resets the password used to protect the
database, setting the matched security context to allow IMA access to this
database.
You must stop the IMA service before using config with the /pwd option.
CAUTION You must specify a /dsn for dsmaint config or you will change the
security context for access to the SQL or Oracle database.
migrate
Existing data store databases can be migrated to a different database software.
For example, you can create a farm with an Access database and later migrate
the farm data store to a SQL Server database. For more information about
migrating the data store to a different database software and which migrations
are supported, see “The Farm Data Store” on page 39.
Important By default, the Access database does not have a user name or
password. When migrating a database from Access, leave the /srcuser: and
/srcpwd: parameters blank.
The connection to a local Access database is based on the host server’s name. If
the name of the server changes, use migrate to change the name of the database.
publishsqlds
Execute publishsqlds only from the server that created the farm. The publication
will be named MFXPDS.
Security Restrictions
The dsmaint config and dsmaint migrate commands can be executed only by a user
with the correct user name and password for the database.
372 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
ICAPORT
Use icaport to query or change the TCP/IP port number used by the ICA protocol
on the server.
Syntax
icaport {/query | /port:nnn | /reset} [/?]
Options
/query
Queries the current setting.
/port:nnn
Changes the TCP/IP port number to nnn.
/reset
Resets the TCP/IP port number to 1494, which is the default.
/?
Displays the syntax for the utility and information about the utility’s options.
Remarks
The default port number is 1494. The port number must be in the range of 0–65535
and must not conflict with other well-known port numbers.
If you change the port number, restart the server for the new value to take effect. If
you change the port number on the server, you must also change it on every client
that will connect to that server. For instructions for changing the port number on
clients, see the Administrator’s Guide for the clients that you plan to deploy.
Examples
To set the TCP/IP port number to 5000:
icaport /port:5000
To reset the port number to 1494:
icaport /reset
Security Restrictions
Only MetaFrame administrators can run icaport.
Go to Document Center Appendix A MetaFrame Presentation Server Commands 373
IMAPORT
Use imaport to query or change the IMA port.
Important When you run MetaFrame Presentation Server Setup, Setup references
port 2513 for communication with the Presentation Server Console. If you change
this port number on the first server in the farm on which you install MetaFrame
Presentation Server, you cannot join additional servers to the server farm.
Syntax
imaport {/query | /set {IMA:nnn | ds:nnn | cmc:nnn}* | /reset {IMA | DS | CMC |
ALL} } [/?]
Options
/query
Queries the current setting.
/set
Sets the designated TCP/IP port(s) to a specified port number.
ima:nnn
Sets the IMA communication port to a specified port number.
cmc:nnn
Sets the Presentation Server Console connection port to a specified port
number.
ds:nnn
Sets the data store server port to a specified port number (indirect servers
only).
/reset
Resets the specified TCP/IP port to the default.
ima
Resets the IMA communication port to 2512.
cmc
Resets the Presentation Server Console connection port to 2513.
ds
Resets the data store server port to 2512 (indirect servers only).
all
Resets all of the applicable ports to the defaults.
374 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
/?
Displays the syntax for the utility and information about the utility’s options.
Go to Document Center Appendix A MetaFrame Presentation Server Commands 375
MIGRATETOMSDE
Use migratetomsde to migrate a server farm’s data store from Microsoft Access to
Microsoft SQL Server 2000 Database Engine (MSDE).
Migratetomsde offers fail-safe operation and automatically rolls back any changes
that it makes to the system in the event of any failures.
The utility is located on the MetaFrame Presentation Server CD in the
Support\MSDE directory.
Syntax
migratetomsde [/instancename:instancename | /dbname:dbname |
/accessuser:user | /accesspwd:pwd | /revert | [/?]
Options
/instancename:instancename
Specify a named instance of MSDE other than the default value of
CITRIX_METAFRAME.
/dbname:dbname
Specify a database other than the default value of MF20.
/accessuser:user
/accesspwd:pwd
Specify the user and pwd values for your Access database if you changed them
using the Dsmaint Config utility.
/revert
Reverts to the Access database originally used as the server farm’s data store.
Running this command restores backups that were made when the migration
was initially done. Any changes made to the farm since the migration from
Access to MSDE are lost.
/?
Displays the syntax for the utility and information about the utility’s options.
376 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
QUERY
Use query to display information about server farms, processes, servers, sessions,
terminal servers, and users within the network.
Query Farm
Syntax
query farm [server [/addr | /app | /app appname | /load]]
query farm [/tcp ] [ /ipx ] [ /netbios ] [ /continue ]
query farm [ /app | /app appname | /disc | /load | /process]
query farm [/online | /online zonename]
query farm [/offline | /offline zonename]
query farm [/zone | /zone zonename]
query farm [/?]
Parameters
appname
The name of a published application.
server
The name of a server within the farm.
zonename
The name of a zone within the farm.
Options
farm
Displays information about servers within an IMA-based server farm.You can
use qfarm as a shortened form of query farm.
server /addr
Displays address data for the specified server.
/app
Displays application names and server load information for all servers
within the farm or for a specific server.
Go to Document Center Appendix A MetaFrame Presentation Server Commands 377
/app appname
Displays information for the specified application and server load
information for all servers within the farm or for a specific server.
/continue
Do not pause after each page of output.
/disc
Displays disconnected session data for the farm.
/ipx
Displays IPX data for the farm.
/load
Displays server load information for all servers within the farm or for a
specific server.
/netbios
Displays NetBIOS data for the farm.
/process
Displays active processes for the farm.
/tcp
Displays TCP/IP data for the farm.
/online
Displays servers online within the farm and all zones. The data collectors are
represented by the notation “D.”
/online zonename
Displays servers online within a specified zone. The data collectors are
represented by the notation “D.”
/offline
Displays servers offline within the farm and all zones. The data collectors are
represented by the notation “D.”
/offline zonename
Displays servers offline within a specified zone. The data collectors are
represented by the notation “D.”
/zone
Displays all data collectors in all zones.
/zone zonename
Displays the data collector within a specified zone.
378 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
/?
Displays the syntax for the utility and information about the utility’s options.
Remarks
Query farm returns information for IMA-based servers within a server farm.
Security Restrictions
Only MetaFrame administrators can run query farm.
Query Process
Syntax
query process [ * | processid | username | sessionname | /id:nn
| programname ] [ /server:servername ] [ /system ]
query process [/?]
Parameters
*
Displays all visible processes.
processid
The three- or four-digit ID number of a process running within the farm.
programname
The name of a program within a farm.
servername
The name of a server within the farm.
sessionname
The name of a session, such as ica-tcp#7.
username
The name of a user connected to the farm.
Options
process
Displays information about processes running on the current server.
Go to Document Center Appendix A MetaFrame Presentation Server Commands 379
process *
Displays all visible processes on the current server.
process processid
Displays processes for the specified processid.
process username
Displays processes belonging to the specified user.
process sessionname
Displays processes running under the specified session name.
process /id:nn
Displays information about processes running on the current server by the
specified ID number.
process programname
Displays process information associated with the specified program name.
process /server:servername
Displays information about processes running on the specified server. If no
server is specified, the information returned is for the current server.
process /system
Displays information about system processes running on the current server.
/?
Displays the syntax for the utility and information about the utility’s options.
Security Restrictions
None.
Query Server
Syntax
query server [ server [/ping [/count:n] [/size:n] | /stats | /reset | /load
| /addr]]
query server [/tcp] [/ipx] [/netbios] [/tcpserver:x] [/ipxserver:x]
query server [/netbiosserver:x]
query server [/license | /app | /gateway | /serial | /disc | /serverfarm | /video]
query server [/continue] [/ignore] [/?]
380 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
Parameters
n
The number of times to ping a server (the default is five times) or the size of
ping buffers (the default is 256 bytes).
server
The name of a server within the farm.
x
The default TCP, IPX, or NetBIOS server address.
Options
server server
Displays transport information for the specified server.
/addr
Displays address information for the specified server.
/app
Displays application names and server load for the specified server.
/continue
Do not pause after each page of output.
/count:n
Number of times to ping the specified server.
/disc
Displays disconnected session data on the current server.
/gateway
Displays configured gateway addresses for the current server.
/ignore
Ignore warning message about interoperability mode.
/ipx
Displays IPX data for the current server.
/ipxserver:x
Defines the IPX default server address.
/license
Displays user licenses for the current server.
/load
Displays local data on the specified server.
/netbios
Displays NetBIOS data for the current server.
Go to Document Center Appendix A MetaFrame Presentation Server Commands 381
/netbiosserver:x
Defines the NetBIOS default server address.
/ping
Pings selected server. The default is five times.
/reset
Resets the browser statistics on the specified server.
/serial
Displays license serial numbers for the current server.
/serverfarm
Displays server farm names and server load.
/size:n
Size of ping buffers. The default is 256 bytes.
/stats
Displays the browser statistics on the specified server.
/tcp
Displays the TCP/IP data for the current server.
/tcpserver:x
Defines the TCP/IP default server address.
/?
Displays the syntax for the utility and information about the utility’s options.
Remarks
Query server displays data about only the servers present on a network within a
server farm running in interoperability mode. It shows every server within the farm,
even if the server is not currently connected to the farm. Query farm is the
recommended command for displaying this information in a farm that is not
running in interoperability mode.
Security Restrictions
None.
382 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
Query Session
Syntax
query session [sessionname | username | sessionid]
query session [/server:servername] [/mode] [/flow] [/connect] [/counter]
query session [/?]
Parameters
servername
The name of a server within the farm.
sessionname
The name of a session, such as “ica-tcp#7”.
sessionid
The two-digit ID number of a session.
username
The name of a user connected to the farm.
Options
session sessionname
Identifies the specified session.
session username
Identifies the session associated with the user name.
session sessionid
Identifies the session associated with the session ID number.
session /server:servername
Identifies the sessions on the specified server.
session /mode
Displays the current line settings.
session /flow
Displays the current flow control settings.
session /connect
Displays the current connection settings.
session /counter
Displays the current Terminal Services counter information.
Go to Document Center Appendix A MetaFrame Presentation Server Commands 383
/?
Displays the syntax for the utility and information about the utility’s options.
Security Restrictions
None.
Query Termserver
Syntax
query termserver [servername] [/domain:domain] [/address] [/continue]
query termserver [/?]
Parameters
servername
The name of a server within the farm.
domain
The name of a domain to query.
Options
termserver servername
Identifies a Terminal Server.
/address
Displays network and node addresses.
/continue
Do not pause after each page of output.
/domain:domain
Displays information for the specified domain. Defaults to the current
domain if no domain is specified.
/?
Displays the syntax for the utility and information about the utility’s options.
Remarks
If no parameters are specified, query termserver lists all Terminal Servers within the
current domain.
384 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
Security Restrictions
None.
Query User
Syntax
query user [ username | sessionname | sessionid ] [ /server:servername ]
query user [/?]
Parameters
servername
The name of a server within the farm.
sessionname
The name of a session, such as “ica-tcp#7”.
sessionid
The ID number of a session.
username
The name of a user connected to the farm.
Options
user username
Displays connection information for the specified user name.
user sessionname
Displays connection information for the specified session name.
user sessionid
Displays connection information for the specified session ID.
user /server:servername
Defines the server to be queried. The current server is queried by default.
/?
Displays the syntax for the utility and information about the utility’s options.
Go to Document Center Appendix A MetaFrame Presentation Server Commands 385
Remarks
If no parameters are specified, query user displays all user sessions on the current
server. You can use quser as a shortened form of the query user command.
Security Restrictions
None.
386 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
TWCONFIG
Use twconfig to configure ICA display settings that affect graphics performance for
clients.
Syntax
twconfig [/query | /q]
twconfig [/inherit:on | off]
twconfig [discard:on | off]
twconfig [/supercache:on | off]
twconfig [/maxmem:nnn]
twconfig [/degrade:res | color]
twconfig [/notify:on | off]
twconfig [/?]
Options
/query, /q
Query current settings.
/inherit:on | off
Set to on to use the ICA display properties defined for the farm. Set to off to use
the settings specified for this server. By default, this is set to on.
/discard:on | off
Discard redundant graphics operations.
/supercache:on | off
Use alternate bitmap caching method.
/maxmem:nnn
Maximum memory (in kilobytes) to use for each session’s graphics (150KB
minimum, 8192KB maximum).
/degrade:res | color
When the maxmem limit is reached, degrade resolution first or degrade color
depth first.
/notify:on | off
If on, users are alerted when maxmem limit is reached.
Go to Document Center Appendix A MetaFrame Presentation Server Commands 387
/?
Displays the syntax for the utility and information about the utility’s options.
Remarks
A server can be set to inherit its ICA display settings from the server farm ICA
display settings. Use /query to display the current inherit settings. If /inherit is on,
the settings displayed with /query are the server farm settings. When /inherit is off,
the settings shown are for the current server only.
Twconfig can be used only to change the settings on this server, for this server. To
change the settings for another server or for the server farm, use the Presentation
Server Console.
Within the maxmem limit, various combinations of session size and color depth are
available. The session size and color depth values are determined using the
following formula: height x width x depth ≤ maxmem, where the height and width
are measured in pixels and depth is the color depth in bytes according to the
following table:
The following is a list of the maximum session sizes with a 4:3 aspect ratio for each
color depth at the default maxmem value (height by width by color depth):
• 1600 by 1200 by 24-bit color
• 1920 by 1440 by 16-bit color
• 2752 by 2064 by 256 colors
• 3904 by 2928 by 16 colors
Security Restrictions
None.
388 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
Go to Document Center
APPENDIX B
Customizing Setup
Important Be sure to read the chapters in this book “Planning for Deployment” on
page 69 and “Deploying MetaFrame Presentation Server” on page 107 before you
attempt the procedures in this chapter.
The basic procedure for effectively customizing the Windows Installer package is
outlined below. Each of these steps is explained in more detail in this chapter. For
more information about Windows Installer, including more details about the
commands briefly described in this chapter, see the Windows online Help or the
Microsoft Web site at http://www.microsoft.com.
390 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
Note If you are creating a MetaFrame Presentation Server farm with multiple
servers, you must modify two transforms: one transform to run on the first
server in the farm, and a second transform to run on the servers joining the
newly created server farm.
2. Open the installation package in your preferred Windows Installer editing tool
and apply a transform. Save the transform with a new name.
Repeat this step for each of the transforms you need to modify. If you are
modifying the installation package for two scenarios—creating a farm and
joining a farm—you will have two modified transform packages when you are
done.
3. Create the network share points for the installation packages. Create two shares:
one for the package transformed to run on the server on which you are creating
the server farm, and one for the package transformed to run on the servers
joining the server farm.
4. Create the administrative installation packages on the network shares you
created in Step 3.
Creating Transforms
You can manipulate the installation process by applying Windows Installer
transforms (files with the .mst extension) to the installation database contained in a
Windows Installer package. A transform makes changes to elements of the
database. A transform file modifies the installation package when it is being
installed and dynamically affects the installation behavior.
Transforms that you create to customize a Windows Installer setup package remain
cached on your system. These files are applied to the base Windows Installer
package whenever the Installer needs to modify it. You can apply transforms only
when you initially install Windows Installer packages; you cannot apply transforms
to software that is already installed.
When you create a transform to apply to the MetaFrame Presentation Server
Windows Installer package, you set your desired values for properties in the
package. When you then apply the transform to the installation package, the
“questions” you would be asked during Setup are answered. Creating a transform
allows you to install MetaFrame Presentation Server in unattended mode.
Go to Document Center Appendix B Customizing Setup 391
There are several commercially available tools you can use to create or edit
transforms.
Citrix provides four sample transforms on the MetaFrame Presentation Server CD,
located in the Support\Install directory. The transforms include sample values for
select properties, allowing you to determine which properties you can edit to
achieve a certain configuration.
For definitions and possible values of the properties in the sample transforms, see
“Setup Property Names and Values” on page 397.
The transforms in the following examples are used to create a server farm using
Microsoft Access for the farm’s data store and a server farm using Microsoft SQL
Server as the farm’s data store.
To apply a transform
Type the following at a command prompt, where package is the name of the
Windows Installer installation package and TransformList is the list of the
transforms that you want to apply:
msiexec /i package TRANSFORMS=TransformList
If you are applying multiple transforms, separate each transform with a semicolon.
For further information about the parameters and switches you can use with these
options, go to the Microsoft Web site at http://www.microsoft.com and search on
“msiexec.”
The properties to set to achieve the results of each sample transform are listed in the
following sections.
392 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
4. Run MetaFrame Presentation Server Setup from the network share points you
created. Start with the share point that contains the image used to create the first
server in the farm. The following is an example of a command line to
accomplish this:
msiexec /i <full path to my new share point mps.msi> /L <full path to a log file
location> /qb-
CTX_MF_USER_NAME
Definition: User name for the initial MetaFrame administrator credentials;
applies only when creating a farm.
Possible values: User defined
Default value: “UserName”
CTX_MF_DOMAIN_NAME
Definition: Domain name for the farm administrator credentials; applies only
when creating a farm.
Possible values: User defined
Default value: “DomainName”
CTX_MF_CREATE_FARM_DB_CHOICE
Definition: When creating a new server farm, specify whether the database is a
local database (Access or MSDE) stored on the first server in the new farm, or a
third-party database stored on a separate database server (SQL, Oracle, or IBM
DB2).
Possible values: “ThirdParty” or “Local”
Default value: “Local”
CTX_MF_LOCAL_DATABASE
Definition: Type of locally stored database that stores the farm data store.
Possible values: “Access” or “SQL” (SQL for MSDE)
Default value: “Access”
CTX_MF_MSDE_INSTANCE_NAME
Definition: If you are using MSDE for a local database, you can specify an
installed instance of MSDE instead of using the default. If you specify an
instance of MSDE other than the default — for example, if you install MSDE
using a command prompt and specify custom options — you must enter the
name of the custom instance you install.
Possible values: User defined.
Default value: “CITRIX_METAFRAME”
CTX_MF_ODBC_PASSWORD
Definition: Password for a third-party database that stores the farm data store.
Possible values: User defined
Default value: “Password”
Go to Document Center Appendix B Customizing Setup 399
CTX_MF_ODBC_USER_NAME
Definition: User name for a third-party database that stores the farm data store.
Possible values: User defined.
Default value: “UserName”
CTX_MF_SILENT_DSNFILE
Definition: Path to the DSN file to be used for the data store - use for silent
installation.
Possible values: Complete path to the DSN file
Default value: “” (null)
CTX_MF_JOIN_FARM_DB_CHOICE
Definition: Use when joining this server to an existing server farm.
Possible values: “Direct”, “Indirect”
Set this property’s value to “indirect” if you are using a Microsoft Access or
MSDE database, stored locally on the first server in the farm on which you
installed MetaFrame Presentation Server, for the data store. Set this property’s
value to “direct” if you are using a Microsoft SQL, Oracle, or IBM DB2
database, stored on a separate dedicated database server, for the data store.
Default value: “Direct”
CTX_MF_INDIRECT_JOIN_DOMAIN_NAME
Definition: Domain name of a user account that has full administrative rights in
MetaFrame Presentation Server. Define if you are joining a farm that uses a
Microsoft Access or MSDE database, stored locally on the first server in the
farm, for the data store (indirect access).
Possible values: Can be any user’s domain (the user account must have full
administrative rights in MetaFrame Presentation Server).
Default value: “DomainName”
CTX_MF_INDIRECT_JOIN_USER_NAME
Definition: User name of a user account that has full administrative rights in
MetaFrame Presentation Server. Define if you are joining a farm that uses a
Microsoft Access or MSDE database, stored locally on the first server in the
farm, for the data store (indirect access).
Possible values: Can be any user who has full administrative privileges in
MetaFrame Presentation Server.
Default value: “Administrator”
400 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
CTX_MF_INDIRECT_JOIN_PASSWORD
Definition: The password for a user account that has full administrative rights in
MetaFrame Presentation Server. Define if you are joining a farm that uses a
Microsoft Access or MSDE database, stored locally on the first server in the
farm, for the data store (indirect access).
Possible values: The password for the user name entered in
CTX_MF_INDIRECT_JOIN_USER_NAME.
Default value: “” (null)
CTX_MF_JOIN_FARM_SERVER_NAME
Definition: Name of a server in the server farm you want to join.
Possible values: Name of a server hosting the Access or MSDE data store.
Default value: “ServerName”
CTX_MF_JOIN_FARM_SERVER_PORT
Definition: Port number for the IMA communication port used to communicate
with the locally stored server farm data store (for example, if you are using a
Microsoft Access or MSDE database, stored locally on the first server in the
farm on which you installed MetaFrame Presentation Server, for the data store).
Possible values: User defined
Default value: “2512”
CTX_MF_ZONE_NAME
Definition: Name of the zone to which the server belongs.
Possible values: Not applicable
Default value: None. The default value for the zone name is generated
programatically, based on the subnet address of the server.
Go to Document Center Appendix B Customizing Setup 401
CTX_MF_ADD_ANON_USERS
Definition: Determines whether anonymous users added to the Users group are
included in the Remote Desktop Users group on Windows Server 2003. This
property is ignored during upgrades.
If set to “Yes” and if CTX_MF_CREATE_REMOTE_DESKTOP_USERS is
set to “CopyUsers” or “DoNothing” during a clean install, the anonymous users
are added to the Remote Desktop Users group. If
CTX_MF_CREATE_REMOTE_DESKTOP_USERS is set to “AddEveryone,”
this property is ignored because the Remote Desktop Users group is configured
so that every user in the Users group is also a Remote Desktop user. Set this
property to “No” during a clean install to prohibit anonymous connections to
MetaFrame Presentation Server running on Windows Server 2003.
Possible values: “Yes”, “No”
Default value: “Yes”
CTX_MF_CREATE_REMOTE_DESKTOP_USERS
Definition: Determines whether or not to add users to the Remote Desktop
Users group on a Windows Server 2003 system. Users must be members of the
Remote Desktop Users group to log on remotely to a Windows Server 2003
system.
Setting this property has no effect if the server is running Windows 2000 or if
the Remote Desktop Users group already has members.
Possible values:
“AddEveryone” — Adds the Authenticated Users group to the Remote Desktop
Users group. This option allows all current and future authenticated users to log
on remotely to the server.
“CopyUsers” — Copies all current users from the Users group to the Remote
Desktop Users group. Any user accounts you add must be added to the Remote
Desktop Users group manually.
“DoNothing” — Does not add any users to the Remote Desktop Users group.
Choosing this option means that no users will be allowed to log on remotely to
the server until you add users to the Remote Desktop Users group in Windows
Server 2003.
Default value: “CopyUsers”
CTX_MF_SHADOWING_CHOICE
Definition: Turns ICA session shadowing on or off.
Important If you turn session shadowing off when you install MetaFrame
Presentation Server, you cannot enable shadowing at a later time through user
policies or connection configuration.
CTX_MF_SHADOW_PROHIBIT_NO_NOTIFICATION
Definition: Prohibits or allows shadowing connections without user notification.
Possible values: “Yes” - Prohibit or “No” - Allow
Default value: “No”
CTX_MF_SHADOW_PROHIBIT_NO_LOGGING
Definition: Prohibits or allows shadow connections without logging.
Possible values: “Yes” - Prohibit or “No” - Allow
Default value: “No”
CTX_MF_XML_CHOICE
Definition: Determines whether Microsoft Internet Information Services (IIS)
and the Citrix XML Service share the same port on this server or use separate
ports. If you do not want IIS and the XML Service to share the same port, you
must set the XML Service port number in CTX_MF_XML_PORT_NUMBER.
Possible values: “Share” - share with IIS or “Separate” - use separate port, set in
CTX_MF_XML_PORT_NUMBER.
Default value: “Share”
CTX_MF_XML_PORT_NUMBER
Definition: Port number you want the Citrix XML Service to use when you do
not want the XML Service and IIS to share ports.
Possible values: User defined
Default value: “80”
CTX_MF_LAUNCH_CLIENT_CD_WIZARD
Definition: Specifies whether or not to launch the ICA Client Distribution
wizard (to update the clients images on the server).
Possible values: “Yes”- Launch wizard or “No” - Do not launch wizard; that is,
do not update client images.
Default value: “No”
CTX_MF_CLIENT_CD_PATH
Definition: Path to the MetaFrame Presentation Server Components CD; to be
passed to the ICA Client Distribution wizard.
Possible values: Complete path to the Components CD.
Default value: “” (null)
404 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
CTX_MF_SERVER_TYPE
Definition: The edition of MetaFrame Presentation Server to be installed. If you
are performing a silent installation and using a command line, the command line
arguments for this property must be set to the correct value.
Possible values: “E” for Enterprise Edition, “A” for Advanced Edition, or “S”
for Standard Edition.
Default value: “E”
CTX_MF_ENABLE_VIRTUAL_SCRIPTS
Definition: Directs MetaFrame Presentation Server Setup to create the virtual
scripts directory. If the value is set to “Yes” or “1”, Setup does not display the
dialog box asking for permission to create the virtual scripts directory, even if
you are running Setup in full UI mode.
If you are running a “silent” installation where this property is not set to “Yes”
or “1” and the XML port on the server is shared with IIS (if you are installing
the Web Interface, for example), Setup aborts and the following error message
is added to the installation log file:
“ERROR: SetIISScriptsDir - Could not get the scripts path because the Virtual
Scripts directory in not enabled in IIS or the property
CTX_MF_ENABLE_VIRTUAL_SCRIPTS is not set to Yes.”
If the property is defined, the silent installation continues with no error.
Possible Values: “Yes” or “1” - Create the virtual scripts directory if it does not
already exist.
Not defined, “0” or “No” - Do not create the virtual scripts directory if it does
not already exist. You are prompted during Setup to create the virtual scripts
directory.
Default Value: Not defined
CTX_MF_ADD_LOCAL_ADMIN
Definition: If enabled, creates MetaFrame administrator accounts for all user
accounts in the local Administrators group.
Possible values: “Yes”, “No”
Default value: “No”
Go to Document Center Appendix B Customizing Setup 405
CTX_ADDLOCAL
Definition: This property is similar to the Windows Installer ADDLOCAL
property.
Possible values: Blank (default), All, CTX_MF_MetaFrame_Core,
CTX_MF_IM, CTX_MF_IM_Packager, CTX_MF_IM_Service,
CTX_MF_LM, CTX_MF_NM, CTX_MF_RM, PN_ENGINE, PN,
PN_AGENT, WMI, MetaFrame_XP, CTX_MF_CMC,
CTX_MF_ICA_Shell_Editor, CTX_MF_IMA_Core, CTX_MF_IM_Plugin,
CTX_MF_RM_Plugin, CTX_SMA, CTX_MF_CTXCPU,
CTX_MF_CTXSFO, CTX_MF_ASCII.
Separate entries by commas. Valid configurations are:
All — Install every feature (XPE configuration).
MetaFrame_XP,CTX_MF_MetaFrame_Core,CTX_MF_IMA_Core,CTX_MF
_ICA_Shell_Editor,CTX_SMA,CTX_MF_CTXCPU,CTX_MF_CTXSFO —
Core MetaFrame, required for any configuration (referred to below as @Core).
PN, PN_ENGINE — Install the full Program Neighborhood client as the Pass-
Through Client (referred to below as @PN).
PN_AGENT, PN_ENGINE — Install the Program Neighborhood Agent as the
Pass-Through Client.
CTX_MF_CMC,CTX_MF_IM_Plugin,CTX_MF_RM_Plugin — Install the
Presentation Server Console (referred to below as @CMC).
CTX_MF_IM_Service — Install the Installation Manager installer service.
CTX_MF_IM_Packager — Install the Installation Manager Packager.
CTX_MF_IM,CTX_MF_IM_Service,CTX_MF_IM_Packager — Install all
Installation Manager components (referred to below as @IM).
CTX_MF_RM — Install Resource Manager.
@Core,CTX_MF_LM,WMI,@CMC,PN,@IM,CTX_MF_RM,CTX_MF_AS
CII — Install all default MetaFrame Presentation Server Enterprise Edition
components.
@Core,CTX_MF_LM,@CMC,PN — Install all default MetaFrame
Presentation Server Advanced Edition components.
@Core,@CMC,PN — Install all default MetaFrame Presentation Server
Standard Edition components.
Default value: Blank
406 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
CTX_RDP_DISABLE_PROMPT_FOR_PASSWORD
Definition: Setting this property to “Yes” changes the security setting on the
server so that passwords from users of Microsoft Remote Desktop Web
Connection software are not required. Users must still enter credentials when
logging on to the Web Interface, but can launch applications without further
prompts for credentials by the server.
Possible values: “Yes”, “No”
Default value: “No”
CTX_MF_LIC_CHOICE_FOR_CREATE
Definition: Configures the server to point to an existing license server. If set to
“Point,” ensure that CTX_MF_LICENSE_SERVER_NAME points to a valid
license server. If you install the license server after installing MetaFrame
Presentation Server, set CTX_MF_LIC_CHOICE_FOR_CREATE to
“DontKnow”.
Possible values: “Point”, “DontKnow”
Default value: “Point”
Note You can also use the Presentation Server Console to configure the server
to point to the license server.
CTX_MF_LICENSE_SERVER_NAME
Definition: Defines the license server to which the server points. Only applies:
• When performing a new installation while joining an existing server farm or
peforming an upgrade and
CTX_MF_LIC_CHOICE_FOR_JOIN_OR_UPGRADE is set to “Point”
• When performing a new installation while creating a new server farm and
CTX_MF_LIC_CHOICE_FOR_CREATE is set to “Point”
Possible values: User defined
Default value: “localhost”
CTX_MF_LIC_CHOICE_FOR_JOIN_OR_UPGRADE
Definition: Configures the server to point to an existing license server. If set to
“Point”, ensure that CTX_MF_LICENSE_SERVER_NAME points to a valid
license server. If set to “UseFarmSettings”, ensure that the existing server farm
is configured to use a license server. If you install the license server after
installing MetaFrame Presentation Server, set
CTX_MF_LIC_CHOICE_FOR_JOIN_OR_UPGRADE to “DontKnow”.
Go to Document Center Appendix B Customizing Setup 407
Note You can also use the Presentation Server Console to configure the server
to point to the license server.
CTX_REMOVE_WI_TURNKEY
Definition: When upgrading from earlier versions of MetaFrame that include
the Web Interface, you must upgrade the Web Interface before upgrading to
MetaFrame Presentation Server. Otherwise, the Web Interface may be removed
from the server as a result of the upgrade. Set this property to “Yes” if you do
not object to the removal of the Web Interface from the server.
Possible values: “Yes”, “No”
Default value: “No”
CTX_MF_ONLY_LAUNCH_PUBLISHED_APPS
Definition: MetaFrame Presentation Server features a security enhancement that
prohibits non-administrative users from launching desktop sessions (but not
published applications). If set to “Yes,” the security enhancement is enabled.
Possible values: “Null,” “Yes,” “No”
Default value: “Null”
Note If set to a value other than “Yes” or “No,” the security enhancement is
enabled when performing a clean install but disabled when performing an
upgrade.
INSTALLDIR
Definition: The target location for the installation.
Possible values: User defined.
Default value: %Program Files%\Citrix
REBOOT
Definition: Standard Windows Installer property that controls whether you
restart a server or prompt for the server to be restarted.
Possible values: “Force” - Forces restart to occur; no further prompts are
displayed.
“Suppress” - Forces restart to not occur by default; a prompt occurs if action is
necessary.
“ReallySuppress” - Force restart to not occur; no prompts appear.
Default value: “Force”
Go to Document Center Appendix B Customizing Setup 409
REINSTALLMODE
Definition: Specifies the type of reinstall to perform. Options are case-
insensitive and order-independent.
Possible values:
p - install missing files
o - replace older versioned or missing files
c - replace corrupt files (checksum validation)
e - replace same versioned or missing files
d - replace files of differing versions
a - replace all files regardless of version
u - replace user registry settings
m - replace machine registry settings
s - replace shortcuts
v - replace the cached .msi package with the package being installed from
Default value: “oums”
CLIENT_INSTALLDIR
Definition: The target location for the Pass-Through Client installation.
Possible values: User defined
Default value: %Program Files%\Citrix\ICA Client
ENABLE_DYNAMIC_CLIENT_NAME
Definition: When using the Pass-Through Client, turn on or off the capability to
use the computer name as the client device name and recognize changes to the
client name.
Possible values: “Yes”, “No”
Default value: “Yes”
PROGRAM_FOLDER_NAME
Definition: Start Menu Program Folder Name, where Start Menu Program
Folder Name is the name of the Programs folder on the Start menu containing
the shortcut to the Program Neighborhood or Program Neighborhood Agent
software.
Possible values: User defined
Default value: Citrix\MetaFrame Access Clients
SERVER_LOCATION
Definition: The URL of the server running the Web Interface. This server hosts
the configuration file for the Program Neighborhood Agent. You must enter the
server address if you want to use the Program Neighborhood Agent as the Pass-
Through Client. The server address can use HTTP or HTTPS.
Possible values: User defined
Default value: localhost
DEFAULT_NDSCONTEXT
Definition: Include this parameter if you want to set a default context for NDS.
If you are including more than one context, place the entire value in quotation
marks, and separate the contexts by a comma.
Examples of correct parameters:
DEFAULT_NDSCONTEXT=Context1
DEFAULT_NDSCONTEXT=”Context1,Context2”
Example of an incorrect parameter:
DEFAULT_NDSCONTEXT=Context1,Context2
Go to Document Center Appendix B Customizing Setup 411
ENABLE_SSON
Definition: Set to Yes to enable Single Sign-On (Pass-Through Authentication)
for the Pass-Through Client. Set to No to disable Single Sign-On for the Pass-
Through Client.
Possible values: “Yes”, “No”
Default value: “Yes”
412 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
Go to Document Center
APPENDIX C
Performance Counters
Counter Description
Bytes Received/sec This counter is for inbound bytes per second.
Bytes Sent/sec This counter is for outbound bytes per second.
Network Connections Number of active IMA network connections to other IMA
servers.
414 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
Counter Description
Application Enumerations/sec The number of application enumerations per second.
Application Resolution Time The time in milliseconds that a resolution took to complete.
(ms)
Application Resolutions/sec The number of application resolutions per second.
Average License Check-In The average license check-in response time in milliseconds.
Response Time (ms)
Average License Check-Out The average license check-out response time in milliseconds.
Response Time (ms)
DataStore Connection Failure The number of minutes that the server running MetaFrame
has been disconnected from the data store.
DataStore bytes read The number of bytes read from the data store.
DataStore bytes read/sec The number of bytes of data store data read per second.
DataStore bytes written/sec The number of bytes of data store data written per second.
DataStore reads The number of times data was read from the data store.
DataStore reads/sec The number of times data was read from the data store per
second.
DataStore writes/sec The number of times data was written to the data store per
second.
DSCHECK Found Errors Flag This counter displays one (1) if DSCHECK finds errors or zero
(0) for no errors.
DSCHECK Number of The number of application errors found by DSCHECK. A
Application Errors maximum value indicates that the application test could not
run.
DSCHECK Number of Group The number of group errors found by DSCHECK. A maximum
Errors value indicates the group test could not run.
DSCHECK Number of Server The number of server errors found by DSCHECK. A
Errors maximum value indicates the server test could not run.
DynamicStore bytes read/sec The number of bytes of dynamic store data read per second.
DynamicStore bytes The number of bytes of dynamic store data written per
written/sec second.
Go to Document Center Appendix C Performance Counters 415
Counter Description
DynamicStore Gateway The number of dynamic store update packets sent to remote
Update Count data collectors.
DynamicStore Gateway The number of bytes of data sent across gateways to remote
Update, Bytes Sent data collectors.
DynamicStore Query Count The number of dynamic store queries that were performed.
DynamicStore Query Request, The number of bytes of data received in dynamic store query
Bytes Received request packets.
DynamicStore Query The number of bytes of data sent in response to dynamic store
Response, Bytes Sent queries.
DynamicStore reads/sec The number of times data was read from the dynamic store
per second.
DynamicStore Update Bytes The number of bytes of data received in dynamic store update
Received packets.
DynamicStore Update Packets The number of update packets received by the dynamic store.
Received
DynamicStore Update The number of bytes of data sent in response to dynamic store
Response Bytes Sent update packets.
DynamicStore Writes/sec The number of times data was written to the dynamic store per
second.
Filtered Application The number of filtered application enumerations per second.
Enumerations/sec
Last Recorded License Check- The last recorded license check-in response time in
In Response Time (ms) milliseconds.
Last Recorded License Check- The last recorded license check-out response time in
Out Response Time (ms) milliseconds.
License Server Connection The number of minutes that the server has been disconnected
Failure from the license server.
LocalHostCache bytes The number of bytes of IMA local host cache data read per
read/sec second.
LocalHostCache bytes The number of bytes of IMA local host cache data written per
written/sec second.
LocalHostCache reads/sec The number of times data was read from the IMA local host
cache per second.
LocalHostCache writes/sec The number of times data was written to the IMA local host
cache per second.
Maximum License Check-In The maximum license check-in response time in milliseconds.
Response Time (ms)
416 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
Counter Description
Maximum License Check-Out The maximum license check-out response time in
Response Time (ms) milliseconds.
WorkItem Queue Executing The number of work items that are currently being executed.
Count
WorkItem Queue Pending The number of work items that are not yet ready to be
Count executed.
WorkItem Queue Ready Count The number of work items that are ready to be executed.
Zone Elections The number of zone elections that occurred. This value starts
at zero each time the IMA service starts and is incremented
each time a zone election takes place.
Zone Elections Won The number of times the server won a zone election.
Go to Document Center Appendix C Performance Counters 417
Note For MetaFrame Presentation Server for Windows, Standard and Advanced
Editions, only the counters marked with an asterisk (*) are installed.
Counter Description
Input Audio Bandwidth The bandwidth, measured in bps, used when playing sound in
an ICA session.
Input Clipboard Bandwidth The bandwidth, measured in bps, used when performing
clipboard operations such as cut-and-paste between the ICA
session and the local window.
Input COM 1 Bandwidth The bandwidth, measured in bps, used when routing a print
job through an ICA session that does not support a spooler to
a client printer attached to the client COM 1 port .
Input COM 2 Bandwidth The bandwidth, measured in bps, used when routing a print
job through an ICA session that does not support a spooler to
a client printer attached to the client COM 2 port .
Input COM Bandwidth The bandwidth, measured in bps, used when sending data to
the client COM port.
Input Control Channel The bandwidth, measured in bps, used when executing
Bandwidth LongCommandLine parameters of a published application.
Input Drive Bandwidth The bandwidth, measured in bps, used when performing file
operations between the client and server drives during an ICA
session.
Input Font Data Bandwidth The bandwidth, measured in bps, used when initiating font
changes within a SpeedScreen-enabled ICA session.
Input Licensing Bandwidth The bandwidth, measured in bps, used to negotiate licensing
during the session establishment phase. There is normally no
data for this counter because this negotiation takes place
before logon.
Input LPT 1 Bandwidth The bandwidth on the virtual channel that prints to a client
printer attached to the client LPT 1 port through an ICA
session that does not support a spooler. This is measured in
bps.
Input LPT 2 Bandwidth The bandwidth on the virtual channel that prints to a client
printer attached to the client LPT 2 port through an ICA
session that does not support a spooler. This is measured in
bps.
418 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
Counter Description
Input Management Bandwidth The bandwidth, measured in bps, used when updating clients
through the auto client update feature.
Input PN Bandwidth The bandwidth, measured in bps, used by Program
Neighborhood to obtain application set details.
Input Printer Bandwidth The bandwidth, measured in bps, used when printing to a
client printer through a client that has print spooler support
enabled.
Input Seamless Bandwidth The bandwidth, measured in bps, used for published
applications that are not embedded in a session window.
Input Session Bandwidth The bandwidth, measured in bps, used from client to server for
a session.
Input Session Compression The compression ratio used from client to server for a session.
Input Session Line Speed The line speed, measured in bps, used from client to server for
a session.
Input SpeedScreen Data The bandwidth, measured in bps, used from client to server for
Channel Bandwidth data channel traffic.
Input Text Echo Bandwidth The bandwidth, measured in bps, used for text echoing.
Input ThinWire Bandwidth The bandwidth, measured in bps, used from client to server for
ThinWire traffic.
Latency - Last Recorded* The last recorded latency measurement for the session.
Latency - Session Average* The average client latency over the lifetime of a session.
Latency - Session Deviation* The difference between the minimum and maximum
measured latency values for a session.
Output Audio Bandwidth The bandwidth, measured in bps, used for playing sound in an
ICA session.
Output Clipboard Bandwidth The bandwidth, measured in bps, used for clipboard
operations such as cut-and-paste between the ICA session
and the local window.
Output COM 1 Bandwidth The bandwidth, measured in bps, used when routing a print
job through an ICA session that does not support a spooler to
a client printer attached to the client COM 1 port.
Output COM 2 Bandwidth The bandwidth, measured in bps, used when routing a print
job through an ICA session that does not support a spooler to
a client printer attached to the client COM 2 port.
Output COM Bandwidth The bandwidth, measured in bps, used when receiving data
from the client COM port.
Go to Document Center Appendix C Performance Counters 419
Counter Description
Output Control Channel The bandwidth, measured in bps, used when executing
Bandwidth LongCommandLine parameters of a published application.
Output Drive Bandwidth The bandwidth, measured in bps, used when performing file
operations between the client and server drives during an ICA
session.
Output Font Data Bandwidth The bandwidth, measured in bps, used when initiating font
changes within a SpeedScreen-enabled ICA session.
Output Licensing Bandwidth The bandwidth, measured in bps, used to negotiate licensing
during the session establishment phase. There is normally no
data for this counter because this negotiation takes place
before logon.
Output LPT 1 Bandwidth The bandwidth, measured in bps, used when routing a print
job through an ICA session that does not support a spooler to
a client printer attached to the client LPT 1 port.
Output LPT 2 Bandwidth The bandwidth, measured in bps, used when routing a print
job through an ICA session that does not support a spooler to
a client printer attached to the client LPT 2 port.
Output Management The bandwidth, measured in bps, used when updating clients
Bandwidth through the auto client update feature.
Output PN Bandwidth The bandwidth, measured in bps, used by Program
Neighborhood to obtain application set details.
Output Printer Bandwidth The bandwidth, measured in bps, used when printing to a
client printer through a client that has print spooler support
enabled.
Output Seamless Bandwidth The bandwidth, measured in bps, used for published
applications that are not embedded in a session window.
Output Session Bandwidth The bandwidth, measured in bps, used from server to client for
a session.
Output Session Compression The compression ratio used from server to client for a session.
Output Session Line Speed The line speed, measured in bps, used from server to client for
a session.
Output SpeedScreen Data The bandwidth, measured in bps, used from server to client for
Channel Bandwidth data channel traffic.
Output Text Echo Bandwidth The bandwidth, measured in bps, used for text echoing.
Output ThinWire Bandwidth The bandwidth, measured in bps, used from server to client for
ThinWire traffic.
Secure Ticket Authority (STA) Performance Counters
The following performance counters are available for the Secure Ticket Authority:
STA Bad Data Request Count The total number of unsuccessful ticket validation and data
retrieval requests during the lifetime of the STA.
STA Good Data Request Count The total number of successful ticket validation and data
retrieval requests received during the lifetime of the STA.
STA Bad Ticket Request Count The total number of unsuccessful ticket generation
requests received during the lifetime of the STA.
STA Good Ticket Request Count The total number of successful ticket generation requests
received during the lifetime of the STA.
STA Peak Data Request Rate The maximum rate of data requests per second during the
lifetime of the STA.
STA Peak Ticket Request Rate The maximum rate of ticket generation requests per
second during the lifetime of the STA.
STA Peak All Request Rate The maximum rate of all monitored activities per second.
STA Ticket Timeout Count The total number of ticket time-outs that occur during the
lifetime of the STA.
STA Count of Active Tickets Total count of active tickets currently held in the STA.
Go to Document Center
APPENDIX D
Glossary
CPU prioritization The feature that allows you to assign each published application in
the server farm a priority level for CPU access. This feature can be used to
ensure that CPU-intensive applications in the server farm do not degrade the
performance of other applications.
custom ICA connection A user-created shortcut to a published application or computer
running MetaFrame Presentation Server.
data store An ODBC-compliant database that stores persistent data for a farm.
Examples of persistent data include configuration information about published
applications, users, printers, and servers. Each server farm has a single data
store. See also local host cache, zone data collector.
delegated administration The feature that allows you to delegate areas of MetaFrame
Presentation Server administration and farm management. Administrators can
assign certain staff members to perform specific tasks such as managing
printers, published applications, or user policies. Specialized staff members
can carry out their assigned tasks without being granted full access to all areas
of server farm management.
disconnected session A client session in which the client is no longer connected to the
server but the user’s applications are still running. A user can reconnect to a
disconnected session. If the user does not do so within a specified time-out
period, the server automatically terminates the session.
display name A name you specify when you publish an application. The display name
appears in the newer Program Neighborhood Client and in Application folders
in the Presentation Server Console. You can also choose to use the display
name in the Web Interface.
dynamic store A data store that contains frequently updated configuration data such as
application load information. A server farm replicates dynamic store
information across multiple servers.
file type association You configure content redirection from client to server by
associating published applications with file types and then assigning them to
the users you want to be affected.
full duplex audio The ability of sound to travel in both directions at the same time. A
telephone, for example, works in full duplex mode, allowing both parties to
speak and be heard at the same time, whereas a walkie-talkie works in half
duplex mode, allowing only one party to speak and be heard at a time.
ICA Independent Computing Architecture. The architecture that MetaFrame
Presentation Server uses to separate an application’s logic from its user
interface. With ICA, only the keystrokes, mouse clicks, and screen updates
pass between the client and server on the network, while 100% of the
application’s logic executes on the server.
ICA asynchronous connections Asynchronous connection types allow direct dial-in to
a computer running MetaFrame Presentation Server without the overhead of
RAS and TCP/IP.
ICA browser See master ICA browser or master browser.
424 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
ICA Client Creator The server utility you use to create disks from which you can install
MetaFrame Presentation Server Clients and the ICA File Editor on a wide
range of client devices.
ICA Client Printer Configuration The utility you use to create and connect to client
printers for the Clients for DOS and Windows CE. You must run this utility in
an ICA session from the client whose printer you want to configure.
ICA Client Update Configuration The utility you use to configure the client update
database.
ICA connection The logical port used by a client to connect to, and start a session on, a
computer running MetaFrame Presentation Server. 1. An ICA connection is
associated with a network connection (such as TCP/IP, IPX, SPX, or
NetBIOS) or a serial connection (modems or direct cables). 2. The active link
established between a client and a computer running MetaFrame Presentation
Server.
ICA Encryption This feature enables use of the SSL (Secure Sockets Layer) or TLS
(Transport Layer Security) protocols to secure communication between the
clients that support SSL and computers running MetaFrame Presentation
Server. SSL provides server authentication, encryption of the data stream, and
message integrity checks. After configuring the Citrix SSL Relay, you can
specify the use of SSL when you publish applications. See also Citrix SSL
Relay.
ICA file A text file (with the extension ica) containing information about a published
application. ICA files are written in Windows ini file format and organize
published application information in a standard way that MetaFrame
Presentation Server Clients can interpret. When a client receives an ICA file, it
initializes a session running the application on the server specified in the file.
ICA protocol The protocol that MetaFrame Presentation Server Clients use to format
user input (keystrokes, mouse clicks, and so forth) and address it to servers for
processing. Servers use the ICA protocol to format application output (display,
audio, and so forth) and return it to the client device.
ICA session A lasting connection between a client and a computer running
MetaFrame Presentation Server, identified by a specific user ID and ICA
connection. It consists of the status of the connection, the server resources
allocated to the user for the duration of the session, and any applications
executing during the session. An ICA session normally terminates when the
user logs off from the server.
Independent Management Architecture (IMA) Citrix’s server-to-server infrastructure
that provides robust, secure, and scalable tools for managing any size server
farm. Among other features, IMA enables centralized platform-independent
management, an ODBC-compliant data store, and a suite of management
products that plug in to Presentation Server Console.
interoperability The ability of MetaFrame Presentation Server to work with servers
running MetaFrame 1.8 in the same server farm. Not all MetaFrame
Presentation Server features are available in such a farm.
Go to Document Center Appendix D Glossary 425
relay listening port The TCP port on a computer running MetaFrame Presentation
Server that the Citrix SSL Relay monitors for data from a Web server.
seamless window One of the settings you can specify for the window size property of
a published application. If a published application runs in a seamless window,
the user can take advantage of all the client platform’s window management
features, such as resizing, minimizing, and so forth.
Secure Sockets Layer (SSL)/Transport Layer Security (TLS) A standards-based
architecture for encryption, authentication, and message integrity. It is used to
secure the communications between two computers across a public network,
authenticate the two computers to each other based on a separate trusted
authority, and ensure that the communications are not tampered with. SSL/
TLS supports a wide range of ciphersuites.
server A server on which MetaFrame Presentation Server software is running. You
can publish applications, content, and desktops for remote access by clients on
these servers.
server farm A group of computers running MetaFrame Presentation Server and
managed as a single entity, with some form of physical connection between
servers and a database used for the farm’s data store.
session ID A unique identifier for a specific client session on a specific computer
running MetaFrame Presentation Server.
Shadow Taskbar The taskbar on a server desktop that you can use to shadow multiple
users and to quickly switch between shadowed sessions.
shadowing A feature that enables an authorized user to remotely join or take control
of another user’s client session for diagnosis, training, or technical support. See
also user-to-user shadowing.
SpeedScreen Browser Acceleration The feature that provides substantial performance
enhancements for users running HTML-capable applications, such as Internet
Explorer, published on computers running MetaFrame Presentation Server.
SpeedScreen Browser Acceleration requires less bandwidth and allows users
running ported applications to interact with the browser while graphically-rich
pages or large images are being downloaded.
SpeedScreen Latency Reduction A combination of technologies implemented in ICA
that decreases bandwidth consumption and total packets transmitted, resulting
in reduced latency and consistent performance regardless of network
connection.
universal printing When you use universal printing you do not need to install and
duplicate a potentially large set of native printer drivers in your server farm.
The universal printer drivers can replace multiple native printer drivers that
would otherwise be needed in diverse printing environments. MetaFrame
Presentation Server Clients can work with universal drivers depending on the
client device’s version and platform.
428 MetaFrame Presentation Server Administrator’s Guide Go to Document Center
user-to-user shadowing The feature that allows users to shadow other users without
requiring administrator rights. Multiple users from different locations can view
presentations and training sessions, allowing one-to-many, many-to-one, and
many-to-many online collaboration. See also shadowing.
Web-based client installation A Web-based method for deploying client software to
users. You construct a download Web site that users access to download the
MetaFrame Presentation Server Client for their client devices.
Windows-Based Terminal (WBT) A fixed-function thin-client device that can run
applications only by connecting to a server. WBTs cannot run applications
locally.
zone A logical grouping of computers running MetaFrame Presentation Server,
typically related to the underlying network subnets. All servers in a zone
communicate with the server designated as the data collector for the zone.
zone data collector A computer that stores dynamic data for one zone in a farm.
Examples of dynamic data include current server load, the number of current
user sessions, and the applications currently running in user sessions on a
specified server.
Go to Document Center 429
Index
G
global groups 78
Go to Document Center Index 431
V
virtual IP addresses 250
virtual loopback 251
virtual memory 301
virtual printers 311
Virtual Private Networks 173
W
Web browsers, optimizing performance 208
Web Interface 87, 93–95, 98, 138, 221, 230–231
Citrix XML Service 134
Web Interface snap-in 152, 155
WinCE 312
Windows Installer
common commands 120
creating a log file 117
creating transforms 141, 389
Msiexec command 120, 142
Windows Installer transforms 389
sample setup transforms 390
Win16 applications 73
X
XML Service
see Citrix XML Service
436 Index Go to Document Center