Ensure that you have set up a Windows PC or Server with Microsoft Internet Information Services (IIS) and HTTPS services installed. If you do not have the HTTPS server installed, then refer to the article about how to setup an HTTPS server at
support.microsoft.com.
Ensure that the web server can identify the file types used by ThinOS. Create two MIME types under IIS. The MIME's option needs to be configured on a per site basis. On a default IIS, install:
Launch the IIS admin console.
Browse to the default website, right-click and select
Properties.
Click the
HTTP Headers tab, and in the
MIME Map section, select
File types > New Type.
Add the two MIME types. Use
.INI and
. for the associated extension fields.
Apply the settings and close the IIS admin console.
Installing IIS creates the default directory
C:\inetpub\WWWroot, which is known as the WWW root. In the
WWWroot directory, create a folder
WYSE and a sub folder
wnos. The directory structure must read as
C:\inetpub\wwwroot\WYSE\wnos.
To upgrade the ThinOS firmware using HTTPS server:
Download the latest ThinOS firmware and latest ThinOS packages that corresponds to your thin client model. If the firmware and packages are in the form of a compressed self-extracting (.EXE) or zipped file (.ZIP), then extract the files. When you download the JVDI.zip package, the
README WITH EULA.txt and
JVDI.i386.pkg files are unzipped. Ensure that you open the readme file and read the EULA agreement.
Place the extracted firmware files in the
C:\inetpub\wwwroot\WYSE\wnos folder, and the packages to
C:\inetpub\wwwroot\WYSE\wnos\pkg on your HTTPS server.
Create a wnos.ini text file (using a text editor) in the
C:\inetpub\wwwroot\WYSE\wnos folder with the following INI parameters:
Autoload=2 loadpkg=1 Addpkg=horizon,JVDI
NOTE: JVDI package is introduced from ThinOS version 8.6 to support Cisco Jabber. However, if you intend to use only horizon package, then do not load the JVDI package to avoid unknown user trap issue.
The option
Autoload=2, ensures that the thin client uses the firmware installed on the server to upgrade, only if the firmware on the thin client is older than the version on the server. The option
LoadPkg specifies how to update the external packages. If
LoadPkg is not in the statement, it will inherit the value of
AutoLoad.
Base package and the PCoIP package are integrated into the ThinOS firmware image. Installing the latest ThinOS firmware image automatically installs the latest version of these packages on the ThinOS client. If you set
AutoLoad=1 LoadPkg=0, the firmware is checked, but the packages are not checked. The packages check is performed after firmware check. From ThinOS 8.3, the external packages update mechanism is changed. Some packages are default, and loaded according to value of
LoadPkg. For example RTME. Some packages need additional parameter
AddPkg to add. For example, Horizon and JVDI. The option
AddPkg is for adding packages. It depends on the value of
LoadPkg. For more information about the INI parameter usage, see
Dell Wyse ThinOS INI Reference Guide.
Save the wnos.ini file.
On the ThinOS client desktop, navigate to
System Setup > Central Configuration > General.
In the
General tab, enter the IP address of the file server or directory. For example:
https://IPaddress/wyse.
NOTE: You can also use DHCP option tags 161 and 162 to configure the ThinOS client, file server and path information. You must create these options on your DHCP server, configure them with the correct server information, and enable the DHCP server scope in your environment.
Click
OK.
Restart the thin client and wait until the auto-installation of packages is complete.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\