You are on page 1of 30

Citrix

Technical

Questions

&

Answers

! " #
Q.1 What is Server Farm ?

Ans:- Server farms are groups of servers running MetaFrame Presentation Server that you can
manage as a unit, enabling you to configure features and settings for the entire farm rather than
configuring each server individually.Servers in a farm share a network connection and a single
data store of the farm’s configuration information.

Q.2 What is Independent Management Architecture (IMA) ?

Ans :-Independent Management Architecture (IMA) provides the framework for server
communications and is the management foundation for MetaFrame Presentation
Server. IMA is a centralized management service comprised of a collection of core
subsystems that define and control the execution of products in a server farm. IMA
enables servers to be arbitrarily grouped into server farms that do not depend on the
physical locations of the servers or whether the servers are on different network
subnets.
IMA runs on all servers in the farm. IMA subsystems communicate through
messages passed by the IMA Service through default TCP ports 2512 and 2513.
The IMA Service starts automatically when a server is started. The IMA Service
can be manually started or stopped through the operating system Services utility.

Q.3 What Independent Computing Architecture (ICA) ?

Ans:- The Independent Computing Architecture (ICA) is the communication protocol by which
servers and client devices exchange data in a server environment. ICA is optimized to enhance
the delivery and performance of this exchange, even on lowbandwidth connections.

Q4. What Information is stored in Data store ?

