Windows Server 2016 will be released the next month said Microsoft the last month. Windows Server 2016 brings a lot of new features compared to the last Windows Server version for Hyper-V, networking and storage. In this topic I will try to convince you to move from prior Windows Server edition to Windows Server 2016 with eight reasons.
New Server Management Tools (SMT) suite now on supports Windows Server 2012 and Windows Server 2012 R2, as it has been recently announced by Microsoft.
SMT includes a collection of well-known tools, such as Task Manager, Registry Editor, Event Viewer, Device Manager and Control Panel. Windows Update has been also added to that list few months ago. The difference is that now these tools actually are services housed in Microsoft’s Azure datacenters. Organizations must set up an on-premises gateway (which is called “server management gateway” by Microsoft) in order to use them.
“All SMT tools, except Windows Update and Device Manager, will now work with Windows Server 2012 R2 and 2012,”- Microsoft.
Microsoft Azure provides a way to deploy Azure VM from the Marketplace or from a generalized image. When you deploy the Azure VM from the Marketplace, no customization is deployed. You have to configure the operating system as your master. When you have several Azure VMs to deploy, the customization of each system can be time consuming. A lot of companies have a master or a baseline image in a VMDK for VMWare, in a VHD(X) for Hyper-V or in a WIM image. In this topic we will see how to create a generalized image from a single Azure VM and how to deploy Azure VM from this generalized image.
In the old portal (https://manage.windowsazure.com), all steps can be done from the GUI but also by using PowerShell. In the new portal (https://portal.azure.com), you have to use PowerShell because it is not yet integrated to the portal. In this topic, I will work from the new portal (AzureRM).
As we know, VMware‘s first attempt in the field of hyperconvergence, the EVO:RAIL, was a good quality software product set, which nevertheless failed because of the licensing policy. Specifically, it demanded that buyers acquire new vSphere licences, with no exception for existing vSphere users who liked the idea of adopting hyperconverged infrastructure.
Microsoft has created its own edition of FreeBSD 10.3 in order to make the OS available and supported in Azure.
As Jason Anderson, principal PM manager at Microsoft’s Open Source Technology Center says, “Redmond took on the work of building, testing, releasing and maintaining the image” so it could “ensure our customers have an enterprise SLA for their FreeBSD VMs running in Azure”.
From December 2015, Microsoft has given the possibility to create your own RBAC roles. I will show you today, how to do this. To start, connect via PowerShell to your Azure RM subscription:
In part two of this multi part blog series, we covered the creation and configuration of a GitHub account, to host a GitHub repository for a Quick Start template, and then we examined Visual Studio Code integration with Git and lastly we pushed commits to a remote repository on GitHub.
In the final post, we will modify and deploy sample and custom template and parameter JSON files.
If you missed Part I and Part II, please make sure to check them here Part I and Part II before you continue with the last part.
(more…)
In part one of this multi part blog series, we explained the benefits of Azure Resource Manager and resource groups in Azure V2 versus the Service Management API in Azure V1, then we looked in depth at JavaScript Object Notation (JSON) Quick Start templates. In the second part, Part II: we will create and configure a GitHub account, if you don’t already have one, to host a GitHub repository for a Quick Start template, and lastly we will examine Visual Studio Code integration with Git and push commits to a remote repository. In the final post, we will modify and deploy sample/custom template and parameter JSON files.
If you missed Part I, please make sure to check it here before you continue with this post.
Applications that are deployed in Microsoft Azure often comprise different but related cloud resources, such as virtual machines, web applications, SQL databases, virtual networks among others. Before the introduction of Azure Resource Manager (Azure V2), it was necessary to define and provision these resources imperatively. However, Azure Resource Manager gives you the ability to define and provision these resources with their configuration and associated parameters declaratively in a JavaScript Object Notation (JSON) template file, known as an Azure Resource Manager template.
In this series of three blog posts, we will show you how to create and deploy Infrastructure as a Service (IaaS) applications using Azure Resource Manager templates.
In this guide, we will explain the benefits of Azure Resource Manager and resource groups, then we will examine and analyze a number of Quick Start Azure Resource Manager templates that are available on GitHub. In the next post, we will create and configure a GitHub account, if you don’t already have one, to host a GitHub repository for a Quick Start template, and lastly we will examine Visual Studio Code integration with Git and push commits to a remote repository.
(more…)
