In this Ask the Admin, I’ll show you how to add Windows Server 2016 Technical Preview 4 Nano Server to an Active Directory domain using the Offline Domain Join (djoin) tool.
At the tail end of last year, I showed you how to deploy Nano Server TP4 to an Azure virtual machine in Install Nano Server in Microsoft Azure on the Petri IT Knowledgebase. Since then, Microsoft’s new management portal for Azure, codenamed Ibiza, reached general availability; so I’ll write all future articles relating to Azure using the new portal. For more information on installing VMs using the new portal, see Deploy VMs Using Azure Resource Manager on Petri.
Before starting, it goes without saying that you’ll need a domain controller that your Nano server can communicate with. I’m performing this demo in Microsoft Azure, but your DC could be running in the cloud or an external network connected to Azure using a VPN.
Some days ago I made a blog post about how you can replace diskpart.exe with the new cmdlets in Windows PowerShell v3. Now my next goal was to replace netsh with PowerShell.
Microsoft offers a lot of new cmdlets for networking tasks lets see what we have here. We got a lot of new PowerShell modules which are related to networking.
Now the two modules which sound really interesting are
By now, we’ve all seen the posts and tweets from the IT blogosphere, heralding the arrival of Docker for Windows. Now, to be clear: the ecosystem of Docker tools for Windows is nothing new. Tools such as Boot2Docker, Kitematic, and the Docker Client for Windows have been around for a while, and their collective functionality for Windows has recently been rolled up into Docker Toolbox. While these tools don’t really provide the full, native Docker experience on Windows, they do provide:
- a gateway drug Docker experience for Windows/Mac users, inside a Linux VM.
- the ability to manage a Linux Docker host from a Windows/Mac workstations.
- a means by which software developers, operations engineers, QA, and other IT staff can work with Docker containers idempotently using Windows/Mac workstations.
Until very recently, it was not possible to use a Windows Server platform to host the Docker Engine without adding an additional layer of virtualization. That all changed with the recent release of Windows Server 2016 TP3, which provides a bona-fide Docker daemon running natively on an actual Windows Server host. To many, this is the long awaited missing piece that clears the path to using Docker containers, tools, and workflows in production Windows environments.
Docker Engine for Windows Server requires Windows Server 2016, which is currently only in the Technical Preview 3 release stage. Like most bleeding-edge projects, Docker Engine for Windows Server is still very much in the skunkworks phase. The current set of official documentation is sparse, fragmented, and a bit elusive. In this walkthrough, we will outline the end-to-end steps required to quickly get up and running Docker Engine for Windows Server, from host OS install through your first
docker run command.
In order to complete this walkthrough the following items need to be in place.
- Windows Server 2016 TP3 or later configured with the Windows Server Container Feature. If you have completed the setup guide, this is the VM that was created in Azure or Hyper-V.
- This system must be connected to a network and able to access the internet.
Basic Container Management with Docker
This first example will walk through the basics of creating and removing Windows Server Containers and Windows Server Container Images with Docker.
To begin the walk through, log into your Windows Server Container Host System, you will see a Windows command prompt.
Start a PowerShell session by typing
powershell. You will know that you are in a PowerShell session when the prompt changes from
C:\> powershell Windows PowerShell Copyright (C) 2015 Microsoft Corporation. All rights reserved. PS C:\>
This quick start will be focused on Docker commands however some steps such as managing firewall rules and copying files will be run with PowerShell commands. Work through this walkthrough from a PowerShell session.
Next make sure that your system has a valid IP Address using
ipconfig and take note of this address for later use.
ipconfig Ethernet adapter Ethernet 3: Connection-specific DNS Suffix . : IPv6 Address. . . . . . . . . . . : 2601:600:8f01:84eb::e IPv6 Address. . . . . . . . . . . : 2601:600:8f01:84eb:a8c1:a3e:96b7:ffcb Link-local IPv6 Address . . . . . : fe80::a8c1:a3e:96b7:ffcb%5 IPv4 Address. . . . . . . . . . . : 192.168.1.25
If you are working from an Azure VM instead of using
ipconfig you will need to get the public IP address of the Azure Virtual Machine.