Ans:-Persistent farm-wide information (information about published application configurations,


available servers, authorized Citrix administrators, trust relationships, and the licenses
available) is stored in a data store on the data collector. Although a database of some kind
(Oracle, Microsoft SQL Server, MS Access, or IBM DB2, MSDE ( MSDE in no more supported
by PS4.5)

• Farm configuration information


• Published application configurations
• Server configurations
• MetaFrame administrator accounts
• Printer configurations
• Trust relationships

Q5. How many server can I have in a Zone ?

Ans:- By default, a single zone supports 512 member servers (prior to MetaFrame XP Feature
Release 3, the default was 256 member servers). If a zone has more than 512 member servers,
each zone data collector and potential zone data collector must have a new registry setting.
This new setting controls how many open connections to member servers a data collector can
have at one time.
You can configure this value by adding the following value, expressed in
hexadecimal notation, to the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\IMA\Runtime\MaxHostAddress
CacheEntries (DWORD)
Value: 0x200 (default 512 entries)

! " #
Note If you do not have more than 512 servers in a zone, increasing this value
does not increase the performance of a zone

Q6. What is LHC and where stored ?

Ans:- The local host cache (LHC) is an Access database located on each member server
in %ProgramFiles%\Citrix\Independent Management Architecture. The local host cache is
important as the backup in case the member server temporarily loses access to the data store,
but it is also helpful under normal conditions—the member server can read or write information
in its local host cache instead of accessing the data store every time it needs something. The
cache is populated when the IMA service on the member server starts, then by periodically
(normally, at intervals of 10 minutes; you can edit this setting to improve performance)

Q7. What is Data Collector server ?

Ans:-Zone data collectors are communication gateways between zones in farms that have
more than one zone. Zone data collectors communicate information used by MetaFrame
Presentation Server to list available applications for users and, when users open an application,
to locate the most appropriate server on which to run the application.

The server responsible for gathering information about the server farm and making this
information available to all member servers is called the data collector. The data collector gets
its information from the member servers in its zone. Any time any of the following events
(collectively known as session data) takes place, the member server informs its data collector:

• ICA client logons and logoffs


• ICA session disconnects and reconnects
• Server and application load changes
• License acquisition and release
• Server brought online or goes offline (either reboots or restarts the IMA service)
• Published application changes
• IP and media access control (MAC—the hardwired network card address) address
changes

Using this information, the data collector can provide a clear picture of the MetaFrame servers
in the farm at any given time: the servers available, the clients using those servers, the load on
each server, the licenses in use, the applications available in the farm, and the network address
of each server. For faster access, the data collector keeps all session data in RAM. If the data
collector doesn’t hear from a member server within the preset interval (by default, 60 seconds),
the data collector will ping the member server through IMA to make sure that the server is still
online.

Q8. How can I verify Win2K Terminal Services is In Application Server


Mode

Ans:- Again, MetaFrame only works on Win2K servers with Terminal Services installed in
Application Server mode, not Remote Administration mode. You can easily check the mode
from the Terminal Services Configuration window, located in the Administrative Tools

! " #
$

program group. Your view of the terminal server mode should look like this figure.

Q9.What is IMA Service Port ?

Ans :- 2512

Q10. Can I change IMA service port ?


Ans:- Yes, Normally, using the default port (2512) for the IMA service will work without any
problems. On the off chance that you need to use another port, you’ll need to edit the server’s
registry

Be careful when editing this key’s value! By default, it’s presented in hexadecimal format. If you
type the value in decimal, you need to select the option button in the Edit DWORD Value dialog
box that changes the value from hex to decimal.

Note :- If no other servers were in the farm when you changed the IMA service’s port, you’re
home free—when installing the other servers, just be sure to point to the correct port when you

! " #
reach the stage of the wizard that Figure 4.12 shows. If you’d created other servers in the farm
before changing the port, you’ll need to edit the value of PsServerPort key (also located in
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\IMA subkey) to the correct port number.

Q11. How Client connects to Presentation Server via web ?

Ans:- A user accesses the Web Interface URL with the Web browser over port 80,
similar to any other Web site.

1. The IIS-based Web service where the Web Interface resides has a default page to
redirect the user automatically to an HTTPS/SSL URL that then passes through the
Secure Gateway service on the same server to secure the traffic over port 443.
2. The user is now interacting securely with the Web Interface/Secure Gateway
environment and is presented with the login page.
3. The user enters his credentials and submits the authentication request, which is
passed encrypted over SSL to the Secure Gateway service (thus preventing the user
credentials from being passed in plain text).
4. Once the Secure Gateway service obtains the user credentials, it opens a state ticket
with the STA server and then passes the credentials to the MetaFrame farm over the
defined XML service port. The default is port 80.
5. The user credentials are checked via the Citrix XML service and verified by Microsoft
Active Directory or other directory services such as Novell e-Dir.
6. Based on a successful authentication, the XML service communicates back to the Web
Interface service and dynamically renders an access page for the user with the
appropriate applications. If any problems occur, they' re displayed on this page within
the MetaFrame Message Center.
7. When a user clicks an ICA-published application, the Web Interface service sends the
IP address and port for the requested MetaFrame server to the Secure Ticketing
Authority Server (STA) and requests a session ticket for the user. The user-installed
ICA client then securely establishes an ICA connection over SSL using port 443.
8. The Secure Gateway service receives the session ticket over port 443 from the client
and contacts the STA for ticket validation. If the ticket is valid, the STA returns the IP
address of the MetaFrame server on which the requested application resides. If the
session ticket is invalid or has expired, the STA informs the Secure Gateway service
and an error message appears on the client device.
9. On receipt of the IP address for the MetaFrame server, the Secure Gateway server
establishes an ICA connection to the MetaFrame server over port 1494 in a proxy-like
manner. When the ICA connection is established, the Secure Gateway server encrypts
and decrypts the data flowing through the connection.

Q12. What are terminal service mode ?


Ans :- There are two modes remote Administration Mode & Application Mode

Q13. What is Zone ?


Ans:- A zone is a grouping of servers that share a common zone data collector. A zone data
collector is a server that manages dynamic information about the servers in the zone. Each
farm has at least one zone.

Q14. What are the Zone Data Collector preference levels ?


Ans:-

Most Preferred
Preferred

! " #
%

Default Preference
Not Preferred

Q15. What Data base can I use for data store ?


Ans:-

Microsoft Access. Access is a lightweight database that is included with Windows server
operating systems. The Access database is created on the first server in a new farm. It is most
appropriate for small to mid-sized farms.
Microsoft SQL Server 2000 Desktop Engine (MSDE). MSDE is a database engine based on
Microsoft SQL Server core technology. The MSDE database is created on the first server in a
new farm. It is most appropriate for small to medium-sized farms and can be administered
using standard Microsoft SQL Server tools.
Microsoft SQL Server. SQL Server is a true client/server database that offers robust and
scalable support for multiple-server data access. It is suited for use in farms of any size.
Oracle. Oracle is a true client/server database that offers robust and scalable support for
multiple-server data access. It is suited for use in farms of any size.
IBM DB2. DB2 is a true client/server database that offers robust and scalable support for
multiple-server data access. It is suited for use in farms of any size.
Note :- MSDE is not more supported by Citrix PS 4.5. (It is replaced by MS SQL Express
Edition 2005)

Tested databases
• 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

Q16. What type of Data base connectivity used by Citrix ?


Ans:- MetaFrame Presentation Server will connect directly to it or indirectly through another
server.

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.
Indirect access. For indirect access, a server connects to an intermediary server
running MetaFrame Presentation Server that connects to the data store directly.

Note Although it is possible to configure multiple servers in the farm to connect


directly to a single MSDE database, Citrix does not recommend this configuration
because it is not supported by MSDE. MSDE allows only five connections per
installed instance of MSDE. If more than five servers attempt to access the MSDE
database at the same time, they cannot connect.

Q17. What are Citrix Editions ?


Standard Edition – Presentation Server, Metaframe Administrator, Printer and Policies

! " #
&

Advanced Edition – Standard edition + Load Manager


Enterprise Edition – Advanced Edition + Resource manager + Isolation environment + Network
Manager +Installation Management

Q18. Citrix – OSI Layer model ?

Q19. Citrix Management Console


Ans:- Central management tool where 98% of farm configuration/maintenance occurs. Works
through the IMA service (dest. port 2513) to access DS, DC, and member servers. Should be
run through a DC that has local access to the DS.

Q20. Citrix Ports ?

! " #
Ans:-

Q21. Installation Requirements –Presentation Server

Ans:-
Operating System:
Windows 2000 Server, Windows 2000 Advanced Server, and Windows 2000
Datacenter with SP4
Windows Server 2003, Standard, Enterprise and Datacenter Editions.

Terminal Services running in application mode


Java Runtime Environment version 1.4.2_06
.NET Framework version 1.1 with Service Pack 1
Microsoft Windows Installer (MSI) 3.0

Q22. Can I Modify zone preference and and failover ?

Ans:- You can configure zone preference and failover in a policy’s properties.

To configure zone preference and failover in a policy


1. In the Presentation Server Console, select the Policies node.
2. On the Contents tab, select the policy for which you want to configure zone preference and
failover.
3. From the Actions menu, choose Properties.
4. In the Properties dialog box, open User Workspace > Connections and select Zone

! " #
'

Preference and Failover.


5. Enable Zone Preference and Failover and assign a connection order to each zone.

Q23. What is Local Host Cache Synchronization and recreation

A subset of data store information, the local host cache, exists on each server in the farm,
providing each member server with quick access to data store information. The local host
cache also provides redundancy of the data store information, if for example, a server in the
farm loses connectivity to the data store.
When a change is made to the farm’s data store, a notification to update the local host cache is
sent to all the servers in the farm. However, it is possible that some servers will miss an update
because of network problems. Member servers periodically query the data store to determine if
changes were made since the server’s local host cache was last updated. If changes were
made, the server requests the changed information.
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.

To recreate the local host cache, stop the IMA Service and then run the command
dsmaint recreatelhc. Running this command performs three actions:
You must restart the IMA Service after running dsmaint recreatelhc. When the
IMA Service starts, the local host cache is populated with fresh data from the data
Store

Q24 What are Citrix Metaframe administrator permission levels ?

Full access to all areas of server farm management


View-only access to all areas of server farm management
Mixed levels of access to areas of farm management or specific tasks within
those areas; administrators can have a mixture of view-only access, write
access, or no access

Q25. What to do when IMA Service Fails to Start ?


The following guidelines and recommendations can be useful when the IMA Service
fails to start:

• Examine the following registry setting:


HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\IMA\
Runtime\CurrentlyLoadingPlugin
• If the value is blank, the IMA Service could not connect to the data store or
the local host cache is missing or corrupted.
• If a value exists, the IMA Service made a connection to the data store. The
value displayed is the name of the subsystem that failed to load.
• If you are connecting directly to the data store, verify that ODBC connectivity
exists.
• If you are connecting to the data store through an intermediary server, verify
that the IMA Service is running on the server that is connecting directly to the
data store.

! " #
• Review the entries in the event log for the IMA Service error code that is
returned.
Master page: First
• Verify that the Spooler service is started in the System context rather than for a
user.
• If you see an “IMA Service Failed” message (with error code 2147483649)
when restarting a server, the local system account may be missing a \temp
directory. Change the IMA Service startup account to the local administrator. If
the IMA Service starts under the local administrator’s account, check for a
missing temp directory. Switch the service back to the local system account and
try manually creating the temp directory %SystemRoot%\temp. Verify that both
the TMP and TEMP environment variables point to this directory. For more
information, see Microsoft Knowledge Base article 251254.
• The Service Control Manager has a time-out of six minutes, but the IMA
Service can take longer than six minutes to start when the load on the data store
database exceeds the capabilities of the database hardware or when the network
is experiencing high latency. If the Service Control Manager reports that the
IMA Service could not be started but the service eventually starts, ignore this
message and change the default time-out value.

Q26. How to set IMA Service Logging ?

To enable server logging of IMA events


1. Modify the following registry values in
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\IMA\Tracer:
• Name: Log to Debugger
Type: REG_DWORD
Data: 0x0 (disables debug output) or 0x1 (enables debug output)
• Name: Log to File
Type: REG_DWORD
Data: 0x0 (disables file output) or 0x1 (enables file output)
• Name: LogFileName
Type: REG_SZ
Data: full path and file name of the output file
2. The HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\IMA\Tracer registry key contains a subkey
for each subsystem about which information can be traced. Tracing for all subsystems is on by
default, but the specific types of messages for the subsystems are off. To enable tracing for a
subsystem, both the default value (specified as the first value in the key) and the message
values must have a value of 1. The default value must be 1 and must not be changed. Other
values within each key correspond to types of messages to log and are set to 0 by default. To
enable tracing for those items, set their value to 1.

Q 27. What is 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.

Q28. What is Citrix XML Service ?


Citrix XML Service is a component of MetaFrame Presentation Server. The service

! " #
is installed by default on all servers.
When clients are configured to use TCP/IP+HTTP for ICA browsing, the XML
Service communicates published application information to clients using the
HTTP protocol and XML data. The XML Service also communicates published
application information to servers running the Web Interface
For example, when a user launches a published application in Program
Neighborhood, the client sends a request for the application. The XML Service
responds with the address of a server on which the application is published.
With the Web Interface, for example, a user connects to a Web page using a Web
browser. The XML Service provides a list of available applications to the server
running the Web Interface. The Web server displays the available applications on
the user’s personalized application Web page.

What is port 1604?


If TCP/IP is specified as the server location network protocol and (Auto-Locate)
appears in the Address List box, clients send UDP broadcasts to the ICA browser
service on port 1604 to locate servers and published applications.

Q29. 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.

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.

Q 30. What are Components of MetaFrame Presentation Server ?

Management Console for MetaFrame Presentation Server. Enables complete, singlepoint


management of the entire server farm through a comprehensive interface.
Installation Manager. (Enterprise Edition only.) Provides centralized, farm-wide
installation capabilities such as support for unattended installs, packager rollback,
scheduled package delivery, and MSI support.
Installer Service. (A component of Installation Manager.) Provides the ability to
install applications packed by the Packager to computers running MetaFrame
Presentation Server.
Packager. (A component of Installation Manager.) Monitors application
installation routines and packages all application files for distribution to your server
farm.
Resource Manager. (Enterprise Edition only.) Provides customizable metrics and
reporting, real-time graphs and alerts, and capacity planning for server farm
resources.
Load Manager. (Advanced and Enterprise Editions.) Provides load balancing of
user connections across servers to more effectively utilize server resources.
Network Manager. (Enterprise Edition only.) Provides the ability to administer
server farms through the native management consoles of leading network
management solutions.
Program Neighborhood/Program Neighborhood Agent. Installs a pass-through client

! " #
on the server.
WMI Providers. (Enterprise Edition only.) Installs WMI providers

How to change XLM port after installation ?

Q31. What are Citrix Client Deployment Methods ?

• Using Microsoft Systems Management Server (SMS) or Active Directory Services in Windows
(for clients that can be installed with Windows Installer packages)
• Using the Components CD
• Using a Web browser
• Downloading from a network share point
• Using installation floppy disks

Q32. 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. When a user starts an application that is configured
for anonymous users, the server does not require an explicit user name and password to log
the user on to the server and run the application.

Anonymous users are granted minimal ICA session permissions that include the
following properties that differ from standard ICA session permissions for the
default user:
• Ten-minute idle (no user activity) time-out
• Log off from broken or timed out connections
• No password is required
• The user cannot change the password
When an anonymous user session ends, no user information is retained. The server
does not maintain desktop settings, user-specific files, or other resources created or
configured for the client.

Q33. 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.

Q34. What is isolation and Isolating Published Applications ?

Isolation environments enable you to isolate a published application within a virtual


environment. The isolation environment protects the operating system and applications from
conflicts and other complications that frequently occur between incompatible or legacy
applications. The isolation environment creates an environment or user-specific copy of the
system resources modified by the published application during installation or runtime. This
allows the application to function without affecting the rest of the system. The isolation
environment also provides a virtual mapping from an application to operating system resources.

! " #
The mapping is accomplished through the use of rules that specify how an application behaves
within an isolation environment.

The basic steps for isolating an application are as follows:


1. Through testing, identify applications that malfunction when used through MetaFrame
Presentation Server or Terminal Services.
2. Ensure isolation environments are enabled for the farm. (By default isolation environments
are enabled at the farm level.)
3. Create isolation environments.
4. Configure the properties of the isolation environment.
5. Isolate the published application.

Q35. How to Configure an Isolation Environment ?

The default settings of an isolation are designed to resolve most compatibility


issues; however, you can refine and optimize isolation environment settings as
required.When you opt to configure an isolation environment, you decide the
following characteristics:
Applications. Specifies applications installed into the isolation environment as well
as applications that are candidates for publishing. You can also specify other
applications published on the server farm that are associated with this isolation
environment.

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

Rules. Specifies whether or not isolation, redirection, or ignore rules need to be


applied to system resources, such as files, registry, and named objects.

Security. Specifies the type of security policy, such as enhanced or relaxed, to


apply to this isolation environment. Selecting enhanced security prevents execution
of files located in the user profile root.

To configure the properties of an isolation environment


1. In the left pane of the console, select Isolation Environments.
2. In the Contents tab, select the isolation environment to configure.
3. On the Actions menu, click Properties.
4. Use the Properties page to add applications and configure roots, rules, and
security settings for the isolation environment. For specific information about
each Properties page, click Help.
5. To save your settings, click OK.

Q36.Can I Uninstall an Isolated application from Add remove program ?

Unlike removing applications not installed into an isolation environment, you can
not reliably use Windows Add/Remove Programs to uninstall applications installed
into an isolation environment. Windows Add/Remove Programs may not
completely delete everything that was installed, resulting in an incomplete uninstall.

Note Citrix recommends before deleting an isolation environment to follow your


company policy for backing up user-specific files.

! " #
$

To uninstall all applications installed into an isolation environment


1. Delete all the files that reside in the installation root location of the isolation
environment (typically C:\Program Files\Citrix\AIE\<aiename>)
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.
Because an application file system and registry are isolated, this procedure provides
a clean uninstall of the applications from the server.

Q 37 What Session Information Displayed in the Console ?


The session information that appears in the console includes details that help you
identify the various types of sessions and the users associated with the sessions. The
following column labels appear on tabs that display session information.

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.

State. A session’s state is listed as Active, Listen, Idle, Disconnected, or Down. The meaning of
session state labels is explained in the following section, which describes commands you use
for managing sessions on servers.

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.

Logon Time. The time at which the user logged on.

Idle Time. The amount of time during which the user has not interacted with the Application

Q38. How Automatic Client Reconnection Works

When a client detects an unintended disconnection of an ICA session, it attempts to


reconnect the user to the session until there is a successful reconnection or the user
cancels the reconnection attempts. When a connection breaks, it may leave the server session
in an active state. Users can reconnect only to sessions that are in a disconnected, or inactive,
state. Cookies containing keys to user credentials and session IDs are created on the client
device when ICA sessions are started. Because users can be reconnected only to
disconnected sessions, Auto Client Reconnect uses the cookie on the client device to
disconnect an active session before attempting to reconnect. Sometimes automatic

! " #
reconnection can result in a new ICA session instead of a reconnected session. A new session
can be created if:
• The cookie on the client containing the key to the session ID and credentials expires. When
the session starts originally, this cookie is sent to the client. This cookie persists on the client for
several minutes after a connection breaks.
• The cookie containing the key does not force users to reauthenticate. Instead,
users are prompted with a logon screen before reconnection occurs.
The following types of disconnections do not result in automatic reconnection
attempts:
• Users disconnect ICA sessions by exiting applications without logging off.
Clients do not make automatic reconnection attempts in this case.
• Anonymous users’ sessions are disconnected.

Q 39. How to apply 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

Q 40 What are MetaFrame Presentation Server Commands

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
query …………………………….View information about server farms, processes, servers, ICA
sessions, and users
twconfig ………………………….Configure ICA display settings

Q 41 How to assign statis port to Citrix License server ?

Setting a Static Citrix Vendor Daemon Port Number

! " #
%

To set the port number, add the path for the options file and the parameters for the new port
number including the startup license file. The modified syntax in the license file is as follows:
VENDOR CITRIX options="C:\Program Files\Citrix\Licensing\MyFiles\CITRIX.opt" port=number
When setting the Citrix vendor daemon port number, you must specify the path to the citrix.opt
file and the port number in every license file on the license server and all subsequent license
files that you download.
To set a static port number for the Citrix vendor daemon

1. From the Windows Services panel, stop the Citrix License Management Console service.

2. Open a license file with any text editor (by default, the license files are located in
C:\Program Files\Citrix\Licensing\MyFiles).

3. In the license file, locate the line VENDOR CITRIX.

4. Modify the line by appending the following: options=<path to the options file> port=<port
number>
Example:
VENDOR CITRIX options="C:\Program Files\Citrix\Licensing\MyFiles\CITRIX.opt" port=27950

5. Save the license file with a .lic extension.

6. Repeat Steps 2 through 5 for each license file on the license server.

7. From the Windows Services panel, restart the Citrix License Management Console
service and the CitrixLicensing service to make your Citrix vendor daemon port number
changes take effect. If a TCP/IP

port number is specified on the VENDOR line, the Citrix vendor daemon may not restart until all
the clients close their connections to the vendor daemon. Note: Do not restart the services until
all license files on the license server have the same port number. If the Citrix vendor daemon
encounters different port numbers in the license files, the license server stops running.

8. Verify that the new Citrix vendor daemon port number is being used by looking for the
lines that use the new port number in the debug log (By default, this file is in
C:\Program Files\Citrix\Licensing\LS). The lines will be similar to the following:
3:13:48 (lmgrd) Starting vendor daemon at port 27950

3:13:51 (lmgrd) Using vendor daemon port 27950 specified in license file
Note: The text shown above many vary slightly depending on which version of Citrix Licensing
you are running.

Changing the License Manager Daemon Port Number


If you need to change the port number, you must specify the new number in all license files on
the server and in the firewall (if you have one). By default, no port number is listed in the
license file. When the License Manager daemon does not find a port number listed in the
license file, it uses port 27000.
To change the license manager daemon port number

1. From the Windows Services panel, stop the Citrix License Management Console service.

! " #
&

2. Using a text editor, modify the SERVER line of the license file by adding a port number
after the hostname. (by default, the license files are located in C:\Program
Files\Citrix\Licensing\MyFiles).
For example:
SERVER this_host HOSTNAME=mps_server1 27900
—or—
SERVER this_host ANY 27900

3. Save the file with a .lic extension.

4. Repeat Steps 2 and 3 for each license file on the license server.

5. From the Windows Services panel, restart the Citrix License Management Console
service and the CitrixLicensing service to make your Citrix license manager daemon
port number changes take effect.
Note: Do not restart the services until all license files on the license server have the same port
number. If the License Manager daemon encounters different port numbers in the license files,
the license server stops running.

6. Verify that the new Citrix license manager daemon port number is being used by looking
for the line that uses the new port number in the debug log. The line will be similar to
the following:
3:13:48 (lmgrd) lmgrd tcp-port 27900
Note: The text shown above many vary slightly depending on which version of Citrix Licensing
you are running.

Resource Manager Summary Database Data Source Name


Q: Is the Resource Manager summary database Data Source Name (DSN) case
sensitive?
A: The RMSummaRyDataBASE DSN is not case sensitive.
Q: Resource Manager was installed on two servers in my farm. After
uninstalling Resource Manager from one of the servers, why does the Resource
Manager icon remain in the Presentation Server Console even though the
uninstallation completed without errors?
A: When at least one member server in a farm has Resource Manager installed,
the Resource Manager node appears in the Presentation Server Console when
viewed on any server in the farm.
Note The Resource Manager node can be removed from a Presentation Server
Console by removing or renaming the ResourceManager.jar file found in
\Program Files\Citrix\Administration\Plugins\ and restarting the Presentation
Server Console.
Q: I installed Resource Manager with the default metrics configured on a server
and I receive alerts about high context switches. The server seems to be
functioning correctly and none of my users are complaining. Is this alert
serious?
A: The default metric threshold values are a baseline configuration for an
administrator to tune and they are determined for a minimal server
configuration. Although most metric defaults are suitable as a “one size fits all”
solution like Processor - %Processor Time defaults, some metrics like System –
Context Switches / Sec must be tuned for the environment in which they
operate.
Q: What does the Zone Elections counter monitor in Resource Manager?

! " #
A: The Citrix MetaFrame – Zone Elections counter monitors the number of data
collector elections that occurred in the server’s zone since the IMA Service
started.
Monitoring this metric can be useful to determine whether or not excessive data
collector elections are taking place. Proactive monitoring can help prevent
excessive amounts of data from transmitting between zones as elections are
won. This can also be tracked with the Citrix MetaFrame – Zone Elections Won
metric.
Q: What needs to be done when I attempt to create the summary database and
the procedure fails with this message appearing in the Resource Manager server
log?
A: This summary database message informs the user that there was an error
deploying the schema for the summary database—for example, server log entry:
11 July 2002 12:26:02 - System - Failed to create summary database.
The most common causes of this error are:
There was a database problem while initially creating the summary database
schema. For example, an Oracle database configuration such as the rollback
segment is too small and non-autoextending; this can prevent successful
deployment of the Resource Manager schema.
Solution: Check the Oracle or SQL Server configuration settings to ensure there
is enough space in the database to create the schema. Several megabytes should
be enough space to create the schema. Also, check that all ‘rollback segments’
are ‘autoextending’; these can be tuned after the database is created.
The database user has insufficient privileges to create the schema. For example,
Resource Manager may not be able to insert data into tables or create packages.
Solution: Ensure that the user has rights to the database and can successfully
communicate with the database server.
Cannot Launch Secure Applications through Internet
Explorer
If you have users connecting through a secure Web Interface page (HTTPS) and
they receive an error message of “ICA file not found,” ensure the security settings
within Internet Explorer are not set to Do not save encrypted pages to disk.
To check security settings in Internet Explorer
1. Open Internet Explorer.
2. Click Tools > Internet Options.
3. Click the Advanced tab.
4. Scroll down to Security.
5. Be sure Do not save encrypted pages to disk is cleared.
6. Click OK.
Content Redirection Options Are Disabled When
Publishing an Application
If you install and then publish applications after installing Presentation Server, you
must update the file type associations in each server’s registry.
To update file type associations in a server farm
1. Open the Presentation Server Console.
2. Expand the Servers node in the left window pane.
3. Right-click a server and select Update File Types from Registry.
4. When the file type updates are complete, check the properties of the published
application. The content redirection options are now enabled.

Isolation Environment Configuration


When you install Office 97, 2000, XP, or 2003 into an isolation environment, fonts
included with the Office suite are not available to the isolated Office applications.
To access specific Office fonts
1. Create an “ignore” rule for the following registry keys where Office font

! " #
'

information is stored:
• HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\
CurrentVersion\
• HKEY_CURRENT_USER\SOFTWARE\Microsoft\Shared Tools\Font
Mapping
2. Copy the Office fonts that you require from the installation root:
%SYSTEMDRIVE%\Program Files\Citrix\AIE\AIE_Name\Device\Drive
Letter\Windows\Fonts
to the system font directory:
%SYSTEMDRIVE%\Windows\Fonts
3. Using the procedures described in the Windows product documentation, install
the required Office fonts.
Installation Procedure
To install Office into an isolation environment called My_AIE using the setup file
setup.exe, type the following command:
AIESETUP My_AIE file_path:\setup.exe

Additional Installation Procedure—Office 2000


When installing Office 2000 on Windows Terminal Server, use a transform (.mst)
file. The Microsoft Office 2000 Resource Kit provides a transform called
Termsrvr.mst. Specify this transform using a command-line switch during setup.
To install Office 2000 into an isolation environment on a Windows Terminal Server,
append the TRANSFORMS parameter to the AIESETUP command:
AIESETUP My_AIE file_path:\setup.exe TRANSFORMS=termsrvr.mst

Registered Citrix Ports


The following table contains the default registered Citrix ports.
Notes: The Default Citrix License Server port is 27000. The Access Suite Console uses
MSRPC on port 135 for communications.
Name Number Protocol Description
ica 1494 TCP ICA
ica 1494 UDP <not used>
ica 0x85BB IPX ICA
ica 0x9010 SPX ICA
icabrowser 1604 TCP <not used>
icabrowser 1604 UDP ICA Browser
icabrowser 0x85BA IPX ICA Browser
citrixima 2512 TCP IMA (server to server)
citrixima 2512 UDP <not used>
citrixadmin 2513 TCP IMA (Presentation Server Console to server)
citrixadmin 2513 UDP <not used>
citriximaclient 2598 TCP Common Gateway Protocol (Session Reliability)
citriximaclient 2598 UDP <not used>
citrix-rtmp 2897 TCP rtmp (Control) Video Frame
citrix-rtmp 2897 UDP rtmp (Streaming Data) Video Frame
Citrix
Systems
3845 MIB Private Enterprise Number. Used for SNMP MIB
Object ID and Active Directory Schema Object

MetaFrame Access Suite are fully integrated, making it easy to add


and extend the value of your MetaFrame implementation.
Citrix MetaFrame Presentation Server for Windows. The foundation of the Citrix
MetaFrame Access Suite, Citrix MetaFrame Presentation Server for Windows is the

! " #
world’s most widely deployed software for centrally managing heterogeneous
applications and delivering their functionality as a service to workers, wherever
they may be.
Citrix MetaFrame Presentation Server for UNIX. Provides users with secure access to
UNIX and Java applications, supporting Sun Solaris, HP-UX, and IBM AIX
platforms.
Citrix MetaFrame Secure Access Manager. Provides secure, single-point access over
the Web to any enterprise resource, including email, applications, network file
services, Internet and intranet sites, and documents. Allows you to protect your
corporate resources while providing secure access, consistent presentation, and easy
navigation for mobile users who may be connecting from anywhere. You can create
and integrate policies to tailor access to different scenarios, such as providing
differentiated levels of trust or permissions based on the identification of a
corporate device or a security scan of the client device. With a powerful set of easyto-
use, wizard-driven configuration tools, you can enable secure access, configured
for each user’s business needs, to your IT infrastructure.
Citrix MetaFrame Password Manager. The most efficient enterprise single sign-on
solution, providing password security and enterprise single sign-on access to
Windows, Web, and host-based applications. Users authenticate once with a
single password, and MetaFrame Password Manager does the rest, automatically
logging into password-protected information systems, enforcing password
policies, and even automating end-user tasks, including password changes.
MetaFrame Password Manager makes connecting to applications faster and more
secure, and can significantly lower help-desk support costs.
Citrix MetaFrame Conferencing Manager. Adds intuitive application conferencing to
MetaFrame Presentation Server that eliminates the geographical distance between
team members, increases the productivity of meetings, and allows easy
collaboration.

! " #
New in Citrix presentation Server Release 3.0

Products in the Citrix MetaFrame Access Suite are fully integrated, making it easy
to add and extend the value of your MetaFrame implementation.
Citrix MetaFrame Presentation Server for Windows. The foundation of the Citrix
MetaFrame Access Suite, Citrix MetaFrame Presentation Server for Windows is
the world's most widely deployed presentation server for centrally managing
heterogeneous applications and delivering their functionality as a service to
workers, wherever they may be.
Citrix MetaFrame Presentation Server for UNIX. Provides users with secure access to
UNIX and Java applications, supporting Sun Solaris, HP-UX, and IBM AIX
platforms.
Citrix MetaFrame Secure Access Manager. Provides secure, single-point access over
the Web to a wide range of internal and external information resources, including
applications, data sources, documents, Web content and services. With a powerful
set of easy-to-use, wizard-driven configuration tools, IT administrators can enable
browser-based access to the entire enterprise.
Citrix MetaFrame Password Manager. Provides universal password security and
single sign-on access to Windows, Web, proprietary, and host-based applications
running within the MetaFrame environment.
Users authenticate once with a single password and MetaFrame Password Manager
does the rest, automatically logging onto any password-protected information
systems, enforcing password policies, monitoring all password-related events, and
even automating end-user tasks.
Citrix MetaFrame Conferencing Manager. Adds intuitive application conferencing to
MetaFrame Presentation Server that eliminates the geographical distance between
team members, increases the productivity of meetings, and allows easy
collaboration.

! " #
Simplified Licensing for the MetaFrame Access Suite
MetaFrame Presentation Server 3.0 uses a new method of licensing. Before you can
use MetaFrame Presentation Server, you must install Citrix licensing, which
includes a license server and a user interface for managing licenses known as the
License Management Console. After you install Citrix licensing, download a
license file from mycitrix.com and store it on the license server.
Whenever you start MetaFrame Presentation Server, it contacts the license server to
verify that you have a license for this product. The License Management Console
lets you run reports to discover when licenses expire, configure the license server,
and display license alerts. The console also provides a handy interface for
downloading license files. You can also manage the license server by using
command line tools and a configuration file known as the options file. Management
of licensed products is simplified in the following ways:
• All MetaFrame Access Suite products now use the same license management
console
• You centrally manage and monitor license usage
• You can access your licensing data remotely
• You can create reports allowing you to analyze trends in license usage
• An electronic backup of all licenses is stored at Citrix
• You can share licenses across farms
Enhanced Support for Large Farms
Zone data collectors now monitor server load information for their own zone
instead of the entire farm. This behavior reduces traffic among zones when users
connect to applications, especially in large farms where zones are connected across
high latency links
Zone Preference and Failover
A new policy rule enables you to direct user connections to preferred zones and set
transparent failover to backup zones when preferred servers are unavailable. When
users open applications, the Zone Preference and Failover policy rule directs their
connections to the server with the highest zone preference and lightest load
Extended Policies
You can now create policies to apply connection settings based on server groups, IP
addresses, and client names—in addition to users or user groups as in earlier
releases. New policy rules give you broader control over bandwidth limits, zone
connection preferences, audio options, and printing.
You can use new policy rules to do such things as:
• Direct user connections to a local zone and set failover options to other zones
• Route print jobs directly from the server to the printer rather than through the
client device
• Control bandwidth limits for sessions
• Control audio sound quality used by client devices
The examples cited above include only a few of the new capabilities provided with
connection policies. You can view other new and enhanced policy rules under the
Policies node of the Presentation Server Console.
Enhanced Delegated Administration
With Enhanced Delegated Administration, you can delegate areas of MetaFrame
Presentation Server administration and farm management. Administrators can
assign specialized 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.
SpeedScreen Flash Acceleration
SpeedScreen Flash Acceleration allows you to optimize the way
MetaFrame Presentation Server renders and passes Macromedia Flash animations
to users. Flash animations are a common component of many Web sites and Web
applications.
SpeedScreen Image Acceleration
Using lossy image compression, SpeedScreen Image Acceleration offers you a
trade-off between the quality of photographic image files as they appear on client
devices and the amount of bandwidth the files consume on their way from server to
client. Lossy image compression reduces the size of image files the server sends to
the client by removing redundant or extraneous data from the files.
Session Reliability
Session Reliability keeps ICA sessions active and on the user’s screen when
network connectivity is interrupted. Users continue to see the application they are
using until network connectivity resumes without re-authentication prompts.
Ability to Hide Disabled Applications
When you disable a published application, you can choose to hide it from lists of
published applications. Hiding the application prevents it from appearing in a user’s
Start menu, Program Neighborhood application set, application folder, or taskbar
while the application is disabled. This option is useful if you need to temporarily
disable a published application while you apply updates or address an issue with the
data source. By default, a disabled application continues to appear in lists of
published applications.
Dynamic Session Reconfiguration
This feature creates a smoother experience for users who switch between client
devices with varying display modes by reconfiguring window appearance
appropriately between devices. When reconnecting to a session on a client device
with different display modes, users do not need to reconfigure the color depth and
resolution. Dynamic session reconfiguration automatically adapts the existing
session’s display mode to the reconnecting client device’s display capabilities and
mode preference.

New Features in Installation Manager


Installation Manager is included with the Enterprise Edition of MetaFrame
Presentation Server.
Enhanced Delegated Administration
With the new Enhanced Delegated Administration feature, you have greater
flexibility and control over the tasks that you delegate to IT staff. For example, the
new Install and Uninstall Packages permission allows you to control which servers
your delegates can deploy packages to using Installation Manager.
Rolling Out Package Groups Using Apputil
The apputil command lets you roll out published applications over additional
servers. Enhancements to apputil in this release provide the ability to roll out
Installation Manager package groups on additional servers. When you run apputil,
the package is scheduled for immediate installation on the target servers.
New Features in Resource Manager
Resource Manager is included with the Enterprise Edition of MetaFrame
Presentation Server, and incorporates the following new features and

! " #
$

enhancements.
Failed Import Alerts
Resource Manager now warns you of failed attempts to update the summary
database, and can be configured to send alerts under these circumstances. In its red
state, a new icon on the Summary Database tab identifies failures to commit the last
update to the database. The Summary Database Configuration dialog box now
allows you to notify administrators of any such failure.
Enhanced Delegated Administration
Enhanced Delegated Administration in Resource Manager allows you to delegate
the tasks of controlling applications and analyzing system and application data to
custom administrators.
Compatibility with Asian Language Web Servers
In the past, some users of European language versions of MetaFrame Presentation
Server Clients could not launch published applications from the Web Interface
running on an Asian language Web server. This would occur when the name of the
application as it appeared on the Web Interface contained Asian language
characters that the European language client was unable to recognize and process.

New in Citrix presentation Server Release 4.0

SmoothRoaming for Personal Access Continuity

Printing Performance Improvements


A new version of the Universal Printer Driver enables MetaFrame Presentation
Server to use the Windows Enhanced MetaFiles Format (EMF) for transferring
print jobs from client to server. This improves printing performance, especially time
to print. You also now have access to more printer properties, such as additional
paper trays and finishing options (stapling and sorting, for example).

Printing Control Improvements


You can now allocate network printers to users through session printers policies
instead of through the properties page of the Printer Management node. This
enables you to create customized printing workspaces based on any policy criteria
without the use of complex logon scripting. When a user logs on to a server, session
printers policies determine:
• Which network printers to connect within a session
• Whether or not a particular printer should be the user’s default printer
• Whether or not the user can override default values for common network printer
settings
When upgrading a prior version of MetaFrame Presentation Server, the installer
automatically converts printer settings into equivalent settings in printer policy
rules.
To administer auto-connect printer objects for servers of versions prior to this
release, you can use a Presentation Server Console locally that matches the server
version.
Further printing enhancements include shorter, more user-friendly client printer
names, and dynamic printers and ports—client printers and ports are visible and
accessible only within the session in which they are created.
USB Synchronization for PDA Devices

! " #
You can synchronize a client-connected USB PDA device using application
software running on MetaFrame Presentation Server, rather than only through
applications on the client device. This feature supports USB-tethered and Microsoft
Windows powered PDAs that use ActiveSync as a synchronization agent.
PDA synchronization is available in the Advanced and Enterprise Editions of
MetaFrame Presentation Server.
Redirection Support for TWAIN Devices
MetaFrame Presentation Server can now redirect client-connected TWAIN
imaging devices, notably document scanners, from the client to the server,
regardless of connection type. This allows users to control client-attached imaging
devices from applications that run on the server; the redirection is transparent.
To capture an image, users connect to a server from a client machine that has an
imaging device and the associated vendor-supplied TWAIN driver installed locally.
When the TWAIN application is run from within this session, the application
detects and interacts with the client-side device. The server-based application that is
accessed runs in the way as a client-based application.
Redirection support for TWAIN devices is available in the Advanced and
Enterprise Editions of MetaFrame Presentation Server.
Smart Card Roaming
SmoothRoaming now enables users to use their smart cards to log on and off
automatically through Program Neighborhood Agent.
This is very useful in an environment where employees use computers as terminals
that are scattered across a facility. To log on automatically and retrieve applications,
an employee inserts a smart card into a terminal. To log off automatically, the
employee simply removes the card.
To gain greater flexibility when a user logs on and off, use SmoothRoaming in
conjunction with workspace control. For more information about workspace
control,
Application Isolation Environments
Application isolation environments solve issues arising from application
compatibility and interoperability in the server environment. These issues not only
increase total cost of ownership, but can potentially hamper the deployment of
MetaFrame Presentation Server on an enterprise-wide level.
Application compatibility issues in a server environment can be characterized as
follows:
Registry conflicts. Applications that do not conform to Microsoft’s guidelines for
use of HKEY_LOCAL_MACHINE can cause a number of problems, such as
limiting the application to run as a single instance, overwriting the previous user’s
settings, an increased likelihood of crashes, or in a worst-case scenario, allowing a
user to read the previous user’s credentials. Conflicts can also occur between
applications, especially between multiple versions of the same application.
DLL versioning. Applications can install a specific version of a DLL in a system
folder while another application overwrites that DLL with a different version,
causing the first application to execute incorrectly. For most applications, installing
a different version removes or conflicts with prior versions.
Incompatibility with Terminal Services. Some applications do not run successfully in
a Terminal Services environment and therefore do not run successfully on
MetaFrame Presentation Server. Incompatibility with Terminal Services is often
caused by registry conflicts, system conflicts, and system objects conflicts.
Post-installation configuration requirements. Many applications require postinstallation
expertise to run successfully on MetaFrame Presentation Server.
Extensive testing requirements. The possibility of application conflicts either at

! " #
%

install or run time requires extensive predeployment testing, which is expensive and
time-consuming.
Maintenance of aging legacy systems. Using and maintaining legacy applications
that support essential business processes are crucial in many organizations. Often
such applications cannot coexist with modern applications and need to be installed
on dedicated servers.
Application isolation environments enable you to publish:
• Multiple versions of applications on a single server
• Applications that were not designed for multiuser or terminal services
Environments

Virtual IP Address and Virtual Loopback Address


Support
Using virtual IP addresses, you can publish applications that require separate IP
addresses per session. This is especially important to Computer Telephony
Integration (CTI) applications, which are widely used in call centers. If an
application you are publishing requires a unique IP address for each user session or
requires a unique loopback address, after publishing the application you can
configure your server to supply virtual IP addresses or a virtual loopback address.
You can use virtual IP addresses or virtual loopback for applications that fail or
malfunction when running in multiple, concurrent sessions. Failure and
malfunctions usually occur with custom applications that are not intended to
operate with Windows Terminal Services. The operational requirements of an
application determine whether it requires a virtual IP address or a virtual loopback
address.
Users of these applications can access them on MetaFrame Presentation Server in
the same way that they access any other published application.
Virtual IP addressing and loopback addressing are available in the Advanced and
Enterprise Editions of MetaFrame Presentation Server.

CPU Utilization Management


CPU utilization management increases perceived single-server scalability. It does
so by modifying the normal job priority scheduling in the operating system. CPU
utilization management smoothes out the normal CPU peaks that most applications
have. In a typical deployment running MetaFrame Presentation Server, a certain
amount of CPU utilization is reserved on each server to handle these CPU spikes.
By normalizing the CPU consumption by each user, the amount of CPU that must
be reserved to handle these spikes can be reduced.
CPU utilization management also limits very CPU-intensive applications to a
limited share of the CPU, so that one user does not inadvertently have an
inappropriate adverse affect on other users.
CPU utilization management makes the CPU time consumed by users easier to
predict. This enables you to better estimate the number of users who can connect to
a server and the number of servers that are required.
CPU utilization management is available only in the Enterprise Edition of
MetaFrame Presentation Server.

! " #
&

Virtual Memory Optimization


Virtual memory optimization enables you to improve application performance and
virtual memory usage through DLL loading optimization. DLL loading
optimization ensures that components of a process load at their preferred base
addresses. As a result, overall virtual memory consumption on the server is
significantly reduced, providing more room for additional users and applications.
The Presentation Server Console contains new options to enable, disable, and
schedule virtual memory optimization.
Virtual memory optimization is available only in the Enterprise Edition of
MetaFrame Presentation Server.

Multi-Language User Interface Support for the Web


Interface
Language packs are provided to localize the Web Interface into the following
languages: English, German, Spanish, French, and Japanese. A language pack
allows you to display sites in a given language, including resource files and
localized images. You can also allow users to select a language when they log on;
the page is then reloaded in that language.

Simplified Customization of the Web Interface


You can now customize the appearance of the Web Interface through the Access
Suite Console, rather than by scripting or custom coding. Some of the options are:
• Overall layout. Customize the overall screen layout or allow users to customize
the layout.
• Branding. Format the screen with a customized look and feel using branding
colors, logo images, and header images.
• Applications window. Specify the window title bar color or image, title bar text
color, number of application icon columns that are displayed, and allow users to
customize these settings.
• Welcome area. Specify the title bar background color, title bar text color,
welcome message text language, welcome message text, and any additional
languages.

New in Citrix presentation Server Release 4.5


Configuration Logging
Configuration Logging enables you to keep track of administrative changes made
to your server farms: which administrator made the change, what the change was,
and when it was made. It also enables you to revert those changes if necessary.
You can also create a Report Center report that lists these details, and also
indicates whether or not the change was successful, the object the change
affected, and various further details of the change
Health Monitoring & Recovery
You can proactively monitor farm health by running Health Monitoring tests on
servers to ensure that if one of them has a problem (for example the Citrix IMA
Service may be down, or there may be a problem with Terminal Services), this does
not interfere with the user’s ability to access the application through another server.

! " #
You can specify different recovery actions to be taken automatically if a server fails
a test; these include restarting the server or preventing it from being used for load
balancing until the problem is fixed.

Citrix Application Streaming


The application streaming feature simplifies application deployment to users.
With the application streaming feature, you can install and configure an
application on one file server and deliver it to any desktop or server on demand.
Upgrading or patching an application is simple, because you are required only to
update or patch an application stored in one place: on the file server

Further Enhancements in this Release


Alerts storage and reporting. Alerts can now be stored in the Resource
Manager summary database, together with related information such as when the
alert occurred and which server was affected. This enables you to create a report
listing all the alerts that were generated during a particular period of time.
Microsoft Operations Manager 2005 support. The Citrix Presentation Server
Management Pack now provides full support for MOM 2005 features.
Monitoring profiles. Rather than configuring metrics for each server, you can
configure a set of metrics, save them as a monitoring profile, then apply that
profile to a range of servers.
Automatic proxy detection support. Proxy servers can be automatically
detected: this means users do not have to configure the proxy server manually. In
larger environments, this also means administrators do not have to support
incorrect or dynamic configurations. For further information
Program Neighborhood Agent backup URL support. Administrators can
specify backup URLs for Program Neighborhood Agent in their Web Interface
configuration. In addition, if Program Neighborhood Agent cannot connect to the
Web Interface, administrators can specify backup URLs in a new .MSI package
property.
Multilingual user interface. The Windows Installer package automatically
installs the clients in all supported languages. Beginning with version 10.0 of the
Clients for Windows, language-specific installation packages are no longer
available.

How to ADD additional language in Citrix


Luckily for us, it’s easy to add additional languages to WI4. In this article, I’ll show you how easy it is to
add Danish or any other new language to WI. All that’s required is a little file editing and some
translation skills.

All of the WI4 language files are located on the WI4 server in the "\Program Files\Citrix\Web
Interface\4.0\languages" folder.

! " #
'

As you can see from the picture above, all you have to do is create a new set of language files from the
existing ones. In this picture, "Danish (DK)" has been added. The *.lang files contain the definition of the
languages. For example, the "dk.lang" file is a text file that contains the definition of the language in the
following format:

FriendlyName=Dansk (Danish)

From here it’s just some hard work to get your own files translated. The main strings are located in
"common_strings_languageID.properties" and "metaframe_strings_languageID.properties" files. An
example of a Danish translation from "common_strings_DK.properties" could be:

ForMetaFrame=til MetaFrame
OK=OK
VersionTitle=Citrix Presentation Server
Help=Hjælp
SelectConnectionSpeed=Forbindelses hastighed:
Custom=Tilpasset
HighBandwidth=Høj - Kabel/DSL/LAN
MediumHighBandwidth=Mellem høj - Modem (>33K)
MediumBandwidth=Mellem - Modem (<=33K)
LowBandwidth=Lav - GPRS/Trådløs
ReconnectTo=Genforbinder til:
DisconnectedApplicationsOnly=Afbrudte programmer
AllApplications=Alle programmer
LogIn=Log på
Welcome=Velkommen
PleaseLogin=Venligst log på
MessageCenter=Meddelelses Center
MessageCenter1=Meddelelses centret viser informationer og eventuelle fejl beskeder.
Settings=Indstillinger

! " #
Refresh=Opfrisk
Error=FEJL

The result is as follows (only partially translated so far):

If you want to limit your users in selecting specific languages just remove the files languageID.lang (i.e.
DK.lang) for the languages you don’t want your users to use.

If you want to remove the language option all together then just remove all the lang-files except the
English one. Now your users won’t be able to select any other language and everything will be in
English.

If time permits you can also translate the WI4 help files. The location is "\Program Files\Citrix\Web
Interface\4.0\localizedContent." Just create a new language folder, copy the English files into it, and
begin translating.

! " #