The HTML5 client works over RDP and includes Ericom Blaze RDP Compression and Acceleration technology. This client is particularly useful for devices for which PCoIP native clients are not available (such as Chrome OS netbooks) or on which PCoIP can't be installed (such as on locked-down PCs and kiosks).
I am sure what you meant to say is, this can be useful for situations where the View Client cannot be installed, such as a locked down PC or kiosk?
The ability to install something in these cases is not unique to a specific remoting protocol RDP, PCoIP, RGS etc. correct? It simply is unique to the model of currently available native View Clients.
Are there any diagrams you can share with the community that explain the integration and how it works? For example; something that shows where the transcoding of the RDP traffic happens, does it happen at the VM, at a Web/App Server? How it integrates with View Security Servers / Connection servers and the connection flow?
This might be helpful for everyone to understand since Ericom does not certify their components with View?
First of all, thank you for your interest in our latest cutting edge product that enhances VMware View and extends its reach to new type of devices.
Yes, you are correct, Ericom’s HTML5 technology can be useful for situations where the View Client cannot be installed, such as a locked down PC or kiosk. You are also correct in stating that the lack of ability to install something in these cases is not unique to a specific remoting protocol - RDP, PCoIP, RGS, etc.
As to the architecture, we are preparing diagrams that will be on our FAQ page. Until then let me explain:
There are 2 installers:
2) Installer for every virtual desktop – this installs the Ericom HTML5 WebSockets Server. You can install it as part of a virtual machine template and reuse it for any virtual machine.
The Ericom HTML5 Client running within the browser will connect using the VMware View Server XML API to the VMware View Server to login and receive the list of available desktops. Once the user selects a desktop to connect to, the entire communication, from the browser all the way to the Ericom HTML5 WebSockets Server, is based purely on standard HTML standards. This means that the transcoding from RDP to HTML is done within the virtual machine itself.
Since the documentation on how to integrate with VMware View Security Server is not available to Ericom, Ericom has developed its own Ericom Secure Gateway.
When an Ericom Secure Gateway is used, the Ericom HTML5 Client connects via the Ericom Secure Gateway rather than directly to the Ericom HTML5 Server.
You are correct that you do not need to install anything on the user client side. Regarding the View Manager side, there are 2 installers:
2) Installer for every virtual desktop. Installs the Ericom HTML5 WebSockets Server. You can install it as part of a virtual machine template and reuse it for all the virtual machines.
Ericom's HTML5 VDI client for VMware is now GA. Ericom AccessNow for VMware View provides seamless, web-based access to VMware View virtual desktops. It’s the first VDI solution to run wholly within any HTML5-compatible Web browser, and works on Chromebooks and natively with Chrome, Safari, Internet Explorer (with Chrome Frame plug-in), Firefox, Opera and other browsers with HTML5 and WebSocket support. The solution does not require Java, Flash, Silverlight or any other underlying technology.
For more info, and to download a demo version, visit:
For a case study of deploying Chromebooks with Ericom AccessNow for VMware View, visit:
Adam (from Ericom)
The Richland School District Two in South Carolina has licensed Ericom AccessNow for VMware View for use by its 30,000 students and staff. AccessNow for VMware View will be deployed across its 35 K-12 schools.
Ericom AccessNow for VMware View is a pure HTML5 RDP client that enables users with HTML5-compatible browsers to connect to their VMware virtual desktops – and run those desktops in a browser. It does not require Java, Flash, Silverlight, ActiveX, or any other underlying technology to be installed on end-user devices – an HTML5 browser is all that is required.
For more information on this case study, visit:
Note: I work for Ericom