REMOTEPC FORUMS WINDOWS 10
REMOTEPC FORUMS LICENSE
REMOTEPC FORUMS SERIES
REMOTEPC FORUMS WINDOWS

Upon further thought, I think that the difference in the CPU load has to do with the fact that VNC offloads the render to the GPU on the slave machine, whereas with RDP it is rendered on the local machine. I understand (from a high level) the differences in the protocols VNC/RDP.

REMOTEPC FORUMS WINDOWS

I'm measuring the CPU and NIC on the slave Windows machine. Going to keep looking at some other options and I will report back. Perhaps RDP is built to utilize max bandwidth? Given the much higher overhead of RDP on the NIC card is probably reason enough to stay away from it. I know the protocols work in quite different ways. So, given all of this it would make sense that RDP has a more responsive feel, because it is basically rendering a higher frame rate.

REMOTEPC FORUMS WINDOWS 10

MacPro (VNC/RDP client) connected via 1Gbps Ethernet to Windows 10 (VNC/RDP server).ĬPU usage max at 10% and Ethernet traffic spikes to about 25 Mbps.ĬPU usage max at 15% and Ethernet traffic spikes to 160 Mbps. Note that this was just my specific scenario, and your mileage may vary.

REMOTEPC FORUMS SERIES

Here are a series of tests I performed, comparing the performance of both protocols (RDP vs. RDP is actually a resource hog compared to VNC (at least, in my case). So, after some tests I'm going to contradict myself. 'The RDP protocol just seems more efficient.' VNC or teamviewer are other alternatives instead of MS Remote Desktop, but I find them both appaling to use, so I just keep using MS Remote Desktop, but granted I have not spent hours and hours working that way and if I started to have any graphics related problems I would definitely switch to VNC. I haven't experienced that yet and not sure what might be going on there, but that seems solvable with some windows OS configuration, of which I am not expert enough to give advice, sorry. I don't know why you're having the local adminstrator account permissions problems. that doesn't mean that there might not be some obscure OpenGL scenario with MirPro causing a problem. But I did run some OpenGL benchmarking tools on this slave and didn't have any problem.

REMOTEPC FORUMS LICENSE

I would need to move my MirPro license over to this slave in order to test that, so I can't vouche for what MirPro is or isn't doing. I have only run into a few glitches with it, and it wasn't neccessarily OpenGL giving me problems, it was Plogue Bidule as a plugin inside VePro. I also much prefer MS Remote Desktop and use it whenever possible. See this thread for more information about Remote Desktop alternatvie: Otherwise, what are the preferred remote login applications (VNC, others?) which aren't clunky and glitchy and provide a responsive display/UI experience?

Has anyone had any luck addressing this issue? Is it related to permissions or something else not fixable? I've also added this user as a member of the 'Remote Desktop Connection' group.

The thing that isn't making sense to me is that the user I'm logging in with is indeed a local Administrator on the machine, with Administrator permissions. With that said, I still get the annoying error message starting VEPro Server 64 and behavior of getting booted out of the RDP connection because VEPro Server 64 requires a 'local Administrator account'. The screen/resolution scales appropriately and it is nearly as responsive as a local desktop, which is really important if you are monitoring quick articulation changes through VEPro. I find that Microsoft Remote Desktop works much better for connecting from a Mac/Master to a Windows/Slave than other things that I've tried.

Remotepc forums