In the following steps we install Docker for Windows enterprise on a Windows Server 2019 which is running on a hypervisor platform in this case VMware to run a Linux container in the Datacenter.
When you are on a virtualization platform like Hyper-V or VMware and you have installed de Virtual machine with Microsoft Windows Server 2019 Standard edition, you must make the virtual processors ready for virtualization.
(Nested Virtualization) otherwise you can’t install Hyper-V on VMware.
This is the error you get.
Enable this feature for virtualization to the guest OS for VMware.
Now we have all the prerequisites installed on Microsoft Windows Server 2019, we can begin with Docker for Windows Enterprise via Powershell in Administrators modus :
Now we have Docker EE version 19.03.5 installed for Windows Server 2019.
It’s ready for Windows Containers.
But we want to run linux containers,
Now that we have Docker installed, we need to make some changes to the default configuration to enable support for Linux Containers. This involves setting an Environment variable and creating a docker daemon configuration file.
Microsoft Azure Cloud Services is evolving really fast with New solutions and features every day for your business. In the following step-by-step guide we will see all the options and features when you create a virtual machine in the Azure Cloud. For this you need a Microsoft Azure subscription to start. When you are in the Azure Portal you begin with + Create a Resource and from there you see all the create items. Click on Computeand you will see the picture above what you can create. I’m going to create a Windows Server 2019 datacenter edition Virtual Machine in the Microsoft Azure Cloud. In the Azure Portal is a step by step wizard to help you with your choices.
Basic tab
We start by selecting the right Azure subscription ( if you have Multiple) like a Hub-Spoke model design
you can choose for your deployment. Then select a Resource Group or Create New. I made a new Resource Group called RSG-Winserv.
When you go further down, you must give your Virtual Machine a name and select the Microsoft Azure region where your VM will run. I Choose West Europe because I life in the Netherlands. For availability options of the Virtual Machine you can choose out of three options :
No infrastructure redundancy required
Availability zone
Availability set
Availability Zones is a high-availability offering that protects your applications and data from datacenter failures. Availability Zones are unique physical locations within an Azure region. Each zone is made up of one or more datacenters equipped with independent power, cooling, and networking
An Availability Set is a logical grouping capability that you can use in Azure to ensure that the VM resources you place within it are isolated from each other when they are deployed within an Azure datacenter. Azure ensures that the VMs you place within an Availability Set run across multiple physical servers, compute racks, storage units, and network switches
Microsoft Azure got a lot of software operating images, I installed Windows Server 2019 Datacenter but have a look at Browse all Public and Private images :
Small Disk Images
More images like Kali and Red Hat
The next step is the VM Size, the “hardware” requirements of the Virtual Machine. When you choose your VM size you have to know the possibilities and feature set of the Virtual Machine. This articledescribes the available sizes and options for the Azure virtual machines you can use to run your Windows apps and workloads. It also provides deployment considerations to be aware of when you’re planning to use these resources.
Here is Microsoft Azure showing 250 different VM sizes
In this window you see the following items of the Virtual Machine specs :
VM Size
Offering
Family
vCPUs
Memory RAM
Data Disks
Max IOPS
Temporary Storage
Premium Disks (Yes or No)
Cost / Month Estimated
So pick the right VM Size for your solution to do the job.
Allow Public Internet Inbound Port Rules
If you need this for example a website, then you can set it right away, but you can set it on None and change the Network Security Group (NSG) or Azure App Gateway or Azure Firewall later and keep it Closed for now. I will show this in the NSG later to get RDP access.
Hybrid Benefit
You can enable great savings in Azure with Windows Server Software Assurance by using Azure Hybrid Benefit for Windows Server. Azure Hybrid Benefit for Windows Server allows you to use your on-premises Windows Server licenses and run Windows virtual machines in Microsoft Azure at a reduced cost (i.e. at Linux rates). You can use your licenses for Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, and Windows Server 2016. The Azure Hybrid Benefit for Windows Server is applicable to Windows Server Standard and Datacenter editions as well as other versions obtained via custom images. With Azure Hybrid Benefit for Windows Server, you can save 40 percent or more1 on Windows Server virtual machines by paying only the base compute2 rates—adding value to your Software Assurance investments. The benefit is available across all Azure regions. Read more here
Disks tab
Disk storage is important for performance, that’s why you can choose for Standard HDD, Standard SSD or
Premium SSD for your OS Disk. When your server need a Data disk, you can add it here or later on.
Here you can read more on Managed disks What disk types are available in Azure?
Networking tab
Here you create your Virtual Network / subnet with a public IP. You can see here when you choose for a specific Virtual machine, you can not use accelerated networking because It’s not supported by the VM size selection.
Here you can choose for a Load Balancer or a Application Gateway
Azure Application Gatewayis a web traffic load balancer that enables you to manage traffic to your web applications. Traditional load balancers operate at the transport layer (OSI layer 4 – TCP and UDP) and route traffic based on source IP address and port, to a destination IP address and port.
Azure Application Gateway
With Azure Load Balancer, you can scale your applications and create high availability for your services. Load Balancer supports inbound and outbound scenarios, provides low latency and high throughput, and scales up to millions of flows for all TCP and UDP applications.
Load Balancer distributes new inbound flows that arrive on the Load Balancer’s frontend to backend pool instances, according to rules and health probes.
Additionally, a public Load Balancer can provide outbound connections for virtual machines (VMs) inside your virtual network by translating their private IP addresses to public IP addresses.
Azure Load Balancer is available in two SKUs: Basic and Standard. There are differences in scale, features, and pricing. Any scenario that’s possible with Basic Load Balancer can also be created with Standard Load Balancer, although the approaches might differ slightly. As you learn about Load Balancer, it is important to familiarize yourself with the fundamentals and SKU-specific differences.
Management tab
When you have deployed your virtual machine, you want to manage it like monitoring and backup for example.
You can do these options also after the Virtual Machine deployment.
Backup of the Virtual Machine can be added when you deploy the VM.
I have a existing Backup Vault called WACvault1
From here you can create your own backup recovery Vault with your Own backup policy and retention times.
The feature provides Azure services with an automatically managed identity in Azure AD. You can use the identity to authenticate to any service that supports Azure AD authentication, including Key Vault, without any credentials in your code. What is managed identities for Azure resources?
Advanced tab
In the advanced tab you can select extensions for your Virtual Machine. These are add-ons and will installed during the deployment. You can now also select Gen 2 VM in Preview. Microsoft Azure has a lot of extensions for your Virtual machine :
List of extensions for your VM
Click on Create for adding Microsoft Antimalware on your VM
Select the options and exclusions
Tags tab
Here you can Tag your deployment
After you apply tags, you can retrieve all the resources in your subscription with that tag name and value. Tags enable you to retrieve related resources from different resource groups. This approach is helpful when you need to organize resources for billing or management. Read more on Tags here
At this moment the validation has passed for deployment with all your settings, but don’t forget to have a look at “Download a template for Automation” before you hit Create.
Here you can download or save the JSON ARM Template
When you you go Back and click on Create the Virtual Machine, this will deploy the VM in Minutes.
The following Azure items are deployed in RSG-Winserv
Now your Virtual Machine is deployed in Microsoft Azure Cloud and is running, you can have a look at all the features of the Virtual Machine in the Portal.
To connect to the Virtual Machine you have to Manage access for your RDP session via the NSG in my case:
Double click on the NSG
I added a new rule to give my IP-address access to the VM
From here you can access the Windows Server 2019 Datacenter Virtual Machine in Microsoft Azure Cloud.
Management of your Virtual Machine
When your Azure Virtual Machine with Windows Server 2019 is running, you want to monitor the VM and see what is happening inside the Virtual Machine. Azure Monitor Insights can help you with this.
Health State of the VM
Connections
When Microsoft Azure Monitoring is on and running you want have important alerts on your Mobile by sms or
via E-mail notification to take action.
Alerts on Winserv2019 VM
High CPU Alert
Here we make an Alert about the CPU which is going higher then 80% average.
Making an Action group for email notification of the Alert
Action Group made
Alert made for the VM
Alert details
Alert rule is set and running for this Virtual Machine.
Conclusion
You can create every virtual machine you want for your business, Windows Server or Linux..
You can mange your own performance for the VM on demand by selecting the right VM Size.
You can set Networking and High Availability
You can set Disk Performance for your IOPS
You can configure your management settings and dashboard for Monitoring.
Security can be set on different levels.
Backup of the Virtual Machine can be set with the right policy before deployment.
and more…….
And keep watching your Azure Advisor for better changes :
New Advise will come !
and of course there are more features and options on this Virtual Machine, Have a look :
Azure Service Fabric is a distributed systems platform that makes it easy to package, deploy, and manage scalable and reliable microservices and containers. Service Fabric also addresses the significant challenges in developing and managing cloud native applications. Developers and administrators can avoid complex infrastructure problems and focus on implementing mission-critical, demanding workloads that are scalable, reliable, and manageable. Service Fabric represents the next-generation platform for building and managing these enterprise-class, tier-1, cloud-scale applications running in containers.
In the following Step-by-Step Guide I created a Standalone Microsoft Azure Service Fabric Cluster
on Windows Server 2019 Insiders Preview for DevOps testing :
Several sample cluster configuration files are installed with the setup package. ClusterConfig.Unsecure.DevCluster.json is the simplest cluster configuration: an unsecure, three-node cluster running on a single computer. Other config files describe single or multi-machine clusters secured with X.509 certificates or Windows security. You don’t need to modify any of the default config settings for this tutorial, but look through the config file and get familiar with the settings.
I made the Unsecure three-node Cluster running on Windows Server 2019 Insiders Preview in my MVPLAB.
Open Powershell in Administrator modus and run the Script :
Service Fabric Explorer (SFX) is an open-source tool for inspecting and managing Azure Service Fabric clusters. Service Fabric Explorer is a desktop application for Windows, macOS and Linux.
I Installed Azure Service Fabric Explorer to visualize the Cluster.
Here we got Azure Service Fabric 3-Node Cluster running on Windows Server 2019 Insiders
Azure Service Fabric CLI
The Azure Service Fabric command-line interface (CLI) is a command-line utility for interacting with and managing Service Fabric entities. The Service Fabric CLI can be used with either Windows or Linux clusters. The Service Fabric CLI runs on any platform where Python is supported.
Prior to installation, make sure your environment has both Python and pip installed. The CLI supports Python versions 2.7, 3.5, 3.6, and 3.7. Python 3.x is the recommended version, since Python 2.7 will reach end of support soon.
Check the Python version and the Pip version by typing :
python –version
Pip –version
The Pip version which is delivered via Python has to be updated with the following command :
python -m pip install –upgrade pip
We now have pip version 18.0 instead of 10.0.1
Installing Service Fabric CLI by command :
pip install -I sfctl
Done ! Service Fabric CLI is installed on my Windows 10 Surface.
sfctl -h
Now we have installed Microsoft Azure Service Fabric Cluster on Windows Server 2019 Insiders Preview and the Service Fabric CLI on Windows 10, we now can connect to the 3-node Fabric Cluster via CLI.
Because we are working under Windows 10 and not on the host itself we have to set an endpoint connection :
Microsoft Visual Studio 2017 Enterprise and Service Fabric SDK
As a Developer or DevOps you like to work from Microsoft Visual Studio to deploy your Apps, Microservices or Containers to the Azure Service Fabric Cluster.
You need to install the Service Fabric SDK in Visual Studio before you can deploy :
Select Service Fabric Application at New Project
Visual Studio 2017 Enterprise : Service Fabric SDK must be installed
Installing Microsoft Azure Service Fabric SDK
Done.
Now you can make your Service Fabric Container.
Happy Developing 😉
More information on Microsoft Azure Service Fabric Cluster :
Windows Insider Program for Server allows you deploy the Windows Server 2019 Insider Preview builds in your enterprise. The docs cover the new enterprise features we’d like you to test and describes how to do the most common tasks.
To allow the Windows Admin Center gateway to communicate with Azure to leverage Azure Active Directory authentication for gateway access, or to create Azure resources on your behalf (for example, to protect VMs managed in Windows Admin Center using Azure Site Recovery), you will need to first register your Windows Admin Center gateway with Azure. You only need to do this once for your Windows Admin Center gateway – the setting is preserved when you update your gateway to a newer version.
In the following Step-by-Step Guide you will connect Windows Admin Center to your Microsoft Azure Subscription.
From here you have to copy the device Code and hit the Link device login ( https://aka.ms/devicelogin )
This will make the connection between Windows Admin Center and your Azure Subscription.
Paste the Code into here and Click on Continue.
Sign in your Azure Subscription.
From here you are connected to your Azure Subscription.
Select the right Azure Tenant and Click on Register.
Go to the Azure AD App Registration link.
Click on Settings
Click on Required Permissions and then on Grant permissions
Click on Yes.
Windows Admin Center has now Permission.
Microsoft Windows Admin Center (WAC) Gateway is now registered to your Azure Subscription and you can use Azure AD Multi-Factor Authentication and Azure Site Recovery to protect your Virtual Machines with WAC.
IMPORTANT : Before you can add Microsoft Azure VM’s to Windows Admin Center, you have to set the Azure Network Firewall portal settings and also the Microsoft Windows OS Firewall of the VM.
Networking Settings of the Azure VM.
Open for http WAC port 5985 and for https 5986.
To make the port more Secure you have these Options in the Firewall rule.
Now you have done this for Azure Networking in the portal, you have to do the same in the Firewall settings of the Virtual Machine Inside.
Join Microsoft Windows Server Summit on June 26, 2018
Join Microsoft on Tuesday, June 26, 2018 for a virtual experience to learn tips and tricks for modernizing your infrastructure and applications—regardless of whether you’re running Windows Server on-premises or in the cloud.