1. Installed Vmware Connection Server ver 6.0.1 build-2088845
Package: VMware-viewconnectionserver-x86_64-6.0.1-2088845.exe
Checked: Install HTML access
2. Issued New SSL Cert For Connection Server from Local CA
3. Installed View Agent on Win Ser 2008 R2 (RDS)
Package: VMware-viewagent-x86_64-6.0.2-2331487.exe
Checked: Install HTML access
4. Installed View Agent on test VM (Win 7 x64)
Checked: Install HTML access
5. Added RDS server to New farm
Created New RDS Pool with new farm
Added BLAST attribute to make RDS visible on HTML portal
When connecting to Win 7 host. No problem works like a charm. Video/Sound/Speed - all normal.
But when connecting to RDS getting Error Message "Unable to set up the desktop session for the display protocol. Please contact your system administrator."
Tried Uninstalling HTML-Access Component from Connection Server. And Installing it from separate Package: VMware-Horizon-View-HTML-Access_x64-2.6.0-2329873.exe
Works for BOTH desktop sources, but very very very laggy with image artifacts.
Does anybody know where I could flip a switch to make it working ???
Thanks
Sounds like you covered all the required steps - did you try with PCoIP to verify it works that way rather than blast?
> When connecting to Win 7 host. No problem works like a charm. Video/Sound/Speed - all normal.
> But when connecting to RDS getting Error Message "Unable to set up the desktop session for the display protocol. Please contact your system administrator."
View Broker 6.0.1 2088845 should install HTML Access 2.5 client, which doesn't support RDSH desktop.
> Tried Uninstalling HTML-Access Component from Connection Server. And Installing it from separate Package: VMware-Horizon-View-HTML-Access_x64-2.6.0-2329873.exe
> Works for BOTH desktop sources, but very very very laggy with image artifacts.
You can take a try via PCoIP or check the RDSH desktop's CPU/RAM.
Had same issue. tried few things as per this post and error disappeared.
Josephvirtual wrote:
Had same issue. tried few things as per this post and error disappeared.
That post basically says reinstall the View Agent. Clearing IE cache shouldn't really matter, but it's true that you do need to install the View Agent last. This has been a long standing rule.
As this is the top Google result for this problem, I thought I'd post another possible cause/solution to this error message.
In my case, the problem was that RDS licensing wasn't properly applied. An easy way to test is to attempt to log in to https://ServerName/RDWeb. If that doesn't work, no apps are going to be published to the Horizon client.
