I currently have an RDS 2012 Farm deployed in Session-Host Mode with a server for the RD Connection Broker server, and a separate server with the RD Web + RD Gateway roles, and separate servers for the RD Session Hosts. Our RDS Farm deployment is set to use an RD Gateway with “Bypass RD Gateway for local addresses”. We need this, as we have some users accessing our RDS Farm externally through RD Web access using RD Gateway outside of our LAN.

All of our Windows 7-Windows 10 machines and their RDP clients respect the “Bypass RD Gateway for local addresses” setting, but our Wyse C10LE and Dell Wyse 3010 (T10) devices do not bypass the RD Gateway when inside the local LAN. They are set up in VDI mode, and use a Connection Broker entry instead of direct RDP connections. They can resolve the DNS of the RD Session Host and reach port 3389 directly. These are the only two criteria that “Bypass RD Gateway for local addresses” checks for. The thin clients are running ThinOS firmware version “8.3_011”.

I have searched for hours for any settings I may have missed in the WNOS.ini file that would cause the Wyse thin clients ignore the “Bypass RD Gateway for local addresses” setting passed from the RD Connection Broker. I cannot find anyone else who has solved this on the Microsoft forums, or elsewhere.

Does anyone have any insight on this?

Hi

Have been testing HDX RTOP with Wyse ThinOS 8.3 running HDX RTME 2.0.100.6

Running XenDesktop 7.8 on Windows 2008R2 with Skype 2013 client

Tried with both RTOP 2.1 and 2.0.100

When RTOP is installed and I test from Skype the Mic is so low it is impossible to hear even if the mic is on full volume in Skype.

Locally on the thin client it sounds fine.

Been testing with

Sennheiser SC70 = bad

Sennheiser SCx8 = bad

Jabra  Speak 510 = bad

Sennheiser SC830 = Good

Using the RTOP the call control panel are working on all headsets

When I uninstall RTOP and do a reconnect then Mic is loud and clear again.

What can i do turn up the microphone volume?

Thanks

Good morning,

I am trying to configure https instead of ftp for the Wyse thin clients to download their wnos.ini files.  It seems to connect but I get the error Fail to validate server

Any ideas?

I am attempting to upgrade a C10LE from ThinOS 7.1 to 8.3 for testing purposes.  I place firmware in my wnos folder along with modified wnos.ini and reboot C10.  C10LE reboots and begins to copy file, displays "Invalid File Format" and boots to desktop.  Anyone seen this issue?

Thank you,

Sean

Hi 

I have Wyse 7020 thin client with dual display port (DVI-I and DisplayPort) . I want to know if I can extend display to 3 or more signals using DVI splitter or DisplayPort hub. 

Thanks

Does ThinOS support Azure MFA’s SMS one-time passcode + PIN? My wnos.ini is configured for LDAP configuration. When I sign in, I get a prompt to set a new PIN because it’s expired (it’s not). This prompt does not accept any form of the OTP+PIN.

We are having issues with green screens and trap page faults with our R00 units.  This happened after we updated our XenApp 6.5 servers to HFR7.  Users would be working in Excel/Powerpoint and copying and pasting data back and forth and their terminals would crash with the page faults and the have to hard reset the R00 unit.  We were on an old firmware 2.0_026 and upgraded to 2.0_512 and this still happened.  Trying to upgrade to any version 2.3 causes the terminal to freeze on install and then we have to hard shut down.  Booting the terminal back up does eventually finish the installation but this doesn't seem to be a very good solution as this requires user intervention on each terminal.  Are there known issues upgrading from 2.0 to 2.3?  Is there a recommended upgrade path?  And will this upgrade fix our trap issue? Thanks

Dear all
I need help regarding password encryption at WNOS 8.3_014
I downloaded Dell Wyse Password Encoder but the passwords created by this tool seem not to be compatible with WNOS 8.3.014.

Some Parts on my ini:
`
AdminMode=yes Admin-Username=XXXXXX Admin-Password=XXXXXX  ;(DES, i guess)
SignOn=NTLM
DefaultUser=MyUser
Password=365fd0ce928697723a57776e9d93f4e8 encrypt=yes
DomainList="corp.mycompany.com"
Seamless=yes HideTaskBar=1 FullscreenReserved=yes
PnliteServer="mycitrix.com/.../my01store1" ReconnectAtLogon=2 ReconnectFromButton=2 CAGAuthMethod=LDAP
`
How can I create a valid (AES) password string at WNOS ???

