This blog post will kick off a series a posts that will go through some of the exiting new features of vWorkspace 6.0 in detail. This first “vWorkspace 6.0 feature spotlight” is about our advancements in flexible computer assignments.
One of the edges that vWorkspace has always had on its competitors it the tremendous amount of flexibility that is offered. One of the best examples of this is the fact that almost every resource in the vWorkspace Management Console ( the vMC - one console to rule them all ) can be assigned not just to users or groups but also to:
- IP subnets. This allows you to create your own location based rules (like for printing).
- Client names. Using client names allow you to link a specific client only to a specific resource.
- Active Directory entities. This way you could use an OU as an assignment filter for a resource.
Prior to vWorkspace 6.0, this flexibility was not available for the assignment of managed desktops but now it is! This means that in vWorkspace 6.0 you can assign a managed desktop to Users, Groups, OUs, Client IPs, or Client Names. This is how it looks.
This way of assigning managed desktops was actually based on several customer requests. Since we have been doing VDI for almost 4 years now (which is a very long time in the VDI space) we have had a lot of time and experience to learn and benefit from the knowledge of our customers. The need for more flexible computer assignment is one of the things we learned. For example, one of our customers is using the more flexible computer assignment options to enable the scenario of the “shift-worker” in a hospital, by assigning a particular desktop to a client machine instead of a user.
So, prior to centralizing their applications and desktops, this customer used to have a rich client in a hospital room that locally ran the applications that were used by multiple nurses subsequently, each one continuing the work where the previous shift left of. With the flexible computer assignment options in vWorkspace 6.0 the nurses are able to work in the exact same manner (which is what end users like) while the hospital was reaping the benefits of centralizing their application and desktop workloads.
This hospital is just one of the examples of how this feature can be used. I have seen many more examples ranging from factory personnel to schools. I am sure you can think of other usage cases as well. This small video shows you how to enable this feature:
Of course this is just one of the many new features in Quest vWorkspace 6.0. You can download a fully functional evaluation version of vWorkspace 6.0 here yourself.
You can leave a response, or trackback from your own site.
