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 ! 😉
Use the Cool TechDays app 2016 for all the information and sessions of this Awesome Event :
There will be Great Speakers to Join and Corey Sanders will do the Keynote and Cool sessions about Microsoft Azure.
Here you find all the great TechDays 2016 Sessions
Hope to Meet you all at Microsoft TechDays 2016 in Amsterdam 😉
Dive in to Windows 10 with award-winning journalist and Windows Expert Ed Bott in this highly curated free eBook covering the top apps, accessories, and utilities included in the box with Windows 10.
The sheer volume of Windows programs and accessories says a lot about the power and complexity of Windows—a fact that every IT pro knows from firsthand experience. There’s a tool for nearly every task, and a large part of the process of becoming a Windows expert is knowing how to find the appropriate one when you need it.
This eBook contains descriptions and hands-on advice to help IT Pros work faster and smarter. Some of these tools are for everybody—end users and experts alike—whereas some are strictly for professionals. A few are so specialized that you’ll only need them once in a blue moon. Collectively, though, they make up a toolbox that can save you (and your company) time and money.
Thank you Ed Bott for this Awesome E-book 😉
Dell Power Edge R710 Server for Microsoft AzureStack TP1 POC
These requirements apply to the Azure Stack POC only and might change for future releases.
|Compute: CPU||Dual-Socket: 12 Physical Cores||Dual-Socket: 16 Physical Cores|
|Compute: Memory||96 GB RAM||128 GB RAM|
|Compute: BIOS||Hyper-V Enabled (with SLAT support)||Hyper-V Enabled (with SLAT support)|
|Network: NIC||Windows Server 2012 R2 Certification required for NIC; no specialized features required||Windows Server 2012 R2 Certification required for NIC; no specialized features required|
|Disk drives: Operating System||1 OS disk with minimum of 200 GB available for system partition (SSD or HDD)||1 OS disk with minimum of 200 GB available for system partition (SSD or HDD)|
|Disk drives: General Azure Stack POC Data||4 disks. Each disk provides a minimum of 140 GB of capacity (SSD or HDD).||4 disks. Each disk provides a minimum of 250 GB of capacity.|
|HW logo certification||Certified for Windows Server 2012 R2||Certified for Windows Server 2012 R2|
Data disk drive configuration: All data drives must be of the same type (SAS or SATA) and capacity. If SAS disk drives are used, the disk drives must be attached via a single path (no MPIO, multi-path support is provided)
HBA configuration options: 1. (Preferred) Simple HBA 2. RAID HBA – Adapter must be configured in “pass through” mode 3. RAID HBA – Disks should be configured as Single-Disk, RAID-0
Supported bus and media type combinations
Deploy Azure Stack POC
This creates the \Microsoft Azure Stack POC\ folder containing the following items:
Important: You must have at least 128GB of free space on the physical boot volume.
bcdboot <mounted drive letter>:\windows
Important: Only one NIC is allowed during the deployment process. If you want to use a specific NIC, you must disable all the others.
Run the PowerShell deployment script
Deployment starts and the Azure Stack POC domain name is hardcoded as azurestack.local.
There are two ways to log in to the Azure Stack POC.
Log in as a service administrator
A service administrator manages resource providers, tenant offers, plans, services, quotas, and pricing.
Log in as a tenant
Tenants provision, monitor, and manage services that they subscribe to, like Web Apps, storage, and virtual machines. A service administrator can log in as a tenant to test the plans, offers, and subscriptions that their tenants might use. If you don’t already have one, Create a tenant account before you log in.
RDP may restrict how many users can access the physical Microsoft Azure POC host. To enable multiple users, see Enable multiple concurrent user connections.
Windows Containers on Hyper-V NanoServer nested Virtualization
The container feature can be installed on Windows Server 2016, or Windows Server 2016 Core, using Windows Server Manager or PowerShell.
To install the role using PowerShell, run the following command in an elevated PowerShell session.
PS C:\> Install-WindowsFeature containers
The system needs to be rebooted when the container role installation has completed.
PS C:\> shutdown /r
After the system has rebooted, use the
Get-ContainerHost command to verify that the container role has successfully been installed:
PS C:\> Get-ContainerHost
Deploying Nano Server involves creating a prepared virtual hard drive, which includes the Nano Server operating system, and additional feature packages. This guide quickly details preparing a Nano Server virtual hard drive, which can be used for Windows Containers.
For more information on Nano Server, and to explore different Nano Server deployment options, see the Nano Server Documentation.
Create a folder named
PS C:\> New-Item -ItemType Directory c:\nano
Convert-WindowsImage.ps1 files from the Nano Server folder, on the Windows Server Media. Copy these to
#Set path to Windows Server 2016 Media PS C:\> $WindowsMedia = "C:\Users\Administrator\Downloads\WindowsServerTP4" PS C:\> Copy-Item $WindowsMedia\NanoServer\Convert-WindowsImage.ps1 c:\nano PS C:\> Copy-Item $WindowsMedia\NanoServer\NanoServerImageGenerator.psm1 c:\nano
Run the following to create a Nano Server virtual hard drive. The
–Containers parameter indicates that the container package will be installed, and the
–Compute parameter takes care of the Hyper-V package. Hyper-V is only required if Hyper-V containers will be created.
PS C:\> Import-Module C:\nano\NanoServerImageGenerator.psm1 PS C:\> New-NanoServerImage -MediaPath $WindowsMedia -BasePath c:\nano -TargetPath C:\nano\NanoContainer.vhdx -MaxSize 10GB -GuestDrivers -ReverseForwarders -Compute -Containers
When completed, create a virtual machine from the
NanoContainer.vhdx file. This virtual machine will be running the Nano Server OS, with optional packages.
If the container host itself will be running on a Hyper-V virtual machine, and will also be hosting Hyper-V Containers, nested virtualization needs to be enabled. This can be completed with the following PowerShell command.
The virtual machines must be turned off when running this command.
PS C:\> Set-VMProcessor -VMName <container host vm> -ExposeVirtualizationExtensions $true
If the container host itself will be running on a Hyper-V virtual machine, and will also be hosting Hyper-V Containers, the virtual machine will require at least two processors. This can be configured through the settings of the virtual machine, or with the following PowerShell script.
PS C:\> Set-VMProcessor –VMName <VM Name> -Count 2
If Hyper-V Containers will be deployed, the Hyper-V role needs to be enabled on the container host. If the container host is a virtual machine, ensure that nested virtualization has been enabled. The Hyper-V role can be installed on Windows Server 2016 or Windows Server 2016 Core using the following PowerShell command.
PS C:\> Install-WindowsFeature hyper-v
Each container needs to be attached to a virtual switch in order to communicate over a network. A virtual switch is created with the
New-VMSwitch command. Containers support a virtual switch with type
This example creates a virtual switch with the name “Virtual Switch”, a type of NAT, and Nat Subnet of 172.16.0.0/12.
PS C:\> New-VMSwitch -Name "Virtual Switch" -SwitchType NAT -NATSubnetAddress 172.16.0.0/12
In addition to creating a virtual switch, if the switch type is NAT, a NAT object needs to be created. This is completed using the
New-NetNat command. This example creates a NAT object, with the name
ContainerNat, and an address prefix that matches the NAT subnet assigned to the container switch.
PS C:\> New-NetNat -Name ContainerNat -InternalIPInterfaceAddressPrefix "172.16.0.0/12" Name : ContainerNat ExternalIPInterfaceAddressPrefix : InternalIPInterfaceAddressPrefix : 172.16.0.0/12 IcmpQueryTimeout : 30 TcpEstablishedConnectionTimeout : 1800 TcpTransientConnectionTimeout : 120 TcpFilteringBehavior : AddressDependentFiltering UdpFilteringBehavior : AddressDependentFiltering UdpIdleSessionTimeout : 120 UdpInboundRefresh : False Store : Local Active : True
Finally, if the container host is running inside of a Hyper-V virtual machine, MAC spoofing must be enable. This allows each container to receive an IP Address. To enable MAC address spoofing, run the following command on the Hyper-V host. The VMName property will be the name of the container host.
PS C:\> Get-VMNetworkAdapter -VMName <contianer host vm> | Set-VMNetworkAdapter -MacAddressSpoofing On
An OS image is used as the base to any Windows Server or Hyper-V container. The image is used to deploy a container, which can then be modified, and captured into a new container image. OS images have been created with both Windows Server Core and Nano Server as the underlying operating system.
Container OS images can be found and installed using the ContainerProvider PowerShell module. Before using this module, it needs to be installed. The following commands can be used to install the module.
PS C:\> Install-PackageProvider ContainerProvider -Force
Return a list of images from PowerShell OneGet package manager:
PS C:\> Find-ContainerImage Name Version Description ---- ------- ----------- NanoServer 10.0.10586.0 Container OS Image of Windows Server 2016 Techn... WindowsServerCore 10.0.10586.0 Container OS Image of Windows Server 2016 Techn...
To download and install the Nano Server base OS image, run the following.
PS C:\> Install-ContainerImage -Name NanoServer -Version 10.0.10586.0 Downloaded in 0 hours, 0 minutes, 10 seconds.
Likewise, this command downloads and installs the Windows Server Core base OS image.
Issue: Save-ContainerImage and Install-ContainerImage cmdlets fail to work with a WindowsServerCore container image, from a remote PowerShell session.
Workaround: Logon to the machine using Remote Desktop and use Save-ContainerImage cmdlet directly.
PS C:\> Install-ContainerImage -Name WindowsServerCore -Version 10.0.10586.0 Downloaded in 0 hours, 2 minutes, 28 seconds.
Verify that the images have been installed using the
PS C:\> Get-ContainerImage Name Publisher Version IsOSImage ---- --------- ------- --------- NanoServer CN=Microsoft 10.0.10586.0 True WindowsServerCore CN=Microsoft 10.0.10586.0 True
For more information on Container management See Windows Containers Documentation