The Right Display Protocol For The VDI Solution

This write-up assumes that the reader is aware of the VDI architectural basics. It further delves into providing an insight to the further questions: • Why is a good Remote Display Protocol needed? • What should be expected out of an efficient display protocol? • Who are the popular manufacturers in Remote Display Protocol currently? • What makes SUNDE-VDI Protocol an obvious choice for the VDI solutions?

For a moment, let us keep the rest of the components of the VDI architecture at backstage, and pick up a single component, which establishes the communication between the server and the endpoint device- the connection broker. Every connection broker follows a specific set of rules to bridge this connection. In other words, the connection broker, which is a software program, uses a Remote Display Protocol which helps in communicating the output from server to the endpoint device.

A good Remote Display Protocol is expected to be equipped with the following properties:

1. It should ensure a reliable data delivery. Transmission Control Protocol (TCP) is a well known protocol, which sends the generated output in small packets of data. The protocol retains the network connection till all the data is transferred, and resends the output if the connection is interrupted. It is a highly authenticated protocol.

2. The data delivery must be fast, especially for transferring the media rich applications. The audio and the video should be synchronized with minimal delay. User Datagram Protocol(UDP), unlike TCP, does not sequence the data packets, and thus is efficient in sending the data faster.

3. There must be no complex hardware extension involved. Most of the display protocols today are those which were designed to be used for Terminal Servers, and needed several hardware extensions before these could be used for the VDI solutions.

The Popular Display Protocols:

Choosing the right protocol depends mainly on the multimedia requirements of the endpoint device. However, the commonly used remote display protocols today are technologically designed to offer:

• A High Resolution session
• Dynamic Object Compression
• USB Redirection
• Multimedia stream remoting
<li>Multi-monitor support

Under VDI architecture, there are 3 such display protocols, which are popular, with their won limitations:

1. Microsoft’s Remote Desktop Protocol(RDP)/ Remote FX:
The RDP has been going through continuous up gradations to meet up with the demanding multimedia requirements. Remote FX is the improved protocol version of RDP for later versions of Windows Server. However, it is not considered the best option for the continually increasing multimedia requirements. Without the required upgrade, the user experience does not suffice.

2. VMWare’s PC-over-IP(PCoIP):
With a low bandwidth consumption over LAN and WAN, PCoIP is preferred over the other display protocols. Its performance is also better since it uses UDP unlike the other display protocols which use TCP as well. However, a major limitation of VMWare’s PCoIP is that it cannot be used with Windows Server 2012, which is wide in use at present.

3. Citrix’s HDX:
Initially called Independent Computing Architecture(ICA), Citrix launched its remote display protocol with an appreciable performance, which was launched as HDX as a part of its 2009 suite release. It offered a very good end-user experience with a low bandwidth and multimedia redirection. The further versions of HDX were multimedia rich. Its biggest limitation however was its incompatibility with later versions of Windows servers, which confined Citrix to a lesser number of users.

While, the companies are still in research mode to offer a PC like multimedia solution under VDI architecture, SUNDE has grown by leaps and bounds in this area:

1. SUNDE-VDI Protocol uses both the TCP and UDP, retaining the reliability and the quickness of the data stream transfer.

2. The graphics acceleration in SUNDE-VDI protocol is efficient enough to handle the rich multimedia, including graphics and animation.

3. This is a server rendering protocol, which means that it depends upon the host for its operations. This eliminates the need of CPU and a huge memory at the endpoint device, making it a good option for zero clients as well.

4. SUNDE-VDI Protocol comes as a part of vPointServer software, which is the connection broker using VirtualBox platform as the hypervisor. Another part of this package is Diana Zero Client, which is the endpoint device from SUNDE. Everything as a package takes care of the compatibility issues between the components, and makes it a perfect choice as a display protocol.

For more details, please visit: http://www.sundenc.com/support/knowledge/The%20Right%20Display%20Protocol%20For%20The%20VDI%20Solution.html

What Is Zero Client & What Is A True Zero Client?

Zero client, also known as ultra thin client, is a server-based computing model in which the end user's computing device has no local storage. A zero client can be contrasted with a thin client, which retains the operating system and each device's specific configuration settings in flash memory.

A typical zero client product is a small box that serves to connect a keyboard, mouse, monitor and Ethernet connection to a remote server. The server, which hosts the client's operating system (OS) and software applications, can be accessed wirelessly or with cable. Zero clients are often used in a virtual desktop infrastructure (VDI ) environment.

Benefits of zero client computing:
-- Power usage can be as low as 1/50th of fat client requirements.
-- Devices are much less expensive than PCs or thin clients.
-- Efficient and secure means of delivering applications to end users.
-- No software at the client means that there is no vulnerability to malware.
-- Easy administration.
-- In a VDI environment, administrators can reduce the number of physical PCs or blades and run multiple virtual PCs on server class hardware.

The term zero client is often misapplied in thin client vendor marketing materials. True zero client endpoints do no local processing and have no client operating systems, drivers, software, storage, or even any configuration settings. They are completely stateless and management-free. Zero clients mean zero endpoint management – absolutely zero.

Some thin client vendors have even tried to make their endpoints look “zero” by keeping the client operating system image on the hard disk of a separate “streaming” appliance, requiring that users wait while it is downloaded to the endpoint’s hard disk or flash storage before use. Unfortunately, this only makes the entire VDI architecture from these vendors even more complex and fragile.

