"Well now, this may push administrators to alternate operating systems such as Linux. Not every IT department can afford new server hardware every year. Many IT departments are cash strapped as it is. Now to mandate new hardware when upgrading an operating system is a joke."
I'm not a Windows fan, but no; usually by the time someone considers slapping a new Windows Server version onto an old server, they find out what Windows Server actually costs and decide blowing a license for that kind of money to stick onto a 10-15 year old computer is silly. Also, similar to going from like XP to Vista or 7, let alone 10, usually they find enough increase in system requirements that the old server would also need a hardware upgrade just to do what it's already doing, let alone anything new.
That said, my two cents on this... Cent one... linux does not run into all these problems despite typically not using secure boot OR TPM. Cent two... I think this is snake oil for systems that just download updates whenever they'd like. That said, I do think this is useful for things like slot machines (I've seen one boot up.. it booted a bootloader, which checksum'ed the BIOS, itself, and a second-layer bootloader... the second-layer bootloader looked suspiciously like grub, but first ran a script to verify the first-level bootloader, the kernel, and the ramdisk it was loading; the ramdisk AGAIN checksum'd the kernel, ramdisk, the bootloader, and whatever code it ran after that. The code than ran after that booted into a slot machine software loader, which ran further checks; FINALLY, the slot machine software loaded and began executing.)