I got through University running Debian testing.
It was mostly fine, some Linux based subjects were way easier without dealing with a VM (they recommended against WSL for some reason).
However there were a couple units that absolutely required you to use Visual Studio (non-code), I occasionally used a VM, the Uni IT also provided me with a remote VM (there's a form to fill and and it's all automated). But I mostly used Rider, which for one unit it confused their CI and I got marked down for (otherwise got top marks so it's fine).
For office, it didn't matter. Group projects mostly used Google Docs, occasionally Microsoft Office where the online version worked fine. All my units wanted PDFs at the end anyway, so it does not matter that you used LibreOffice or whatever. Some units provided you with DOCX templates, I had no issues opening them with LibreOffice.
Edit: People are mentioning online exams, my Uni did 'online quizzes' which worked fine, and some had to be done in class on their PCs anyway. Final exams where always done on paper.
Ahh sorry, I thought you meant you plugged it into the input side. If that's the case then are you running anything that measures CPU usage? I run the TIG stack, it might be able to give you some hits. Also back to my original point which is already unlikely, if it's a modified sinewave UPS, it can confuse some measuring devices while it's on battery.
It's weird to do this daily, but it's possible that the UPS is doing a self test, which would drain the battery a little and the load is from charging it back up.
I never mentioned vulnerabilities, I just wanted to point out that, RDP doesn't really work without a graphical session, Windows Server Core gets around this by being a graphical session (although very basic).
Also I'm not sure, but I don't think Windows handles RDP on the kernel level, it's just nicely tied in with DWM and doesn't have to deal with the multitude of window managers on Linux.
Handling RDP on the kernel level does sound like a bad idea security wise, but there should be a better way.
Windows Server Core still has a window manager, just all it does show a command prompt very similar to the one in the usual Windows recovery environment.
Unless you are moving gigabits of data, you won't notice the difference the smaller header payload of ipv6 offers.
IPv6 headers are usually bigger anyway1, so the only advantage is more efficient routing (so infinitesimally better latency), but in my experience most routers only support IPv4 hw offload and not IPv6, so it's only more efficient in theory.
I just like IPv6 because I get a whole /56 prefix to play with, and devices often randomise their host portion through the privacy extensions, meaning they use a new address each day or so.
1 IPv4 is usually ~20 bytes, but it can be up to 60 bytes if you stack a lot of options, IPv6 is only 40 bytes AFAIK.
It seems like it's fixed now, but if possible use one of the mirrors, so everyone's not hitting that one server all that hard, it's usually faster too.
You can try
ignore_resource_conflictwhich is it87 specific, rather than a system wideacpi_enforce_resources.modprobe it87 force_id=0x8628 ignore_resource_conflict=1The reason why this is needed is ACPI claims the I/O ports required to talk to the it87, and Linux doesn't want to override that.