cscript c:\windows\system32\slmgr.vbs /upk cscript c:\windows\system32\slmgr.vbs /cpky slmgr /ckms slmgr /ipk VK7JG-NPHTM-C97JM-9MPGT-3V66T
cscript c:\windows\system32\slmgr.vbs -skmskms1.kms.sjsu.edu cscript c:\windows\system32\slmgr.vbs -ato
You can just follow the instructions provided in the AWS official guide. Those apply for any Windows server installation, including on-premise and not using AWS in general.
[Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters] AllowInsecureGuestAuth:1
enable_background.reg
Windows Registry Editor Version 5.00 [-HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\System] "DisableLogonBackgroundImage"=dword:00000001
disable_background.reg
Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\System] "DisableLogonBackgroundImage"=dword:00000001
It's not a really known feature but Windows support symbolic links! Yes, not the way you are used on *nix, for example symlinks on remote shares are not supported.
There's not a native way to make a symlink anyway you can use junction tool.
> junction "link" "real_destination"
> mklink /D "link" "real_destination"