Machines / scenarios not suitable for webrdp

【 Not suitable for webrdp Machine / scene 】

CPU Machines with low memory allocation

Low bandwidth machines

Local mstsc A normal machine

Overseas machines

The remote picture has rich color fineness 、 A machine for scenes with high frame rate , Such as online games or videos

Security software installed ( such as 360、 Safety dogs, etc ) Machine , Reference resources https://cloud.tencent.com/developer/article/1909626

Installed jinwanwei GNWay Machine

Machines with higher system versions are more viscous

webrdp Not suitable for 2012 The following systems , Or not , Or the disconnection and retry are very frequent 、 It is too frequent to be used normally ;≥2012 It works , But the system with higher version is sticky , Follow mstsc It's too far from

It is not recommended to log in using the console standard , If the local mstsc normal , It is recommended to give priority to local mstsc, There's a ratio mstsc Easy to use remote software multidesk, Recommended multidesk replace mstsc,multidesk Please refer to ：https://cloud.tencent.com/developer/article/1557779

【 Local mstsc When the remote is not available, you can consider using the console vnc, At this time, if it is necessary to remote , Reuse webrdp】

If the local mstsc Remote not available 、 Other clients can work normally mstsc, And must be remote （ For example, paste some Chinese characters remotely ,vnc Is not supported ）, At this point, you can try the console standard login , After all, there are agents , Although the effect of this proxy is average , However, when there is a single point network problem from the local to the peer and there is a strong demand for remote , This is the only quick choice .

As a whole , Recommended sequence （ The priority drops gradually ）：multidesk → mstsc → vnc → webrdp