The next version of VMware View will have better PCoIP performance, more client device support,a storage management feature similar to Citrix IntelliCache and -- finally -- integrated profile management.
A VMware View integrator based in New England who is privy to company details said VMware View 5 will have a storage management feature similar to Citrix IntelliCache. Storage costs and performance issues plague virtual desktop customers, so this would alleviate those issues.
Sources close to VMware also said Virtual Profiles will be part of the View picture later this year, but the functions will be limited. Specifically, it won't include the desired Windows XP to Windows 7 profile compatibility.
That means many VMware View shops will still need to buy third-party profile management tools. VMware endorses Liquidware Labs profile management product, and Liquidware offers its ProfileUnity product at a discount intermittently for View customers. The company's profile management offering does much more than the Virtual Profiles management tool VMware acquired from RTO Software in 2010.
VMware declined to comment on View 5. However, IT pros expect the company to disclose the product's advances at VMworld 2011 in August.
Source: http://searchvirtualdesktop.techtarget.com/news/2240036965/VMware-View-5-to-add-profiles-PCoIP-and-client-support
Showing posts with label View. Show all posts
Showing posts with label View. Show all posts
Friday, June 24, 2011
Monday, March 9, 2009
View Designing
When doing a design for a View Architecture there are a lot of things to think about in difference areas, the following rules are general and can be used for doing the View design.
The following design specifications will be observed when designing the View Composer architecture:
•Every View partition with View Composer desktops requires that View Composer is installed on that container’s vCenter Server system
•Maximum of eight ESX/ESXi hosts per View Composer cluster
•Maximum of 500 vClones (linked clones) per Parent VM replica; this is a good practice for recompose/refresh operations
•Maximum of three 500 VM clusters per View container; this is to stay clear of the 2,000 VM limit in vCenter Server 2.5
•Maximum of 64 linked clones per datastore
There are a lot of other objects to observe, i will try to write them down here in the future.
The following design specifications will be observed when designing the View Composer architecture:
•Every View partition with View Composer desktops requires that View Composer is installed on that container’s vCenter Server system
•Maximum of eight ESX/ESXi hosts per View Composer cluster
•Maximum of 500 vClones (linked clones) per Parent VM replica; this is a good practice for recompose/refresh operations
•Maximum of three 500 VM clusters per View container; this is to stay clear of the 2,000 VM limit in vCenter Server 2.5
•Maximum of 64 linked clones per datastore
There are a lot of other objects to observe, i will try to write them down here in the future.
Subscribe to:
Posts (Atom)