Remote Desktop Protocol (RDP) Licensing Agreement Between Microsoft And Trugrid

Microsoft Corp. and Trugrid (N.E. Desktop Software, Inc.) have entered into a licensing agreement to enable access to Microsoft’s Remote Desktop Protocol (RDP) technology for TruGrid’s simple and secure workplace, hosted in Microsoft Azure. This agreement will give a client straightforward yet secure access solutions to do business in digital world. The RDP license allows the companies that are creating an implementation of the Remote Desktop Protocol (RDP) set to license the Intellectual Property Rights they need from Microsoft by signing the RDP client license. Non-windows thin client devices and non-windows based client software are the products that might need these rights to interact with Windows Remote Desktop Servers (Sessions or VM based).

TruGrid includes fully integrated security and cloud scalability and it simplifies corporate-wide access to Enterprise workplaces that are based on Microsoft Remote Desktop Services (RDS). Micky Minhas, head of Microsoft Technology Licensing said that the licensing agreement with TruGrid can help partners around the world to meet the evolving needs of their customers in the cloud.[1] The partners who are involved in developing variety of different solutions including non-windows thin client services and third party collaboration software that consumes RDP system will ultimately get the benefit from the Remote Desktop Protocol Licensing Agreement.

RDP implementer are required to obtain a patent license for RDP from Microsoft to use the RDP 8 feature set. Microsoft under a fixed fee agreement made it easier to obtain required patent license to use the RDP 8 feature set to interact with the appropriately licensed Windows Remote Desktop clients and servers. Peter Ayedun, CEO of TruGrid said, “The agreement will enhance Microsoft RDP and enables TruGrid to support and secure millions of simultaneous connections via our integration with the Microsoft Azure Cloud.[2]

The RDP client license helps the RDP implementer in:

  1. Providing free documentation support via community forums.
  2. Free attendance at the protocol PlugFest events where attendees get a chance to meet the Microsoft engineers directly and receive presentations about any specific area of protocol technology.
  3. Getting access to Network Analyzer tool which helps a protocol analyzer can capture, view and analyze network traffic.
  4. Test suites: Microsoft has begun releasing test for different protocols and will continue to roll them out over time.
  5. RDP license enables the RDP implementer to get access to :-
  6. RDP 7.1 reference sources
  7. RDP 8 progressive codec and clear codec reference sources[3]

Author: Rishabh Tripathi, Intern at Khurana & Khurana, Advocates and IP Attorneys. In case of any queries please contact/write back to us at pratistha@khuranaandkhurana.com.

References:

[1]https://www.microsoft.com/en-us/legal/intellectualproperty/mtl/trugrid

[2]https://www.microsoft.com/en-us/legal/intellectualproperty/mtl/trugrid

[3]https://techcommunity.microsoft.com/t5/Enterprise-Mobility-Security/Remote-Desktop-Protocol-Licensing-Available-for-RDP-8/ba-p/248069

Leave a Reply

Your email address will not be published. Required fields are marked *

4 × 1 =

Archives

  • June 2021
  • May 2021
  • April 2021
  • March 2021
  • February 2021
  • January 2021
  • December 2020
  • November 2020
  • October 2020
  • September 2020
  • August 2020
  • July 2020
  • June 2020
  • May 2020
  • April 2020
  • March 2020
  • February 2020
  • January 2020
  • December 2019
  • November 2019
  • October 2019
  • September 2019
  • August 2019
  • July 2019
  • June 2019
  • May 2019
  • April 2019
  • March 2019
  • February 2019
  • January 2019
  • December 2018
  • November 2018
  • October 2018
  • September 2018
  • August 2018
  • July 2018
  • June 2018
  • May 2018
  • April 2018
  • March 2018
  • February 2018
  • January 2018
  • December 2017
  • November 2017
  • October 2017
  • September 2017
  • August 2017
  • July 2017
  • June 2017
  • May 2017
  • April 2017
  • March 2017
  • February 2017
  • January 2017
  • December 2016
  • November 2016
  • October 2016
  • September 2016
  • August 2016
  • July 2016
  • June 2016
  • May 2016
  • April 2016
  • March 2016
  • February 2016
  • January 2016
  • December 2015
  • November 2015
  • October 2015
  • September 2015
  • August 2015
  • July 2015
  • June 2015
  • May 2015
  • April 2015
  • March 2015
  • February 2015
  • January 2015
  • December 2014
  • November 2014
  • October 2014
  • September 2014
  • August 2014
  • July 2014
  • June 2014
  • May 2014
  • April 2014
  • March 2014
  • February 2014
  • January 2014
  • December 2013
  • November 2013
  • October 2013
  • September 2013
  • August 2013
  • July 2013
  • June 2013
  • May 2013
  • April 2013
  • March 2013
  • February 2013
  • January 2013
  • December 2012
  • November 2012
  • September 2012
  • August 2012
  • July 2012
  • June 2012
  • May 2012
  • April 2012
  • March 2012
  • February 2012
  • January 2012
  • December 2011
  • November 2011
  • October 2011
  • September 2011
  • August 2011
  • July 2011
  • June 2011
  • May 2011
  • April 2011
  • March 2011
  • February 2011
  • January 2011
  • December 2010
  • September 2010
  • July 2010
  • June 2010
  • May 2010
  • April 2010