Virtualization Personalization (Windows Profile Management and the management of all user customization data) is a problem increasing in market scope (XenApp, fat client desktops, and VDI), technical scope (profiles, group policies, unique user settings, unique user customizations in applications, and unique user settings in the OS), leading both AppSense and RTO to invest heavily in a layer of solutions that are focused upon managing the personalization of the environment while not breaking and reducing the value of centralized management.
In many cases when you start to discuss security of virtualization, you soon drop into a discussion of virtual networking, and management network security. In other words you are laying out the traditional security zones that exist within the networking world. Network security, virtual and physical, is extremely important however there is more to virtualization security than just your network. Here are some new ways to consider virtualization security.
VMware is trying to package Microsoft Windows out of existence by allowing applications to run in guest with no OS from Microsoft or Red Hat. Microsoft is trying to package VMware out of existence by including Hyper-V for free in Windows Server, and by providing application virtualization functionality that makes virtualizing server operating systems unnecessary.
Liquidware Labs is focuses upon defining a methodology (Assess–>Design–>Deploy–>Manage) for VARs and service providers to use in VDI projects, and upon providing a toolkit that implements much of this methodology in software.
The recent VMware Communities Podcast had ThinApp engineers on the call. Their mantra when presented with questions on licensing was “Ethics do not ship with the code.” In other words, applications that could end up as ThinApps could violate your End User License Agreements (EULA).
Veeam has posted a blog of their own trying to explain why they are no longer selling Veeam Backup 3.x for the Free version of VMware ESXi. It is perfectly understandable that Veeam would comply with VMware’s requests in this matter as Veeam as a company depends upon their relationship with VMware to further their own business aims. In other words, Veeam has done nothing that could be considered wrong. However, VMware making the request in the first place should be a major concern to current and future vendors of VMware products.