There are different methods that you can use to schedule an update or push a package to the thin clients. For more information about these methods, see the documentation for the thin clients and for the thin client management tool.

Note	All package names, filenames (including .rsp and .ini files), and folders must be lower-case.

For example, assuming <packagename>.rsp is the RSP file, the folder structure required to register the package is as follows:

Note	If a folder does not contain a required file for the package, the folder can be omitted from the package folder structure. For example, if the package contains no graphics, the \wlx\bitmap folder is not required.

After you register the package, the thin client management program stores the package files in the software repository under c:\inetpub\ftproot\Rapport\<packagename>.

Caution

Do not attempt to modify a registered package located in the Rapport folder. To modify a package, create and register a new package that includes the required changes.

You use the following scripts when you create a Dell Wyse Device Manager package.

Note	The examples for each script use variables for the filenames, which are different for each release.

install-sletc-addons.sh

#!/bin/bash
source /tmp/update-addons-list
WYSE_INIT_ADDON_UPDATE=/etc/wyseinit_factory_reset
NEED_REBOOT=no
for A in ${UPDATE_ADDONS_LIST} ; do
if [ -e /tmp/${A} ] ; then
/usr/sbin/addon-install /tmp/${A}
# Find WYSE_INIT addon among the list of
specified addons
WYSE_INIT=${A:0:9}
if [ "$WYSE_INIT" = "wyse_init" ] ; then
/bin/touch $WYSE_INIT_ADDON_UPDATE
/bin/sync
NEED_REBOOT=yes
fi
fi
done
sync
# WYSE_INIT addon needs reboot
if [ "$NEED_REBOOT" == "yes" ] ; then
/sbin/init 6
Fi

update-addons-list

# Quick guide
# Copy all the add-ons needs to be installed in to this directory
~install-sletc-addons/install-sletc-addons/
# Specify list of add-ons to be installed/updated preferably order
in which you wish to install as explained below
#
# Do not modify below line
UPDATE_ADDONS_LIST=
# Specify each add-on full name in separate line, with leading one
space enclosed inside quotes, as shown in below example
# Example:-
# Lets say you want to install following two add-ons
# abcd-xyz-1.1.1.sletc11sp3.rpm and aaaa-xxxx-2.2.2.sletc11sp3.rpm
# Specifiy these two add-ons as below
# UPDATE_ADDONS_LIST+=" abcd-xyz-1.1.1.sletc11sp3.rpm"
# UPDATE_ADDONS_LIST+=" aaaa-xxxx-2.2.2.sletc11sp3.rpm"
#
UPDATE_ADDONS_LIST+=" abcd-xyz-1.1.1.sletc11sp3.rpm"
UPDATE_ADDONS_LIST+=" aaaa-xxxx-2.2.2.sletc11sp3.rpm"

CiscoVXME_x.x.rsp

Note	This RSP script is provided as an example; you may need to specify different parameters depending on your environment. For details about how to create RSP files, see the administration guide for your thin client management software.

[Version]
Number=CiscoVXME_x.x
Description=Cisco Virtualization Experience Media Cisco Virtualization Experience Media Engine
OS=SLX
Category=Cisco
USE_Pxe=NO
[Script]
CO "SLX"
LU
SF "<regroot>/*" "/tmp/"
EX "dos2unix /tmp/update-addons-list"
EX "dos2unix /tmp/install-sletc-addons.sh"
EX "/bin/bash /tmp/install-sletc-addons.sh &"
EL

Add a desktop shortcut to the user documentation, for users who do not connect to their hosted virtual desktops in kiosk mode. Users can click the shortcut to access the documentation and to get help.

You can add a link to the Citrix landing page. This link is important for Citrix connections that operate in kiosk mode. In kiosk mode, the users have no access to the thin client desktop.

Note	You must be a Desktop Delivery Controller (DDC) administrator.

You can add a link to the VMware prelogin banner. This link is important for VMware connections that operate in kiosk mode. In kiosk mode, the users have no access to the thin client desktop.

Note	You must be a VMware Connection Server administrator.