The printers require AD authentication to print but no prompt? Is Kerberos setup correctly for CUPS?

Checking Mangajikan website... Redirecting to a .cc domain... And... its back lol

Mundane tasks weren't really the focus. This was a debate between Redhat and the Linux old guard where the points were all based on the extremes. They follow different ideas on how tools should work, though. Init systems focus on doing one or few things but doing them very well (the traditional UNIX approach). Systemd is a suite of many moving parts to accomplish a whole range of tasks (more modern). Init is mostly just bootstrap and services, but systemd is that plus networking, plus user sessions, plus logging, etc etc. More moving parts means increased complexity and more chance for failure. Systemd as a suite then becomes a potential single point failure where init based systems would not be. Scripting for either can be involved, but generally speaking init is/was easier to write things for.

I think most users today focus on Redhat's control and not putting too much faith in one setup for diversity's sake rather than the other points, but the original debate really was a philosophically based one. There isn't a right or wrong on these, but some really interesting history.

I think for those people it boils down to systemd being an init system that does more than an init system maybe should. Combine that with it being more complicated to work with and with Redhat not really being that open to feedback.

Honestly, most of your selling points while completely valid don't matter in this case I think. The problem is that is a repair business doing work for non-technical people and those are technical selling points. For example, my wife is allergic to tech. She wouldn't care about dual-booting or telemetry. She just wants the simplest possible solution that she doesn't have to think about. She's bored having to listen to me talk about projects/work and while she has to have a PC for daily life, that doesn't mean she wants to have to have it. She just needs it and needs it to be easy.

The biggest selling points to her would be:

1. It just works
2. She doesn't have to relearn things (meaning the layout and where to click on things)
3. It runs her stuff (literally all browser based applications)
4. Her files and pictures are there

That's it. I think the biggest positive sell to repair shop users would be "its just like Windows". They don't need it to be better, they just need it to be the same.

"Will not connect to the internet" is probably too vague to troubleshoot. Isolate exactly what part is failing. Is the device receiving an IP address? Are you able to ping anything on the local network? Are you able to ping a remote IP address? If you aren't receiving an IP address, is DHCP running? Can you statically set your IP and ping out? Is there another switchport you can try on the router?