Quantcast
Channel: Wyse ThinOS - Recent Threads
Viewing all 74 articles
Browse latest View live
↧

Wyse T10 and Certificates

July 24, 2017, 6:38 am
$
0
0

Hi, hope someone can help me out!!

We have some Wyse t10 (Firmware 8.1.27)  and are trying to connect to storefront using https (works with http) using a FTP server with DHCP options set.

The certificates seems to be the issues as we have a root, intermediate1 and intermediate2, intermediate 2 is trusted by Intermediate1 which is trusted by Root Ca.

When we add these to thinos the two certificates for the intermediates appear as trusted by the rootCa, not in the correct chain.

It works fine on a t3030 Terminal in Legacy mode.

Failed on a t3030 if Storefront=Yes is set, Error is Parent certificate is invalid"

Doesn't work at all using HTTPS on a T10.

From what I understand thin OS should understand the Certifcate chain beig 3 Deep but its not doing so?  

Chain is

RootCA

Intermediate1

Intermediate2

anyone else seen, experienced this issue?

↧
Search

V10L & 8.0_512 – "INSUFFICIENT MEMORY FOR THE NEW TASK"

August 9, 2017, 5:54 am
$
0
0

Hi Guys,

In my environment I have some V10L terminals. Recently, for compatibility purposes I decided to upgrade them to the latest available firmware for them: 8.0_512.

On some of the upgraded terminals I get “Insufficient memory for the new task” while trying connecting to the Citrix application. However, after accepting the error message it is possible to connect to the application.

Looks like the issue happens only on the terminals where Event Log says: "VGA: offscreen video ram = 0MB". On the working terminals the video ram is 8MB. Can this be changed or it mean I have two different flavours of V10Ls?

I have already reset these terminals to factory defaults which does not seem to help.

Is there anything I can do to get rid of this error message?

PS Dell/Wyse support - thank you in advance for any answers like "this model is EOL, please scrap them and buy a new ones"

↧
↧

Typo in 5010 Firmware for 5010 series

August 10, 2017, 12:57 pm
$
0
0

Hi All,

I was wondering what method I would go to report this to Dell, or if someone from Dell will see this that can fix it.  This typo first seemed to appear in ThinOS 8.3 for the 5010 model, and now continues to exist in 8.4.

Essentially the "Shutting down the System" actually says "Shuting down the system", took me awhile to notice but now I just can't unsee it!

↧

Anyone running 5010, 2GB RAM WES 7 on horizon 7.0.2

August 15, 2017, 7:21 am
$
0
0

Anyone successfully running horizon 7.0.2 on the wyse 5010 boxes. As the 5010 with 2gb RAM struggles to run PCOIP without VMware Remote MKS error message.

↧

5010 Citrix Adaptive Transport UDP Support

August 18, 2017, 8:25 am
$
0
0

Hello,

I was inquiring to find out what the general time frame for firmware on ThinOS that will fully support UDP Procotol based on Adaptive Transport?

Thanks!

Gary Adkins

↧
↧

wnos.ini help connecting to XENAPP 7.11 farm

August 24, 2017, 11:01 am
$
0
0

Greeting all. I am having trouble getting a 3030 LT to connect to my new Xenapp 7.11 farm.

Just can't get the syntax correct.

I'd like to have the terminal automatically launch a single app full screen. I've been able to do this on my 6.5 and below farms. Windows clients are no problem. Just the terminals that I want to have no user interaction to start up the app.

my wnos,ini looks like this.

# wnos.ini file is used to lock down winterm and set specific settings
# --------------------------------------------------------------------
SignOn=0
autoload-1
autopower=yes
ScreenSaver=0
MaxVNCD=1 VNCD_8bits=yes
VNCprompt=NO
VNCpassword=pwd encrypt=no
Privilege=high
Timeserver=ntp1.timeserver.com Timeformat="12-hour format" Dateformat=mm/dd/yyyy
TimeZone='GMT - 08:00' ManualOverride=yes Daylight=yes Start=030507 End=100507 TimeZoneName="Pacific Standard Time"
IcaBrowsing=UDP
DNSIPVersion=ipv4
DNSServer=IP
DNSDomain=domain
;
PnliteServer=store.com/.../config.xml \
DefaultSettings=XenApp
ReconnectAtLogon=2
ReconnectFromButton=2
AutoConnectList="APP"
UserName=username
Password=password
DomainList=domain
AdminMode=yes

Thanks in advance.

Dan

↧

Testing Firmware 8.4_009 and launching Published Apps or VDI's gives SSL Error 4

August 28, 2017, 7:20 am
$
0
0

