Professional Documents
Culture Documents
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.
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.
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.
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
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)
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:
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.
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.
Ans :- 2512
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.
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.
Most Preferred
Preferred
! " #
%
Default Preference
Not Preferred
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
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.
! " #
&
! " #
Ans:-
Ans:-
Operating System:
Windows 2000 Server, Windows 2000 Advanced Server, and Windows 2000
Datacenter with SP4
Windows Server 2003, Standard, Enterprise and Datacenter Editions.
Ans:- You can configure zone preference and failover in a policy’s properties.
! " #
'
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
! " #
• 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.
! " #
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.
! " #
on the server.
WMI Providers. (Enterprise Edition only.) Installs WMI providers
• 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
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.
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.
! " #
The mapping is accomplished through the use of rules that specify how an application behaves
within an 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
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.
! " #
$
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.
Idle Time. The amount of time during which the user has not interacted with the Application
! " #
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.
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
! " #
%
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).
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
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.
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
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.
! " #
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.
! " #
'
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
! " #
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.
! " #
$
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.
! " #
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
! " #
&
! " #
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.
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
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.
! " #