Nigger, put this infohash into Tixati (or your favorite modern Torrent client):
66817A94A70EE41BF7B0782CAF5E621F109BE18C
Make sure you get this ISO, exclude the rest to save space or not:
en_windows_server_2016_x64_dvd_9327751.iso
Windows Server 2016 Datacenter because
When it finishes, make sure its SHA256 is:
4caeb24b661fcede81cd90661aec31aa69753bf49a5ac247253dd021bc1b5cbb
If it's anything different, it's not a Microsoft-released ISO for "9327751."
You don't have to get Server 2016 Datacenter. Windows is the same Windows pretty much under the hood between Windows 10 Home up to Server 2016 Datacenter. The difference is a few switches and toggles Microsoft has with the license system, which limits your hardware, concurrent SMB connections, ability to remotely log into your computer WITHOUT kicking your sister/wife off the console, etc.
You can refer to this list for ISO filenames. Also with them are their hashes. So long as your downloaded ISO's hash matches the list, you're not going to pwn yourself in the butt with some cheeky-chink's hyper-malware:
bpaste.net/raw/6ebf157f9873
As for Windows Product Activation, I suggest this:
Stick strictly to Windows Server 20, or Windows *Enterprise Edition* (or Professional). You need to stick with editions which act as KMS clients.
To activate KMS client editions of Windows, seek out a FOSS-licensed KMS emulator called vlmcsd. Make a Hyper-V or VirtualBox VM for the vlmcsd floppy image. Make your router give that MAC the same IP. Google how to add a SRV record for _vlmcs._tcp to your router's DNS (or to your DNS server) that points to this VM. Keep this VM running. Any KMS-activated Microsoft product, be it Office or Windows, will activate against the VM automatically if you configure DNS.
If you can't configure DNS for the automagic, you can use slmgr to set the KMS server in Windows, and ospp.vbs to set it in Office.
Enjoy!