One needed to select 32-but colour to get a better protocol version and turning off double-buffering in some apps (eg emacs) helped.
#MICROSOFT REMOTE DESKTOP VNC WINDOWS#
I’ve had reasonable success with xrdp on the server and a windows client. So this may be part of the reason: fewer people see Remote Desktop as necessary.Ĥ.
And for web things you can do set up a socks proxy over ssh which I think can work for a lot of apps which are really just web sites. Text editors can work ok in terminals, especially fancy modern ones with eg mouse support. You can also try mosh to compensate for high latency connections. A lot of the time for Linux the solution is to use ssh and terminal apps as they tend to make smaller updates and require less bandwidth. Very modern apps that use special apis to do lower latency scrolling/resize may be a little better.ģ. Looking at api use from eg X may help with old apps that make small updates but more modern apps (or even modern fonts) which just render to gpu buffers and composite are less amenable to this. There is some trade off of latency for bandwidth: it may take more time to figure out a small change to send over the network. I think the windows server implementation can take advantage of information about the composition of the screen from windows.ġ. I think it does a bunch of raster things (eg maybe caching floating windows like right-click menus). It has eg commands that correspond to scrolling regions of the screen to save on network use, a framerate limit (25fps I think) and allows some colour space reduction to reduce bandwidth too. RDP is not as simple as sending draw commands. However RDP client is built into all Windows versions.0. Also RDP struggles handling complex 3D DirectX type stuff, where as VNC would probably also struggle but more on a performance basis that it couldn't render enough frames to make it worth using. You can't have someone seeing what you have on screen at the server like you can with VNC/remote assistance. I think it's' 3 with win2k3, unless you add extra licenses with terminal services. RDP will limit you to one session if you are using XP Pro/Vista Ultimate or Business. It does however depend on what you are aiming to do, horses for courses etc. If using Vista you can even make Aero work.
#MICROSOFT REMOTE DESKTOP VNC FULL#
It also allows full screen regardless of the different graphics hardware, and screen hardware, so I can have 1650x1024, even though the servers only at 1024x768 etc. It's also easy to have the sound transfered across the RDP, and even printers and devices. If we want files we can just set up a network share. This has the added bonus of a secure connection with the vpn. We have it setup so that we have a VPN connection to the network across the interweb, then RDP to the machine we need. RDP can help you with this by rendering a smaller desktop, and lower colours, and turning animation effects off. We've seen no issues for CPU load or network strain, although you will notice if the connection is very bad no matter what you use. RDP is easilly the best for user experience, with it rendering everything at the client rather than copying everything as the others do, as a result it often does feel like you are using the same machine. Various VNC's, RDP, Windows Remote Assistance, LanDesk etc. I've used a whole bunch of these with work.
0 kommentar(er)
