Flexible Desktop: Comparison of two kinds of terminal virtualization architecture models

Terminal virtualization, the virtualization of end-user desktops in a central repository, differs in many ways from server virtualization. A major difference is the construction of end-user virtual machines. There are two ways to create a desktop virtual machine, each of which provides a different terminal virtualization model.

Persistent end user virtual machines

The first thing you need to consider when determining your terminal virtualization model is to create a persistent or non-persistent one. Persistent end user virtual machines each user uses a dedicated virtual machine. This dedicated virtual machine will include the end-user-required applications, data, and the internal user status of the virtual machine, as well as the requirement not to support external services. However, as disk files for virtual machines increase as they are used, the terminal virtualization model will require a lot of storage space under a centralized storage structure.

This means that disk files for virtual machines require long-term management, helping to control the consistency and size of virtual machines by using defragmentation, compression, and virtual Disk file maintenance tools. Persistent virtual machines Each disk file usually starts with a 10GB, which can increase significantly as the user increases the data disk file size within the virtual machine.

But persistent virtual machines do not address many of the problems that organizations face when they run physical desktops. Because end-user data is stored inside the virtual machine, the organization must use a variety of ways, typically through a terminal virtualization backup tool to protect the data.

Non-persistent end user virtual machines

Non-persistent End user virtual machines do not have these requirements. Because it is created temporarily when the user logs on. Non-persistent virtual machines require three core components to work properly-in fact, the most critical terminal virtualization build pattern in these three core components is the first part of the following description:

A source-side desktop virtual machine that contains only the updated operating system and required utilities, such as management and Anti-malware tools.

Virtualized applications or programs that are processed through Application Virtualization (creator VIRTUALIZATION,APPV) tools to capture their running state rather than the installation process. So the virtual application is not installed but is transferred to the terminal, which starts when the end user actually uses the program-because of this, the virtual application can be applied to any virtual machine when the user logs on.

User state VIRTUALIZATION,USV, which is implemented through custom tools in the terminal virtualization Suite or standard Microsoft tools such as Folder redirection and roaming profiles. USV continues to protect end-user data because it keeps user data out of the virtual machine, which is also true when users log on to the VM.

In fact, because the virtual machine contains only the OS, the program and end user data is only applied at logon, and each virtual machine is non-persistent, because once the user logs out the virtual machine can be discarded. Therefore, the non-persistent virtual machine mode of terminal virtualization is more general than persistence mode.

This terminal virtualization model also saves storage space because you no longer need to store a single virtual machine. Instead, you store the original copy of the virtual machine to create a new virtual machine as needed. It should be noted that both APPV and USV have their own advantages over terminal virtualization.

Finally, the terminal virtualization virtual machines vary in size and complexity depending on the end user's type of work. VMware divides end users into three different types, each with their own needs:

Task-oriented employees focus on a small number of repetitive activities based on a small amount of application, so the demand for virtual machines is relatively low.

Knowledge workers rely on performance tools to manage information, and they often need complete productivity kits such as Microsoft Office, and they often need access to the Internet. The need for virtual machines is medium.

Advanced users use complex applications such as development tools or drawing tools, and the need for virtual machines is even more compelling.

When developing a server resource plan for terminal virtualization, it is necessary to understand your user needs, as each virtual machine requires adequate memory, paging files of the appropriate size to reduce disk access, and the appropriate size of the virtual disk file.

Consider the two modes of persistent and non-persistent end-user virtual machines to determine which terminal virtualization architecture is best for your infrastructure. "

(Responsible editor: The good of the Legacy)