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

Power Automate: Get first item in output

By -
Image
One of the most annoying things about Power Automate for me is when I am trying to use the output of a previous action and as soon as I click that dynamic content button, it pops my new action into a For Each loop. It does this because the previous action could have more than 1 item returned and this would clearly fail unless it was in a loop. But if you have used the Row Count or Top option in the proceeding action, or you know full well that only 1 item will return, it is nice to avoid bloating the flow with an unnecessary loop. There are a couple of way to do this: First function You can craft your filter expression so that the output is wrapped in the First function. This will tell Power Automate to only look at the first item. First(variables('Array')) Calling Index You can edit your filter expression to tell it which item from the source you want. Zero being the first item e.g. variables('Array')[0] Which one to use? I use the index and the main reason is due to...
Read more

De-selectable radio buttons - Power Apps

By -
Image
Introduction When creating a Canvas Power App you can choose from a large number of controls and specifically input controls designed to get information from the user. One of these controls is the humble radio button. This is a good control which provides possible options without requiring a user action. In comparison a dropdown would require the user to click to expand all of the possible options. Example radio button input One of problems with this control is the fact you cannot de-select it. Once an option has been chosen, you can change it but you cannot undo it. The post shows a way to make de-selecting possible in a Canvas Power App. One simple way to achieve this is to have a button or icon next to the radio button and its OnSelect property to be Reset(rdoButton). This is easy, but if there are many radio button controls, it could result in lots more controls on a screen or in an app. Power Apps recommends keeping under 500 for an app and 300 maximum per page. The followi...
Read more