Dell Wyse 5470 All-In-One Wyse ThinOS Version 8.6 and ThinOS Lite 2.6 Operatin - Page 171

Firmware upgrade using HTTPS

Page 171 highlights

3. Create a wnos.ini text file (using a text editor) in the C:\inetpub\ftproot\WYSE\wnos folder with the following INI parameters: Autoload=2 loadpkg=1 Addpkg=TCX,FR,horizon 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, FR, Horizon, and TCX. 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. 4. Save the wnos.ini file. 5. On the ThinOS client desktop, navigate to System Setup > Central Configuration > General. 6. In the General tab, enter the IP address of the FTP server or directory. For example: 150.00.0.260/wyse. The Username field must have the value Anonymous and the Password field is already pre-configured. NOTE: • If there is no default password or if the password is changed, then you must set your password. For example, [email protected]. You can also reset the thin client to factory default settings. When you reset the thin client to factory default settings, the anonymous user is configured with the default password. However, you need to reconfigure the thin client. • 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. 7. Click OK. 8. Restart the thin client and wait until the auto-installation of packages is complete. To verify that the thin client is upgraded, on the ThinOS desktop, navigate to System Information > General, and check the System Version. Firmware upgrade using HTTPS 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: 1. Launch the IIS admin console. 2. Browse to the default website, right-click and select Properties. 3. Click the HTTP Headers tab, and in the MIME Map section, select File types > New Type. 4. Add the two MIME types. Use .INI and . for the associated extension fields. 5. 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: 1. Ensure that you have downloaded 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. 2. 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. 3. 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=TCX,FR,horizon Upgrading firmware 171

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174

3.
Create a wnos.ini text file (using a text editor) in the
C:\inetpub\ftproot\WYSE\wnos
folder with the following INI parameters:
Autoload=2 loadpkg=1 Addpkg=TCX,FR,horizon
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, FR, Horizon, and TCX. 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.
4.
Save the wnos.ini file.
5.
On the ThinOS client desktop, navigate to
System Setup
>
Central Configuration
>
General
.
6.
In the
General
tab, enter the IP address of the FTP server or directory. For example:
150.00.0.260/wyse
. The
Username
field
must have the value
Anonymous
and the
Password
field is already pre-configured.
NOTE:
If there is no default password or if the password is changed, then you must set your password. For example,
You can also reset the thin client to factory default settings. When you reset the thin client to factory default
settings, the anonymous user is configured with the default password. However, you need to reconfigure the thin
client.
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.
7.
Click
OK
.
8.
Restart the thin client and wait until the auto-installation of packages is complete.
To verify that the thin client is upgraded, on the ThinOS desktop, navigate to
System Information
>
General
, and check the System
Version.
Firmware upgrade using HTTPS
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:
1.
Launch the IIS admin console.
2.
Browse to the default website, right-click and select
Properties
.
3.
Click the
HTTP Headers
tab, and in the
MIME Map
section, select
File types
>
New Type
.
4.
Add the two MIME types. Use
.INI
and
.
for the associated extension fields.
5.
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:
1.
Ensure that you have downloaded 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.
2.
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.
3.
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=TCX,FR,horizon
Upgrading firmware
171