- This topic has 8 replies, 2 voices, and was last updated 4 years, 9 months ago by
.
-
Posts
-
My apologize, was not sure where to put this, I am hoping you could answer what should be a fairly basic question for me.
Scenario –
20 Wyse terminals (Thin OS -8.5+) – Managed by WMS (Internal Use only)
Need – High Availability – 2 Session Hosts(Shared DNS entry for both RDS), 2 Connection Brokers(Shared DNS entry for both RDB) (In High Availability active)
All of that is set up and working flawlessly failover and everything, now here is the dumb question. (Overkill I know but following direction)
In WMS – I have it setup to use the Microsoft Broker, however it fails due to SSL Certificate Authority Unknown (Was trying to use http instead of https as I was directed that Certs were not needed due to these being all internal on their own private internal network). Anyways to make this work without certs?
That does not sound like a ThinOS issue, but a general MS RDSH issue.
Can you connect without certificates via http from a PC?CG
I went ahead and just did certs for it (which has been hit and miss)
Via a PC – no issues at all, working very flawlessly
Via Wyse – Controlled reboot talking to the Management Suite – Connects
–If the Wyse is brought down by being unplugged (simulating a power loss), it will not connect to the broker, as if some of the settings from the Management Suite are being lost? If I then do a proper restart, it works, then unplug it and then it errors.
Negative, I have not, would the wyse management software be considered the file server?
or am I going to have to setup a network share and host a file? If so is there a way to download the config file I have setup in the management software to host it?No, WMS will act as the Fileserver in this case and the client will cache the config locally.
CG
I went ahead and tweaked some settings –
Here is what I am seeing, every other boot it allows me to connect to the connection broker, no matter how I disconnect. Almost wondering if there is something else wrong or I am missing – Steps below1) Sign in normally – works
2) Reboot – RD Broker Connection Failed
3)Reboot – works
4)Reboot – RD Broker Connection Failed
5)Reboot (pulled the plug and put it back in) – Works
Sounds like your DNS round-robin is the root cause.
Have you tried to connect to both RDSH server directly via FQDN?
I assume the first will work and second won’t.CG
- You must be logged in to reply to this topic.