I think I am in the same sort of situation, but still confused as all <insert favorite expletive>
My view environment consist of three virtual servers.
1 connection server
1 security server
1 composer server
Connection Server
fqdn in windows AD is:
View-Conn.domain.local
10.10.144.47
internal DNS resolves…
View-Conn.domain.local
to
View.domain.local
So using the URL
internal users are able to log in and get a desktop securely and I can administer securely is I using the url
https://view.domain.local/admin
To make all of this secure, what I did was…
On this connection server I have installed under “Private” a secured certificate under the name of
View.domain.local
Now, I am not a certificate expert and I hate dealing with these… but the certificate I got from Go Daddy… it allows me to also create “5 SAN” names…
again, IDK, so what I did was.. tied to this same certificate I created 4 more additional SANs:
So, I am not sure if I did it right but now when I log into the administrator console
So, my first question is this...
Did I do everything correct up to this point?
Because I am receiving errors when attempting to log in via WYSE terminal...
when I attempt to connect to my connection server via a WYSE terminal
when I supply
view.domain.local or ServerName.domain.local as the connection server name...
I still receive a certificate error...
even though the cert details contain correct information. including SAN names
What am i missing? any thoughts?