I would like to know if anyone is trying to use a chromebook with HTML access, and, if so, how you dealt with the lack of function keys. Thanks.
I thought I would share our experience thus far with using a Chromebook and HTML Access:
Bottom line (so far): The keyboard issues are enough to prevent the use of Chromebooks as a viable "mobile" thin client, even if HTML Access performance improves.
Thank you for your feedback! We know that Chromebooks are not yet replacements for a thin client. At this point, if a company wants to generally use Chromebooks and also has a couple of legacy apps, HTML Access would fit the bill. But I've noted your comments and will consider them as future enhancements.
Amitava, your enable HTML Access for View by installing View 5.3 and the feature pack.
The VMWare/Google announcement at partner's exchange that the Chromebook can be used to access a VDI desktop was really old news. My hope is this new partnership will result in a View client for the Chromebook with USB pass through, great audio and video performance (PCoIP), and some good work arounds for the keyboard issues. I am in K-12 education and the Chromebook might make a great device to give to students who need to bounce from using web apps/cloud storage to Windows applications and local storage. Perhaps the next version of View will allow HTML access to be as good as using a client.
The announcement talked about trying to move the Chromebook into the enterprise. VMWare has made a decent start towards this but there is work to be done.