Windows – Bootable Windows Server 2016 USB Drive

You could try the following, I've not got a nano server to try it out on. Drop the select if it gets you something else and see if what you want is stored under a different property in Server 2016 Nano

Get-CIMInstance -ClassName Win32_OperatingSystem -Property * | select caption

When tested on a real Nano instance the -session parameter was not needed, but if you need it at some future date, here's the variant with -session:

$cuser = "Your username"
$cservername = "Your Servername"
$csession = New-CimSession –Credential $cuser –ComputerName $cservername
Get-CIMInstance –session $csession -ClassName Win32_OperatingSystem -Property * | select caption

You cannot easily do that; even if you manage to create a bootable USB loading the kernel and the initrd, the initrd parameters are going to still require network assets. from your example

append initrd=kernel/init.gz root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns=10.10.10.5 storage=10.10.10.211:/imaging/images/ driversstorage=10.10.10.211:/imaging/drivers/ imaging_server=10.10.10.211:20444 symmetric_key=KsqRwghBK+l/LGQ83kOp3Gl8Xos9mrTItQ69MJabgAv5DqcKakVCwNpE4QJ+A9zzDoSAhdREIVK4lkUZP67XXg loglevel=4a

init.gz takes as parameter ip=dhcp telling the booting executive to get its IP by DHCP, next it loads storage=10.10.10.211:/imaging/images/ telling the booting executive that the rest of the boot/install components are stored on a network location, etc etc.

As you can see trying to do what you want requires editing your initrd parameters (Distro dependent) and removing all the network references; not a trivial task that can be made just by a canned utility.