We are currently using 5010 D10D running firmware 8.3_012 connecting to NetScaler running version 10.1.31 to XenApp 7.14 environment.. This works fine currently, however, testing 5010 thin client with version 8.4_009 firmware I get SSL Error 4: Mocana SSL error 24. We do have a test NetScaler running version 11.1.51 and when we test to that environment we are now getting Protocol Driver error when launching published apps or VDI's. I can revert the thin client back to 8.3 and everything works great, it is only with firmware 8.4_009 that we get this issue.

↧

Dell wyse 3030 thin client big pixel on screen.

August 29, 2017, 12:20 am
$
0
0

Hi,

I have Dell wyse 3030 thin client (thinOS), with two Dell P2417H monitors, and sometimes big pixeles appears on the screen. See attachment:

I tried different monitors, but nothing has changed. I use RDP connections.

I would like to buy more, but as long as the bug is still there, I'll wait.

Can anyone experienced this?

Andrew

↧
Search

SFTP option for INI

August 29, 2017, 10:07 am
$
0
0

Has there been any advancement towards defaulting to SFTP or FTPS for the initial communication to grab the INI files for ThinOS? Security at our organization is getting tighter and tighter and I'd like to have this available when they ask. Unless HTTPS is meant to be the successor and secure replacement for FTP?

↧
↧

RDP reconnect behavior with RD Gateway

August 29, 2017, 4:34 pm
$
0
0

I'm posting this question to verify if anyone else is seeing this behavior:

We have ThinOS clients(8.3) configured to use RDP to a RD Gateway(2012 R2) and then to a Win7 VM or to a Server 2008 R2 RDS server. When the remote target or the gateway itself reboots the client doesn't immediately go into reconnect mode. Instead the user will need to generate some activity on the client side like a key press or move the mouse before the reconnect window launches.

This behavior is different from a direct RDP session from a thin client to a workstation or rds server where the client will immediately try to reconnect at the interval specified in the ini file.

Is this normal, or is there a configuration/design that is making the clients behave this way?

NLA is enabled and I can provide INI files for clarification.

↧

Dell Wyse 5213 WTOS - Is there a way to enable relative mouse?

August 30, 2017, 10:48 am
$
0
0

We have a unique software program that requires relative mouse mode and I do not see an option to enable this on the Dell Wyse 5213 AIO.  Using the Horizon Software client the option is there and works.  We are using WTOS version 8.0_512 but have access to all versions if this option is available in later releases.

Does anyone know how to enable relative mouse mode on WTOS on a 5213?

↧

Allow users to configure their resolution

September 12, 2017, 7:38 am
$
0
0

Hello team, I have searched every where with no luck for a solution. We have the 3030 devices and want the users to have the ability to manage/configure their own screen resolution. In the WDS we have the settings configured for DDC. Someone mentioned removing these two lines from the wnos.ini file. When I looked in the ini file, those lines are not there. So here I am, thanks for any suggestions

Remove two lines from my wnos.ini file.

Screen=1 Resolution=DDC

Screen=2 Resolution=DDC

↧

Save local connection

September 12, 2017, 7:50 am
$
0
0

Is there a way to allow the 3030 thin clients to save local connections so that when they are rebooted, users do not have to recreate a new one under the Add a connection tab?

↧
↧

3040 - Citrix Receiver Version

September 25, 2017, 1:07 am
$
0
0

Hallo

Question - Is it possible to update the Citrix Receiver software installed on the clients ?
Just updated a 3040 to the newest firmware, however its still running an extremly old version of the Citrix receiver - Why is that? And how to get that updated so it can support all the new features (Such as Adaptive Transport etc)

Currently its running 14.0.0.91 (And according to google that is from like 2013)..

Thanks in advance 
//Martin Mouritsen

↧

V10LE & 8.0_512 – FREEZING AND CRASHING (W2K8R2 & XENAPP6.5 & .NET APPS)

September 29, 2017, 1:08 am
$
0
0

 Hi guys & Roger,

In one of my environments I have a mixture of 500x clients: V10LE (90%) & T10 (10%) thin clients. Please note the clients are V10LEs not V10Ls...

V10LEs have been rock stable for years with no issues. Around 6-9 months ago we upgrade them from 7.1_033 to 8.0_512. All was fine till recent 3 weeks when MULTIPLE V10LEs started to crash/freeze at the same time. We are not 100% sure if T10s are also affected...

When V10LEs freeze they lose network connectivity with the last displayed screen state, i.e. there is no Trap error on screen, just the last application state. Obviously, something triggers this multi-freeze issue but I don't know what.

My questions to you guys are:

- have you experienced similar issues with V10LE on 8.0_512?

- do you think that not resetting V10LEs to factory defaults after the upgrade from 7.1_033 to 8.0_512 could contribute to the above issue?

Thank you,

Regards,

↧
Search

WYSE V10L _ WNOS.INI _ DHCP161 _ 2 VDI CLUSTER´S(VM VIEW)

October 4, 2017, 9:45 am
$
0
0

Hello there,

