用户手册 — Wyse v90le

目录

• TABLE OF CONTENTS

  2
• Summary 3

  2
• Audience 3

  2
• Affected Products 3

  2
• Requirements/Issues 3

  2
• Procedure/Solution 4

  2
• Wyse Simple Imager Installation on a Windows 2003 server 4

  2
• WSI installation on a Windows XP Professional Machine 7

  2
• Wyse Simple Imager Usage 10

  2
• Troubleshooting 13

  2
• The thin client gives an “ARP Timeout” error when attempting to image it. 13

  2
• Getting “Incompatible Firmware” messages. 13

  2
• The image was sent to the thin client but the device boots normally. 13

  2
• A DHCP server is not installed on my XP machine. Where can I get one? 13

  2
• Getting “Illegal TFTP operation” error messages on the thin client. 13

  2
• When attempting to image I get a message “Boot file not found” 13

  2
• Getting “File not found” error messages 14

  2
• Not getting an IP Address 14

  2
• Getting the following Error: “Failure: Firmware is not compatible” 14

  2
• After re-imaging, the Thin Client reboots and starts the process again, and becomes and endless loop. 14

  2
• Getting an error “PXE-E78” on the thin client and cannot re-image. 15

  2
• When re-imaging a device, the thin client reboots as normal. 15

  2
• I have a Viance Desktop device, what model should I pick? 15

  2
• I have one of the new R series devices, what model should I select? 15

  2
• I have one of the larger laptops devices, what model should I select? 15

  2
• I followed the instructions and I still can’t image the thin client. 15

  2
  • Summary

    3
• This is a Quick Start Guide to help you install and run the Wyse Simple Imager version 1.3.6

  3
  • Audience

    3
• Customers, 1st Level Support, and Systems Engineering Group

  3
  • Affected Products

    3
• Wyse Simple Imager V1.3.6

  3
  • Requirements/Issues

    3
• Execution of this application requires

  3
•  A Windows 2000 server SP4 or Windows 2003 SP1 server (If you wish to use Windows XP Pro SP2, see important notes below), IN AN ISOLATED NETWORK.

  3
• IT CANNOT BE INSTALLED ON THE SAME SERVER WITH WYSE DEVICE MANAGER.

  3
•  The WSI server and Thin Client MUST BE CONNECTED TO EACH OTHER BEFORE INSTALLING THE SOFTWARE. Failure to connect the devices before installation will result in a loopback network condition and a subsequent inability to re-image your thin clients.

  3
•  DHCP, IIS with FTP Services installed and running

  3
•  Single network adapter supported. If you have two adapters, you must disable one

  3
•  All software firewalls and Antivirus services stopped

  3
•  A simple hub, unmanaged (inexpensive) switch or a crossover cable

  3
•  Wyse Simple Imager software V1.3.6

  3
•  An image file for the device requiring the image

  3
• IMPORTANT for Windows XP Pro SP2 Users:

  3
• 1. You will need to provide a working DHCP server. Windows XP Pro does not include one.

  3
• 2. When installing and using WSI, ensure to run it on an isolated network.

  3
• 3. See Page 7 for installation instructions on Windows XP Pro.

  3
• NOTE: If a previous version of WSI exists, you must remove it before installing this version.

  3
  • Procedure/Solution

    4
  • Wyse Simple Imager Installation on a Windows 2003 server

    4
• 1. Verify that IIS, FTP services are installed and running. (Refer to Microsoft documentation for details)

  4
• 2. Setup FTP. Browse to “Settings\Control Panel\Administrative Tools\Internet Information Services (IIS) Manager” and launch the applet.

  4
• From the IIS Manager screen (Figure 1), select the “Default FTP Site” on the right pane, then “Right Click” and select “Properties”.

  4
• NOTE: If you cannot find this option, verify that FTP services are installed.

  4
• Figure 1 - Windows 2003 Server IIS Manager - FTP Site Select

  4
