Forum Replies Created
-
Posts
-
Do you know if there’s any plans to put back in the ability to configure RDS connections at the device level again? For many of our use cases it’s easier to teach the end users how to set up a new connection on the device then to have to set up a server to manage them or use a file that you download to them so I’m wondering if I need to move away from the Wyse thin clients since they no longer have that simple option to configure it and have it stick when rebooted.
Do you know of a way to suppress the RDS certificate warning (similar issue to this post: https://technicalhelp.de/topic/wyse-3040-thinos-rds-certificate-warning/ ) We sometimes end up in situations where we’re referencing the RDS server(s) by IP address because there’s no DNS server in the mix so we’ll see that same error in those situations. Can that be suppressed in the configuration that is loaded?
That’s a “feature” of their newer ThinOS versions. Hopefully they remove that feature in the future and allow that configuration option from connection manager. In the meantime, I was able to load the config from USB (have to factory reset the thin client with the network disconnected and choose to load config from USB drive) and then the config stayed. I just added the RDS connections to the config that I was loaded so it would look something like this:
;*************************************************************
;* *
;* This wnos.ini file was generated with the *
;* Configuration Generator 8.5.02 *
;* Copyright by Thomas Moellerbernd *
;* *
;* https://technicalhelp.de *
;* *
;*************************************************************;*************************************************************
;* General 1 *
;*************************************************************autoload=2
EnableLocal=yes;*************************************************************
;* General 2 *
;*************************************************************MirrorFileServer=yes
;*************************************************************
;* Peripherals *
;*************************************************************Language=Us
;*************************************************************
;* Network *
;*************************************************************SignOn=No
;*************************************************************
;* RDP *
;*************************************************************;————————————————————-
;- RDP Session 1 –
;- Each line but the last must end with a ‘\’ –
;————————————————————-CONNECT=RDP \
Host=whatever your host is \
Description=”Your Description” \
AutoConnect=yes \
Reconnect=yes \
Fullscreen=yes \
Username=username
Password=password
Domainname=domain
LocalCopy=noYou can in multiple RDS sessions if you need using that same config style for each session needed.
Looks like I did not initially have those two options, Mirrorfileserver=yes and EnableLocal=yes in the ini that I generated. Added those options and the RDP connections stay in the connection manager so I think I should be good. It would be nice if they would remove that “feature” that does not allow the connections to be created right from the connection manager. Thanks for your assistance with this.
I’ll verify that. Do you know the version when that started? Is there a version I can downgrade to that will allow the RDS connections to be created right in the connection manager again?
Ok…so I wonder what I’m doing incorrectly then with the config generator? I’m using the config generator to generate the config with the RDS connections that I want and have the file on a USB drive. I reset the 5070 to factory defaults and choose to load the config from USB, it tells me that it finds it and I see it go through the paces, but then end up still with an empty Connection Manager when it boots up.
I finally got around up updating the firmware to the 7.1_207 version and that seems to have resolved the issue. Thanks.
Well, I was hoping it could be done on the thin clients themselves, because the servers that they’ll be connecting to for the remote desktop sessions are going to be moving into a domain at a customer site, and we’re not sure what type of settings are going to be in place as far as group policy, security, etc., and we don’t have control over anything except for the couple servers that we’re implementing for this project. I was thinking if we could handle it at the thin client level, that would make it as easy as possible for the operators of those thin clients, while also not complicating the server side of things if something were to go wrong in the future. If it can’t be done at the thin client level, then I guess it may be that we need to handle it through some sort of software once everything is implemented into the domain
