Wyse ThinOS 7.1 session disconnecting

By -
We utilise Wyse ThinOS terminals for users at my organisation.  They connect to a full published desktop based on XenApp 6.  The Wyse terminals have been really useful as they load very quickly and configuration is easy using INI file and DHCP flags.  This means we can ship a new unit out to site with zero configuration.  True plug and play in action!!!

We have started to purchase some newer terminals recently including the R10 and T10.  The R10 is a little older and originally came with 7.0 firmware.  The T10 is a newer terminal which is the replacement for C10 and S10 terminals.  It has a small form factor and can handle multi monitors very well indeed.

The T10 ships with firmware version 7.1.  We have found this to be very problematic in our environment.  Users would start their desktops and get disconnected at random points in the day.  We downgraded any R10s with 7.1 firmware back 7.0 and it fixed the issue.  Unfortunately you cannot downgrade the T10!!

To reproduce this problem I would watch the following video file from Gizmodo

http://gizmodo.com/5743871/the-most-beautiful-short-film-about-cryptography-youll-see-today

After about 30-60 seconds the session would disconnect.  Our terminals are configured to shutdown on session end, which means the user would have to boot the terminal again. 

If the terminal is not configured for auto shutdown the following error would appear in the system information tab.

ICA: read error 0 from ica_frame_recv

We opened a support case with Wyse and they informed us that this issue had something to do with session reliability.  To workaround the issue you can disable session reliability in the wnos.ini file

CONNECT=ICA \
BrowserIP=Server1,Server2 \
Application="AppName" \
Description="AppDesc" \
Icon=icon.JPG \
AutoConnect=Yes \
Username=$UN \
Password=$PW \
Domainname=domain \
Encryption=128 \
Resolution=DDC \
Fullscreen=yes \
HTTPBrowsing=yes \
SessionReliability=no \
Mapdisks=yes \
MapdisksUnderZ=yes \
LowBand=no \
UniSession=yes \
LocalCopy=no

This had an immediate impact.  The testing showed no disconnects, but we like session reliability.  If a network link goes down for 10 seconds we do not want all users being disconnected!

Wyse have provided me with a limited release hotfix (7.1._126.01) which resolves the issues without needing to turn off session reliability.  This will be included in WTOS 08 which is due for release in Q4 2012.

Thanks
Sam

Comments

  1. Anonymous26 July 2013 at 21:41

    My company have a similar issue, do you have ant case number or Wyse KB with this workaround?

    ReplyDelete

Post a Comment

Popular posts from this blog

Assigning Windows 10/11 Enterprise Subscription Activation Licences to Hybrid Azure AD Joined Devices

By -
Image
Introduction Starting with Windows 10, version 1703, Windows 10 Pro supports the Subscription Activation feature, enabling users to “step-up” from Windows 10 Pro to Windows 10 Enterprise automatically if they are subscribed to Windows 10 Enterprise E3 or E5. The Subscription Activation feature eliminates the need to manually deploy Windows 10 Enterprise or Education images on each target device, then later standing up on-prem key management services such as KMS or MAK based activation, entering GVLKs, and subsequently rebooting client devices. It’s important to note that the Windows 10 Enterprise subscription activation is designed to “step-up” a device from Windows 10 Pro to Windows 10 Enterprise. Therefore, your device is required to have a Windows 10 Pro license activated as a baseline. For Windows 10 Enterprise Subscription Activation to function, there a several prerequisites which need to be in place. This blog is aimed for organisations which have Active Directory on premises an
Read more

Autopilot Hybrid Azure AD Join with Customised First Login Status

By -
Image
Introduction This is my flavour of deploying a customised HAADJ progress status, building on work by Joymalya Basu Roy's detailed article - https://joymalya.com/autopilot-hybrid-azure-ad-join-reworked-with-joy/ . The differences in my version are: Not using Active Setup to run the HAADJ retry process or Splash Screen as I found this didn't work as expected and I didn't want to add a registry item to affect all future logins with a reboot from the HAADJ process. Running the processes under the context of the SYSTEM account, but displaying status to the interactive user. Avoid the HAADJ process running again after the initial success. This provides a customised first login status which prevents the user from using the devices until Hybrid Azure AD Join from the Autopilot process. It's use is primarily for when the User ESP is configured to be skipped. Files This is my version of customised HAADJ which is built on work and guidance in blogs/articles from Michael Niehaus, S
Read more

Upgrade Samsung Galaxy Ace 2 (I8160) to Android Jelly Bean

By -
Image
There has been talk of Samsung working on an Android build of Jelly Bean for the Samsung Galaxy Ace 2 (I8160) for quite some time. A couple of leaked versions of the build have been available since the end of February and during March, but these contained various bugs as you might expect. On April 2nd, an official release was available on www.sammobile.com and available for install using KIES or OTA, but only for Portuguese customers on the TMN network.  This was curious as this network didn't actually sell the phone.  It could be a way of getting the early adopters to test this version before the big operators like Telefonica and Vodafone build and release a version themselves. There are many online guides on how to manually download the firmware and apply it to your device, but if you make the direct jump from Gingerbread (2.3) to Jelly Bean (4.1.2) you will likely have RAM issues. The gingerbread versions only allocated around 500MB for RAM whereas Jelly Bean needs more
Read more