Happy Learning with your online LAB
Jeff Woolsey in action Talking about Windows Server 2016 Security and Containers
Thanks Jeff Great Sessions !
#MVPbuzz Time with Ask Me Anything (AMA) sessions at the Microsoft Tech Summit 2017
Great questions and feedback on Microsoft :
Windows Server 2016
Operations Management Suite (OMS)
Microsoft Tech Summit 2017 Amsterdam Dutch MVP’s at the Booth
Build your cloud and infrastructure skills with a two-day free technical training event
Here you can see in which cities the Microsoft Tech Summit 2017 is
Thank you Microsoft and Community for these Awesome two Cloud and Infrastructure Days in Amsterdam ! 😉
Gain hands-on experience with the new version of Windows Server in security, software-defined datacenter and containers, using the latest virtual labs.
Guided labs make it easy to check out what’s new without spending time and money to install and configure an environment. Using the virtual labs for Windows Server 2016 you can learn about what the new technology does and how to configure it. It’s not a video, a demo you watch, or a simulator; it’s you connecting with your browser, on your PC, to our lab for free.
When you sign in with your Microsoft account you’ll be able to access any of the individual labs in a private, sandboxed environment. It all adds up to about 6 hours of content, and you can come back later if you need to.
Check out each of these 60-minute experiences:
Example of TechNet Virtual LAB Managing Windows Server 2016 :
Virtual LAB information before you begin 😉
JUST push Launch Lab to begin.
Let the Virtual LAB Windows Server 2016 Nano Server Begin 😉
Microsoft MAP Toolkit 9.6
The Microsoft Assessment and Planning Toolkit (MAP) is an agentless, automated, multi-product planning and assessment tool for quicker and easier desktop, server and cloud migrations. MAP provides detailed readiness assessment reports and executive proposals with extensive hardware and software information, and actionable recommendations to help organizations accelerate their IT infrastructure planning process, and gather more detail on assets that reside within their current environment. MAP also provides server utilization data for Hyper-V server virtualization planning; identifying server placements, and performing virtualization candidate assessments. More information about MAP Toolkit can you find here
Export results in Excel for Windows Server 2016 Assessment Example
Microsoft Azure Virtual Machine Sizing Example in Excel
With MAP Toolkit Training available 😉
Build your cloud and infrastructure skills with a two-day free technical training event March 23-24, 2017.
More information about the Microsoft Tech Summit 2017 Amsterdam and Registration you can find here
Here you find more cities for Microsoft Tech Summit 2017 Event when you are not from the Netherlands.
Hope to meet you in Amsterdam 😉 #MVPbuzz
What are Containers
Basically, a container is an isolated place where an application can run without affecting the rest of the system and without the system affecting the application. Containers are the next evolution in virtualization.
If you were inside a container, it would look very much like you were inside a freshly installed physical computer or a virtual machine. And, to Docker, a Windows Server Container can be managed in the same way as any other container.
Windows Container Types
Windows Server Containers – provide application isolation through process and namespace isolation technology. A Windows Server container shares a kernel with the container host and all containers running on the host.
Hyper-V Containers – expand on the isolation provided by Windows Server Containers by running each container in a highly optimized virtual machine. In this configuration the kernel of the container host is not shared with the Hyper-V Containers.
When you begin working with containers you will notice many similarities between a container and a virtual machine. A container runs an operating system, has a file system and can be accessed over a network just as if it was a physical or virtual computer system. That said, the technology and concepts behind containers are very different from that of virtual machines.
Container Host: Physical or Virtual computer system configured with the Windows Container feature. The container host will run one or more Windows Containers.
Container Image: As modifications are made to a containers file system or registry, such as with software installation they are captured in a sandbox. In many cases you may want to capture this state such that new containers can be created that inherit these changes. That’s what an image is – once the container has stopped you can either discard that sandbox or you can convert it into a new container image. For example, let’s imagine that you have deployed a container from the Windows Server Core OS image. You then install MySQL into this container. Creating a new image from this container would act as a deployable version of the container. This image would only contain the changes made (MySQL), however would work as a layer on top of the Container OS Image.
Sandbox: Once a container has been started, all write actions such as file system modifications, registry modifications or software installations are captured in this ‘sandbox’ layer.
Container OS Image: Containers are deployed from images. The container OS image is the first layer in potentially many image layers that make up a container. This image provides the operating system environment. A Container OS Image is Immutable, it cannot be modified.
Container Repository: Each time a container image is created the container image and its dependencies are stored in a local repository. These images can be reused many times on the container host. The container images can also be stored in a public or private registry such as DockerHub so that they can be used across many different container host.
You have to install these Windows Server 2016 Rolls and Feature first before you start with Containers :
My Windows 2016 Server Build version.
Here is an example on my Windows 2016 Server to get started with Windows Containers :
Install-Module -Name DockerMsftProvider -Repository PSGallery -Force
Install-Package -Name docker -ProviderName DockerMsftProvider
Here we pull out of the Docker Hub the Microsoft Nanoserver Container.
Downloading the Image.
Automatically extract the image.
Docker run -i -t microsoft/nanoserver
( you will see the container with Nanoserver is running)
Inside the container.
Running Powershell inside the container.
Containers for Developers
From a developer’s desktop to a testing machine to a set of production machines, a Docker image can be created that will deploy identically across any environment in seconds. This story has created a massive and growing ecosystem of applications packaged in Docker containers, with DockerHub, the public containerized-application registry that Docker maintains, currently publishing more than 180,000 applications in the public community repository.
When you containerize an app, only the app and the components needed to run the app are combined into an “image”. Containers are then created from this image as you need them. You can also use an image as a baseline to create another image, making image creation even faster. Multiple containers can share the same image, which means containers start very quickly and use fewer resources. For example, you can use containers to spin up light-weight and portable app components – or ‘micro-services’ – for distributed apps and quickly scale each service separately.
Because the container has everything it needs to run your application, they are very portable and can run on any machine that is running Windows Server 2016. You can create and test containers locally, then deploy that same container image to your company’s private cloud, public cloud or service provider. The natural agility of Containers supports modern app development patterns in large scale, virtualized and cloud environments.
With containers, developers can build an app in any language. These apps are completely portable and can run anywhere – laptop, desktop, server, private cloud, public cloud or service provider – without any code changes.
Containers helps developers build and ship higher-quality applications, faster.
Containers for IT Pro’s
IT Professionals can use containers to provide standardized environments for their development, QA, and production teams. They no longer have to worry about complex installation and configuration steps. By using containers, systems administrators abstract away differences in OS installations and underlying infrastructure. Containers help admins create an infrastructure that is simpler to update and maintain
Lot of Success with Containers and Nanoserver
An integrated, easy-to-deploy environment for building, assembling, and shipping applications from a Windows PC, Docker for Windows is a native Windows application with a native user interface and auto-update capability, deeply integrated with Windows native virtualization, Hyper-V, networking and file system, making it faster and more reliable than previous ways of getting Docker on a Windows PC
Before you install Docker for Windows 10 make sure you have the right Windows 10 version.
The current version of Docker for Windows runs on 64bit Windows 10 Pro, Enterprise and Education (1511 November update, Build 10586 or later).
And have the Hyper-V feature of Windows 10 installed. Here you can download Docker for Windows 10
Click on Install.
Click Finish and Launch Docker
The Docker VM
Now you can work from Powershell with Docker Containers :
There is also a graphical GUI called Kitematic with the Docker Hub connection for the Container marketplace.
This will download Kitematic.
Kitematic with recommended Docker Containers to download 😉
If you search for Azure you find a lot of Azure related Docker Containers.
It’s so easy to download a container from the Docker Hub and make it running on your Windows 10 Machine, here is an example of an Jenkins Container:
It’s downloading the Docker Container Image.
Jenkins is already running in the Docker Container and is
asking some questions for the setup.
Jenkins is setting up the environment.
And now we have Jenkins in a Container running.
Here you can find more information about Jenkins
And with Kitematic you can see the log of the Jenkins Container
Here you can start, restart or stop the Docker Containers.
Here I did a Docker Inspect Jenkins to see settings of the Container.
Hope this blogpost is useful to play with Docker Containers on your Windows 10 device 😉
When you want to learn more about Microsoft Windows Containers you can start here :
When you want to learn more about Microsoft Azure Container Services you can start here :
Lot of Success with running Containers !