Administration Guide for Cisco Virtualization Experience Client 2112/2212 ICA Firmware Release 7.1_118
Central configuration setup
Downloads: This chapterpdf (PDF - 1.15MB) The complete bookPDF (PDF - 6.18MB) | Feedback

Central configuration setup

Central configuration setup

Set up automatic updates and configuration

This appendix describes how to set up your environment to provide your zero clients running WTOS with automatic updates and configurations in three simple steps.


Note


For more detailed information on the network architecture and enterprise server environment needed to provide network and session services for your zero clients, see Automated updates and configuration using central configuration.



Tip


You can use Cisco Virtualization Experience Client Manager (Cisco VXC Manager) for more hands-on management of your zero clients. For information about configuring your zero clients to communicate with a Cisco VXC Manager server, see the Cisco VXC Manager related INI parameters in DHCP options setup and INI Files Reference Guide for Cisco Virtualization Experience Client 2112/2212.


For a Cisco VXC 2112/2212 zero client running WTOS to successfully access INI files and update itself from a server, you must set up the server with the correct folder structure (where the INI files and other update files are located), direct the zero client to the server, and then reboot or start the zero client.

After DHCP and servers are configured and available, the zero client checks (at each boot up) to see whether or not any updates are available on a predefined server (DCHP Option #161 specifies the server URL, DCHP Option #162 specifies the root path to the server). If updates are available, the updates are automatically installed.

Procedure
    Step 1   Prepare the Root Directory and Folder Structure on the Server:

    Set up the following folder structure on your server under the C:/inetpub/ftproot folder (for FTP) or C:/inetpub/wwwroot folder (for HTTP or HTTPS) and place your INI files and other necessary files inside the structure as noted (this list describes the folder structure, starting with the root directory).

    /cisco/

    (Required) The root directory. It stores the wnos folder.

    /cisco/wnos

    (Required) The main INI configuration folder.

    It stores the wnos.ini file and the following optional folders:

    • bitmap folder
    • cacerts folder
    • font folder
    • inc folder
    • ini folder
    • locale folder
    • trace folder
    /cisco/wnos/bitmap

    (Optional) The folder where you can place custom images you plan to use.

    /cisco/wnos/cacerts

    (Optional) The folder where you can place the CA certificates that can be imported to a zero client.

    Note   

    Use the AddCertificate INI parameter in the wnos.ini file to import the certificates to zero clients.

    /cisco/wnos/font

    (Optional) The folder where you can place font files for languages that require the file (Chinese Simplified, Chinese Traditional, Japanese, Korean).

    /cisco/wnos/inc

    (Optional) The folder where you can place the mac.ini files (note that the use of the parameter Include=$mac.ini will load “/wnos/inc/ mac-address.ini” so that you can use inc in the folder structure and use $MAC.ini).

    /cisco/wnos/ini

    (Optional) The folder where you can place the {username}.ini files and {group} folder.

    /cisco/wnos/locale

    (Optional) The folder where you can place locale message files.

    /cisco/wnos/trace

    (Optional) The folder where you can place the trace files that you can capture and play back (be sure to enable the parameter, EnableTrace=yes).

    Be sure to create/activate the two required MIME Types (.ini and .) under IIS (on a per site basis) to enable downloading. Also be sure your Web server can identify the file types used by the zero clients.

    To create/activate .ini:

    1. On your IIS server, use the File Types menu to add a New Type.
    2. In the File Type dialog box, enter the Associated extension .ini and Content type (MIME) text/plain.

    3. Click OK to apply the settings.

    To create/activate .:

    1. On your IIS server, use the File Types menu to add a New Type.
    2. In the File Type dialog box, enter the Associated extension . and Content type (MIME) text/plain.

    3. Click OK to apply the settings.

    For detailed instructions about adding the required MIME types, see HTTPS/​SSL server setup.

    Step 2   Direct the Zero Client to the Server Using DHCP Options

    After you set up the folder structure and populate it with the correct files, you must then direct the zero client to the location of the server using DHCP.

    Information about the server and root directory is obtained from the following DHCP options:

    • 161 - The server.
    • 162 - Root path to the file server (ftp/http/https).
      • If no root path is defined, /cisco is assumed.
      • If a root path is defined, the additional path will be appended to the URL supplied by option 161.
    • 184 - (Optional) Server username (to server specified in option 161).
    • 185 - (Optional) Server password (to server specified in option 161).

    Use the guidelines in DHCP options setup.

    Step 3   Reboot or Start the Zero Client

    After you reboot or start the zero client, it will look in the defined root path for the latest available image and update if necessary.