INI Files Reference Guide for Cisco Virtualization Experience Client 2112/2212 ICA Firmware Release 8.0
Sample INI files
Downloads: This chapterpdf (PDF - 1.1MB) The complete bookPDF (PDF - 2.48MB) | The complete bookePub (ePub - 199.0KB) | Feedback

Sample INI files

Sample INI files

Sample user INI file

#
# This is an example of a file that specifies an environment for a
# particular user. If the sign-on name is user1, this file would
# be named user1.ini and must be located in the ini subdirectory
# of the wnos directory. This file completes the environment
# description started by wnos.ini, in that it contains additional
# connection definitions, specification of a display resolution to
# be used for this user, and (possibly) designation of this user
# as one who has additional privileges.
#
# CAUTION: The user PASSWORD string is included here for reference
# only. It must not be created manually or modified by the network
# administrator. It is an encrypted string generated and entered
# by the Cisco VXC unit; it can be changed only by the user via
# the Cisco VXC Change Password dialog box (see Cisco VXC
# ICA Appliance Users Guide). Initially a new user account does
# not require a password, but as soon as one is entered (or
# subsequently changed) the Cisco VXC device encrypts it and places
# the encryption string on the first line of this file. If the user
# forgets the password for this account, the network administrator
# can delete the entire PASSWORD line to allow the user to create a
# new password. The format is:
#
# PASSWORD = [Encrypted user password string created by
# the Cisco VXC]
#
# The following password entry was automatically encrypted and
# entered by a Cisco VXC as a result of typing "user" as the
# password.
#
PASSWORD = lFmaRU6KufIAU
#
# The following directive establishes this user as one who has the
# ability to view and alter the network configuration on any
# Cisco VXC on which this user is logged in. It also grants the
# ability to temporarily define new connections and view and/or
# temporarily alter existing connection definitions using the
# Connection Settings dialog box. If the argument to this
# directive is set to zero or if the directive is omitted from
# the user1.ini file, the individual(s) using this sign-on do not
# have this privilege.
#
privilege=1
#
# The following directive establishes the maximum display
# resolution available to this user. If the attached display
# device is capable of communicating with the Cisco VXC using the
# DDC II protocol and the monitor has a lesser display capability
# than contained in the directive, the lower resolution will be
# used. Even if the monitor is capable of higher resolutions than
# defined in this directive, they will not be used while this user
# is logged on. The statement can be used to adapt the device to
# the visual abilities of a user. The example limits the display
# to an image 800 pixels wide by 600 pixels high.
#
resolution=800x600
#
# The following directive establishes the maximum time a connection
# can be idle before the Cisco VXC will disconnect from the host.
# The default value used if the directive is omitted is zero,which
# means that the client will never disconnect. Otherwise, the
# units are minutes and the range of acceptable values is from 10
# to 480 (8 hours). The server may also have a configured idle
# time that is independent of this setting.
#
inactive=150
#
# The following directive describes the ICA connection to a
# published application (WordPad for this example). The connection
# is started as soon as the user signs on. When it terminates, the
# user remains signed on and a standard desktop is displayed. The
# connection can be reactivated by signing off and on again or by
# selecting either the corresponding icon or the entry in the
# Connect Manager dialog box. Note that the directive is continued
# onto multiple lines. Continuation is accomplished by putting the
# following characters at the end of each line to be continued:
#
# \<Enter>.
#
# This only works if there is no space between the \ and the
# <Enter> character (the line will not be continued otherwise).
# There must also be a space between each argument on the
# reassembled line. The continuation sequence does not constitute
# a space; instead, each argument has a trailing blank space.
# Leading <TAB> characters on the continuation line serve the same
# function and also contribute to the overall readability. The
# function of each of the arguments is:
#
# connect=ica Specifies that this is a connect statement
# and that the type of connection is ICA,
# (currently, ICA is the only supported
# connection type). This must be the first
# item specified on the line.
# description="x" Text to appear either under the icon on the
# Cisco VXC desktop or in the Connect Manager
# The text must be surrounded by double
# quotation marks if it contains space or
# punctuation characters.
# icon=default The bitmap to be used for the Cisco VXC
# desktop display. The argument is either
# default or a file name. If a file name is
# specified, it must be located in the bitmap
# directory under the wnos directory on the
# FTP server.
# username=me The username on the server which runs the
# published application. The username
# determines the privileges and default
# directory used on the server.
# password="x@y" The password for the specified username.
# The password must be surrounded by double
# quotation marks if it contains spaces or
# punctuation characters. This is the actual
# unencrypted password for the account.
# domainname=mine The Windows domain which defines the
# specified username.
# browserip=a,b,c The IP address(es) or DNS name(s) of
# machines that might be the ICA master
# browser. When the master browser is
# contacted, it is used to resolve the
# application name to a specific server that
# can provide the requested service. In this
# example, a list of possible master browsers
# is provided. The servers on the list are
# accessed in order until one is found that is
# operational. That server is consulted for a
# resolution of the published application
# name. To establish a connection
# successfully, the first operational server
# contacted must be capable of resolving the
# application name.
# application=Notepad The name of an application published
# using MetaFrame administrative tools. This
# application will be run when a server has
# been selected and the login to the server
# is successful.
# autoconnect=1 The connection will be attempted as soon as
# this file has been processed and any
# software updates have been completed.
#
# The username, password and domainname fields may be omitted if
# the ICA anonymous user provides sufficient access and privilege
# to accomplish the intended task.
#
connect=ica \
description="Word processing" \
icon=default \
username=me password="x z" domainname=sqa \
browserip=nil,132.237.176.7 \
application=wordpad \
autoconnect=1
#
# The following directive describes the ICA connection to a fixed
# server. When the connection is activated, it will stop when the
# login dialog box for the ICA server is displayed. The user must
# log in manually and run applications using a normal desktop
# display. No master browsers are named, so the host name must be
# either resolvable by the locally contactable ICA master browser
# or by the DNS server in use. The name will be resolved by
# appending the DNS domain name to the host name and querying the
# DNS servers. Both pieces of information might be obtained from
# a properly configured DHCP server or might come from the local
# network configuration.
#
connect=ica \
host=seven \
description="Lab machine" \
icon=lab.bmp
# Note: it is recommended to start each statement at the beginning
# of a new line, and all continuation options are indented with a Tab
# character or multiple spaces for readability.

