DR Foster
1 Copper

Server 2016 and ThinOS 8.4

Since upgrading our RDS  from 2012 R2 to 2016, we've had an issue with the clients not being able to connect.

When logging into the client, the wyse 5010 just locks on VDI Authenticating.

WNOS.ini as below:

VDIBroker=https://*gatway address*
ConnectionBroker=Microsoft
SignOn=Yes
DomainList="*Domain Name*"

SessionConfig=RDP EnableNLA=yes EnableGFX=yes EnableTSMM=yes USBRedirection=RDP TSGWEnable=no

Looking at the IIS Logs we can see the following:

2017-10-10 14:37:17 10.1.1.40 GET /rdweb/feed/WebFeed.aspx - 80 - 172.21.0.2 WTOS/1.0 - 302 0 0 0

2017-10-10 14:37:17 10.1.1.40 GET /rdweb/feed/WebFeed.aspx - 443 - 172.21.0.2 WTOS/1.0 - 301 0 0 0

2017-10-10 14:37:17 10.1.1.40 GET /rdweb/feed/WebFeed.aspx - 80 - 172.21.0.2 WTOS/1.0 - 302 0 0 0

2017-10-10 14:37:17 10.1.1.40 GET /rdweb/feed/WebFeed.aspx - 443 - 172.21.0.2 WTOS/1.0 - 301 0 0 0

2017-10-10 14:37:17 10.1.1.40 GET /rdweb/feed/WebFeed.aspx - 80 - 172.21.0.2 WTOS/1.0 - 302 0 0 15

2017-10-10 14:37:17 10.1.1.40 GET /rdweb/feed/WebFeed.aspx - 443 - 172.21.0.2 WTOS/1.0 - 301 0 0 0

But the terminal won't progress any further.

We're currently on 8.4.B108

Has anyone experienced anything similar?

0 Kudos
2 Replies
johhen1
1 Copper

RE: Server 2016 and ThinOS 8.4

Do you have correct certificates in place?

Have you tried without https:// in the VDIBroker setting?

Our config is working with latest ThinOS 8.4_108 and Server 2016 Gateways.

VDIBroker=portal.domain.com
ConnectionBroker=Microsoft
AddCertificate=GeoTrustPrimaryCA.cer
AddCertificate=BPClass3CA3.cer
AddCertificate=BPClass3Rot.cer

0 Kudos
DR Foster
1 Copper

RE: Server 2016 and ThinOS 8.4

Thanks for your reply.

Certificates are added in fine and are visible.

Our Windows PC's are able to connect through fine, it's just the Wyse which are locking up at VDI Authenticating screen.

For completeness, our SSL Details are:

AddCertificate=SSL_Root.crt

AddCertificate=SSL_Int.crt
AddCertificate=-.**Domain Cert**.crt

0 Kudos