Visual artifacts in Desktop connection mode on Windows 7 SP1 (with\without Aero) and Windows Server 2008 R2.

[tersion]

I've tested Desktop connection mode on several real PC's and VM's, which runs Windows 7 SP1 (with\without Aero) or Windows Server 2008 R2 (Classic theme) installed on them and experienced visual artifacts this kind: This happens while web browsing or moving windows which breaks all user experience and done any kind of remote work almost impossible. I've tested this with latest avaliable version (0.8.79) of MeshCentral with default configuration on my LAN network and also using your Public server. In both cases result the same - visual artifacts is present. BUT on one PC which run Windows 10 (2004 version) all FINE. No any of those artifacts, moving windows is smooth and nice. I suppose MeshAgent desktop grabbing algorithm optimized for more recent version of WDDM? Or I missing some server setup options in config.json?

[Ylianst]

Is this the MeshAgent or MeshCentral Assistant doing the remote desktop? This sort of thing has been reported for MeshCentral Assistant and I need to look into it.

[VINISHVV]

@Ylianst - The picture showing mesh agent is running.

[Ylianst]

It looks like the browser is "skipping" images and so, you don't see all the images and it leads to the screen above. Can you indicate what browser you are using? Do you have desktop multiplexor enabled on the server? Also, if you open the browser's console, do you see any errors?

Lastly, if you reduce the quality of the remote desktop, do you still see these problems?

[tersion]

Ylianst, this is MeshAgent (not Assistant). Here the link to the video where I demonstrate visual difference between Windows 10 and Windows Server 2008: https://drive.google.com/file/d/19YRRxD4pln-IGYjDQMYLFJzQ3vFvCHT5/view?usp=sharing For this video I use your public MeshCentral server, but in my LAN setup with latest available version result the same. About Desktop Multiplex - when I wrote my first message about this problem, I don't use this function. After enabling it nothing change - still the same visual artifacts. In browser console log no errors at all. I've tested in Firefox (89.0.2) and Chrome (91.0.4472.164). As I mentioned earlier, using the same agent on remote side with Windows 10 and the same browser on local side - all FINE, but when using Windows 7 or Windows Server 2008 R2 - there're visual problems.

[Ylianst]

Oh wow. Thank you for the video and details. This is very interesting and something Bryan needs to look at.

[Ylianst]

Working on adding more test devices to the MeshCentral test fleet. Added a Windows 7 Home Basic and Ubuntu 16.10. So far, I have not seen the artifacts, but I will keep adding more devices.

[tersion]

Ylianst, I've done some more tests and found out that if I install MeshAgent in a Service mode, then NO visual artifacts. But if I run agent in a temporary mode, then visual artifacts still appears. I've noticed, that when MeshAgent installs in a Service mode, several firewall rules was added for inbound TCP\UDP ports: 16990, 16991. For some minutes I was sure that problem was in lack of those rules. But after adding the same rules for another MeshAgent .exe-file which I run in temporary mode, doesn't fix issue. And MORE - if I delete all added by MeshAgent Service firewall rules, restart MeshAgent Service, connect in a Desktop mode - NO visual artifacts. So MeshAgent in a Service mode with or without TCP\UDP firewall rules works fine, without any noticeable visual artifacts. BUT in my scenario I need work with MeshAgent in temporary mode, so issue is still need to be fix. And last notice - visual artifacts still related only for Windows 7\Server 2008 R2. On my test machine with Windows 10 (2004) and with running MeshAgent in a temporary mode, without any firewall rules for inbound connection works fine. It's all very strange.