Dell Wyse ThinOS Version 8.6.1 Administrator's Guide

Use the troubleshooting options

1. From the desktop menu, click Troubleshooting.
   The Troubleshooting dialog box is displayed.
2. Click the General tab, and do the following:

   

   • Select any one of the following target devices that you want to use for CMOS management:
     • USB—Select this option to set the USB drive as the destination device.
     • File Server—Select this option to set the file server as the destination device.
     • IDE—Select this option to set the local storage as the destination device. The destination is redirected to C: Disk of IDE.
   • Extract CMOS—Click this option to extract the CMOS settings and certain BIOS settings to the USB drive or file server based on your target device selection. ThinOS reads the CMOS settings from the SMBIOS Interface for Dell BIOS.

     NOTE: : You can only extract the BIOS settings that are supported by the INI parameter Device=DellCMOS. If you select the destination as IDE, the Extract CMOS option is not available.

   • Restore CMOS—Click this option to write the CMOS settings and BIOS settings from the USB drive to the target thin client.

     NOTE: : You can restore the BIOS settings that are supported by the INI parameter Device=DellCMOS. If you select the destination as IDE, the Restore CMOS option is not available.

   • Performance Monitor—Click this option to display the CPU usage history with frames per second (FPS), Memory, and Networking information. The graphs display on top of all windows.
   • Force Coredump—Click this option to forcibly generate the debug information for technical investigation when your system is not responding. Both the coredump file and the trap information image are saved to the local drive. After you restart the thin client, both the coredump file and trap issue screenshot file are uploaded to the /wnos/troubleshoot/ directory of the file server or a USB drive.
   • Export Shadow Tmp—Click this option to export temporary logs for debugging purpose. All log files can be exported to a USB drive or file server depending on the target configuration.
   • Export Screenshot—Click this option to export screenshots to the file server or a USB drive. The exported file name is added with build information for a better troubleshooting. If a screenshot is present in the clipboard, it is exported to the target location. If the screenshot is not available, the full screen is copied automatically and exported to the target location.
   • Export INI files—Click this option to export the global INI file (wnos.ini), ccm.ini, mac.ini, or other machine-based INI file to the file server or a USB drive. Only username.ini file cannot be exported.
   • Extract IDE trouble_shoot—Click this option to export all the data that is stored in the C:/wnos/trouble_shoot folder to the USB driver or file server. This option is available only when you select the destination as either USB or File Server.
   • Delete IDE trouble_shoot—Click this option to delete the folder C:/wnos/trouble_shoot from IDE.
   • Days to keep troubleshooting files in IDE—From the drop-down list, select the number of days you want to store the troubleshooting files in IDE. After you restart the thin client, the files in C:/wnos/trouble_shoot are checked. If the created date is older than the days you have selected, the troubleshooting files are automatically removed.
3. Click the Trace tab to configure the trace actions and delay on trace. The available options for trace action are None, Capture, and Playback.

   

4. Click the Capture tab, and configure the export event log, network capture, wireless capture, and capture USB packets as per your requirements.

   

   1. Export Event log—Click either the One-time or Persistent option to enable logging any unexpected error messages. You can turn off logging and check the logfile under the folder ftp:/wnos/trouble_shoot. Ensure to enable the Enable Trace option of the Privilege parameter in a wnos.ini file. For more information, see the Dell Wyse ThinOS INI Reference Guide.
   2. Enable SmartCard log—To enable the client to log error messages of the smart card, select the Enable SmartCard log check box.
   3. Enable Application Console Log—To enable the client to log error messages of an application console, select the Enable Application Console Log check box. All logs are saved to the trouble_shoot folder with the name TerminalName_proc_name_date_time.log.

      In the Application List field, enter the name of the application for which you want to generate logs. The name in the list can be part of the application name. For example, the PCoIP application name is /pcoip/pcoip and blast application name is /usr/lib/vmware/view/usb/horizon. If you want to generate logs for both PCoIP and Blast applications, enter pcoip;vmware in the Application List field. By default, the Application List filters are not applied and all logs are saved to the target folder.

   4. Network capture—Click either the One-time or Persistent option to enable the capture of network information. Enabling this option captures the network trace of all traffic coming in and out of the thin client to the USB drive or IDE. This option is available only when you select the destination drive as either USB or IDE.

      After you log in and use the Citrix Apps and Desktops server or network, you can view the /wnos/troubleshoot/[Terminal Name]_[ENET or WS].[Date_Time].pcap file in the USB drive. If you use IDE, the troubleshooting files are saved to C drive. You need to export troubleshooting files in IDE to either USB drive or file server and then view the relevant file.

      You can analyze using software such as a packet analyzer used for network troubleshooting, and analysis.

   5. Wireless capture—Click either the One-time or Persistent option to enable the capture of wireless network information. Enabling this option captures the wireless network trace of all traffic coming in and out of the thin client to the USB drive or IDE. This option is available only when you select the destination drive as either USB or IDE.
   6. Capture USB Packets—Click either the One-time or Persistent option to enable the capture of USB packets.
   7. Export PCoIP log—Click either the One-time or Persistent option to export PCoIP logs on the PCoIP-enabled clients.
5. Click the Ping tab, and use the following guidelines to start the ping-diagnostic utility and display response messages:

   

   • Enter Hostname or IP—Enter the IP address, DNS-registered hostname, or WINS-registered hostname of the target to be pinged.
   • Data area—Displays ping response messages. The ping command sends one echo request per second, calculates round-trip times and packet loss statistics, and displays a brief summary upon completing the calculation.
   • Start—Executes the ping command. If the host is operational and on the network, it responds to the echo request. By default, echo requests are sent until interrupted by clicking Stop.
   • Stop—Terminates the ping request and leaves the Ping dialog box open, so you can read the summary posted in the data area.

   NOTE: :

   Ping sends an echo request to a network host. The host parameter is either a valid hostname or an IP address. If the host is operational and on the network, it responds to the echo request. Ping sends one echo request per second and calculates round-trip times and packet loss statistics. It displays a brief summary upon completion of the calculation.

   The ping utility can be used to:

   • Determine the status of the network and various foreign hosts.
   • Track and isolate hardware and software problems.
   • Test, measure, and manage networks.
   • Determine the IP address of a host if only the hostname is known.

   Important: Not all network equipment responds to ping packets, as this is a common mechanism that is used in denial-of-service attacks. Lack of response does not necessarily indicate that the target of the ping is unusable for other purposes.

6. Click the Trace Route tab, and use the following guidelines to start the tracert diagnostic utility and display response messages:

   

   • Enter Hostname or IP—Enter the IP address, DNS-registered hostname, or WINS-registered hostname of the target to be traced.
   • Data area—Displays round-trip response time and identifying information for each device in the path.
   • Start—Executes the tracert command.
   • Stop—Terminates the tracert command and leaves the Trace Route dialog box open, so that you can read the information posted in the data area.

   The tracert utility traces the path from your thin client to a network host. The host parameter is either a valid hostname or an IP address. The tracert utility sends out a packet of information three times to each device (routers and computers) in the path and displays the round-trip response times and identifying information in the message box.

7. Click the Telnet tab, and do the following:

   

   1. Enter the hostname.
   2. Click Connect to connect to a remote host or device.
      The Telnet window is displayed, and the troubleshooting window is closed automatically.
8. Click OK to save your settings.