We have a Wyse R10L that during POST has the error message

"System Configuration Data updated

ERROR

System Configuration Data Read Error"

I'm trying to use the USB firmware tool and have managed to pull an image off a working R10L using the del key at boot and Fireport password. Plus I've also downloaded a firmware image to the USB stick. However I cannot seem to make it boot from the USB on the damaged R10L client.

Any suggestions on what to try?

Hello,

I am having a random problem that appears to be affecting users on Windows Terminal Server 2012 R2 that are on Wyse 5010 Terminals. All my terminal have dual monitors.

These blocks appear on screen that let you see the terminal server background through the application. If you hit the start key on your keyboard the start menu appears just fine but when you go back to the desktop the squares remain.

If I shadow the session, I don’t see the problem. If I use VNC to get into the terminal I see the issue.

Here is a copy of my config: The users use RDP Session 3.

;*************************************************************
;*                                                           *
;*         This wnos.ini file was generated with the         *
;*              Configuration Generator 7.7.01               *
;*              Copyright by Thomas Moellerbernd             *
;*                                                           *
;*                 http://www.technicalhelp.de               *
;*                                                           *
;*************************************************************

;*************************************************************
;*                          General 1                        *
;*************************************************************

autoload=2
AdminMode=yes Username=admin Password=password

;*************************************************************
;*                          General 2                        *
;*************************************************************

reboot=yes Time=23:00
EnableGKey=yes

;*************************************************************
;*                          General 3                        *
;*************************************************************

Autopower=yes
AutoSignoff=yes Reboot=yes
ShutDown=standby
SysMode=VDI ToolbarStay=2

;*************************************************************
;*                          Privilege                        *
;*************************************************************

Privilege=None

;*************************************************************
;*                         Peripherals                        *
;*************************************************************

Language=Us ManualOverride=yes
Device=audio EnableSpeaker=no

;*************************************************************
;*                           Display                         *
;*************************************************************

DeskColor="255 255 255"
DesktopColorDepth=16
Desktop=LOGOCOLOR.jpg Layout=Center
Dualhead=yes MonitorAutoDetect=yes
Screensaver=15 LockTerminal=no Type=0
ShutDownInfo=yes

;*************************************************************
;*                             Time                          *
;*************************************************************

Timeserver=dc.DOMAIN.com Timeformat="12-hour format" Dateformat=mm/dd/yyyy
TimeZone='GMT - 05:00' ManualOverride=yes Daylight=yes Start=030207 End=110107 

;*************************************************************
;*                           Network                         *
;*************************************************************

Device=Ethernet Speed="Auto" StaticIPWaitFileServer=255
Community=itnssnmp
DNSIPVersion=ipv4
SignOn=No
MaxVNCD=1
VncPassword="password"
VncPrompt=No Accept=10 

;*************************************************************
;*                       General Session                     *
;*************************************************************

SessionConfig=ALL DisableSound=Yes

;*************************************************************
;*                             RDP                           *
;*************************************************************

SessionConfig=RDP DefaultColor=1 Dragging=no Animation=no Theme=no EnableGFX=yes EnableTSMM=no USBRedirection=RDP

;-------------------------------------------------------------
;-                        RDP Session 1                      -
;-         Each line but the last must end with a  '\'       -
;-------------------------------------------------------------

CONNECT=RDP \
       Host=TSFARM \
       Description="REMOTE" \
       AutoConnect=No \
       Reconnect=No \
       Colors=16m \
       Fullscreen=yes \
       Domainname=DOMAIN \
       KeepAlive=5 \
       LocalCopy=no

;-------------------------------------------------------------
;-                        RDP Session 2                      -
;-------------------------------------------------------------

CONNECT=RDP \
       Host=TSFARM \
       Description="REMOTE (1440x900)" \
       AutoConnect=No \
       Reconnect=No \
       Colors=16m \
       Fullscreen=yes \
       Resolution=1440x900 \
       Domainname=DOMAIN \
       KeepAlive=5 \
       LocalCopy=no

;-------------------------------------------------------------
;-                        RDP Session 3                      -
;-------------------------------------------------------------

