squirrel

Forum Replies Created

Viewing 14 posts - 1 through 14 (of 14 total)
  • Author
    Posts
  • in reply to: Reboot Loop When Upgrading to 7.1_207 #23716
    squirrel
    Member
    • Total Post: 18
    • Regular Joe
    • ★★

    @ConfGen wrote:

    Correct RapportDisable is depreciated. But the new parameter is WDMService=no

    But nevertheless, the device should not reboot perpetually.

    CG

    Contacted Wyse support and for some reason the behavior changed and you can no longer use the “Rootpath” parameter and DHCP option 162 at the same time in this firmware version. If you comment out Rootpath it works fine. This is unfortunate because roothpath is the easiest way to test new firmware, so now I have to use the parameter to update the firmware and then comment it out to stop the reboot loop. I’m waiting for the official response as to why this changed.

    in reply to: Reboot Wyse V10L remotely #23400
    squirrel
    Member
    • Total Post: 18
    • Regular Joe
    • ★★

    @ab17182 wrote:

    Oh! Also, how are you running the cmd? If you are copying this into a batch file, remember to double up on the % symbols…

    I’m just running it from the command prompt on a single device:

    SnmpSet.exe -v:1 -c:SNMPSTRING -r:IPADDRESS -o:.1.3.6.1.4.1.714.1.2.6.1.1.0 -val:0 -tp:int

    I also tried -v:2 since the link you sent said Wyse is v2 compliant. There is no firewall between the device and me so I don’t know how the port would be blocked unless it is on the device. I’ve tested on a V10L and a C10LE running 7.0.0_133. I noticed your devices are a different model, so maybe something is different between these models/firmware.

    in reply to: Reboot Wyse V10L remotely #23337
    squirrel
    Member
    • Total Post: 18
    • Regular Joe
    • ★★

    @squirrel wrote:

    @ab17182 wrote:

    Just as a head’s up, you can also use snmpset.exe as it can also be used to reboot a list of WYSE thin clients or a single one as well. Download snmpset here [http://www.snmpsoft.com/freetools/snmpset.html] and install it. Then run the below cmd against a list of thin client IP addresses. PLEASE err on the side of caution when running this as it could be disruptive to end users if the incorrect IPs are in the list:

    for /f %i in (c:tempthin_client_IP_addresses.txt) do @c:toolssnmpset -v:1 -c:SNMPWYSE -r:%i -o:.1.3.6.1.4.1.714.1.2.6.1.1.0 -val:0 -tp:int

    The above runs snmpset against a text file which contains a list of IPs. The WNOS.INI has SNMP enabled along with setting the community string to SNMPWYSE [i.e. Community=SNMPWYSE]. The OID is .1.3.6.1.4.1.714.1.2.6.1.1.0.

    Hope this helps. 🙂

    This would be excellent if it works, I’ll give it a shot. Thanks for the information. Where did you find the OID? I’m curious if there is a different OID to trigger a factory reset remotely using this method.

    I’m getting “%Failed to set value to SNMP variable. Timeout.” when testing this on a single client. I’ve set the SNMP community and it shows up correctly in the event log. I also tried explicity setting Service=SNMPD disable=no, but I assume it’s enabled by default. Any suggestions?

    in reply to: Reboot Wyse V10L remotely #23336
    squirrel
    Member
    • Total Post: 18
    • Regular Joe
    • ★★

    @ab17182 wrote:

    Just as a head’s up, you can also use snmpset.exe as it can also be used to reboot a list of WYSE thin clients or a single one as well. Download snmpset here [http://www.snmpsoft.com/freetools/snmpset.html] and install it. Then run the below cmd against a list of thin client IP addresses. PLEASE err on the side of caution when running this as it could be disruptive to end users if the incorrect IPs are in the list:

    for /f %i in (c:tempthin_client_IP_addresses.txt) do @c:toolssnmpset -v:1 -c:SNMPWYSE -r:%i -o:.1.3.6.1.4.1.714.1.2.6.1.1.0 -val:0 -tp:int

    The above runs snmpset against a text file which contains a list of IPs. The WNOS.INI has SNMP enabled along with setting the community string to SNMPWYSE [i.e. Community=SNMPWYSE]. The OID is .1.3.6.1.4.1.714.1.2.6.1.1.0.

    Hope this helps. 🙂

    This would be excellent if it works, I’ll give it a shot. Thanks for the information. Where did you find the OID? I’m curious if there is a different OID to trigger a factory reset remotely using this method.

    in reply to: Logon Screen Customization with .INI #23234
    squirrel
    Member
    • Total Post: 18
    • Regular Joe
    • ★★

    I looked through all of the release notes and .ini guides. “toolbardisablehotkey=yes” is mentioned in 7.0.0_30, but I was unable to find mention of it any subsequent release. Usually they mention if it was depreciated, so I’ll probably open a case.

    in reply to: V10L without a OS #23228
    squirrel
    Member
    • Total Post: 18
    • Regular Joe
    • ★★

    @longcat wrote:

    i wrote to the wyse support and i dont get an answer…
    how can i get login to the self-service-center? i dosent have a company so i cant register…
    is there a another way? can i install thinstation?

    Without an active support contract, you won’t be able to download any software from the self service center. Your options are to purchase 1 year of support (http://www.cdw.com/shop/products/Wyse-Thin-Client-Software-Maintenance-technical-support-1-year/2116278.aspx for example) or obtain a working V10L and follow the instructions at the end of this thread for copying over the WTOS: http://www.freewysemonkeys.com/modules.php?name=Forums&file=viewtopic&t=7751

    in reply to: Logon Screen Customization with .INI #23206
    squirrel
    Member
    • Total Post: 18
    • Regular Joe
    • ★★

    @ConfGen wrote:

    Which version have tested wirh? What is no longer working?

    CG

    I mentioned the wrong version. In version 7.0.0_30 it looks and behaves like in the image below. In version 7.1_122 you see the “Sys info/Admin mode/Shutdown/Login” buttons and cannot click on the background for the options menu.

    This is how we want it to look in the newer firmware version if possible:

    in reply to: Reboot Wyse V10L remotely #23203
    squirrel
    Member
    • Total Post: 18
    • Regular Joe
    • ★★

    @ConfGen wrote:

    For a reboot just send
    &V52&CI=59|RB=1 to the client. That’s all.

    CG

    In my testing, this command will shut down the terminal, not reboot it. Does it act differently with different firmware versions perhaps?

    in reply to: Conditional Factory Reset, Switching from VDI to ICA #23154
    squirrel
    Member
    • Total Post: 18
    • Regular Joe
    • ★★

    @ConfGen wrote:

    No, there is no conditional factory reset.
    Have you tried adding VDIBroker=”” to your mac.ini?

    CG

    Setting VDIBroker=”” worked wonderfully, thank you so much. It’s actually much better than a factory reset because it maintains display settings!

    squirrel
    Member
    • Total Post: 18
    • Regular Joe
    • ★★

    I just spoke with Wyse and they are saying the Z90D7 is the only one that is compatable, once it’s outfitted with an SSD: http://www.wyse.com/products/cloud-clients/thin-clients/Z90D7

    Still curious to hear if anybody has any other recommendation for this.

    in reply to: Flashing V10L that does not have WTOS #22701
    squirrel
    Member
    • Total Post: 18
    • Regular Joe
    • ★★

    Just wanted to follow up and say that I was able to clone the OS from a working V10L using the following method:

    -Boot from gparted live CD, enter command shell (not gui)
    – mkdir /mnt/tmp
    – mount /dev/sda1 /mnt/tmp (mount usb for storing image)
    – dd if=/dev/hda of=/mnt/tmp/wyse.img

    Then just complete the same steps on another v10l without the OS, reversing the dd command. Works great!

    in reply to: Flashing V10L that does not have WTOS #22671
    squirrel
    Member
    • Total Post: 18
    • Regular Joe
    • ★★

    Wyse support gave me the same story: must send it in to the factory for “repair”. I asked about a conversion kit and he did not know if any exists.

    I’m following up with our regional product specialist to see if he can make an exception and provide the reference image or has another solution, but in the meantime, I’ll try imaging the device with linux and let you know if it works … once I get my hands on a working V10L.

    in reply to: Flashing V10L that does not have WTOS #22666
    squirrel
    Member
    • Total Post: 18
    • Regular Joe
    • ★★

    If you have a working V10L with WTOS installed, can you use a linux live CD to make an image of the 128 MB flash drive using DD and then restore to the other device? I’m assuming this won’t work, guessing they have some sort of protection in place to prevent it from working.

    in reply to: Flashing V10L that does not have WTOS #22650
    squirrel
    Member
    • Total Post: 18
    • Regular Joe
    • ★★

    I have the same problem, did WYSE provide the Merlin image? I opened a support ticket, but your comments made me un-optimistic that they would help.

Viewing 14 posts - 1 through 14 (of 14 total)