- This topic has 5 replies, 2 voices, and was last updated 3 years, 2 months ago by
.
-
Posts
-
Hello,
We deploy new RDS 2019 farm for sessions to replace Windows 2008 R2 RDS. We have one broker and few RDSH hosts configured for the same session collection.
After wnos.ini is updated to login to new 2019 farm, we have two logon phases.
First, the logon ask for user and password. After validation, we have another logon prompt for the password and the user is mentioned as “DOMAIN\User” in the logon field. If we enter the password a second time, we connect to the session.
What can be the issue ? We have the same on different Wyse / Dell terminals, like 3010, 5040, 5470…
It is not clear in the documentation, but I understand the MS Broker configuration is only for VDI purpose, because it never works for my sessions.
The wnos file :
Autoload=1
SignOn=no
Seamless=yesAddCertificate=RDSCertificate.cer
CONNECT=RDP \
Host=RDSBROKER \
Description=”RDSCollection” \
Domainname=domain.local \Your wnos.ini snippet shows that you are using a simple RDP connection.
Don’t do that when using a broker.
Remove the Connect=RDP part and replace it withSignon=yes ConnectionBroker=Microsoft Host=RDSBroker RDCollections=RDSCollection DefaultDomain=domain.localCG
When I configure the broker mode, I have always the “invalid username or password” message.
Have you configured Remote Desktop Web Access on your broker?
This is needed by ThinOS.CG
Yes, the web access is configured with a self signed certificate.
This certificate is added to the terminals.
The RDWA works fine with PC.
- You must be logged in to reply to this topic.