When will PCoIP Protocol be supported ?

[fuman_]

Hi,

I already understood that at this time only RDP is supported with VMware View, not PCoIP.

In my opinion - and from a customers point of view - PCoIP is one of the major features reagarding performance AND security for Virtual Desktops.

Is there any Information about the Juniper Roadmap to support PCoIP Protocol for VMware View? (Maybe from JTAC?)

Will it ever happen?

The Question is if customers can plan with that feature in the near Future or not......

[kpeterson_]

It's actually supported today and the solution is to use Network Connect. Specifically, you will want to use Network Connect with the ESP transport. This is required since PCoIP used both TCP and UDP and the Network Connect ESP option, which uses UDP port 4500 by default, maintains the performance benefit provided by PCoIP in the first place.

From a user's perspective, they will just log into the SSL VPN, either manually or automatically launch Network Connect, and then run the View client the same as if they were on the LAN.

[snaslund_]

I noticed this post and have a question. The SA configuration for network connect leads me to believe that Junos Pulse does not use ESP only SSL. The question I have is does the Junos Pulse client support PCOIP?

Steven Naslund

Chicago IL

[kenlars_]

I would expect it to work, but the wrapping of SSL around PCoIP would probably not be pretty from a performance perspective. ESP is good from a performance perspective because it avoids a lot of the TCP overhead of SSL, assuming that the payload protocols can handle error-checking and retransmission.

Ken

[VikingWay_]

Would be nice to have a native built in option for PCOIP. If it's being considered I'd vote for it.

[nminakis_]

You have my vote too. Every customer that I've worked with that has View deployed utilizes PCoIP and was disappointed with the available solution. It should be integrated in the clientless as a supported protocol.

[yahnnie_]

Absolutely it should be supported client less (without network connect). In the client less process the machine is still required to have the vmware view client installed locally. Regardless of the local client default settings you are forced into RDP. Only advantage of the client less at this point is single sign on.

It doesn't help that clever wording( http://www.vmware.com/files/pdf/VMware-View-JuniperNetworks-SSLVPN-SO-EN.pdf ) leads you to believe PCoIP is supported and with single sign on. It could be argued either way based off the text alone I guess however, The diagram makes no mention of needing Network Connect for PCoIP connections nor is the text definitive.

[SonicBoom_]

you have my vote as well for pcoip via WSAM since i just had to enable this but needed to have users hit a totally new realm so they can have NC launch automatically since we are a WSAM shop.

[michael.saw_]

Thanks for sharing, zanyterp!

[Zcript3r_]

Does anybody know of any roadmaps that show IVE natievely supporting PCoIP? And why does the client need to include VMWare View installed on the desktop. Is there some sort of rendering that Juniper doesn't want to get in-between that is happening client side?

Even so, I am fine with having to install a VMWare View client on the PC. The SSO is the huge thing we are missing as doctors deplore having to type usernames and passwords.