• 3. Select the “Home Directory” Tab (Figure 2). Verify that the “Read, Write, Log visits” privileges are set, and the MS-DOS® option is selected.

  4
• Figure 2 - Check FTP Configuration – Windows 2003 Server

  4
• 4. Verify DHCP. Before installing WSI, make sure that DHCP is running. You can do this by connecting a device to the server’s hub, unmanaged switch or crossover cable and verify that you get an IP address. If this is not the case, correct the problem first. IF DHCP IS NOT RUNNING, DO NOT INSTALL WSI.

  5
• 5. Install Wyse Simple Imager.

  5
•  Double-click on the WSISetup.exe file and follow the installation prompts. Use the “default” installation parameters. Verify that the installation path is the same as the Default path of the IIS FTP root path (see Figure 2).

  5
• Figure 3 - FTPRoot Install Path

  5
• 6. After WSI Setup is complete, a Wyse Simple Imager shortcut will be created on the desktop from which the application can be run.

  5
• Figure 4 - WSI Icon

  5
• 7. Setup TFTPD. From “Start”, go to “Run” and browse

  5
• C:\inetpub\ftproot\rapport\tools\sa\util and run the file TFTPD32.exe.

  5
• 8. Enter the following information in the TFTPD32 settings screen

  6
• o Security = None

  6
• o Server Configuration

  6
• Timeout = 3

  6
• MAX Retransmit = 40000

  6
• TFTP Port = 69

  6
• o Base Directory

  6
• C:\InetPub\FTProot\Rapport\Tools\sa

  6
• o Advanced TFTP Options

  6
• Option Negotiation = Enabled

  6
• Show Progress bar = Enabled

  6
• Activate Tftpd32 on this interface = Enabled

  6
• Figure 5 - TFTPD32 Settings

  6
  • WSI installation on a Windows XP Professional Machine

    7
• Follow these three steps:

  7
• 1. CONNECT:

  7
• Connect your Windows XP Professional machine and the device(s) you need to re-image via a simple hub, unmanaged switch or a crossover cable. Verify that the Thin Client has power, a monitor, keyboard and mouse attached, but it’s NOT powered-on. During the WSI installation, a Proxy server is installed. If the devices are not connected, a loopback network connection is created and you will not be able to image your devices.

  7
• Note: Disable all software firewalls and antivirus.

  7
• 2. INSTALL:

  7
• Install the required software components IIS, FTP, DHCP and WSI.

  7
• Note: For this example we are using DHCP turbo. This program is not supplied nor supported by Wyse.

  7
• 3. CONFIGURE:

  7
• Configure TCP/IP properties, TFTPD, DHCP turbo and FTP in that order.

  7
• TCP/IP properties (See Figure 6)

  7
• Set the TCP/IP properties for the alternate configuration as follows:

  7
• IP address: 10.1.1.12

  7
• Subnet mask: 255.255.255.0

  7
• Default gateway: 10.1.1.254

  7
• Figure 6 - Alternate Configuration Settings.

  7
• TFTPD (Figure 7)

  8
• i. Setup TFTPD. From “Start”, go to run and browse C:\inetpub\ftproot\rapport\tools\sa\util and run the file TFTPD32.exe.

  8
• ii. Enter the following information in the TFTPD32 settings screen (Figure 7)

  8
•  Security = None

  8
•  Server Configuration

  8
• o Timeout = 3

  8
• o MAX Retransmit = 40000

  8
• o TFTP Port = 69

  8
•  Base Directory

  8
• o C:\InetPub\FTProot\Rapport\Tools\sa

  8
•  Advanced TFTP Options

  8
• o Option Negotiation = Enabled

  8
• o Show Progress bar = Enabled

  8
• o Activate Tftpd32 on this interface = Enable

  8
• iii. Click “OK” and close the window.

  8
• Figure 7 - TFTDP Settings

  8
• Figure 8 - DHCP Turbo settings

  8
• DHCP Turbo (Figure 8)

  8
• DHCP Scope need not be set, but here are the recommended parameters:

  8
