VMware Horizon Community
kaspianx
Contributor
Contributor

Horizon View Defaulting to RDP

I'm wondering if anyone else has seen this problem.  We upgraded from View 7.8 to 7.9.  We're using Windows for our security and connection servers.  Everything works fine until we do a recompose on the pool.  After, no one can log into any desktops.  Took me a while to figure out, but it seems after the recompose, View defaults to the RDP protocol.  When you look at the pool settings, it shows Blast, but it's actually using RDP (which can't go through our firewall).  I have to set the protocol to RDP, save, then change to Blast and save again.  Then people can start logging in.

Am I the only one experiencing this?

Reply
0 Kudos
5 Replies
strizzz
Contributor
Contributor

same problem on horizon 7.9 happens yesterday. simply change the protocol on the pool on pcoip, try a login and after that switch back to blast.

everythink works correctly

Reply
0 Kudos
gneville1985
Enthusiast
Enthusiast

HI We did the upgrade last week and we had few connection servers in old version and be had request default to RDP . We worked with VMware support and was informed to upgrade all the servers in the POD after upgrading every thg is back to normal.

Thank you

Reply
0 Kudos
jmacdaddy
Enthusiast
Enthusiast

Yes.  Experiencing this same issue on a number of different 7.9.0 deployments.  This problem is not Agent version or OS specific, as I see it with 7.1.0, 7.8.0 and 7.9.0 agents.  Definitely a 7.9.0 connection server bug.  Seems to only happen after a recompose. It will try to connect via RDP even though the pool is configured for PCOIP.  As stated by OP, editing the pool to change the preferred protocol to RDP, saving, and then changing it back to PCOIP and saving will fix the issue until the next recompose.

Would be curious if anyone experiencing this issue has tried upgrading Connection Broker to 7.10 to see if that fixes it.

Reply
0 Kudos
Chris_Nodak
Enthusiast
Enthusiast

Going to throw out a "me too" post in hopes of hearing of a fix for this. I've run into the same issue with 7.9. The only users that don't have a problem are those with PCoIP zero clients. Have not even begun to look at 7.10 yet myself.

Reply
0 Kudos
Jsteyskal
Contributor
Contributor

We are also seeing this issue. Our workaround was to set the pool to blast and not allow the users to change. I have not been able to confirm if this breaks again on recompose

Reply
0 Kudos