Forum Replies Created
-
AuthorPosts
-
Thanks a lot Thomas.
To me it seems like 3600 seconds is the default reconnect timeout then, as this is what we experiences in production incidents we’ve had.I will speak to Wyse Support about it and request it to be changed so “Reconnect=yes” command without any timeout specified, reconnects indefinitely.
Regards,
Interstingly, in Wyse 3040 base package is loaded at first boot and stays in the device even if “autoload=1 LoadPkg=0” entry is in use.
Hi guys,
I tried both “Autopower=yes” and “Device=DellCmos Audio=no ACRecovery=PowerOn” entries and Autopower functionality is not working in Wyse 3040.
Firmware 8.4_B112 / BIOS 1.2.2
Can anyone confirm this?
I am surprised about the prospective impact of “autoload=1 LoadPkg=0” entry.
I use it for my production clients with no problems so far, however, they don’t use any multimedia features. I definitely would like to avoid 600 clients in a warehouse to download packages from FTP server at the same time after power failure…
Does it mean that when WDM FTP server is not available (and unable to download the packages), in some scenarios thin clients may be unable to connect to resources even if “EnableCacheIni=yes” is used…?
October 31, 2017 at 3:53 pm in reply to: V10LE & 8.0_512 – freezing and crashing (W2k8R2 & XenApp6.5 & .NET apps) #45537Hi,
The same issue with crashed/frozen thin clients (T10s this time) is appearing now also in a completely different site in my environment. It started to happen couple of weeks ago with random, single clients but recently it happened to around 30 clients at the same time.
Very strange and worrying issue.
Regards,October 2, 2017 at 10:22 am in reply to: V10LE & 8.0_512 – freezing and crashing (W2k8R2 & XenApp6.5 & .NET apps) #45301UPDATE:
Looks like T10s with 8.3_014 firmware are also affected.Seems like to serious vulnerability in Wyse thin clients then…
Our support teams are investigating but so far nobody has a clue what was causing this.
Exactly the same issue here.
Just updated BIOS to the version available online with no change.
My firmware is 8.3_210.
Will report this to Wyse Support.
After testing 3040 it seems to provide far better experience than 3010 & 3020.
With 3040 while working in XenApp 7.x you feel almost as working locally on a PC – it is very responsive when scrolling graphics-rich websites which were lagging badly on previous thin clients.
If my tests were valid this is a revolution in TC responsiveness and experience. It is even better than if running XenApp session from my i7 PC…
July 7, 2017 at 1:32 pm in reply to: Error when i want launch Xenapp apps with ThinOS 8.3.014 #44746Thanks Thomas.
I cannot force this TC to upgrade or downgrade unfortunately.
PS. By the way, thanks again for all your help on this site and for the Config Generator. You support here is priceless. Unfortunately, Wyse&Dell is same like Citrix where users have to support each other as the companies fail to deliver a good support for their products.
July 6, 2017 at 11:09 am in reply to: Error when i want launch Xenapp apps with ThinOS 8.3.014 #44735Hi guys,
I just found a C10LE terminal in my environment with the same issue as above: Exec “ica”: No such file or directory. Firmware version is 8.3_014 and I cannot downgrade it to any earlier version – it is not picking up the firmware file(s).
I was trying to follow the above advice and delete “base.i386.pkg” package, however, System Tool->Packages tab is missing on my device.
How can I get into the Packages and delete “base.i386.pkg”?:)
Thanks!
Legend!
Thank you Thomas:)
Regards,
Thanks Thomas,
I am logging in with “domain\username”.
If it works for you it seems to be a bug in my case.
Regards,
December 30, 2016 at 4:33 pm in reply to: C30LE – possible to install 3rd party apps or browsers? #43638Thank you Thomas
From 8.3_014 firmware you may also use the TrapReboot=yes entry will will automatically reboot a TC on any Trap errors.
Hi mate,
This issue has been fixed in 8.3_014.
What was strange to me about this issue that once you upgraded to 8.3_011, downgrading the firmware was not fixing the AutoPower bug.
Regards, -
AuthorPosts