Guia De Configuração Rápidaíndice analíticoTABLE OF CONTENTS2Summary 32Audience 32Affected Products 32Requirements/Issues 32Procedure/Solution 42Wyse Simple Imager Installation on a Windows 2003 server 42WSI installation on a Windows XP Professional Machine 72Wyse Simple Imager Usage 102Troubleshooting 132The thin client gives an “ARP Timeout” error when attempting to image it. 132Getting “Incompatible Firmware” messages. 132The image was sent to the thin client but the device boots normally. 132A DHCP server is not installed on my XP machine. Where can I get one? 132Getting “Illegal TFTP operation” error messages on the thin client. 132When attempting to image I get a message “Boot file not found” 132Getting “File not found” error messages 142Not getting an IP Address 142Getting the following Error: “Failure: Firmware is not compatible” 142After re-imaging, the Thin Client reboots and starts the process again, and becomes and endless loop. 142Getting an error “PXE-E78” on the thin client and cannot re-image. 152When re-imaging a device, the thin client reboots as normal. 152I have a Viance Desktop device, what model should I pick? 152I have one of the new R series devices, what model should I select? 152I have one of the larger laptops devices, what model should I select? 152I followed the instructions and I still can’t image the thin client. 152Summary3This is a Quick Start Guide to help you install and run the Wyse Simple Imager version 1.3.63Audience3Customers, 1st Level Support, and Systems Engineering Group3Affected Products3Wyse Simple Imager V1.3.63Requirements/Issues3Execution of this application requires3 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.3IT 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 running3 Single network adapter supported. If you have two adapters, you must disable one3 All software firewalls and Antivirus services stopped3 A simple hub, unmanaged (inexpensive) switch or a crossover cable3 Wyse Simple Imager software V1.3.63 An image file for the device requiring the image3IMPORTANT for Windows XP Pro SP2 Users:31. You will need to provide a working DHCP server. Windows XP Pro does not include one.32. When installing and using WSI, ensure to run it on an isolated network.33. See Page 7 for installation instructions on Windows XP Pro.3NOTE: If a previous version of WSI exists, you must remove it before installing this version.3Procedure/Solution4Wyse Simple Imager Installation on a Windows 2003 server41. Verify that IIS, FTP services are installed and running. (Refer to Microsoft documentation for details)42. Setup FTP. Browse to “Settings\Control Panel\Administrative Tools\Internet Information Services (IIS) Manager” and launch the applet.4From the IIS Manager screen (Figure 1), select the “Default FTP Site” on the right pane, then “Right Click” and select “Properties”.4NOTE: If you cannot find this option, verify that FTP services are installed.4Figure 1 - Windows 2003 Server IIS Manager - FTP Site Select43. Select the “Home Directory” Tab (Figure 2). Verify that the “Read, Write, Log visits” privileges are set, and the MS-DOS® option is selected.4Figure 2 - Check FTP Configuration – Windows 2003 Server44. 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.55. 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).5Figure 3 - FTPRoot Install Path56. After WSI Setup is complete, a Wyse Simple Imager shortcut will be created on the desktop from which the application can be run.5Figure 4 - WSI Icon57. Setup TFTPD. From “Start”, go to “Run” and browse5C:\inetpub\ftproot\rapport\tools\sa\util and run the file TFTPD32.exe.58. Enter the following information in the TFTPD32 settings screen6o Security = None6o Server Configuration6Timeout = 36MAX Retransmit = 400006TFTP Port = 696o Base Directory6C:\InetPub\FTProot\Rapport\Tools\sa6o Advanced TFTP Options6Option Negotiation = Enabled6Show Progress bar = Enabled6Activate Tftpd32 on this interface = Enabled6Figure 5 - TFTPD32 Settings6WSI installation on a Windows XP Professional Machine7Follow these three steps:71. CONNECT:7Connect 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.7Note: Disable all software firewalls and antivirus.72. INSTALL:7Install the required software components IIS, FTP, DHCP and WSI.7Note: For this example we are using DHCP turbo. This program is not supplied nor supported by Wyse.73. CONFIGURE:7Configure TCP/IP properties, TFTPD, DHCP turbo and FTP in that order.7TCP/IP properties (See Figure 6)7Set the TCP/IP properties for the alternate configuration as follows:7IP address: 10.1.1.127Subnet mask: 255.255.255.07Default gateway: 10.1.1.2547Figure 6 - Alternate Configuration Settings.7TFTPD (Figure 7)8i. Setup TFTPD. From “Start”, go to run and browse C:\inetpub\ftproot\rapport\tools\sa\util and run the file TFTPD32.exe.8ii. Enter the following information in the TFTPD32 settings screen (Figure 7)8 Security = None8 Server Configuration8o Timeout = 38o MAX Retransmit = 400008o TFTP Port = 698 Base Directory8o C:\InetPub\FTProot\Rapport\Tools\sa8 Advanced TFTP Options8o Option Negotiation = Enabled8o Show Progress bar = Enabled8o Activate Tftpd32 on this interface = Enable8iii. Click “OK” and close the window.8Figure 7 - TFTDP Settings8Figure 8 - DHCP Turbo settings8DHCP Turbo (Figure 8)8DHCP Scope need not be set, but here are the recommended parameters:8Scope Information:8Start Address: 10.1.1.138End Address: 10.1.1.208Mask: 255.255.255.08Lease: 6 Hours or less8FTP9Browse 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.9Figure 9 - Default FTP Properties9Press “Apply” and “OK”9Verify that all software firewalls and antivirus are disabled.9Restart DHCP Turbo before you start WSI.9Where to get DHCP Turbo: http://www.tucows.com9Wyse Simple Imager Usage101. Connect the client (to be imaged) to the Wyse Simple Imager machine, through a hub, unmanaged switch or cross-over cable.102. Launch Wyse Simple Imager103. Select the appropriate Product you wish to image from the Product list.104. Click on the “Add” button Figure 510Figure 10 - Select Product and Firmware10Figure 11 - Completed WSI Add Image page10Note: 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.10To 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.10Part Number10WSI Model10Part Number10WSI Model10S1210V9210S3210V3210S5210V5210S9210V9210V3210V3210V5210V5210V9210V9210V1210V3210V3210V5210V5210V9210V92105. Fill in the fields with appropriate values. WSI uses these parameters to build the directory structures and filenames.11Where11Product11Provides a dropdown list of the supported models.11IMPORTANT: For the V30L / V30LE use V32, for the V50L / V50LE use V52, and for the V90L / V90LE use V92.11Image Version11Refers 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.11Flash Size11This 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.11Description11For your information. This information will help you identify the characteristics of the device this image is for. (See figure 6 for an example).11Important: Use only “Alpha Numeric” (A through Z, 0 through 9, underscore ( _ ) or spaces.11Image File11The 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.116. Click on the “Browse” button and select the image file which is already downloaded/given from Wyse.117. Click “Ok” and wait for the message ‘Image is successfully added”.11Figure 12 - WSI Successful Image Added message118. Added image will appear in the firmware list.119. Select the firmware and click on “Submit”.1110. The TFTP application will automatically launch. Note: this application window should not be closed until the client is successfully imaged with the new firmware.12Figure 13 - TFTPD Application window1211. Wait for the message ‘Please start/restart the client to start imaging’.12Figure 14 - Restart Client Message window.1212. Click “Ok” and the “Log message” screen will appear.12Start/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.12Troubleshooting13Problem 1:13The thin client gives an “ARP Timeout” error when attempting to image it.13Solution 1:13This 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.13Problem 2:13Getting “Incompatible Firmware” messages.13Solution 2:13Review notes on page 10 of this document.13Problem 3:13The image was sent to the thin client but the device boots normally.13Solution 3:131. 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.132. Verify that the FTP Server has “Write” permission enabled (page 9)133. 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.134. Verify the directory structure is set to:13c:\inetpub\ftproot\rapport13c:\inetpub\ftproot\rapport\tools13c:\inetpub\ftproot\rapport\tools\sa135. Check for spaces in the firmware filename under C:\inetpub\ftproot\rapport\<product>. FTP does not recognize spaces.13Problem 4:13A DHCP server is not installed on my XP machine. Where can I get one?13Solution 4:13You 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.13Problem 5:13Getting “Illegal TFTP operation” error messages on the thin client.13Solution 5:13Try 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.13Problem 6:13When attempting to image I get a message “Boot file not found”13Solution 6:13Verify 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.13Problem 7:14Getting “File not found” error messages14Solution 7:14Verify that your default FTP server address is set correctly using the IIS Administration utility14Problem 8:14Not getting an IP Address14Solution 8:14Verify 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.14Problem 9:14Getting the following Error: “Failure: Firmware is not compatible”14Solution 9:14Open the most recent log file in the C:\INETPUB\FTPROOT\RAPPORT\TOOLS\SA\LOGS directory. Look for an error message similar to14Evaluating: Unable to Open Source (archive/ftp//anonymous:xxxx@10.1.1.12/Rapport/Wyse5S50\5150_128_WyseS505150/5S50.i2d)14Verify the path of the file. In the case of the path for the example above, it should be14C:\inetpub\ftproot\rapport\Wyse5S50\5150_128_WyseS50515014What you may find is that the path is actually:14C:\Inetpub\ftproot\Rapport\Wyse5S50\5150_128_WyseS505150,NewVersion14Note that an invalid character such as a “,” (comma) will cause the WSI to truncate from that point on, giving you the above message.14Solution: Rename the path so that you remove the invalid character. You can substitute the “,” (comma) for an underscore.14Problem 10:14After re-imaging, the Thin Client reboots and starts the process again, and becomes and endless loop.14Solution 10:14Verify 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.14To 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:14Evaluating:14'ftp//anonymous:xxxx@10.1.1.12/Rapport/Tools/sa/9V90/push.k' to 'stream/sec/test'14Unable to Open Source (ftp//anonymous:xxxx@10.1.1.12/Rapport/Tools/sa/9V90/push.k)14If you have a V90LE, the directory it’s looking for should be “9V92”.14Solution: Re-import the “.i2d” file using V92 as the product”.14Problem 11:15Getting an error “PXE-E78” on the thin client and cannot re-image.15Solution 11:15PXE-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.15Problem 13:15When re-imaging a device, the thin client reboots as normal.15Solution 13:15To correct this problem, go to the WSI main screen (See figure 10), click on the “Delete Logs” button, and try re-imaging.15When 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 device15.end” indicates a “Failure” to image a device15“.log” contains the “Transaction” information of the imaging process.15These files are located in the following directory:15C:\inetpub\ftproot\rapport\tools\sa\logs15You can also manually delete these files and try again.15Problem 14:15I have a Viance Desktop device, what model should I pick?15Solution 14:15For a Viance Appliance, select model V72.15Problem 15:15I have one of the new R series devices, what model should I select?15Solution 15:15If you have a Linux device (R50L) use the WSI model R6015If you have an XPe device (R90L or R90LE) use the WSI model R9015Problem 16:15I have one of the larger laptops devices, what model should I select?15Solution 16:15If you have a Linux device (X50L) use the WSI model X6215If you have an XPe device (X90L or X90Le) use the WSI model X9015Problem 17:15I followed the instructions and I still can’t image the thin client.15Solution 17:15De-Install WSI, De-Install DHCP Turbo. Read this document over and install according to the instructions.15Remember: When all else fails, READ THE INSTRUCTIONS.15XP_Pro7TFTPD8DHCP_Turbo8FTP9WSI_Usage10Figure_1010Tamanho: 1000 KBPáginas: 15Language: EnglishAbrir o manual