The pinboard for cheat sheets.
Over the years I've used VNC, or Teamviewer, and just connected to the machine and controlled the keyboard and mouse. Teamviewer is nice because it works through the internet and you don't have to worry about SSH'ing in first or a VPN or anything(which you'd need to tunnel VNC through SSH, or use a VPN for it to be secure if not on the local network - don't open normal VNC traffic to the internet). It's not nice because it will quickly flag you as not being 'personal use' if you have a lot of computers. It also seems to work somewhat inconsistently connecting to Windows machines(any time a UAC prompt comes up I have to refresh it a bunch / change the graphics quality back and forth or I get a black screen). VNC works inconsistently for me on Linux, a lot of times it loses connectivity and won't work again until the VNC server is restarted or the machine is. I'm not sure if maybe it's because of the high CPU usage running BOINC projects. The other issue with either is if you do not have a monitor attached on boot up it's almost unbearably slow(like 10+ seconds in between clicks). I've used HDMI dummy plugs to get around that.
Some options that I can think of-
I know X11 forwarding is an option to launch a Linux desktop from a remote machine but I've never used it. I'm not sure if that's a viable option or the pros/cons.
Using SSH and doing everything through command line is an option, but not one I'm necessarily wanting to do, but with being able to run BOINC Manager or BOINC tasks on another machine might not be terrible. I did setup BOINC Tasks for the first time yesterday and it's pretty great. I should have set that up way sooner.
For Windows machines that don't have GPU's Windows RDP is hard to beat. It's fast, it sets the screen resolution to match the client machine, etc. I only have one machine running Windows without a GPU crunching, though, and it's about to be 0, so this isn't viable.
I'm not looking to reinvent the wheel, so I thought you guys may have some suggestions on this. I appreciate the input!
I now use AnyDesk. So far it works just as good as TeamViewer. My only gripe with it is the only way to have an "address book" stored of your rigs is to pay for it. However, as long as you write down (I took pictures of all the rigs on my phone, so I can pull them up remotely with my phone) the numbers you can connect anywhere including over the Internet.
Although once you connect once it usually saves those instances in recent sessions, but I'm not sure how long they remain "recent" and if they will drop out.
When setting them up make sure you set a password on each host to allow unattended access. Otherwise, you'll have to physically be on the remote computer to accept the connection.
I haven't spent a ton of time looking into it but I find this pretty interesting - https://pikvm.org/ IP KVM switches are incredibly expensive compared to a Raspberry Pi and some other basic hardware, I probably wouldn't put it on all machines since it would be fairly cost prohibitive, but there are a few machines where hooking up a monitor to them would be a pretty big pain so it would be nice to have. Almost none of my computers are server motherboards with IPMI or anything like that.
I forgot to mention that Chome Remote Desktop has worked really well for me between Windows machines, or even from a Linux box to a Windows machine, but have not had good luck getting into a Linux box with it. It's so good that on my Milkyway Windows PCs, that's all I install.
I don't have any dummy plugs on any of my remote machines and they all work just fine. I've only used a monitor on them to initially set them up, but once I did that nothing is plugged into the GPUs.
Also, you can edit the cc_config and app_config files through BOINCTasks.
Just go to the project list column. Select the project you want to edit. Then click Extra > Edit config file (app_config.xml) and a window will pop up allowing you to edit the app_config file.
Do the same thing for the cc_config, but you only need to select the host in the host column.
It doesn't seem to affect all machines, but especially ones that are Intel onboard video with no other video card run absolutely awful through Teamviewer if they are not booted up with a monitor attached. Like unbearably slow, 10-20 seconds between mouse clicks, etc. slow. In addition, you get a tiny little desktop window since the screen resolution goes to 640x480 or whatever with no monitor attached. These make it appear that there is a 1080p monitor(or whatever resolution the dummy plug is) so that it gets a normal desktop.
On linux, without it you can run xrandr --fb 1280x720 (or whatever you want the resolution to be) from a terminal and it overrides it even with no monitor, you just have to disconnect and reconnect teamviewer. I only use the dummy plugs on machines that run poorly without them, which is mostly but not exclusively Intel onboard video ones.
...I was wrong on that. I do run one system with HD Graphics. I was just checking to make sure my next statement was correct in that you can change the resolution with AnyDesk even if a monitor isn't attached. That's when I realized it's actually running on the Intel HD graphics. Default it runs 1280x800 (or something similar) but I was able to change the resolution to 1920x1200 within' AnyDesk (just changed the settings in Windows using AnyDesk) and it gave me a much bigger window to work with.
I do not experience any slow down with AnyDesk when connected to it.
Also note I am running the CPU at 100% on one project and Collatz on the Intel HD graphics.
Connecting to a Linux machine with Teamviewer without the dummy plugs is where I really see terrible performance, when it does have the issue. Some machines seem to be fine without it. The dummy plugs are a cheap solution at least. You can even make one pretty easily with a DVI to VGA adapter and some resisters, if your machine has DVI - https://rumorscity.com/2013/12/06/how-t ... ics-cards/
The rig I tested it on was running Windows 10, but I'm pretty sure it works on my Windows 7 PC with discrete graphics cards. It runs headless and I have to remote into it often to add new content to Plex. 1080p is the resolution it connects with.
I only use SSH for Linux. I dislike Linux's GUI desktops.