Install Cisco Virtualization Experience Media Engine

Install Cisco Virtualization Experience Media Engine
Install Cisco Virtualization Experience Media
Engine
• Install Cisco VXME Components Workflow, page 1
• Download the Cisco VXME Client Add-on, page 2
• Download the Cisco VXME Agent, page 2
• Download the Cisco AnyConnect Add-on, page 3
• Create a Dell Wyse Device Manager Package, page 3
• Schedule an Update or a Push, page 7
• Enable AutoLogin, page 8
Install Cisco VXME Components Workflow
Important
The Cisco Jabber for Windows or Cisco UC Integration for Microsoft Lync version must match the Cisco
Virtualization Experience Media Engine for SUSE Linux version. See the "System Requirements" section
of the release notes documentation for your Virtualization Experience Media Engine release.
Procedure
Command or Action
Step 1
Download the Cisco VXME Client Add-on, on page 2
Step 2
Download the Cisco VXME Agent, on page 2
Step 3
(Optional)Download the Cisco AnyConnect Add-on, on page 3
Step 4
On the thin client, install the Cisco Virtualization Experience Media
Engine (VXME) prerequisite add-on.
Purpose
Only perform this step if
users require VPN
connectivity.
Deployment and Installation Guide for Cisco Virtualization Experience Media Engine for SUSE Linux Release 10.6
1
Install Cisco Virtualization Experience Media Engine
Download the Cisco VXME Client Add-on
Command or Action
Purpose
Step 5
On the thin client install the Cisco Virtualization Experience Media You can deploy Cisco
Engine (VXME) add-on. See Create a Dell Wyse Device Manager AnyConnect at the same
Package, on page 3.
time.
Step 6
On the HVD, uninstall any previously installed versions of Cisco
VXME Agent (formerly Cisco VXME Utilities) and Cisco Unified
Communications clients, such as Cisco Jabber, Cisco UC
Integration for Microsoft Lync, or Cisco Unified Personal
Communicator.
Step 7
On the HVD, install Cisco VXME Agent.
Step 8
On the HVD, install Cisco Jabber or Cisco UC Integration for
Microsoft Lync.
Related Topics
File Names
Download the Cisco VXME Client Add-on
Note
The CiscoVXMEClient.zip file includes a prerequisite add-on, which you must install on the thin client,
before you install the Cisco VXME Client add-on.
Procedure
Step 1
Step 2
Step 3
Step 4
Go to the following URL:
http://www.cisco.com/cisco/software/navigator.html
Choose Products > Unified Communications > Unified Communications Applications > Messaging >
Virtualization Experience Media Engine > Virtualization Experience Media Engine for SUSE Linux.
From the list, choose the file for your release.
Select Download or Add to cart and follow the prompts.
Download the Cisco VXME Agent
Install Cisco VXME Agent on the hosted virtual desktops (HVD), before you install Cisco Jabber for Windows.
If you plan to install Cisco UC Integration™ for Microsoft Lync, do not perform this procedure. Cisco UC
Integration™ for Microsoft Lync includes Cisco VXME Agent.
Deployment and Installation Guide for Cisco Virtualization Experience Media Engine for SUSE Linux Release
10.6
2
Install Cisco Virtualization Experience Media Engine
Download the Cisco AnyConnect Add-on
Procedure
Step 1
Step 2
Step 3
Step 4
Go to the following URL:
http://www.cisco.com/cisco/software/navigator.html
Choose Products > Unified Communications > Unified Communications Applications > Messaging >
Virtualization Experience Media Engine > Virtualization Experience Media Engine for SUSE Linux.
From the list, choose the file for your release.
Select Download or Add to cart and follow the prompts.
Download the Cisco AnyConnect Add-on
If users require VPN connectivity, download the Cisco AnyConnect add-on.
Procedure
Step 1
Step 2
Step 3
Step 4
Go to the following URL:
http://www.cisco.com/cisco/software/navigator.html
Choose Products > Unified Communications > Unified Communications Applications > Messaging >
Cisco Virtualization Experience Media Engine > Cisco Virtualization Experience Media Engine for
SUSE Linux.
From the list, choose the file for your release.
Select Download or Add to cart and follow the prompts.
Related Topics
File Names
Create a Dell Wyse Device Manager Package
Wyse Device Manager is the recommended deployment tool to deploy the Cisco Virtualization Experience
Media Engine add-on to the thin clients. See the Dell Wyse documentation for supported versions. You can
also use this procedure if the thin clients are already running the required base image and you want to deploy
an add-on.
Follow the optional steps in this procedure to deploy Cisco AnyConnect with the Cisco Virtualization
Experience Media Engine add-on. In the procedure examples, <version> means <[Release Number]-[Build
Number]-[Platform (SP2/SP3)].
Deployment and Installation Guide for Cisco Virtualization Experience Media Engine for SUSE Linux Release 10.6
3
Install Cisco Virtualization Experience Media Engine
Create a Dell Wyse Device Manager Package
Before You Begin
• Ensure that the thin clients are running the required firmware build; see Release Notes for Cisco
Virtualization Experience Media Engine for SUSE Linux for your release. If necessary, contact Dell
Wyse to get a compatible image.
• Obtain all of the required installation files: VXME, and if required, the optional AnyConnect VPN.
• Ensure that the thin clients are checked-in to Dell Wyse Device Manager (WDM). The devices should
appear green in WDM.
Procedure
Step 1
On the server, on which you have WDM installed, extract the add-on files to a local folder.
The extracted add-on folder structure appears as follows:
~/<local folder>/addons/vxme-pre-reqs-<version>.rpm
~/<local folder>/addons/cisco_vxme_client-<version>.rpm
~/<local folder>/addons/directory
Step 2
Step 3
(Optional) To deploy Cisco AnyConnect with Virtualization Experience Media Engine, extract
anyconnect_bundle.<version>.zip.
Copy vxme-pre-reqs-<version>.rpm and vxme-<version>.rpm to ~/CiscoVXME/CiscoVXME_x.x, where
x.x is your release number.
The folder structure is as follows:
~/CiscoVXME/CiscoVXME_x.x/install-sletc-addons.sh
~/CiscoVXME/CiscoVXME_x.x/update-addons-list
~/CiscoVXME/CiscoVXME_x.x/vxme-pre-reqs-<version>.rpm
~/CiscoVXME/CiscoVXME_x.x/cisco_vxme_client-<version>.rpm
~/CiscoVXME/CiscoVXME_x.x.rsp
Step 4
Step 5
(Optional) To deploy Cisco AnyConnect with Virtualization Experience Media Engine, copy the
anyconnect_bundle<version>.rpm file to ~/CiscoVXME/CiscoVXME_x.x where x.x is your release number.
(Optional) To deploy Cisco AnyConnect with Virtualization Experience Media Engine, add the following
line to update-addons-list: UPDATE_ADDONS_LIST+=" anyconnect_bundle-<version>.rpm"
UPDATE_ADDONS_LIST+=" anyconnect_bundle-<version>.rpm"
Step 6
Step 7
Step 8
Step 9
In the navigation pane of the Administrator Console, right-click Package Manager and then choose New >
Package.
In the Package Wizard window, select Register a Package from a Script File (.RSP), and then select Next.
Enter the path to the CiscoVXME_x.x.rsp file (where x.x is your release), and then select Next.
Tip
You can select Browse to find and choose the
file.
In the Software Package Information dialog, check Active, and then select Next.
This step makes the WDM package active for distribution.
Step 10 To create and register the WDM package, select Next.
Step 11 Select Finish.
WDM copies the package to the Master Repository, where it appears under the appropriate category. The
package is ready for distribution.
Deployment and Installation Guide for Cisco Virtualization Experience Media Engine for SUSE Linux Release
10.6
4
Install Cisco Virtualization Experience Media Engine
Folder Structure
What to Do Next
Use the Default Device Configuration (DDC) method to upgrade the thin client.
For information about additional configuration required to enable Cisco AnyConnect VPN connections, see
Cisco AnyConnect Secure Mobility Client.
Related Topics
File Names
Folder Structure
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:
Folder
Description
~\<packagename>.rsp
The unique RSP file, located in the same folder as the matching root package
folder.
~\<packagename>\
The root package folder. It stores the wlx folder and the add-ons folder. It
also stores the following files, which are used for imaging and updating
devices:
• Latest-image.raw
• Latest-image.raw.info
~\<packagename>\wlx
The main INI configuration folder. It stores the following:
• wlx.ini file and $MAC.ini file
• bitmap folder
• certs folder
• ini folder
~\<packagename>\wlx\bitmap The folder where you can place custom images you plan to use.
~\<packagename>\wlx\certs
The folder where you can place the CA certificates that can be imported to
a thin client.
Note
Use the Certs and ImportCerts INI parameters in the wlx.ini file to
import the certificates to thin clients.
~ \<packagename>\wlx\ini
The folder where you can place the {username}.ini files.
Deployment and Installation Guide for Cisco Virtualization Experience Media Engine for SUSE Linux Release 10.6
5
Install Cisco Virtualization Experience Media Engine
Scripts
Note
Folder
Description
~\<packagename>\addons
The folder where you can place the add-ons you want to use. It also stores
the folder file and the *.rpm packages available to be installed on the thin
client. The folder file should list all available add-ons. The folder file is
required in the add-ons folder to guarantee that add-ons are properly located.
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.
Scripts
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
Deployment and Installation Guide for Cisco Virtualization Experience Media Engine for SUSE Linux Release
10.6
6
Install Cisco Virtualization Experience Media Engine
Schedule an Update or a Push
~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.sletc11sp2.rpm and aaaa-xxxx-2.2.2.sletc11sp2.rpm
# Specifiy these two add-ons as below
# UPDATE_ADDONS_LIST+=" abcd-xyz-1.1.1.sletc11sp2.rpm"
# UPDATE_ADDONS_LIST+=" aaaa-xxxx-2.2.2.sletc11sp2.rpm"
#
UPDATE_ADDONS_LIST+=" abcd-xyz-1.1.1.sletc11sp2.rpm.rpm"
UPDATE_ADDONS_LIST+=" aaaa-xxxx-2.2.2.sletc11sp2.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
Schedule an Update or a Push
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.
Important
We strongly recommend that you use the Default Device Configuration (DDC) method to push packages
to the thin clients. The Drag-and-Drop method may function, but it is only recommended in small
environments or for test purposes. Drag-and-Drop does not function at all for thin clients behind a Cisco
AnyConnect VPN.
Deployment and Installation Guide for Cisco Virtualization Experience Media Engine for SUSE Linux Release 10.6
7
Install Cisco Virtualization Experience Media Engine
Enable AutoLogin
Enable AutoLogin
AutoLogin is disabled by default (AutoLogin=no). If enabled, the AutoLogin feature automatically logs the
user in as the Default User, unless you cancel the AutoLogin before the CountDown interval expires. You
can cancel AutoLogin by pressing the ESC key. This feature is useful for kiosk environments.
To enable the AutoLogin feature, change the AutoLogin parameter in the wlx.ini file to AutoLogin=yes. For
more information about how to edit the wlx.ini file, or about the AutoLogin or Countdown parameters, see
the INI reference guide for the thin client.
User Mode
If you enable AutoLogin, the thin client automatically boots and signs in as the default user (thinuser mode),
which restricts user access.
In thinuser mode, the FireFox shortcut does not appear in the Start menu and xterm does not appear in the
Application Browser. Users can access System Information by clicking an icon in the notification area of the
task bar. To set up access to FireFox, edit the wlx INI file to specify the required parameters.
Example:
CONNECT=BROWSER \
Description="Cisco Home Page" \
URL=http://www.cisco.com \
Resolution=FullScreen \
Mode=Normal
After application of the new wlx INI file, an icon for FireFox appears on the thin client desktop. For more
information about how to edit the wlx INI file, see the INI reference documentation for your device.
Note
Dell Wyse thin client users do not have access to the WDM icon in thinuser mode. This behavior is
expected because users do not need this access. If you require access WDM to troubleshoot device check-in
issues, you can open the application from xterm. For more information about how to manage Dell Wyse
thin clients, see the administrator guides for your base image version.
Deployment and Installation Guide for Cisco Virtualization Experience Media Engine for SUSE Linux Release
10.6
8
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising