An Introduction to Neocoretech NDV

Neocoretech does not have an operating system requirement, as part of the installer will install a bespoke Linux build, optimised to run the Neocoretech solution. The installation package can be deployed in minutes via a CD ROM, with subsequent servers dynamically integrated into the architecture.

NDV supports multiple operating systems, including Windows and Linux, with both 32-bit and 64-bit distributions supported.  The GUI based management console is intuitive, utilising a “drag and drop” interface.

High Availability can be quickly configured and deployed, without a requirement for a SAN.  Direct Attached Storage is utilised for media storage, but with an innovative architecture, RAM is utilised to create quick virtual PCs, without the IOPS storm even if multiple virtual PCs are started.

“Read-only” virtual PCs can be created giving the user a clean PC every day.  This leads to convenient management, standard build control, better disk usage and better administrative control. Persistent (personal) virtual machines can be created as well, giving a more conventional PC experience.

There are three deployment options, including:

1)      Single server deployments, hosting all the functions

2)      Two server deployments, giving a highly available architecture

3)      Multiple server deployments, giving distributed functionality and large scale deployments

If you are interested in becoming a reseller or want to see a web demo, please contact e92plus for more information.

Neocoretech – Reduce your VDI project cost and improve performance!

When I talk about the Neocoretech NDV VDI solution, the common question I’m asked by VMware View engineers is “How do I size the SAN?”

There is normally a confused look, when I suggest there is no need for a SAN!

We first of all have to understand that VMware View is built on the VMware ESX infrastructure, where the Storage Area Network (SAN) is a requirement for server virtualisation. 

For VMware View, the backbone of the solution is shared storage, where SANs are often used to provide this. The underlying VMware ESX infrastructure has to be configured to use logical unit number (LUN) addresses in order to give high availability.  This means they reserve a LUN on a SAN for 2 servers, so if one server goes down the other still points to the same disk. Using direct attached storage cannot work with this approach as Direct Attached Storage (DAS) by definition cannot be shared.

Neocoretech provides a different approach based on clusters, utilising direct attached storage. A dedicated Ethernet interface links two servers to that disk cluster and the disks are mirrored over the LAN. This also improves performance as there are more disks and therefore more spindles are available to deliver disk IOs.

In combination with utilising read-only desktops on the Neocoretech NDV solution, means that the VDI infrastructure is only delivering the desktop, which means dedicated network storage can (and should) be used to manage the data and storage.

With correct sizing and infrastructure, Neocoretech NDV will not only lower the TCO giving quicker ROI, but it also means there is no need to endure the SAN IOPS storm in the morning!

Why use VDI, when I can use Terminal Services?

Working with Neocoretech NDV VDI solution, I see many advantages for using it over VMWare View or Citrix XenDesktop, due to the way it utilises RAM and negates the need for SAN solutions by using “Read only” desktops.  A common question when discussing virtual desktop solutions, is why use VDI when I can use Terminal Services. 

These points were addressed by Christophe Rettien, CTO of Neocoretech.

Architecture

• Neocoretech NDV is a 1:1 connection between 1 Thin Client and 1 Hosted PC (in this case a Virtual PC)
• Terminal Services is a 1:n connection between n Thin Clients and 1 Hosted Server (could be a physical virtual Server)

Protocol

• Neocoretech NDV is not tied to RDP and can use any available protocol including rich multimedia support, bi-directional sound and USB redirection. Available protocols are RDP, UXP, NX, RDP TCX...
• Terminal Services IS RDP so no protocol choice here. If Terminal Services does not provide sufficient performance, nothing can solve that!

Supported OSs

• Neocoretech NDV supports any x86 OS, which allows a user to run a Microsoft Windows XP, Windows 7 or Linux, with 32-bit or 64-bit distributions.
• Terminal Services is only supported by Microsoft servers, so the end user can run a remote session on a Windows 2003 or 2008 Server. Some tweaks exist to create a Windows 7 look and feel from a Windows 2008 session.

Supported Software

• Neocoretech NDV runs a single computer for each user, which means any application available on the OS used will be available to the user.
• Terminal Services runs multiple shared instances of a unique program within the same server (2003 or 2008) and only applications allowed to be shared are available to the end user.

Summary

Neocoretech NDV provides:

• Operating system choice
• All applications are supported
• Different applications installed according to user profile
• All protocols supported
• High availability options

NDV consequences:

• Requires powerful servers

Terminal Services provides:

• High density - good ratio server sizing/number of users

Terminal Services consequences:

• CAL licensing cost per session and per application
• Poor multimedia performance
• Complex GPO settings, if different desktops are to be presented based on user profiles (all applications need to be installed)

Conclusion

As with all solutions, it is more important to understand the requirement, rather than push a technology.  We need to understand when one solution would fit better than the other.

Terminal Services works well in environments with budget constraints or require a “vanilla” suite of applications.  VDI solutions such as Neocoretech NDV offer greater flexibility, management, operating system choice, supports a greater number of clients, and can be easily managed.