tencent cloud

Cloud Virtual Desktop

Release Notes
Product Introduction
Overview
Strengths
Scenarios
Basic Concepts
Use Limits
Billing
Billing Overview
Purchase Method
Auto-Renewal
Overdue Payments
Refund
Getting Started
User Guide
Administrator
End Users
Use Cases
Replacing VNC and RDP for Remote Desktop Ops
How to Restrict CVD Access to Specific IP Addresses Only
API Reference
Introduction
FAQs
Administrators
End User Usage
Related Agreement
Service Level Agreement
Privacy Policy
Data Processing And Security Agreement
Contact Us
DocumentationCloud Virtual DesktopUse CasesReplacing VNC and RDP for Remote Desktop Ops

Replacing VNC and RDP for Remote Desktop Ops

PDF
Focus Mode
Font Size
Last updated: 2026-01-16 10:49:16

Using a CVD Instance to Replace VNC and RDP for Remote Desktop Ops

Cloud Virtual Desktop (CVD) offers virtual desktop services featuring on-demand and quick delivery. It uses an encrypted adaptive transmission protocol and policy-based security controls to build a secure portal for business access on the cloud. CVD instances can replace Virtual Network Computing (VNC) and Remote Desktop Protocol (RDP) for efficient Ops and secure R&D, enhancing the security and continuity of business access.

Diagram of Using a CVD Instance for Efficient Ops and Secure R&D





Feature Comparison: CVD vs. VNC, RDP, and WebRDP

CVD enables batch deployment, security control, and convenient access. The following table compares its features with existing VNC, RDP, and WebRDP solutions.
Comparison Item
VNC
RDP
WebRDP
CVD
Access terminal
H5
Client
H5
HTML5 or client
Access latency
High
Medium
Medium
Low
Whether an EIP is required
Not required
Required
Required
Not required
Whether operations for shortcut keys such as copy and paste are supported
Not supported
Supported
Supported
Supported
Whether file transfer is supported
Not supported
Supported
Not supported
Supported
Whether adaptive resolution is supported
Not supported
Supported
Supported
Supported
Whether accessing customer resources over private networks is supported
Supported
Supported
Supported
Supported
Whether access to GPU desktops is supported
Not supported
Supported
Supported
Supported
Whether access to Linux desktop systems is supported
Supported
Supported
Supported
Supported
Whether security policies such as watermark are supported
Not supported
Not supported
Not supported
Supported
Whether restricted access for specific users is supported
Not supported
Not supported
Not supported
Supported
Whether restricting access by user ID or to users in specific regions is supported
Not supported
Not supported
Not supported
Supported
Whether two-factor authentication is supported
Not supported
Not supported
Not supported
Supported
Whether an SDK (which integrates the service into the customer's Ops platform) can be provided
Not supported
Not supported
Not supported
Supported

Example: Connecting a CVD Instance to a CVM Instance

Prerequisites

The CVD instance and the target Cloud Virtual Machine (CVM) instance are in the same VPC network, or their private networks are connected via Cloud Connect Network (CCN).
You have purchased and assigned a CVD instance. The end user can log in to it normally. For more information, see Getting Started.
The security group rules of the CVM instance allow access from the IP address of the CVD instance and the required ports. For specific ports, see Common Server Ports.

Example 1: Connecting a CVD Instance to a Windows CVM Instance





Example 2: Connecting a CVD Instance to a Linux CVM Instance




Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback