- This topic is empty.
-
Posts
-
Hello ThinkThin,
We want to update a 9V90 Wyse Client with the following image:ftp://support-emea.wyse.com/public/xpe/SP2/9V90_S551_512.exe
I guess we have a basic problem, that avoids us to use the Wyse Simple Imager (WSI) at our side. We can’t load or push a image like you describe it as pre-condition in your Tech Docs article: “Creating Images with Wyse Simple Imager”.
We use a new setup W2k3 Server with SP2 and the the WSI. We installed the WSI exact according to the WSI 1.2.0 Quick Start Guide from -> http://www.wyse.com/supportdownload/9series/WSIv1.2.0_RevA.zip
This Quick Start Guide seem to be incomplete in some point. Because the WSI installs TFTPD32, I guess the imaging process is PXE based. I a installation following the guide above no pxe bootfile is specified and bootp protocoll is not activated.
My best guess would be to use bootp and specify rapportift.0 as bootfile. Additionaly we configured the settings for DHCP and FTP according to this description:
http://www.freewysemonkeys.com/downloads/DHCP%20%20FTP%20blazer.pdfThis will start a pxe bootimage with the WISard 4.4.02 PXE Agent. This Agent searches for interface and after a while it tries to download a file with the name of its MAC-adress. This should be executable – if I interpretate the messages correctly.
A’m I on a completely wrong way or what else is needed to get the WSI running?
We also set up a wnos.ini file (c:InetPubftprootWysewnoswnos.ini) including only a AutoLoad=1 option and copy the updatefile above to c:InetPubftprootWysewnosUTC_b512 .
I guess we are stucked at this point. I googled a lot and found a lot of information but nothing as brought us a step nearer to our goal to update the client.
Some addition remarks:
* we deactivated firewall, antivirus etc on the server
* we crosschecked the installation according to the
883861-01B_WSI_Admin_Guide from the Wyse side
* we crosschecked the installation according to the
User Guide for WSIField from the Wyse side
* we don’t use WDM (Wyse Device Manager)Peter
Intersting thing. First, a V90 is not able to upgrade itself the same way a ThinOS unit is. So copying the V90 image to wnos folder won’t succeed.
A few questions:
– What language is your W2K3 server?
– Is is an isolated enviroment?
– What DHCP server are you using?ConfGen
Hell Conf Gen,
* W2k3 Server is installed in german
* The environment is isolated (just a cross-over cable between V90
and server)
* DHCP Server is from MSDHCP Options we set are:
003 Value:10.1.1.12
015 Value:10.1.1.12
043 Value:0
067 Value: rapportift.0
161 Wyse FTP Server (Value: 10.1.1.12)
162 Wyse FTP Folder (Value: /$)Peter
Hello Conf Gen,
067 Value is rapportitf.0 and PXEboot-Agent starts as mentioned above (…This will start a pxe bootimage with the WISard 4.4.02 PXE Agent…)
Peter
I have rechecked your DHCP option and there is one option missing and one is wrong.
66 should be the IP of your server (10.1.1.12 )
43 is a bit more complicated. Enter the following value in the correct order:
60
4
73
84
70
0
67
9
114
111
111
116
46
105
50
117
0
0ConfGen
Thanks Thomas,
this was the missing part. I filled in Option 66 and 43
I had to fill in Option 43 in hex, so this hexcode reads like:
3C 04 49 54 46 00 43 09
72 6F 6F 74 2E 69 32 75As ascii text this reads similar to: ‘< ITF C root.i2u '
Just to complete documentation, here is my full wnos.ini:
autoload=1
Fileserver=10.1.1.12
Rootpath=/$
Rapportserver=10.1.1.12
SignOn=NoThank you for your assistance. I guess without your support I never filled in this hexcode to option 43.
Peter
- You must be logged in to reply to this topic.