yeah but from a University IT Admin standpoint NixOS would just be so much easier to maintain and set up. you literally would just need one config file to slap on all the machines. Install the OS, clone the config, rebuild, walk away and go to the next computer. Program causing issues and needs to be removed? cool edit the config, push it to the repo, clone it to all the machines, rebuild.
Install the OS, clone the config, rebuild, walk away and go to the next computer.
Honestly, I’d automate it to be even fewer operations. The Windows process is already down to only four keystrokes, and three of them are just to boot into PXE. The fourth is just a pause to make sure every computer has booted into Clonezilla (Debian preloaded with the cloning software and my own scripts, pulled from a TFTP server) before they start pulling the Windows image and the network becomes saturated.
yeah but from a University IT Admin standpoint NixOS would just be so much easier to maintain and set up. you literally would just need one config file to slap on all the machines. Install the OS, clone the config, rebuild, walk away and go to the next computer. Program causing issues and needs to be removed? cool edit the config, push it to the repo, clone it to all the machines, rebuild.
I don’t know of any organization using it though
Don’t reinvent the wheel. Ansible is well proven and works on many systems.
You also could use Fog
You would just be cloning the 1 install anyway.
Honestly, I’d automate it to be even fewer operations. The Windows process is already down to only four keystrokes, and three of them are just to boot into PXE. The fourth is just a pause to make sure every computer has booted into Clonezilla (Debian preloaded with the cloning software and my own scripts, pulled from a TFTP server) before they start pulling the Windows image and the network becomes saturated.