The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
You can open System Information to verify the build version.
| Step 1 |
In the notification area of the taskbar, click the System Information icon. |
| Step 2 |
Click the Identity tab. |
| Step 3 |
In the System section, look for the Build line. |
You can use System Information to verify that Cisco VXME Client is installed. You can also verify the version of Cisco VXME Client or the version of another add-on.
| Step 1 |
In the notification area of the taskbar, click the System Information icon. |
| Step 2 |
Click the Packages tab. |
| Step 3 |
Scroll down the alphabetical list and look for cisco_vxme_client (or another add-on). The add-on versions appear in the Versions column. |
 Note |
By default, Secure Shell (SSH) is disabled. For information about how to enable SSH, see the administration guide for your thin client. |
| Step 1 |
Use SSH to connect to the thin client. |
| Step 2 |
Confirm the version of Cisco VXME Client. rpm -qa | grep vxme You can also use the versionInfo command. |
You can use the Windows Control Panel to verify that Cisco VXME Agent is installed. You can also verify the version.
| Step 1 |
From Control Panel, open Programs and Features (Windows 7) or Programs (Windows 8). |
| Step 2 |
Scroll through the list of installed programs to locate Cisco VXME Agent. The Cisco VXME Agent version appears in the Versions column. |
The vxc process is part of Cisco Virtualization Experience Media Edition (VXME) and it must be running for VXME to function.
| Step 1 |
Use Secure Shell (SSH) to connect to the thin client. |
| Step 2 |
Search the running programs for vxc. ps -ef | grep -r vxc You should see the following lines: |
Users see a prompt to reconnect to their hosted virtual desktops (HVDs). After the users reconnect, Cisco Jabber call control features do not work.
This problem can occur if the thin client loses network connectivity.
To resolve this issue, have the users exit Cisco Jabber and disconnect from their HVDs. Next they can log back in to their HVDs and sign back in to Cisco Jabber to restore call control.
Users receive a prompt to log back in to their hosted virtual desktops (HVD) during an active call, and the call drops. The other party to the call has no indication that the call has ended, except the line is silent.
This issue can occur if the connection between the thin client and the HVD drops, causing a temporary loss of registration and call control.
To work around this issue, users can call the other party back. If the other party is not available, users can send an instant message (IM).
The Problem Reporting Tool (PRT) is a small program that automatically runs if Cisco Jabber encounters an unrecoverable error, unhandled exception, or crash. The tool collects logs from the thin client and hosted virtual desktop and then creates a problem report. The report is a zip file that you can send to the Cisco Technical Assistance Center (TAC), to provide the necessary information to solve the problem. The tool saves the file to the user's desktop.
If a user experiences an error that does not crash the software, the user can run the PRT from the Cisco Jabber menu; .
Users can generate a problem report from the Windows Start menu if Cisco Jabber is not running. To access the tool from outside the application, choose .
 Tip |
Advise users to include a memory dump with the problem report if Cisco Jabber crashes. |
We recommend that users provide a description of the circumstances that lead up to the error. For more detailed information about how to run the PRT, see the Troubleshooting section in the applicable user guide.
Note |
Users must accept the privacy agreement to run the PRT. |
If the virtual channel goes down, the Problem Reporting Tool (PRT) cannot gather the Virtualization Experience Media Edition logs from the thin client. You can use Dell Wyse Device Manager (WDM) to gather the logs.
You must have an FTP server set up, if you want to use FTP.
| Step 1 |
In WDM, right-click on the thin client and select Execute Command. |
| Step 2 |
In the Execute dialog box, enter the following command. This step collects the logs and creates a compressed package. |
| Step 3 |
Send the file to the FTP server, by entering the following command. Where 1.1.1.1 is the IP address of the FTP server: |
| Step 4 |
Remove the .tar.gz file, by entering the following command. |
Feedback