locked
When to use Nano, Hyper-V, or Container for a Role? RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    I've been doing alot of reading about the changes Windows Server 2016 brings.  Currently we use 2008r2.

    But for as much googling and searching as I've done, whenever I search for "when to use nano for a server role" or similar efforts, I just keep getting results that explain the basic differences between containers and hyper-v containers and so on.

    What I really want to learn now is - how BEST do you use these? In our current structure for example, our file server is in a HyperV-VM. That VM also acts as a DNS server. Another VM hosts our Remote Desktop Service for remote users. And a third VM hosts another DNS and a WSUS server.

    So with 2016, should we change this up to place the DNS into a nano server? A Hyper-V container? How much more work is it to manage a DNS server, with a dozen or so manual entries in the zone for internal needs, using the command line tools versus the GUI we've been so used to?

    Can WSUS be run in a container? Or should it remain in a full Hyper-V machine?

    And what about a file server?

    These be questions keeping me up at night.. how to best deploy roles with these new container options.

    Wednesday, January 18, 2017 3:11 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Here's what I would do:

    Print Server = Server Core running on a Hyper-V VM

    RDS = Server Core running on a Hyper-V VM

    Windows Backup Service = Full GUI running on a Hyper-V VM

    Nano server can only be managed from a remote PowerShell or WinRm session. If you have an Azure subscription, you can also use Server Management Tools. This requires installing a 'gateway' on your network and some other configuration. 

    It's always good to learn something new :) 

    Check out the Microsoft Virtual Academy for courses on PowerShell and PowerShell DSC. These will help you not only with Nano Server, but managing Microsoft services in general. 

    Let me know if I can help with anything else.

    Cheers,

    Ryan

    Microsoft Server Engineer

    Blog:   Twitter:   LinkedIn:   

    Please remember to mark the replies as answers if they help.

    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

    • Marked as answer by JH1962 Wednesday, February 1, 2017 9:56 PM
    Thursday, January 19, 2017 2:37 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Nano server is a scaled back version of a standard Windows Server. It has a considerably smaller footprint, requires less patches, and less reboots. Only certain roles can be hosted on Nano server. These include DNS, IIS, Hyper-V, Scale Out File Server (different from a standard file server), and cloud application servers. You can also host containers on a Nano Server. To answer one of your questions; yes, you can host DNS in a Nano Server. 

    You can find more info on Nano Server here:

    https://technet.microsoft.com/en-us/windows-server-docs/get-started/getting-started-with-nano-server

    Containers are a bit different. You can imagine them as buckets on your desktop. Each bucket can host an application. But the buckets are isolated from one another. They are basically servers that are designed for one purpose. As a result, they are extremely small. 

    Standard containers share a kernel with the host operating system and all other containers on the host. Hyper-V containers have their own kernel.

    Docker is required to work with containers on Windows Server. You need to install the Containers role and the Docker daemon. Once you do this, you can create container images and apply packages to them. Packages are things like roles and applications. 

    I personally think managing DNS records with PowerShell is very easy. You can find information on the DNS Server cmdlets here:

    https://technet.microsoft.com/en-us/library/jj649850.aspx

    WSUS should not be run in a container, containers are not designed for this purpose. I would continue to run it in a full Hyper-V VM. Though, I would install the WSUS role on a Server Core installation, rather than a full GUI installation. 

    You can install the File Server role on Nano Server, though I personally have never done this. I did quick Google search and found this article. Hopefully it helps.

    http://www.ntweekly.com/?p=13722

    Let me know if I can answer any other questions. 

    Cheers,

    Ryan

    Microsoft Server Engineer

    Blog:   Twitter:   LinkedIn:   

    Please remember to mark the replies as answers if they help.

    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

    • Proposed as answer by Ryan Nemeth Thursday, January 19, 2017 2:06 AM
    Wednesday, January 18, 2017 3:28 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thank you for your reply Ryan.

    Perhaps I can further refine my question here with a specific list of roles, and then I'll be able to read more on how each would be achieved.

    Nano-possible roles:
    DNS, and using powershell cmdlets to manage/change settings/add and remove entries as per your note
    File Server potentially as per your thoughts

    Hyper-VM suited:
    WSUS

    Where would these roles best fit under?
    Print Server
    Remote Desktop Services (I'd assume a Hyper V but..)
    Windows Backup Service (which has other questions.. but not for here today)

    We use DFS to replicate files to multiple sites (5). Does anyone out there reading this post have comment on how manageable that remains if the file server is installed under a Nano approach? Yes... yes I have been a GUI-leaning slave. My command line work has typically been reserved to batch and simple powershell tools, troubleshooting connectivity issues, etc., not server management tasks. But I'm willing to learn that approach.

    Thanks again for the clarifications thus far.

    Thursday, January 19, 2017 2:30 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Here's what I would do:

    Print Server = Server Core running on a Hyper-V VM

    RDS = Server Core running on a Hyper-V VM

    Windows Backup Service = Full GUI running on a Hyper-V VM

    Nano server can only be managed from a remote PowerShell or WinRm session. If you have an Azure subscription, you can also use Server Management Tools. This requires installing a 'gateway' on your network and some other configuration. 

    It's always good to learn something new :) 

    Check out the Microsoft Virtual Academy for courses on PowerShell and PowerShell DSC. These will help you not only with Nano Server, but managing Microsoft services in general. 

    Let me know if I can help with anything else.

    Cheers,

    Ryan

    Microsoft Server Engineer

    Blog:   Twitter:   LinkedIn:   

    Please remember to mark the replies as answers if they help.

    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

    • Marked as answer by JH1962 Wednesday, February 1, 2017 9:56 PM
    Thursday, January 19, 2017 2:37 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,
    Are there any updates?
    You could mark the reply as answer if it is helpful.
    Best Regards,
    Leo

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, January 27, 2017 2:47 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Actually.. as I re-read this, to be clear... when you say

    "Print Server = Server Core running on a Hyper-V VM"

    Do you mean...

    Install Server 2016 baseline/host.

    Deploy a Hyper-V VM

    Deploy inside that VM, Server Core

    Inside the server core, install the Print Server role?

    That doesn't seem right.. like it would be many extra layers?

    Wednesday, February 1, 2017 9:59 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Actually.. as I re-read this, to be clear... when you say

    "Print Server = Server Core running on a Hyper-V VM"

    Do you mean...

    Install Server 2016 baseline/host.

    Deploy a Hyper-V VM

    Deploy inside that VM, Server Core

    Inside the server core, install the Print Server role?

    That doesn't seem right.. like it would be many extra layers?

    Yes, that is exactly what I am saying. Create a virtual server running Server Core, and install the Print Server role on it. 

    Cheers,

    Ryan

    Microsoft Server Engineer

    Blog:   Twitter:   LinkedIn:   

    Please remember to mark the replies as answers if they help.

    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

    Thursday, February 2, 2017 1:16 AM