Sometimes new ideas are a rework, improvement, or different application to an existing idea. The intent of this post is to both educate on emerging alternative client compute models, but also to request inputs from the Symantec Connect Community how existing tools can be applied to enhance or migrate to these compute models. Thus the application of joint experiences and understanding.
Alternative compute models are emerging for a client computing environment, and are what Intel calls “Dynamic Virtual Clients”. In some respects, the alternative models already exist. The difference is the direct hardware, software, and related ecosystem support to further enhance these model.
The following picture provides an overview which information available via a whitepaper on alternative compute models (see http://communities.intel.com/docs/DOC-2550) or via a recorded webinar (see http://communities.intel.com/community/openportit/vproexpert/emergingcomputing/blog/2009/11/18/watch-it-on-demand-intro-to-dvc-recording-now-available)
In discussing the alternative compute models with a variety of individuals, the question is often raised: How does Symantec enable or enhance these models?
The verbal answer points to a variety of Symantec products including Client Management Suite, Workplace Streaming (i.e. Appstream), SEP (Symantec Endpoint Protection), BESR (Backup Exec System Recovery), Workflow, and more.
In briefly discussing each of the Symantec products, a deeper understanding is obtained how that individual product might help achieve the overall vision. Product managers, consultants, and others all agree in principle how Symantec products might come together for the realization of a DVC solution. However, a conclusive end-to-end story still seems ethereal… and thus the intent of this article to educate and solicit inputs on the full realization of an alternative compute model. The clarify – how Symantec products help to achieve that realization in connection with tools outside Intel and Symantec.
Background on the Models and Players
There are a variety of reasons and in-roads to why these alternative compute models are of interest. Often the intent is to remove a user’s direct dependency on a particular client computing device. Related intents might be to minimize application compatibility constraints, improve management, and so forth.
Those who take the “thin client” approach are looking for central management of data and application. This model allows any user to login to any terminal system, yet still have their profile of applications, data, and so forth. Security is also a factor in why a thin client approach is used. Generally speaking, the actual client device is a small and must have connectivity to a backend infrastructure which must be expanded to handle all the sessions. Thin clients are a common model for call center, retail, healthcare, or related environments.
A “rich client” approach suggests local data storage, local application usage for rich media, and so forth. This model allows mobile, off-line usage. Management and security at the endpoint device is important. This is the model to which many laptop users, mobile workforce, analysts, engineering, or related types of users may be accustomed.
The image below depicts a third model – Dynamic Virtual Client. The intent is to merge the benefits of a thin client and managed rich client environment. The previous image highlighted a few examples such as operating system streaming, application or environment virtualization, or client side virtualization.
The alternative compute or DVC models have reinforced a concept which has existed for years yet is fairly new for the client environment. The concept is virtualization, with a distinction between Type 1 and Type 2 hypervisors.
In summary – the difference between a virtualization layer directly below or on top of the client operating system. More explanation on hypervisors is available at http://en.wikipedia.org/wiki/Hypervisor.
Those providing the hypervisors for the DVC model include:
- Citrix XenClient – Type 1 Hypervisor
- VMware Client Virtual Platform (CVP) – Type 1 Hypervisor
- Microsoft Hypervisor for Windows 7 XP-Compatibility mode – Type 2 Hypervisor
All of the hypervisors utilize hardware virtualization such as Intel VT.
In addition to those offering hypervisor solutions for full operating environment, Symantec provides application virtualization for Windows clients. Symantec Workplace streaming, formerly called Appstream, has been used in production environments for several years. This solution is being enhanced with greater Intel vPro technology platform capabilities (see solution brief at http://www.symantecintelalliance.com/public/pdf/INT_Sym_EndpointVirtualization_SB.pdf).
There are other pieces, components, and players to the Dynamic Virtual Client paradigm. Pilot deployments are occurring today, and more deployments will be occurring in the coming year.
Yet in the all of the hoopla around DVC, how does migration to the environment occur or what further enhancement are obtainable using currently available Symantec products?
How Symantec Can Help Achieve the DVC vision
At the beginning of this article, the question was raised on how do the various Symantec products help to achieve DVC. In providing the background, a few ideas may have surfaced around direct or indirect involvement.
The following diagram provides an overview with a few brief explanations on what Symantec products might help achieve this vision. Some items have been tested in the lab, or verbally confirmed by product experts. Other ideas are theoretical based on discussions.
I am open to the thoughts and inputs of the community. Again – the intent is for mutual understanding and collaboration as the alternative compute models are deployed. The desired outcome is for confirmation on the combination of tools, examples where combined tools (or alternative tools) are being used today, and even feedback on to make the process\solution even better.
Based on the above model, a few Symantec solution platforms and tools that come to mind to brief the “Managed Client” to the “Dynamic Virtual Client”.
- Symantec Manageability Platform (i.e. Altiris) – With Out-of-Band management and Intel vPro technology, the ability to remote power, boot redirect, and perform other functions at the hardware layer to assist with the migration. Deployment solution can be used to apply the hypervisor environment and other needed partitions\files to the target systems
- Symantec BESR – Enable physical-to-virtual conversion. Output can be VHD (Microsoft Hyper-V) or VMDK (VMware) based. For a Microsoft Windows 7 deployment, the BESR product combined with Deployment solution can capture the current environment in case of application compatibility or other needed.
- Symantec Workplace Virtualization\Streaming – Application virtualization, license management, and other capabilities within the deployed DVC environment.
- Symantec Workflow – The orchestration of events across the different product lines to help with the migration to DVC.
There are likely other Symantec products that could help or enhance this environment. In your own experience or understanding, if there’s an idea to be shared… please do share.
Concluding Thoughts
Alternative client compute models are already emerging with the advent of Hyper-V inside Windows 7 deployments, Citrix XenClient, VMware CVP, and so forth. The links shared above or an Internet search will point to the production examples that are occurring. The alternative models help to address a gap between thin client and a rich managed client, providing an improved operating environment to the user. Understanding how Symantec products currently assist – or could potential assist – in achieving a DVC solution is a mutual interest beyond just Intel and Symantec. Thus the final request - if you agree/disagree, have further insights, or simply want more information - please indicate
The opinions expressed on this site are mine alone and do not necessarily reflect the opinions or strategies of Intel Corporation or its worldwide subsidiaries