To see if vendor claims of “zero-ness” are valid, apply these tests:
1. Does the endpoint include a CPU of any kind? Any RAM or Flash Memory? Any storage devices or moving parts at all?
2. Are you forced to configure the endpoint in any way before use?
3. Do you need to reconfigure the endpoints before you are able to swap them between users?
4. Does the endpoint need to download an operating system image or any software before you can use it?
5. Are you not able to use the native Windows drivers that Microsoft or the manufacturer supply to connect to a new peripheral?
6. Does the endpoint require you use an embedded management tool?


Article submitted by : http://www.sundenc.com/support/knowledge/What%20Is%20Zero%20Client.html

VDI hardware comparison: Thin vs. thick vs. zero clients

When it comes to virtual desktop infrastructure, administrators have a lot of choices. You may have wondered about the differences between VDI software options, remote display protocols or all the licenses out there. In this series, we tackle some of the biggest head-scratchers facing VDI admins to help you get things straight.

When you deploy VDI, you need to figure out what hardware your virtual desktops will run on. To host virtual desktops, you have a lot of choices: thin clients, zero clients and smart clients -- not to mention tablets and mobile devices. Thin clients and other slimmed-down devices rely on a network connection to a central server for full computing and don't do much processing on the hardware itself. Those differ from thick clients -- basically traditional PCs -- that handle all the functionality of a server on the desktop itself.

Understanding the benefits, challenges and cost implications of all these VDI hardware options will help you make the right choice. Let's get this straight:

Thick clients

It's possible to use thick clients for desktop virtualization, but many organizations don't because it doesn't cut down on overall hardware and requires all local software. If you use traditional PCs to connect to virtual desktops, you don't get many of the benefits of VDI, such as reduced power consumption, central management and increased security.

How thick clients compare to thin

Since a thick client is basically a PC running thin client software, it is usually more costly than a thin client device. Plus, thick clients have hard drives and media ports, making them less secure than thin clients. Finally, thin clients tend to require less maintenance than thick ones, although thin client hardware problems can sometimes lead to having to replace the entire device.

Thin clients

With thin client hardware, virtual desktops are hosted in the data center and the thin client simply serves as a terminal to the back-end server. Thin clients are generally easy to install, make application access simpler, improve security and reduce hardware needs by allowing admins to repurpose old PCs.

What to look for in thin client devices

Thin clients are meant to be small and simple, so the more advanced features you add, the more expensive they get. As you choose thin client devices, consider whether you need capabilities such as video conferencing and multi-monitor support. You should also take into account your remote display protocol and how much display processing your back end can supply. Aside from being cheap and uncomplicated, thin clients should also offer centralized management. For instance, you can automatically apply profile policies to groups of thin clients with similar configurations. That tends to be easier than individual manual management. Plus, you want your VDI hardware to be simple enough for nonveteran IT staff or those at remote branch offices to be able to deploy.

Zero clients

Zero clients are gaining ground in the VDI market because they're even slimmer and more cost-effective than thin clients. These are client devices that require no configuration and have nothing stored on them. Vendors including Dell Wyse, Fujitsu, and SUNDE offer zero client hardware.

Pros and cons of zero clients So what are the benefits of this kind of VDI hardware? First off, zero clients can be less expensive than thick and thin clients. Plus, they use less power and can simplify client device licensing.

Still, there's a catch: Vendors often market zero clients as requiring no management or maintenance, which isn't always true. Some products do require software or memory and other resources. In addition, zero clients tend to be proprietary, so organizations could run into vendor lock-in.

Contact us: http://www.sundenc.com

Article submitted by: SUNDE VDI delivers an extremely high performance virtual desktop for users including rich multi-media, dynamic graphics, and seamless responsiveness.

What’s the difference between virtualization and cloud computing?

Virtualization is a computing technology that enables a single user to access multiple physical devices. Another way to look at it is a single computer controlling multiple machines, or one operating system utilizing multiple computers to analyze a database. Virtualization may also be used for running multiple applications on each server rather than just one; this in turn reduces the number of servers companies need to purchase and manage. It enables you to consolidate your servers and do more with less hardware. It also lets you support more users per piece of hardware, deliver applications, and run applications faster.

Cloud computing offers scalable infrastructure and software off site, saving labor, hardware, and power costs. Financially, the cloud’s virtual resources are typically cheaper than dedicated physical resources connected to a personal computer or network. With cloud computing, the software programs you use aren’t run from your personal computer, but rather are stored on servers housed elsewhere and accessed via the Internet. If your computer crashes, the software is still available for others to use. Simply, the cloud is a collection of computers and servers that are publicly accessible via the Internet.

One way to look at it is that virtualization is basically one physical computer pretending to be many computing environments whereas cloud computing is many different computers pretending to be the one computing environment (hence user scaling). Virtualization provides flexibility that is a great match for cloud computing. Moreover, cloud computing can be defined based on the virtual machine containers created with virtualization. Virtualization is not always necessary in cloud computing; however, you can use it as the basis. Cloud computing is an approach for the delivery of services while virtualization is one possible service that could be delivered. Large corporations with little downtime tolerance and airtight security requirements may find that virtualization fits them best. Smaller businesses are more likely to profit more with cloud computing, allowing them to focus on their mission while leaving IT chores to those who can do more for less.

Plainly, virtualization provides more servers on the same hardware and cloud computing provides measured resources while paying for what you use. While it is not uncommon to hear people discuss them interchangeably, they are very different approaches to solving the problem of maximizing the use of available resources. They differ in many ways and that also leads to some important considerations when selecting between the two.

Article submitted by: http://www.sundenc.com