So after testing quite few windows OS'es in past year or so i came to conclusion that the ones which work smoothest with Anydesk on local connection are 2016, 8.1, 2012-R2, however 2012-R2 and 8.1 will not be getting support for browser updates anymore so i had to move to other version, either 2016 LTSB, 2016 Datacenter server with desktop experience or 2021 LTSC, 2019 server etc... For some strange(to me) reason every single newer version of either server or LTSC Windowses are not smooth while controlling them via Anydesk, performance is laggy and not as smooth as compare to 2016 Datacenter server / LTSB as well as 8.1 and 2012-R2. Maybe it could be DWM or some module inside newer windows versions that makes it much more laggy and less smooth.... If anyone has some idea why and what could be the cause, feel free to share... Also tested slimdown10 with 2021 LTSC IoT. Slimdown10 makes it a bit more smoother than vanilla 2021 LTSC IoT however versions such as 2016, 8.1 and 2012-R2 are still much more smoother while for example dragging anything that has text on it, its more responsive almost like controlling physical machine, however it's just being controlled via Anydesk. I've tested normal windows RDP and it can't really compare to Anydesk since it's still faster and i wonder why... Is this a generally Anydesk issue or just newer versions of Windows are poorly optimized... The way i run my Windows VM's is via bare-metal type1 hypervisor called Proxmox, its basically better version of VirtualBox/Vmware and possibly Hyper-V on Windows due ability to create LXC containers, anyways what matters is that i am not doing GPU passthrough in any of my Windows VM's, for some reason using earlier Windows versions seem to work much better with for example Anydesk since smoothness when you are connected to VM is much better as if you were doing gpu passthrough however after testing newer versions of Windows for some reason the smoothness is not there anymore, it feels laggy and overall poor experience on Windows 11, Windows 10 2021 LTSC IoT, Windows Server 2022 and 2019 compare to 2016/8.1 Windows versions and such which run much better in same environment for some reason. Looking for reasons and perhaps solutions to what could be the thing which causes this sort of "issue" with newer versions of Windows. If anyone has similar experience feel free to share if anyone nerded this topic out. PS: The best way for me to explain this would be like having to do a GPU passthrough for win 11 or so in order to be able to have "smooth" experience while controlling it. While on windows 10 LTSC iot / 1607 i don't actually have to do gpu passthrough and it's smooth as i were to do it.. For some reason.
I've always found working in an RDP environment a better experience than the likes of Anydesk/Teamviewer. The smoothness and clarity replicates being at the machine. That said, RDP is not really applicable when connecting to a client's desktop or laptop.
Why on heart a sane minded person would want to use Teamviewer or other crap like that, locally, when RDP works so well, w/o any need of connecting to questionable third party servers? ???
Exposing RDP's port to the internet isnt good either. Id prefer Teamviewer over that. Alternatively use VPN first
I never said anyone used internet Opening ports like 3389 is never a good idea. I couldve added a slight FYI before
What's supposed to be the problem in using RDP locally? (on a port that isn't necessarily 3389) Perhaps I still have to see a convincing motivation in favor of the Temviewer security over RDP, once you have something that open a door to the outside world you have a weak spot (or a potential weak spot) no matter what you use. Teamviewer's advantage is mainly the ability to access a PC that is behind a NATted network that wouldn't be accessible via traditional methods, but that isn't a problem when you need just to access a VM running in the basement or in the server room.
Well, when you connect to a client’s PC via RDP, you disconnect their session. That’s ok if they don’t mind not seeing what you’re doing or if you’re working on their machine after-hours. RDP is great for server administration and connecting to your own VMs. Connecting via the likes of Teamviewer let’s the client see what you’re doing and allows other interactions via the options in the menu. So, both have their benefits and weaknesses.
There is VNC, if you need such kind of administration. I use RDP and/or VNC when I need to administer something *locally*, depending the actual case, obviously Teamviewwer like things are better options when you need to support a random private client, But that isn't what the OP is doing (If I understand correctly his message). As always happens.
In recent windows, no setting = Hyper-V enabled (which is the opposite of what happened say in LTSB2016) That said you can't suggest blindly to disable H-V, maybe the user use WSL2/WSA an HV VM, or something else. The list becomes longer on each windows release.
Hey, reason why is very simple. RDP is much less smoother, it feels actually feels like it's streaming in 15 or 30 fps while Anydesk is much more smoother. Try changing your refresh rate to 30 or 60 and try moving window or cursor, then switch to 240HZ or however many you have and you will definitely notice difference. There is something special about Anydesk that it performs better from my testings than TeamViewer or RDP for controlling a local VM. Btw Anydesk doesn't use their servers for displaying image, instead it's all on LAN.
Windows defender is totally removed/stripped so it shouldn't be an issue. I've updated my post with a "PS:" i tried to sum it up as easy as i could.
There isn't free launch the aglo-saxons say The video may be smoother, but may come at a price of lack of sync with audio, or at the price of latency with input commands. For now I have yet to see something that is "globally" better than RDP, let alone RemoteFX
As i said, i have tried RDP, it feels like it's "streaming" at low FPS/high latency, while other option such as Anydesk is much faster, it's as i were to have gpu passtru to my VM's while i don't need to do it. I don't use audio however latency with input commands is just as fast. If you mean typing by that. Mind telling me who uses built in RDP for gaming, pretty much no one as it is very slow and latency is high... Anyways each on their own..
Not knowing the capabilities of something and lack of technical merits are two very different things. By your metrics native vhds and deduplication should be considered crap (albeit they are (by far) among the best things MS produced in 30 years), given they are almost unknown even in technical forums like MDL. RemoteFX is (was) another thing that belongs to the above category. It's by far the best way to play a game remotely. Even VMware using its proprietary remote console is not as reactive as RDP with RemoteFX. And I'm not talking of the latest (poorly documented) innovations like GPU Partition, Discrete Device Assignment and so on... In short there isn't the best solution for everything but RDP is, all taken in account, the best compromise.
I will give the thing you mentioned a try, i will try to experiment with it as i think you were up to something. Feels like that Microsoft removed some type of vGPU or proper hardware acceleration on newer versions such as 22H2, while 21H2, Win 8, Server 2016, Win version 1607 work really fine and much smoother than for example Windows 11 or 22H2.. Also Servers, 2019, or server 2022 don't work as smooth, it feels like Microsoft flipped the switch and removed some hardware acceleration stuff that came with earlier windows versions and that makes them feel "laggy" while controlling them with for example Anydesk, if i wanted to have smooth experience with 11 as i do with versions i mentioned above, i'd need to do gpu passtru and i am not going to bother with that, instead i will stick with "older" verisons i mentioned above, until i find solution in meantime. Also another part i forgot, in my testing some Windows versions had a "bug" as soon as i connected to them via Anydesk the Desktop Window Manager[DWM] started using CPU around 20% and controlling the said VM with Anydesk was not as smooth, it was "laggy", dragging windows, and such activities were clearly sluggish, then what i did was i went into task manager, i killed the Desktop Window Manager and it spawned back, but after that it wasn't taking much CPU at all and then only after that i had smooth experience again, so that's kinda weird behavior where upon connecting to a VM i had to quickly restart DWM by killing it, it obviously spawned back, but after that it didn't take much CPU usage at all. And i might be able to record a video in OBS so i could demonstrate that, however the problem is that is very hard to explain it, easiest would be someone to test themselves... Also other versions did not have this "issue" or "bug" if its one. I didn't have to bother and restarting DWM upon connecting to a VM via Anydesk, keep in mind that Anydesk automatically detects that i am on LAN so it doesn't use their servers to do processing. Also i am 98% sure that this isn't hardware issue as some other versions work just as smooth, while for example 11 or 22H2 isn't working as smooth, feels like they dont have proper hardware acceleration and they need GPU passtru, while some other versions on 10 don't need gpu passtru and they work exactly as 11 would work BUT it would require to have GPU passtru.
Clearly they change things under the hood over time. And most of them aren't advertised and/or documented. For example some major changes happened for sure between 1507 and 1511. I remember that on my old microserver I could enable Hyper-V in 1507 w/o any drawback, while doing the same in 1511+ resulted in black screen in WMC and other media players. They changed something again in 1703+ (overlay mixer output result in black screen) They added the OpenGL support to RemoteFX in 1607 They removed the RemoteFX after 19041.868 (and anything else since April 2021 They introduced the ability to run wayland and GUI linux programs in W11, then backported those features in W10. While for the casual user everything still works and looks the same, if you take your time dual booting and comparing the differences becomes evident. It's a moving target, that will never stop moving.