Posted by: shu in vmware, view, vdi, Ericom on
Jul 4, 2011
Do you remember when you first saw Microsoft’s Xbox Kinect in action? Playing games without a controller! It looked kind of dumb at first, people standing in front of a TV making exaggerated and weird moves, but when you tried Kinect yourself for the first time, it was fun to do and it worked pretty well. However, after a while it turns out that Kinect is a 1.0 version with it’s own limitation and you’ll have to wait for a year before new games will come out that uses all of the capabilities of the Kinect. This is kind of the feeling I have now about Ericom AccessNow for VMware View, the HTML5 client for VMware View. At first you think it’s probably not that good without a “real” VMware View client installed, but once you try it, you’re amazed how easy it is to setup and use it. After a short while, you see the limitations the product still has and you’d rather wait for a next version which has more features and has a better user experience.
In my last blog I talked about Obsolete clients in ConfigMgr. This happens during multiple deployments on the same device. There is also a known issue between ConfigMgr in combination with VMware View. Till VMware View v4.0 there was no refresh option possible, so when deleting and provisioning a new VDI desktop, a new object gets created in ConfigMgr collections.
Virtual Desktop Infrastructure, or VDI, is hot. It’s cool, secure, centrally managed, flexible - it’s an IT manager’s dream.
If you use non persistent desktops with VMware View, there are two options to reset the machine to its default state. One is immediately after a user logs off, the other is manually by a View Administrator. Currently, there is no way to schedule a VM reset at, say, 2PM.
A basic Windows XP machine can do a lot of things. Apart from facilitating an environment for a user's applications, it can do things like self maintenance, updates, hardware changes, etc. This is nice in a physical environment with lots of different pieces of hardware but in a virtual instance things hardly change, the environment is pretty much set and all tricks to speed things up usually have an adverse effect on the infrastructure. All these virtual instances need to share the often rather limited amount of resources.
