Forum Replies Created
-
Posts
-
If they do I will move to a different platform. My thought is using either mini pc and/or stick pc’s with windows 10 built in. Lock down windows 10 using group policies and use remote desktop. There are many of them out there priced lower than $350.00.
I have used the Terryza stick pc’s for our digital signage and other things in the company. They are so cheap we just have spares sitting on shelf to replace them. Honestly it has just ran for the past couple years with no issue.
YES, I would love to do those but my boss gave me the big NO when she saw the price of $700.00 per as compared to the $375.00 for the 3040.
Thanks for the information though, I appreciate it.
I just compared the 5070 thin client we have to our Optiplex MFF pc and they are the same size. For some odd reason I thought they where much larger, sorry about that.
In our establishment (medical) size does matter. Our desk are very small and space is extremely limited with all the other items that are in and around the desk. I will not go into the details of everything I tried with the 5070’s because it is alot (monitor mount, wall/under desk mount, monitor with arm mount and others), but there was no solution that made our doctors happy.
The 3040’s P monitor mount works great because it really tucks in behind the monitor.
Do you think dell will come out with something that is similar in size to the 3040 once it is EOL?
Is there any update on this? I also heard the 3040 is going bye and there will not be a replacement for it. Also I noticed every 3040 is not available on Dell’s website last week.
I am very concerned about this since the 5070 thin client form factor is huge for no apparent reason. It is larger than our Optiplex 5070 PC’s.
If they don’t come out with something in the similar form factor I will have to start using ncomputing devices or something else.
Just another thought.
I have a couple T10 devices laying around if you want to post your wnos.ini configuration I can test it on my device to see if I get poor performance. Maybe this will tell you if it is the configuration on the Wyse client.
I would also look in the windows 2019 event viewer log under Application and Service Logs->Microsoft->Windows->RemoteDesktopServices-RdpCoreTS.
If there are RemoteFX issues going on it will show in there and I read many post about where RemoteFX causes disconnects and redirection issues.
I was testing out a ncomputing device the other day and had random disconnects along with other issues and it appeared to be something with the RemoteFx settings.
We are getting true color when connecting, I have to make sure of it because we are a medical facility and our staff views imaging on our units. If the coloring is not proper it would be an issue. We also are using H.264 with our connections but this also must be enabled at a server level to work. I did this thru group policy settings on the server.
Configure H.264/AVC hardware encoding for Remote Desktop Connections: Enabled
Prioritize H.264/AVC 444 graphics mode for Remote Desktop Connections: Enabled
In the config above all RDP sessions are set to true color at the session config level.
SessionConfig=RDP MaxBmpCache=128 DefaultColor=2
per the INI manual at a session level
DefaultColor — Specifies the default color depth to use for
the session 0=256, 1=High color (16-bits), 2=True Color (32-bits)Now there is also a RDP connection level option called colors. which has more options, but true color at a session or rdp level is the same setting. Make sure your ini does not have both specified.
Colors={256, 32k, 64k or high, 16m, true}
Default is high.
Session color mode. For faster display performance, use 256
colors for the session.
● 256 is 8-bits
● 32k is 15-bits
● 64k or high is 16-bits
● 16m is 24-bits
● true is 32-bitsThis may not help but I have around 70 T10 (3010) running 8.6_206 without issue. They do not respond as well as the 3040 thin clients but are very acceptable. I would recommend checking the ini because when I went to the 8.6 version there where many parameter changes in the ini file.
Also I always check RDP from a Windows 10 machine to see if it is the server vs wyse client. Windows 10 is running the newer RDP client which has features that would be enabled in the version 8.6 firmware.
Here is the wnos.ini I use.
autoload=1 LoadPkg=1 VerifySignature=no
AdminMode=yes Username=*** Password=**** ShowAdmin=yes
WMSEnable=no
WDMService=No Discover=No
CCMEnable=No Discover=No
Device=DellCmos WakeOnUSB=yes InternalSpeaker=no Microphone=no
AutoPower=yes
SecurityPolicy=lowreboot=yes Time=03:00
MirrorFileServer=yes
Autopower=yes
SysMode=VDI toolbardisablemouse=yes toolbardisablehotkey=yes DisableAddConnection=yes
Privilege=None ShowDisplaySettings=Yes
Language=Us ManualOverride=yes
KeySequence=yes Ctrl+Alt+Up=no Ctrl+Alt+Down=no Ctrl+Alt+Left=no Ctrl+Alt+Right=no
Device=Camera Disable=yes
Device=mouse Speed=4Screen=1 Resolution=DDC ManualOverride=yes
DeskColor=”0 0 0″
Screensaver=30 LockTerminal=0 Type=0 Sleep=30
Desktop=Timeserver=time.google.com Timeformat=”12-hour format” Dateformat=mm/dd/yyyy
TimeZone=’GMT – 06:00′ ManualOverride=yes Daylight=yes Start=030208 End=110101Device=Ethernet Speed=”Auto”
SignOn=No
MaxVNCD=1 VNCD_Zlib=yes
VncPassword=”*****”
VncPrompt=NoService=ThinPrint disable=yes
SessionConfig=ALL MouseQueueTimer=1 UnmapClipboard=yes Fullscreen=yes Resolution=default MultiMonitor=yes
UniSession=yesSessionConfig=RDP MaxBmpCache=128 DefaultColor=2
CONNECT=RDP \
Host=rds.host.com \
Description=”Remote Desktop” \
NoReducer=yes \
Rdp_No_Wallpaper=yes \
Rdp_No_Animation=yes \
Username=$TN \
Password=1 \
Domainname=host.comThanks, I have no real need to get on ThinOS 9 yet so I will stick with the INI until I have to make the move.
I have kinda found that out. It actually seems to cause more problems then it is worth. I was having trouble updating to the latest version and wyse did not provide much assistance. So i shut down the WDM services and the update went thru. Odd. I could see some value to the enterprise version but it is not worth the $40.00 a station.
I have 2 RDP Servers with a Session Broker Server, it was fairly easy to setup and has been working just fine. Here is the link I used to set it up. The Broker server I just setup in a Virtual Machine. The broker server also holds the user logon profiles.
http://technet.microsoft.com/en-us/library/cc772418%28v=ws.10%29.aspx
