Having spent a little time with this issue myself recently, I just want to throw in the suggestion that the native Windows Remote Desktop Connection is an absolute hog of CPU resources. It's fine for low load use, but turns into a system killer quickly without much additional load.
I had been using it myself for the last couple of months, but having recently added just 8MP of additional cameras to my system, real time viewing load via RDC started to consistently hit close to 100% whereas it was only about 70-80% before. Running as just a service, the CPU load was previously just shy of 30% and now sits around 37% with the added cameras without the RDC active. (Yes, the live view load can be cut drastically by keeping the default 5s update period for the RDC, but where's the fun in that?)
Although it does not provide the same screen real estate, I have since started using the Chrome Remote Desktop, and it has far less impact, running at an average of 45% load with unthrottled live viewing. All of the same things, providing full admin control of BI, can still be done short of maximizing the display for higher resolution monitors.