Nano Server is an installation option in Windows Server 2016, offering a tiny footprint, better security and better servicing than Server Core or full Server. Please consult the official [Nano Server documentation](https://technet.microsoft.com/library/mt126167.aspx) for more details and download links for 180 Days evaluation versions.
There are 3 easy ways for you to try out Nano Server, when you sign in with your MS account:
Before proceeding with this tutorial, you will need the [published](../publishing/index.md) output of an existing ASP.NET Core application. Ensure your application is built to run in a **64-bit** process.
[Create a new Virtual Machine using Hyper-V](https://technet.microsoft.com/en-us/library/hh846766.aspx) on your development machine using the previously downloaded VHD. The machine will require you to set an administrator password before logging on. At the VM console, press F11 to set the password before the first log in.
Then you also need to check your new VM's IP address either my checking your DHCP server, fixed IP supplied while provisioning your VM or in Nano Server recovery console's networking settings.
> [!NOTE]
> Let's assume your new VM runs with the local V4 IP address 192.168.1.10.
After running the above commands you should be able to access this share by visiting `\\192.168.1.10\AspNetCoreSampleForNano` in the host machine's Windows Explorer.
Note: This code line is divided by a line breaker escape character that helps reading by wrapping too long lines of code. If you copy-paste it directly
into your Powershell Remoting prompt it may not work as expected. It works fine, though, if you paste it in the Powershell ISE and execute the script or selected lineswith F8.
To quickly verify if IIS is setup correctly, you can visit the url `http://192.168.1.10/` and should see a welcome page. When IIS is installed, by default a web site called `Default Web Site` listening on port 80 is created.
The ASP.NET Core Module is an IIS 7.5+ module which is responsible for process management of ASP.NET Core HTTP listeners and to proxy requests to processes that it manages. At the moment, the process to install the ASP.NET Core Module for IIS is manual. You will need to install the version of the [.NET Core Windows Server Hosting bundle](https://dot.net/) on a regular (not Nano) machine. After installing the bundle on a regular machine, you will need to copy the following files to the file share that we created earlier.
Replace `C:\windows\system32\inetsrv` with `C:\Program Files\IIS Express` on a Windows 10 machine
On the Nano side, you will need to copy the following files from the file share that we created earlier to the valid locations. So, run the following copy commands:
.NET Core must be installed on the target machine. Execute the following Powershell script throughout a remote Powershell session to install the .NET Framework on your Nano Server.
> to understand the differences between Framework-dependent deployments (FDD) and Self-contained deployments (SCD) check
Run the following commands in the remote session to create a new site in IIS for the published app on a different port than the default website. You also need to open that port to access the web.
This script uses the `DefaultAppPool` for simplicity. For more considerations on running under an application pool, see [Application Pools](../publishing/iis.md).
The published web app should be accessible in browser at `http://192.168.1.10:81`. If you have set up logging as described in [Log creation and redirection](../hosting/aspnet-core-module.md#log-redirection), you should be able to view your logs at *C:\PublishedApps\AspNetCoreSampleForNano\logs*.
The published web app should be accessible in browser at `http://<nanoserver-ip-address>:8000`. If you have set up logging as described in [Log creation and redirection](../hosting/aspnet-core-module.md#log-creation-and-redirection), you should be able to view your logs at *C:\PublishedApps\AspNetCoreSampleForNano\logs*.