CONNECT=RDP \
       Host=remote.DOMAIN.com \
       Description="New Terminal Server Farm" \
       AutoConnect=No \
       Reconnect=No \
       Colors=high \
       Fullscreen=yes \
       Rdp_No_Dragging=yes \
       Rdp_No_Animation=yes \
       Rdp_No_Theme=yes \
       Rdp_No_Fontsmoothing=yes \
       Domainname=DOMAIN \
       Mapdisks=yes \
       KeepAlive=5 \
       WyseVDA=yes \
       AudioQualityMode=2 \
       LocalCopy=no

;*************************************************************
;*                      General 2 Special                    *
;*************************************************************

Include=$mac.ini

The terminals had 8.3_12 and I have updated them to 8.3_14. I am not quite sure what to do and I have an open ticket with Dell and the technician has no idea what the problem is either.

Any advice would be appreciated.

My Security Team wants us to setup our ThinOS devices to authenticate to wireless Per Device as separate users.  I figured I'd just use the $Mac.ini and it would work...  (These are Wireless Medical Carts)

There seem to be a couple of issues.

1) One issue is how exactly to setup the two .ini files.  If I have no wireless in the WNOS.ini file, it fails to connect upon reboot.  If I have a GenericUser in WNOS.ini, and the SpecificUser setup in the MAC.ini file, it sees a wireless change and gets caught in a reboot loop.    If I just have the User/Password variables (see below) it seems to ignore it since it has already authenticated to wireless to get the files!!

2) Another issue is that the 'MirrorFileServer=yes' command only seems to cache the WNOS.ini file (and wireless setting) So upon reboot, it fails... Can I cache the MAC.ini file?

I'd appreciate it if you could help me find a solution.  Is everyone here just using a single login for wireless on all ThinOS wireless devices?

WNOS.ini

...

MirrorFileServer=yes

;*************************************************************
;*                     Wireless / 802.1x                     *
;*************************************************************
;
IEEE8021X=yes network=wireless access=WPA2-ENT eap=yes eaptype=EAP-PEAP peapeap=EAP-MSCHAPV2 peapmschapun=GenericUser wdEnc=MDELKEDGNDNOLPCLPIHBLI peapmschapdm=My.Domain.org
Device=Wireless Mode=Infrastructure SSID="Mywireless" DisableWLAN=EnetUp

Include=$MAC.ini

MAC.ini

peapmschapun=b121896 peapmschappwdEnc=PBCDOPCGLCCHLLCMKI

; IEEE8021X=yes network=wireless access=WPA2-ENT eap=yes eaptype=EAP-PEAP peapeap=EAP-MSCHAPV2 peapmschapun=SpecificUser peapmschappwdEnc=PCDOPCGLHLLCMKI

Exit=all

Went to Dell's Digital Locker  to download version 8.2 to update from version 8.1 but can not find a line for ThinOS 8.2 _C10LE.  The only version update I can find is 8.3 for the C10LE.  Since you can not update from 8.1 to 8.3 where in the Digital Locker can version 8.2 be found?  Is it named something other than 8.2....C10LE_Eng?

The problem we are facing with our C10LE is quite complex, let me explain:

Our Wyse units gets into a boot loop every time its first booted. The temporary solution we have found is to upgrade the firmware by FTP from its original version that it comes with (unkown) to 7.1_033. However, the same boot loop appears after installing the latest update and activating the CCM.

After installing the 7.1 update, we upgrade the firmware in the following sequence:

7.1_033 > 8.0_037 > 8.0_411 > 8.1_011 > 8.1_027 > 8.3_011 > 8.3_014

After installing the last update (8.3_014) and activating our CCM, the unit reboots, and after we perform a check on the system and shut it down with resetting to factory settings and booting it again, the unit goes into a boot loop again just like in the beginning before installing the updates.

What could be the reason for which our unit goes into a boot loop?

I am using a thin client T10 and I am trying to run a dual monitor setup with 1 standard monitor and 1 ELO touch screen. The monitors are stacked verticle with the touch screen on the bottom and starndard monitor on top. The issue I am having is being able to calibrate the touch screen monitor located on the bottom, every time I go to calibrate the tocuh screen it always picks monitor 1 which is the standard monitor, even when I move the main display to monitor 2 which is the ELO, when I go to calibrate the touch screen it alwasy defaults to display 1. Is there anyway to force the thin client to pick monitor 2 when performing a screen calibration.

