Warning: count(): Parameter must be an array or an object that implements Countable in /home/customer/www/vmguru.com/public_html/wp-content/plugins/amp-plugin-filter/amp-plugin-filter.php on line 24

Warning: Illegal string offset 'width' in /home/customer/www/vmguru.com/public_html/wp-content/plugins/amp-plugin-filter/amp-plugin-filter.php on line 28

Warning: Illegal string offset 'height' in /home/customer/www/vmguru.com/public_html/wp-content/plugins/amp-plugin-filter/amp-plugin-filter.php on line 28

Warning: Illegal string offset 'width' in /home/customer/www/vmguru.com/public_html/wp-content/plugins/amp-plugin-filter/amp-plugin-filter.php on line 28
PCoIP Support for Microsoft RDS

PCoIP Support for Microsoft RDS

This week Teradici, creator of the PCoIP protocol, released a technology preview of their new product named Teradici Arch. Teradici Arch is asoftware-based solution that enables the use of the PCoIP protocol for Microsoft  RDS as an alternative to Microsoft RDP.

This should provide better user experience and access to the entire PCoIP ecosystem, PCoIP thin clients, APEX accelerator cards, etc.

Teradici has been forced to delay the release of Arch due to a scalability issue but a new tech preview will still allow enterprises to familiarize themselves with the product. The final product release is expected in Q3 2013.

This solution should be an ideal solution for enterprises with mixed environment of VMware View VDI and Microsoft RDS. I wonder how many of these mixed environments exist. The only mixed PCoIP/RDP environments I have seen in my work are View environments where both protocols are used to connect to the same View desktops to use MMR instead of PCoIP acceleration.

The PCoIP protocol is now available for use with terminal services for more performance over any network type and access to the PCoIP ecosystem of products including low maintenance, ultra-secure zero clients. Teradici Arch enables customers to:

I understand Teradici’s move to broaden their scope and support Microsoft RDS. Teradici was a hardware company and only moved to software with the VMware View opportunity, but Teradici seems they don’t want to be a one trick pony. So with the release of Arch, Teradici makes a move for Microsoft Remote Desktop Services.

There are few things that will be interesting as soon as this new solution is available. Will companies pay for a View license so they can run Microsoft RDS? Teradici has also started working on adding support for a Microsoft Connection Broker but even if they can use the PCoIP protocol without VMware View, will companies pay the extra money instead of using RemoteFX?

But the technology is awesome, it enables companies to:

 

But how does it work? Teradici Arch published desktop is implemented by the PCoIP Connection Manager (PCM), a virtual appliance that incorporatestworoles: an internal connection manager and a security gateway. The PCM handles communication between the View Connection Server (VCS) and end points, and enables access to both View VDI and RDS published desktops. The PCM can be implemented in the corporate LAN, and in a DMZ for remote access. When the PCM is located in a DMZ, its PCoIP Security Gateway (PSG) component must be enabled. The PSG is an optional component of the PCM .ova package and replaces the VMware View Security Gateway. It allows users to access their remote desktops from the Internet without having to set up a VPN connection

For now Teradici Arch only supports Microsoft RDS publishing over the PCoIP protocol using a VMware View Connection Server but in a subsequent release they are going to support Microsoft customers who don’t have View and really just want to add PCoIP.

The Teradici Arch solution will be generally available in Q3, 2013 and sold for a list price of USD $60, per named user through Teradici distribution channels. This is a perpetual license and includes the first year of maintenance and support from Teradici. Subsequent years of maintenance and support are available for USD $10, per named user.

To use Teradici Arch (release 1.0) you need the following:

Software solution

    1. EXE file: to be installed on each Windows server
      Note: RDP won’t be available anymore for this Windows server
    2. OVA file: for the front end virtual appliance
      (PCoIP Connection Manager – PCM)

System requirements

Device compatibility

Display support

USB support

Related posts

VMGuru’s browser and OS statistics

by Alex Muetstege
13 years ago

How to install Rancher on k3s

by Dimitri de Swart
3 years ago

VMware to acquire RTO Software

by Anne Jan Elsinga
14 years ago
Exit mobile version