> Customer Stories (13)
> How SUNDE helps (17)
> Knowledge Base (9)
> News & Releases (7)
> Video Center (5)
GRG Banking (002152) Brands
HUIYUAN CO., LTD.
What Most of Us Do Not Know About VDI Solution
To resolve the problem of application incompatibility is the one of the key reasons that drives RDS (formerly known as Terminal Services –TS) users to move to VDI. Also, when software vendors realized the great damage to their benefits, they have taken or are taking actions to protect their single software from being shared by multiple users. This makes VDI a necessity for users in demand of an independent desktop to run diverse applications.
However, the issue came when they still found some applications, like Adobe Premium, not able to run with the newly deployed VDI solution. What happened to the VDI solution they replaced with? Isn’t that VDI outweighs RDS in supporting applications?
Let’s have a look at the VDI solution they deployed.
Session Based VDI:
It consists of all VDI components. There is a hypervisor responsible for creating virtual machines. There are connection brokers which make use of the protocols for the remote data transfer. The users connect to the individual virtual machines, use remote display protocols to enhance their graphic and multimedia output quality. To an extent, the desktop personalization and user isolation is also well achieved.
It all appears to be the VDI like arrangement, where the complete server environment is being utilized by the hypervisor along with the connection brokers and management tools playing their respective roles. You may be convinced about this being the VDI solution of your choice.
BUT IT MAY NOT BE !! Look closely at how endpoint devices connect to the virtual machines. Isn’t that similar to the previous architecture of RDS?
The features of this form of virtualization lie in between RDS and VDI. If the complete concept is to be understood in a single line equation:
(Features of Session based VDI) = (session connection like RDS) + (Architecture like VDI)
Now users can understand why come applications are still not supported in this session based VDI. It fixed the problem of applications not supported in the multi-user environment but does still not support applications that are not allowed in a remote connection environment but requires local connection.
This is not the only problem with the session based VDI.
Due to the session connection, more issues are met at the endpoint
Is there any other type of VDI that helps?
Virtual machine based VDI:
Virtual machine based VDI addresses a complete PC like experience, achieved by the full control of virtual machines rather than sessions. The endpoint device has the complete control over the virtual machine to which it makes the connection through some independent VDI protocol as the remote display protocol instead of remote desktop protocol that was originally used in RDS to connect remote desktop sessions.
Due to the virtual machine connection, full powered virtual desktops are delivered to the terminal users.
Distinguish virtual machine based VDI from session based VDI
How terminal devices make connection differentiates virtual machine based VDI from session based VDI. Endpoint devices and the remote display protocol play a vital role. Thin clients which were originally designed to run sessions are not able to acquire virtual machine level authority. There are only a few purposed built zero clients can run virtual machines via VDI protocols. A typical example is SUNDE. SUNDE has their own independent VDI protocol for their VDI client named Diana. SUNDE’s protocol enables the terminal users to access virtual machines rather than session based virtual desktops.
|Sunde Smart PC|