When I try to upgrade the firmware on an existing T10 Thin Client, the system talks to our FTP server, obtains an IP address via DHCP and then sees the DOVE_boot file but indicates 'Invalid File Format'. I've looked at countless discussion forums and other online resources which give no indication as to whether 8.0_105 can be directly upgraded to 8.3_014. Can this be done? What am I missing?

After upgrading our Wyse D10D thin clients to the latest available firmware version 8.3_012, we found an issue with accessing empty flash drives.  We are using Xenapp 7.6 and Kingston DataTraveler G4 16 GB drives.  If there are no files or folders on the drive, we will receive the following message when clicking on the drive:

\\Client\D$ is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.  The filename, directory name, or volume label syntax is incorrect.

If we copy an type of file or folder to the flash drive using a laptop, the drive will then be accessible on the thin client.  This issue is also occurring with firmware version 8.2_015.   However, if we roll back to firmware version 8.0_510 the issue is resolved and the empty drive can be accessed.

I hope this is a known issue with the newer firmware that is already being looked into. If not, I hope it gets attention.  Has anyone else seen this issue?

OK, 

First up I am very seriously *** off!

How bad is it when the maker no longer has a simple guide of; 

• You need to download this for this model 
• You need X USB version
• and you should get  X when loading the firmware

NOT A SINGLE ONE!

Now that vents over and I am still angry to find shitful dell taking over wyse - I need to following since I have wasted 2 days while in the middle of a Citrix zone build; 

• ZX0 client on version 8 THINOS will not work with storefront, unable to resolve names when launching an app which is *** since DNS is perfect and its using storefront via DNS names anyway. Turns out to be a BUG!
• Steps to upgrade thinOS \ Zx0 terminal from ver 8 to 8.3 
• need to know which firmware files - download addy lists many and doesn't *** say which is for the Zx0 - tried everyone so far with nothing working. https://appservices.wyse.com/pages/serviceandsupport/support/dlOraFW.asp?which=189&model=5020/7020(ThinLinux) 
• which version of the USB image tool to use? FFS! Make a new one - get rid of old but one - but new one doesn't work with old version and vice versa. 

So far I have been through downloading the following; 

1.image-upgrade-1.0.1-Wyse.zip
(589 MB)1.0.1image-upgrade-1.0.1-Wyse on 5020/7020
 28-Jul-20162.all-addons-1.0.1-Wyse.zip
(251 MB)1.0.1Option Add-ons File
 28-Jul-20163.1.0.1_Z50Q_D50Q_Z50Qq_merlin.exe
(692 MB)1.0.1ThinLinux 1.0.1 Merlin Image on 5020/7020
 28-Jul-20164.1.0.1.zip
(588 MB)1.0.11.0.1 RSP zip file
 28-Jul-2016

None have worked at all! Got an older version of USB imaging tool - none worked

20 years dealing with Citrix and I have never had such a stuff around with a wyse terminal. It will be the last time I recommend them!

Where are the right files for this Zx0 model ?

Which is the right tool?

Thanks in advance

Looking for the right image files to upgrade Zx0 to 8.3 since ver8 has a bug and wont work with storefront. 

Every image I have tried so far does not load - thinos only. 

I added the snmp statement in wnos.ini file and works fine. The question I have is will snmpv3 work and how it's setup

Hello community,

i want to use Dell Wyse Model N06D (3030LT) with ThinOS 8.3.011 to connect to a connection broker of Microsoft RDS with a collection of apps.

I do not have any FTP-Server or Virtual Desktops. How can i configure the Wyse client locally to connect successfully? Is it possible to configure the Wyse Client to display a login window after boot where you have to log in and then you can see your applications published through the RDS collection? Or are there some requirements like virtual desktops?

I made the config for Microsoft as Broker Type and as Host the Connection Broker Server. I imported the certificates for the servers but i still get the error "RD Broker Sign On failed". The event log of the wyse client did not have any entries but the security event log of the connection broker logged my user successful and in the same second logged him off.

Also my global.ini field is empty and cannot be edit. Is it possible to give the client an ini-file without FTP Server? In this forum i saw often specific lines for the ini, for example the option "VDIBroker", but only with FTP.