
Chapter 1
If a client machine has an ICA client already installed on it and the client machine connects to a
MetaFrame server with a more recent version of the ICA client files available, then that user will
be prompted to automatically install the update. You can configure the update settings with the
ICA Client Update Configuration tool.
ICA Client Update Configuration
When you first open this tool, it appears to present you with nothing more than a list of all the
ICA clients for the supported platforms. To a degree, this information is what the tool provides.
However, the tool’s a bit more than that. As I pointed out in the previous section, ICA clients can
be automatically updated on the client side if a client connects to a MetaFrame server with a
more recent version of the ICA client. The settings available for each of these clients determine
whether those automatic updates will take place and the conditions under which they will take
place. If you right-click on a client and choose Properties from the pop-up menu, you’ll see a
dialog box like the one in Figure 1.2.
As Figure 1.2 shows, the properties sheet contains four tabs. The Description tab shown gives
you basic information about the client file: its version, its description, and whether clients can
update to this version (an option you might want to disable if you’re working with a beta version
of a new client, for example).
The Update Options tab, which determines the client update settings, is the most complicated.
From this tab, you can decide whether users should be notified before their ICA clients are
updated (the options are Ask User, Notify User, or Transparent to just perform the update
without letting the user know). It also contains the version-checking settings so that you specify
whether the client should update only ICA clients older than this one (the default) or update any
ICA client to meet this version. From this tab, you can specify whether users whose clients are
being updated will be disconnected then reconnected when their ICA client files are updated
(No, by default) and whether to update ICA client files in the background while the user is
connected (Yes, by default). The amount of difference between client versions will determine
your settings. If the previous client files obviously lacked capabilities present in the version
being downloaded, such as support for full color, then you’d probably want users to be
disconnected then reconnect with the new client. Finally, from this tab you can create a message
to display to inform users whose ICA clients have been automatically updated.
The remaining tabs are simpler. From the Event Logging tab, you can check a box specifying
whether a log should record the event when updated clients are downloaded (No, by default) and
whether errors should be logged (Yes, by default). Finally, the Client Files tab is just a list of the
files used to support the ICA client.
Shadow Taskbar
Clicking the Shadow Taskbar opens a logon box that prompts you for the logon credentials of the
account you’ve used to log on. After you’ve provided them, a bar appears across the top of the
screen with a Shadow button on the left-hand side. To shadow a session, click that button to open
a dialog box like the one in Figure 1.3.
8
Kommentare zu diesen Handbüchern