@Martin9700 "Which seems odd if you're trying to do automation and NOT spend tons of money. So many things you can do with PowerShell! We have 2 dedicated servers at my work that ALL they do is run PowerShell scripts (maybe 1 old VBS)!"
Not really. Group Policy handles almost all the automation I need. Windows is a wrapper for some legacy applications, that's about it. I don't need Windows to do much except "not crash".
99.95% of my "automation" is done on Linux systems. The overwhelming majority of that automation is pulling various kinds of information from various systems, translating, then injecting. For example, pulling an HTML report from one server, stripping out the useful information and then translating that to XML, which we then inject via API into another system.
I do virtually all of that work with PHP and shell scripts. All the rest of the automation I require is VMware-based, and most of htat is handled by actual applications (like Veeam).
For me at least, Windows is a legacy platform. It's something I'm forced to use, not something I choose to use. When and where there is a specific need to mount up a Windows application, I will. Outside of that, everything I run goes on Linux. The licensing is just easier.