Hello all! I began working today, where the work is closely related to programming. Despite this, the work computer is set up as Windows (eww). I want to look for work-arounds, as installing linux on a work machine is a no-go.

I wonder, what is the way to minimize pain from having to use windows? Either that, or a way to maximize work done on linux-like stuffs. A linux server is given for us, and I think I can install WSL. Any recommendations on this setup?

Especially, I miss the virtual desktop feature, is there any way to use it? Is there a way I can run compositor through WSL? Also, should I install Pop! OS for the feature, or is it available on e.g. Ubuntu (default WSL)?

Sorry to ask a non-exclusively-linux question, but I think, hopefully, many linux people have experience to give me pointers what to do with a windows work environment.

EDIT: The Windows is Windows 10.

  • Cyborganism@lemmy.ca
    62·
    16 hours ago

    I tried at my job. Basically the IT guys are too incompetent and don’t know how to manage Linux computers.

    But the company had to be able to have control over what users install, they must also have a VPN and proxy set up in a way that they can monitor what employees do or what they browse. They currently use Zscaler.

    • lud@lemm.ee
      1·
      1 hour ago

      Or they are simply overworked like most IT teams.

      Managing Linux devices is more complicated since it was very poor Intune and GPO support so you basically have to have another separate system for that.

      We only have Linux workstations at work because a dev outside IT, setup their own Linux platform and does it support it. IT support won’t help with any problems though.

      The only way Linux workstations are officially supported is that they have certificates for 802.1x.

      If the person that supports the Linux platform quits I’m not sure anyone else could take up the task. The Linux sysadmins might but I doubt they have the time for that.

      A few people also setup their own Linux computers and abused a flaw in the 802.1x. implementation that allowed them to use Ethernet with a username and password instead of a certificate. That is fortunately fixed now.