Wyse ThinsOS 7.1 resolutions

By -
Hi there!

My company uses a large set of Wyse ThinOS terminals all the way from the old 1200LE to the new T10.

The T10 is a cracking piece of kit, dual monitor in a tiny form factor which can also handle Citrix HDX and boot in seconds....it is pretty neat.

For this reason we have been keen to replace some of the old 1200LEs and S10 devices with the T10.  Intially this was held up due to the session reliability issue I blogged about a while ago

http://www.teamas.co.uk/2012/06/wyse-thinos-71-session-disconnecting.html

This was fixed with hotfix 130 (7.1_130).

The latest problem we had was with custom resolutions.  We use a WNOS.ini file to configure the terminals with a fairly basic configuration.  This will tell the terminals to use the DDC to determine the best resolution of which the monitor and device can handle.

We then use a username.ini file when the user logs in, this will start the appropriate Citrix session for them.  This will also launch at the best resolution for them e.g. A user with poor sight could start a terminal which is using 1280x1024 resolution, when they logon the session size will then become 1024x768.

This works really well as the support team does not need to configure specific terminals and best of all the users settings follow them!

Now 7.1 of ThinOS firmware screwed this up with the introduction of the VDI toolbar zero launchpad.  When users tried to logon to these terminals the resolution would never follow the details in the username.ini file.

To troubleshoot I tried to make a new connection and you can see there is no option to specify a different resolution.


 You can see that only "Default" is specified

Now, if you change the interface to be in classic desktop by going to System Preferences > Remote Connections > Visual Experience.  This can be achieved in the ini file by entering command

sysmode=classic



When you press OK you will be prompted to restart the terminal.  At the point the OS will look similar to pre 7.1 ThinOS with the connect manager window appearing on the desktop.

Try to add a new connection and you will see a list of resolutions can now be specified!!





I suspect that VDI mode has been streamlined and changing resolution per connection is not by design.  It would be nice if Wyse had documented this "feature" or responded within the 2 months to the support call we had opened with them!!!

Thanks
Sam

Comments

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