There may be several versions of firmware in the Wyse Winterms that are currently deployed in the field. The firmware versions possibly deployed and their ability to support upgrading via Wyse Remote Administrator 3000 are listed below:
|
Firmware Version |
RA 3000 Upgradeable |
|
3.2 (Build 228m) |
No |
|
3.3 (Build 289) |
Yes |
|
3.31 (Build 289.14) |
Yes |
|
3.32 Patch #7 (Build 289.57) |
Yes |
NOTE: Those Winterms that cannot be upgraded via Wyse Remote Administrator 3000 CAN be upgraded from the Winterm via the Terminal Tab (or Upgrade tab) accessible through the Winterm Connection Manager. The steps to upgrade the firmware are detailed below.
Determine the firmware version of the Winterm via Remote Administrator 3000. If the firmware version is less than 3.3.289.14, use the following procedures to download a newer version of firmware to the Winterm.
1. Cycle power on the Winterm.
2. Upon reboot, when the Winterm displays the Single Button Connect box, press ESC to access the Winterm Connection Manager. Note that if this Winterm has never been configured, it will boot to the Winterm Connection Manager automatically.
3. At the Winterm Connection Manager screen, press F2 to select Terminal Properties.
4. At the Terminal Properties screen, click the Terminal tab (if no Terminal tab, click the Upgrade tab).
5. Ensure the “Use Local FTP Information” radio button is selected, and enter the following information:
Server Name: 10.x.x.x (IP address of the FTP server)
Server Directory: WYSE\CE\LEO\NON-FP\USA (default path for the firmware binary file)
NOTE: The IP address specified above in the Server Name field is the IP address for the FTP server being used for firmware downloads and Winterm configuration management. This can be an NT Server 4.0 or TSE running IIS, or an NT Workstation 4.0 running PWS. The Server Directory is the path off the \\server\Intepub\ftproot subdirectory. It is not necessary to specify the Intepub\ftproot piece of the path.
6. Ensure the “User ID” field contains the user anonymous.
7. Click on Apply, and then click on Upgrade to begin the firmware download.
M WARNING: Before initiating the firmware download to the Winterm, ensure the firmware subdirectory contains the desired version of firmware. Use the following guidelines for determining which version of firmware resides in the download subdirectory:
|
Filename |
Firmware Version |
|
? |
3.2 (Build 228m) |
|
? |
3.3 (Build 289) |
|
L289_14Wye.bin |
3.31 (Build 289.14) |
|
L289_57Wye0.bin |
3.32 Patch #7 (Build 289.57) |
If the download subdirectory contains an incorrect version of firmware, copy the firmware files from the appropriate subdirectory to the download subdirectory specified below:
\\server\InetPub\ftproot\wyse\ce\leo\non-fp\usa
The files required for the download are as follows:
· Bootstrap.exe
· L289Wye.bin (or L289_14Wye.bin or L289_57Wye0.bin)
· Params.ini
8. When you click Upgrade, a dialog box displays warning that a Firmware Upgrade is about to occur. You cannot cancel or abort this process or you risk corrupting the flash memory. While the firmware downloads, a status bar indicates the progress of the download. Within the box, the following messages display:
· Reading File
· Writing to flash
9. Once the firmware upgrade is complete, the Winterm will restart.
10. After the Winterm restarts, any further configuration can be done via the Wyse Remote Administrator 3000.
Determine the firmware version of the Winterm via Remote Administrator 3000. If the firmware version is 3.3.289.14 or above, use the following procedures to download a newer version of firmware to the Winterm using the Wyse Remote Administrator 3000 management utility.
1. Access the Wyse Remote Administrator 3000 (RA3K) remote management utility.
2. In RA3K, select Utilities, then Setup.
3. In the “Discover IP Sub Net(s)” field, enter the first three octets of the IP address of the subnet upon which the Winterm to be upgraded is located.
4. In the “IP Range in Subnet(s)” field, specify the specific 4th octet of the Winterm you want to upgrade to prevent downloading firmware to the incorrect Winterm. Enter this number in both the boxes.
5. Click OK to close the RA3K Setup screen.
6. Click UtilitiesàDiscover to locate the Winterm you want to upgrade. It should display in the Terminal window of RA3K.
7. Check the firmware Version of the Winterm by highlighting the Winterm in the Terminal window.
8. Before continuing, verify that the correct version of firmware is located in the firmware download subdirectory of the FTP Server (see the Warning under step 7 in Section I for more information).
9. In RA3K, click UtilitiesàUpload/DownloadàDownload Firmware.
10. In the Download Firmware window, ensure the correct path is specified in the “Enter Firmware Path” field. The path should be specified as follows:
C:\InetPub\ftproot\Wyse\CE\Leo\NON-fp\USA
11. Highlight the Winterm to be upgraded in the Select Download Destination window, then click OK to begin the download.
12. Messages displays in RA3K indicating that Firmware files are being sent to the FTP Server, and then downloaded to the selected Winterm.
13. A message displays on the Winterm indicating that the Firmware is being upgraded. You can have the user press Yes to accept the upgrade and begin the download, or you can wait for the 15-second timeout to expire and begin downloading the firmware automatically.
14. Once the firmware upgrade is complete, the Winterm will restart.
15. After the Winterm restarts, any further configuration can be done via the Wyse Remote Administrator 3000.
As the traffic on networks continues to increase, the strain on the network infrastructure/resources also increases. In response to this increased demand, Microsoft is building a set of components into Windows 2000 for network bandwidth
management - called Quality of Service. These components allow network engineers or administrators to specify how bandwidth will be utilized on a network by defining traffic control patterns for different types of network traffic. With the increased interest in quality of service in networking in general, Windows 2000`s Quality of Services will be important as Windows 2000 is implemented.
For a book on the subject from Amazon click here.
Websters defines portal as a doorway. When referring to a portal on the web we are referring to a page or site that is an entry point for content and services offered locally or on the Web.
Vortal, a contraction for Vertical Portal, is a new word recently invented. Vortal refers to a web site that gathers like content and services and make them available to industry members. WorldOfAsp.Com could be considered to be a Vortal.
Application service providers include a new generation of companies that manage high-availability data centers that deliver application-hosting services to software vendors and end users.
The goal for the ASP industry is to make the management of information technology as transparent ... and reliable ... as the management of sophisticated public telecommunications and data communications systems. Running information systems for other entities is the ASP’s primary business. The ASP has the staff expertise and state-of-the-art equipment to maintain and sustain the most reliable and up-to-date service.
While the ASP market is relatively new, computer industry analysts have predicted the size of the ASP market to be into 6.8 billion dollars by the end of 2001.
SLA stands for Service Level Agreement. Application Service providers offer SLA`s as an incentive for customers to purchase their service. An SLA will often guarantee an enduser a certain amount of uptime. Since no provider can absolutely guarantee 100% uptime, providers offer a minimum availability level which if not met will result in the customer getting service fee refunds. Of the major ASP`s most are offering an SLA guaranteeing between 99.5%-99.9% per month of uptime. Some SLA`s not only guarantee application availability but also suggest average response times. It is often understood that while ASP`s are likely to reimburse customers if they fail to meet agreed upon levels but no providers are likely to reimburse customers for lost time, revenue and customer goodwill when business cannot be conducted when there is a failure on the ASP end. A few things to consider when looking at an ASP are.... Can the provider guarantee its quality of service? Will it put those guarantess in writing? How quickly will the ASP respond when there are problems? Does the ASP allow for an easy out of the contract? What kind of Network Monitoring Tools is the ASP using to assure quality?
Discuss your Terminal Services & Citrix issues with thousands of other SBC experts. Click here to join!