As discussed in the previous section, most of the Windows PowerShell cmdlets that you are familiar with can establish a remote connectivity and manage a Nano Server instance.
The usage for Nano is different, depending on if it's virtualized or not. Nano as a VM is meant to be just an engine; it might live for 10 seconds or 10 days, it is just a part of a huge application platform (the purpose is to execute apps on servers). But when running Nano on a physical machine, it is basically a cloud infrastructure (Hyper-V, storage, clustering) and nothing else. Nano is double-edged with dual purpose.
Nano Server was designed for high density deployment. Imagine trying to manage 1,000 Nano Servers using GUI-based tools. These tools might be fine for managing a relatively small number of servers, but are simply not practical for managing large-scale deployments. Nano Server is not really meant to be managed by a domain when running virtualized, it is designed...