I'm just tired. On the last post about having Linux at our work, many people that seems to be an IT worker said there have been several issues with Linux that was not easy to manipulate or control like they do with Windows, but I think they just are lazy to find out ways to provide this support. Because Google forces all their workers to use Linux, and they have pretty much control on their OS as any other Windows system.
Linux is a valid system that can be used for work, just as many other companies do.
So my point is, the excuse of "Linux is not ready for workplaces" could be just a lack of knowledge of the IT team and/or a lack of intention to provide to developers the right tools to work.
Is there something I'm missing? Teamviewer is available for Linux and I've done remote support with it: https://www.teamviewer.com/en/download/linux/
I...assume it also works as the machine being remoted into?
Ah, I see. I only used it once, so it's not something I do often, but it worked perfectly for me as a client to a Windows computer.
I would probably go with VNC or something else instead of Teamviewer for supporting Linux desktops remotely. Maybe set people up with a pointy-clicky script to do a reverse SSH tunnel to a central host, or do it over a VPN connection.
Yeah, I'm not sure what the state of the art is these days. Maybe SPICE? I've used that to control VMs through tunneled SSH before.