• Scope Information:

  8
• Start Address: 10.1.1.13

  8
• End Address: 10.1.1.20

  8
• Mask: 255.255.255.0

  8
• Lease: 6 Hours or less

  8
• FTP

  9
• Browse to Control Panel\Administrative Tools\Internet Information Server Default FTP Site then “Right Click” select “Properties” then select the “Home Directory” Tab. Verify that the “Read, Write, Log visits” privileges are set, and the MS-DOS® option is selected.

  9
• Figure 9 - Default FTP Properties

  9
• Press “Apply” and “OK”

  9
• Verify that all software firewalls and antivirus are disabled.

  9
• Restart DHCP Turbo before you start WSI.

  9
• Where to get DHCP Turbo: http://www.tucows.com

  9
  • Wyse Simple Imager Usage

    10
• 1. Connect the client (to be imaged) to the Wyse Simple Imager machine, through a hub, unmanaged switch or cross-over cable.

  10
• 2. Launch Wyse Simple Imager

  10
• 3. Select the appropriate Product you wish to image from the Product list.

  10
• 4. Click on the “Add” button Figure 5

  10
• Figure 10 - Select Product and Firmware

  10
• Figure 11 - Completed WSI Add Image page

  10
• Note: A recent change in manufacturing to make our devices ROHS compliant, required us to use different hardware components and make changes to the software to accommodate and recognize these components. To address this issue and to prevent any damage to the hardware with Wyse Simple Imager, new "Product Numbers" where added.

  10
• To avoid an “Incompatible Firmware” message or an “Imaging and re-booting” loop, check the part number of your thin client, and use the following table to cross reference your thin client model to the equivalent model to select under WSI 1.3.6 when "Adding" or “Submitting” the new firmware into WSI. This is only for the Sx0 and Vx0 series.

  10
• Part Number

  10
• WSI Model

  10
• Part Number

  10
• WSI Model

  10
• S12

  10
• V92

  10
• S32

  10
• V32

  10
• S52

  10
• V52

  10
• S92

  10
• V92

  10
• V32

  10
• V32

  10
• V52

  10
• V52

  10
• V92

  10
• V92

  10
• V12

  10
• V32

  10
• V32

  10
• V52

  10
• V52

  10
• V92

  10
• V92

  10
• 5. Fill in the fields with appropriate values. WSI uses these parameters to build the directory structures and filenames.

  11
• Where

  11
• Product

  11
• Provides a dropdown list of the supported models.

  11
• IMPORTANT: For the V30L / V30LE use V32, for the V50L / V50LE use V52, and for the V90L / V90LE use V92.

  11
• Image Version

  11
• Refers to the Firmware version and could be a numerical value such as 559. This value is normally part of the filename you downloaded from Wyse.

  11
• Flash Size

  11
• This parameter is from the amount of Flash memory installed in your device. You can use this parameter to separate image files if your environment includes multiple versions of the same device and you need specific image files for the amount of flash memory on the devices. Sizes can be 16M, 32M, 192M, 256M, 512M, etc.

  11
• Description

  11
• For your information. This information will help you identify the characteristics of the device this image is for. (See figure 6 for an example).

  11