Sample sign-in INI file

#
# This file provides an example of an environment where all users
# will log on following processing of this file. Each user will
# have (potentially) a different desktop display of available
# connections. Each user may have a different password for
# authentication.
#
# The user desktop displayed following sign-on will be a combination
# of connections specified here (global) and connection specified
# in their individual environment specifications. Cisco VXC
# is capable of accepting up to 16 connection definitions, total.
# Those defined globally will be displayed first, followed by those
# specified for the individual. If the sum of the number of
# connections in the two files exceeds sixteen only the first
# sixteen will be processed.
#
# The following directive enables the use of the sign-on dialog box.
#
signon=1
#
# The following directive allows the Cisco VXC to attempt to
# locate code files on the FTP server and to update the current
# code on the device if the version on the server is different.
#
autoload=1
#
# The following URL specifies a bitmap file which overlays the top
# left part of the sign-on dialog box. It can be used to present a
# company logo, special instructions for the day (of limited length)
# or any other desired customization. The Cisco VXC will attempt to
# locate the file in the directory named bitmap, directly under the
# directory named wnos, which contains this file.
#
formurl=blazer.bmp
#
# The following directive causes the Cisco VXC to use a different
# FTP server. This overrides and replaces the fileserver in the
# local network setup and/or the one obtained from DHCP option 161.
# It will be used from the time this directive is processed until
# the value in the local user interface is manually edited, until a
# new value is obtained from a DHCP server on reboot, or until
# another fileserver directive is processed. Until reset using one
# of the named methods, the new value will persist across reboots
# and power cycle events. The argument may be either an IP address
# or a DNS name.
#
FileServer=filesrv.cisco.com
#
# The following directive causes the Cisco VXC to access a different
# path on the FTP server. This overrides and replaces the path in
# the local network setup and/or the one obtained from DHCP option
# 162. Its characteristics are the same as the fileserver
# directive. When this is actually used, the directory name wnos
# will be appended to the rootpath before use. For instance,
# (assuming that the DHCP server does not supply values for options
# 161 and 162) immediately after the reboot following the processing
# of these two directives the Cisco VXC will start an FTP session
# with fileserv.cisco.com and attempt to retrieve
# /blazer/cisco/wnos/wnos.ini
#
RootPath=blazer/cisco
#
# The following directives specify the global connections that
# will be present on all user desktops or in all user Connect Lists
# following sign-on.
#
# The following directive will, when activated, establish a
# connection to a specific ICA server. Note that the directive is
# continued onto multiple lines. Continuation is accomplished by
# putting the following characters at the end of lines to be
# continued:
#
# \<Enter>
#
# This only works if there is no space between the \ and the
# <Enter> character; the line will not be continued otherwise. The
# function of each of the arguments is:
#
# connect=ica Specifies that this is a connect statement
# and that the type of connection is ICA,
# (currently, ICA is the only supported
# connection type). This must be the first
# item specified on the line.
# description="x" Text to appear either under the icon on the
# Cisco VXC desktop or in the Connect List.
# The text must be surrounded by double
# quotation marks if it contains spaces or
# punctuation.
# icon=default The bitmap to be used for the Cisco VXC
# desktop display. The argument is either
# default or a file name. If a file name is
# specified, it must be located in the bitmap
# directory under the wnos directory on the
# FTP server.
# host=IP The IP address or DNS name of the ICA server
# to be contacted when this connection is
# established.
# username=me The username on the server that runs the
# published application. The username
# determines the privileges and default
# directory used on the server.
#
# Since the following connection omits the password and domainname
# fields, the client will attempt to perform a login using no
# password and the default domain (whatever was last used on that
# system). This will probably fail and present the user with
# a login dialog box. This is more secure than putting passwords
# into a file on an FTP server, which can be downloaded by anyone.
#
connect=ica \
description= "Global1" \
icon=noname.ico \
host=132.237.20.80 \
username=test1 password="test password"
# Note: it is recommended to start each statement at the begining
# of a new line, and all continuation options are indented with a Tab
# character or multiple spaces for readability.

