- This topic has 7 replies, 3 voices, and was last updated 3 years, 2 months ago by
.
-
Posts
-
Hello,
We actually using FTP server to push wnos.ini file on wyse 3040. We are in a production area so this function suit our buisness model, even if it’s not very secure. (but we have restrict access to specific IP etc..)
We are installing DELL ThinOS 8.6_606 on wyse 3040 and it appears that the FTP is not working anymore.
We will use this firmware update to go on a “more secure model” with the HTTPS. I try to find some document where it explain how to configure HTTPS and how configure DHCP and wyse. I see here that a doc is mentioned but I’m unable to find it.
If someone have this it would be wonderfull!
Thanks
Simple steps.
– create a server certificate or buy one
– assign this cert to your webserver and bind it to the https protocol
– copy the root certificate (not the server cert) to the ThinOS deviceCG
Hello ConfGen
I reply after a long time but i need some information please.
I create a self signed certificate with this command, in order to have a certificate longer than 1 years
New-SelfSignedCertificate -Subject “myserver.local” -DnsName “myserver.local” -CertStoreLocation “cert:\LocalMachine\My” -KeyAlgorithm RSA -KeyLength 2048 -KeyExportPolicy Exportable -NotAfter (Get-Date).AddYears(10)
I bind this server to my https protocol (not sure about the difference betwenn assign and bind)
Then i go to the mmc console and extract the .cer that i found in the local computer\personnal folder. Once extract i push this cert with WMS
Is it the correct one? because you tell the root and not the server cert?
My issue is in ThinOs 8.6_013 everything is ok, my wyse grab the certificate and read the wnos that are on my webserver, and connect to machin using rdp
In thinOS 8.6_511 and later I have a certificate error. The certificate are well push from WMS, the wnos is read by the Wyse but ask me for a ceritifcate. This certificate seems to be the one of the machine that i try to reach in RDP.
Can you help me on this? is there something wrong in my config, or does the new ThinOs firmware bring new function, and new things to configure?
Thanks!
Add the following to the top of your wnos.ini
SignOn=no EnableMessage=no
I already have the SignOn=0
I try your command line but it’s the same.
Here is my wnos.ini:
signOn=no
EnableMessage=no
autoload=0
autopower=yes
screen=1 resolution=1920×1080
screen=2 resolution=1920×1080
SEAMLESS=no
Privilege=High SuppressTaskBar=yes
DESKTOP=background.bmp
DeskColor=”255 255 255″
MaxVNCD=1
SessionConfig=RDP ForceSpan=yes
EnableLocal=yes
ConnectionBroker=VDM
EnableLocal=No
SysMode=classic
Language=Uk
Dualhead=yes
Mainscreen=1
ScreenSaver=0
TerminalName=TestWyse2#TOMNEW
connect=rdp \
Autoconnect=2 \
Fullscreen=no \
Resolution=DDC \
console=no \
OnScreen=1 \
description=TOMNEW \
host=192.168.1.28 \
Username=test \
Password=test \
Domainname=test \I also try the SecurityMode=low with the same result
Here is the error that I have. The certificate is the one install on the Remote machine. If I click on Continue the connection is working
If I click on Cancel I have this error
How can I bypass this warning and say to the ThinOs that it always accept?
It looks like the client is looking for the certificate of the Terminal Server.
Have you installed that on the client also?
Alternatively, you also add
SecurityPolicy=lowto your wnos.ini.CG
The config is simple:
1 Wyse 3040 that retrieve the wnos.ini on a HTTPS server. The wnos.ini configure a RDP connection on a windows10 client.
The certificate asking is the one of the windows10 client (like when you do a RDP from a windows to a windows)
The SecurityPolicy=low is working perfectly!!!! In the wnos.ini reference guide I see the SecurityMode and don’t see the SecurityPolicy one….thanks you so much xD
This topic is solved
- You must be logged in to reply to this topic.