• Important: Use only “Alpha Numeric” (A through Z, 0 through 9, underscore ( _ ) or spaces.

  11
• Image File

  11
• The name of the file you wish to add. Click on the browse button to see navigate to the list of available files. This should be the directory where you unzipped the downloaded image file.

  11
• 6. Click on the “Browse” button and select the image file which is already downloaded/given from Wyse.

  11
• 7. Click “Ok” and wait for the message ‘Image is successfully added”.

  11
• Figure 12 - WSI Successful Image Added message

  11
• 8. Added image will appear in the firmware list.

  11
• 9. Select the firmware and click on “Submit”.

  11
• 10. The TFTP application will automatically launch. Note: this application window should not be closed until the client is successfully imaged with the new firmware.

  12
• Figure 13 - TFTPD Application window

  12
• 11. Wait for the message ‘Please start/restart the client to start imaging’.

  12
• Figure 14 - Restart Client Message window.

  12
• 12. Click “Ok” and the “Log message” screen will appear.

  12
• Start/Reboot the client. When client finishes the imaging process, the Log screen will display the log messages and the final status. If the imaging was successful, ‘Success’ will be displayed. If it failed, it will display an error message.

  12
  • Troubleshooting

    13
• Problem 1:

  13
  • The thin client gives an “ARP Timeout” error when attempting to image it.

    13
• Solution 1:

  13
• This means that the thin client was unable to get an IP address from your DHCP server ARP=Address Resolution Protocol). This indicates a problem with your DHCP Server. If you have DHCP Turbo installed, de-install it, re-install DHCP Turbo and configure it using parameters on page 8.

  13
• Problem 2:

  13
  • Getting “Incompatible Firmware” messages.

    13
• Solution 2:

  13
• Review notes on page 10 of this document.

  13
• Problem 3:

  13
  • The image was sent to the thin client but the device boots normally.

    13
• Solution 3:

  13
• 1. Verify the boot order. Power on the thin client, press and hold the “DEL” key to enter the BIOS setup. When prompted, enter the password “Fireport” (case sensitive). The first boot device should be set to “PXE” or “LAN”. If that is not the case, make the necessary changes.

  13
• 2. Verify that the FTP Server has “Write” permission enabled (page 9)

  13
• 3. Verify on the WSI server, the TFTPD screen. If you see an IP address of 127.0.0.1 anywhere, you have a loopback network condition. To recover from this, “De-Install WSI ONLY”, make sure you connect the WSI server and the thin client (with power applied to it, but NOT powered-on), and then re-install WSI. Refer to page 7 for more details.

  13
• 4. Verify the directory structure is set to:

  13
• c:\inetpub\ftproot\rapport

  13
• c:\inetpub\ftproot\rapport\tools

  13
• c:\inetpub\ftproot\rapport\tools\sa

  13
• 5. Check for spaces in the firmware filename under C:\inetpub\ftproot\rapport\<product>. FTP does not recognize spaces.

  13
• Problem 4:

  13
  • A DHCP server is not installed on my XP machine. Where can I get one?

    13
• Solution 4:

  13
• You can download a DHCP server (i.e. DHCP Turbo) from www.tucows.com. NOTE: This information is provided for your convenience and Wyse does not endorse or supports any of these programs.

  13
• Problem 5:

  13
  • Getting “Illegal TFTP operation” error messages on the thin client.

    13
• Solution 5:

  13
• Try re-imaging a different Thin Client. If the issue is resolved, you have a hardware problem and will need to send the defective Thin Client to our service department (1-800-800-9973 option 2 or www.wyse.com/serviceandsupport/service/service.asp ) for repair.

  13
• Problem 6:

  13
  • When attempting to image I get a message “Boot file not found”

    13
• Solution 6:

  13
• Verify that the “Scope” is set on DHCP Turbo as per the instructions on page 8. Also, if you have a VPN client installed on the WSI server, remove it and try again.

  13
• Problem 7:

  14
  • Getting “File not found” error messages

    14
• Solution 7:

  14
• Verify that your default FTP server address is set correctly using the IIS Administration utility

  14
• Problem 8:

  14
  • Not getting an IP Address

    14
• Solution 8:

  14
• Verify that the “Database” section of DHCP Turbo does not exceed five (5) IP Addresses. Otherwise just clear the displayed addresses and try again to connect.

  14
• Problem 9:

  14
  • Getting the following Error: “Failure: Firmware is not compatible”

    14
• Solution 9:

  14
• Open the most recent log file in the C:\INETPUB\FTPROOT\RAPPORT\TOOLS\SA\LOGS directory. Look for an error message similar to

  14