I need a help to set DHCP and WNOS.INI.

I have a IBM_BLADE Cluster running virtual desktops with Vmware View 5.0. We connect using thin client´s Wyse V10L , WNOS.INI on server VMwareView5.

Now I have one new DELL Cluster with VmwareHorizon7.

Is that possible set 2 IP´s(View5 & Horizon7) in DHCP_FTP_161, and in WNOS.INI ?

How can I do it ? How can my wyse connect in virtuals machines from both clusters, servers… ?

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

SignOn=Yes SaveLastDomainUser=yes EnableOK=yes
EnableCacheini=yes
Rapportserver=http://IP
connectionbroker=vdm
VDIBroker=https://ServerViewName
SignOn=Yes
DomainList=”domain.com”
MaxVNCD=1
VncPassword=”PASS” Encrypt=yes
VncPrompt=No Accept=5 ActiveVisible=yes

Now I was looking for more information on how to make a “WYSE V10L” connect in 2 differents servers (1 (CPVVIEW01); 2 (CPVCONNECTION)), diffeferent VMware_View_servers/ clusters.

WYSE already connects to CPVVIEW01. In DHCP I have option 161 pointed to CPVVIEW01. And on this server I have the file wnos.ini.

Now I would like WYSE to be able to connect to the virtual desktops of both servers, not just CPVVIEW01.

I inserted a line in WNOS.ini = SelectServerList = VDI; View5 – https://cpvview01; Horizon7 – https://cpvconnection

With this I was able to appear the option of “VDI SERVER” at the moment of inserting the ID and PASSWORD of the user.
But I still can not connect the virtual desktops/machines from “CPVCONNECTION”.

It is missing some configuration that I do not know what it is.
Who could help me ?

aditional information : when I try to connect on CPVCONNECTIO it show this error : VDI/M server sign-on failed !

↧

Dell Wyse 3030 grey blocks appearing on the screen

October 9, 2017, 11:01 pm
$
0
0

Hi

we recently purchased a few 3030 thin clients and are also experiencing the same issue where random grey block start appearing on the screen

i have shadowed the rdp session and it does not show the blocks on the screen

if we restart the thin client the blocks disappear for a while and randomly comes back

how would we go about to obtain the firmware

will the basic warranty cover this issue

there is another topic with the same issue where they say that the new firmware resolved the issue
en.community.dell.com/.../21024468

regards

Kobus

nwasupport@pretor.co.za or kobus@nwa.co.za

↧
↧

Problems after updating firmware t 8.3_011

October 24, 2017, 11:14 am
$
0
0

Greetings all.

I'm currently trying to update a few Wyse 3010 Tx0 thinclients to the latest firmware.

Following the instructions from Dell/Wyse support on the phone I upgraded one unit from 8.1_027 to 8.1_031 then to 8.3_011 all using WMS 1.0.0.36801, the plan was to go from there to 8.3_014, 8.3_109, and finally 8.4_009

As soon as the update to 8.3_011 was complete I can no longer push commands or new firmware updates to the device. I get the following error on the Wyse terminal:

SSL: error ERR_SSL_UNKNOWN_CERTIFICATE_AUTHORITY

SSL: unable to setup connection. (err=7517)

I'm not certain what to do to get this device back into the WMS to continue updating firmware. I've tried adding an advanced option to that group with the line:

SecurityMode=No

But the device still refuses to check back into the WMS. Any ideas on how to proceed?

Ideally I want to be able to update these devices without having to ever physically touch them (there are hundreds, many in remote office locations that are not easy for us to deploy personnel to).

↧

XenDesktop ICA session disconnection

October 25, 2017, 11:24 am
$
0
0

Using Wyse T10 thin clients to connect to a XenDesktop 7.12 environment. Randomly users will get almost immediately disconnected from the ICA session when they log in. The help desk has been rebooting the user's VM to force them onto another one. When the disconnection occurs the thin client logs the following:

VDCAM RTP: trap 4, EIP 0xd5090, CR2 0x194

In the network trace I see the thin client send a FIN to VDA. Nothing shows up in the application or system logs on the VDA. Nothing in the Delivery controller either. Anyone know what the above error means? 

↧

Resolution settings in username.ini not applied

October 30, 2017, 2:34 am
$
0
0

I want monitors to always startup with de best settings for that display and for some users with a specified resolution. Since 8.4.108 it's possible to change the resolution without a reboot, so I thought it would be possible. But I can't get it working.

I created a wnos.ini with Screen=1 Resolution=DDC setting and a username.ini with Screen=1 Resolution=1440x900.

The DDC resolution is used, but when the user logs in, it will not change to the specified resolution.

When I use Screen=1 Resolution=1920x1080 in the wnos.ini it's working. But some displays do not support the 1920x1080 resolution. That's why I want to use DDC by default.

↧
Viewing all 74 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>