Sample kiosk INI file

##
# This file provides an example of an environment where all users
# will use the same ICA connection to perform their work. The
# connection will start as soon as the unit is turned on. In this
# example the connection is to a published application (which could
# be a Windows desktop, but is not in this example).
#
# The following directive disables display of the sign-on dialog
# box.
#
signon=0
#
# The following directive allows the Cisco VXC to attempt to
# locate code files on the FTP server and to update the current
# code on the unit if the version on the server is different.
#
autoload=1
#
# The following directive describes the ICA connection to a
# published application (NotePad in this example). The description
# field provides text that identifies the connection, either under
# the icon on the Cisco VXC desktop (if an icon is specified) or in
# the Connect List dialog box. Note that the directive is continued
# onto multiple lines. Continuation is accomplished by putting the
# following characters at the end of the line to be continued:
#
# \<Enter>
#
# This only works if there is no white space between the \ and the
# <Enter> character (the line will not be continued otherwise).
# There must also be white space between each argument on the
# reassembled line. The continuation sequence does not constitute
# white space; instead, each argument has a trailing blank. The
# leading <TAB> characters on the continuation line serve the same
# function and also contribute to the overall readability. The
# function of each of the arguments is:
#
# connect=ica Specifies that this is a connect statement
# and that the type of connection is ICA
# (currently, ICA is the only supported
# connection type). This must be the first
# item specified on the line.
# description="x" Text to appear under the icon on the Cisco VXC
# desktop and in the Connect List dialog box.
# The text must be surrounded by double
# quotation marks if it contains white space
# or punctuation.
# icon=default The bitmap to be used for the Cisco VXC
# desktop display. The argument is either
# "default" or a file name. If a file name is
# specified, it must be located in the bitmap
# directory under the wnos directory on the
# FTP server.
# username=me The username on the server that runs the
# published application. The username
# determines the privileges and default
# directory used on the server.
# password="x@y" The password for the specified username.
# The password must be surrounded by double
# quotation marks if it contains punctuation
# or spaces. This is the unencrypted password
# for the account.
# domainname=mine The Windows domain that defines the specified
# username.
# browserip=a,b,c The IP address(es) or DNS name(s) of machines
# that might be the ICA master browser. When
# the master browser is contacted, it resolves
# the application name to a specific server
# that can provide the requested service. In
# this case, a list of possible master browsers
# is provided. The servers on the list are
# accessed in order until one is found that is
# operational. That server is consulted for a
# resolution of the published application name.
# To establish a connection successfully, the
# first operational server contacted must be
# capable of resolving the application name.
# application=notepad The name of an application published
# using MetaFrame administrative tools. This
# application will be run as soon as a server
# has been selected and the login to the server
# is successful.
# autoconnect=1 The connection will be attempted as soon as
# this file has been processed and any software
# updates have been completed.
#
# The username, password and domainname fields may be omitted if the
# ICA anonymous user provides sufficient access and privilege to
# accomplish the intended task.
#
connect=ica \
description="Text capture" \
icon=default \
username=me password="x z" domainname=sqa \
browserip=nil,132.237.176.7 \
application=notepad \
autoconnect=1
# Note: it is recommended to start each statement at the begining
# of a new line, and all continuation options are indented with a Tab
# character or multiple spaces for readability.