It's just such a weird concept to me, to make a budget server, an all-in-one multi capable machine. A server handles requests from outside the machine. These machines should be run headless. So doing it from windows just makes no sense whatsoever. You build multiple machines with multiple upgrade paths for about the same money. Get out of your comfort space and use the right operating system for the task. FTP serving on windows was never a great idea because it's far to resource intensive. A four year old system of midrange parts as a file server will be able to handle more requests than a one year old windows system of midrange parts. Build a NAS, use an RPi3B as the intermediary between file management and the interior network. Build a video enc/dec beast, run this machine in windows if you want for software familiarity. Network the NAS to the media server, and let the RPi run the FTP daemon headless. Doing it all from one system is just asking for bottlenecks, especially since NTFS is a shitty filesystem for high bandwidth applications, like file serving and caching whatever video content.
So things that come into play, are your network configuration skills. If someone doesn't like doing network setup(the non-automated kind) they almost never want to build the LAN itself.
Then the other would be command line interfacing to reduce the amount of graphics power needed for luxuries, thus going headless. If someone does not like the idea of eliminating the mouse, and needing elaborate menus, etc, then you need the computational power to drive the GUI, all which add cost, power, and maintenance. You could setup in a live environment, and save configs, then go headless.
Or I'm just getting trolled. Like someone asking how to make a good fishing helicopter for $10k that needs to seat 10 people and not scare all the fish off when hovering over the lake.
40-60% performance increases on the same hardware for most of your criteria is worthy of some persistence.