• Evaluating: Unable to Open Source (archive/ftp//anonymous:xxxx@10.1.1.12/Rapport/Wyse5S50\5150_128_WyseS505150/5S50.i2d)

  14
• Verify the path of the file. In the case of the path for the example above, it should be

  14
• C:\inetpub\ftproot\rapport\Wyse5S50\5150_128_WyseS505150

  14
• What you may find is that the path is actually:

  14
• C:\Inetpub\ftproot\Rapport\Wyse5S50\5150_128_WyseS505150,NewVersion

  14
• Note that an invalid character such as a “,” (comma) will cause the WSI to truncate from that point on, giving you the above message.

  14
• Solution: Rename the path so that you remove the invalid character. You can substitute the “,” (comma) for an underscore.

  14
• Problem 10:

  14
  • After re-imaging, the Thin Client reboots and starts the process again, and becomes and endless loop.

    14
• Solution 10:

  14
• Verify that the correct model was selected for the “Product” field when the “.i2d” file was added. See table on page 10 and compare the part number with the appropriate model.

  14
• To verify this problem open the most recent log file in the C:\INETPUB\FTPROOT\RAPPORT\TOOLS\SA\LOGS directory. Look for an error message similar to:

  14
• Evaluating:

  14
• 'ftp//anonymous:xxxx@10.1.1.12/Rapport/Tools/sa/9V90/push.k' to 'stream/sec/test'

  14
• Unable to Open Source (ftp//anonymous:xxxx@10.1.1.12/Rapport/Tools/sa/9V90/push.k)

  14
• If you have a V90LE, the directory it’s looking for should be “9V92”.

  14
• Solution: Re-import the “.i2d” file using V92 as the product”.

  14
• Problem 11:

  15
  • Getting an error “PXE-E78” on the thin client and cannot re-image.

    15
• Solution 11:

  15
• PXE-E78 means "Unable to locate boot server". The most common cause of this is when the WSI server is installed by itself with no other devices connected to the network; you get a "loopback" ip address created for the proxy server in WSI.

  15
• “De-Install WSI ONLY”, make sure you connect the WSI server and the thin client (with power applied to it, but NOT powered-on), and then re-install WSI. Refer to page 7 for more details.

  15
• Problem 13:

  15
  • When re-imaging a device, the thin client reboots as normal.

    15
• Solution 13:

  15
• To correct this problem, go to the WSI main screen (See figure 10), click on the “Delete Logs” button, and try re-imaging.

  15
• When a device is imaged, two log files are created. These files will have the extensions of “.log” and either “.fin” or “.end”

  15
• “.fin” indicates a “Successful” imaging of the device

  15
• .end” indicates a “Failure” to image a device

  15
• “.log” contains the “Transaction” information of the imaging process.

  15
• These files are located in the following directory:

  15
• C:\inetpub\ftproot\rapport\tools\sa\logs

  15
• You can also manually delete these files and try again.

  15
• Problem 14:

  15
  • I have a Viance Desktop device, what model should I pick?

    15
• Solution 14:

  15
• For a Viance Appliance, select model V72.

  15
• Problem 15:

  15
  • I have one of the new R series devices, what model should I select?

    15
• Solution 15:

  15
• If you have a Linux device (R50L) use the WSI model R60

  15
• If you have an XPe device (R90L or R90LE) use the WSI model R90

  15
• Problem 16:

  15
  • I have one of the larger laptops devices, what model should I select?

    15
• Solution 16:

  15
• If you have a Linux device (X50L) use the WSI model X62

  15
• If you have an XPe device (X90L or X90Le) use the WSI model X90

  15
• Problem 17:

  15
  • I followed the instructions and I still can’t image the thin client.

    15
• Solution 17:

  15
• De-Install WSI, De-Install DHCP Turbo. Read this document over and install according to the instructions.

  15
• Remember: When all else fails, READ THE INSTRUCTIONS.

  15
  • XP_Pro

    7
  • TFTPD

    8
  • DHCP_Turbo

    8
  • FTP

    9
  • WSI_Usage

    10
  • Figure_10

    10