October 2021 Update

README.md

@@ -6,11 +6,10 @@ Welcome to the Azure Stack HCI 20H2 Evaluation Guide
 
 In this guide, we'll walk you experiencing a number of the amazing capabilities within [Azure Stack HCI 20H2](https://azure.microsoft.com/en-us/products/azure-stack/hci/ "link to the Azure Stack HCI 20H2 landing page"), and set the foundation for you to explore in your own time.  You'll cover aspects such as:
 
-* Deploying Azure Stack HCI 20H2 nodes
-* Deploying supporting management infrastructure, including Active Directory domain and management tooling
-* Building a Hyperconverged cluster using Windows Admin Center, including configuring a cloud witness
+* Building a hyperconverged Azure Stack HCI cluster using Windows Admin Center
+* Configuring a cloud witness
 * Registering Azure Stack HCI 20H2 with Azure
-* and more...!
+* Creating storage volumes and deploying a VM
 
 Contents
 -----------
@@ -18,7 +17,12 @@ Contents
 - [Contents](#contents)
 - [What is Azure Stack HCI 20H2?](#what-is-azure-stack-hci-20h2)
 - [Why follow this guide?](#why-follow-this-guide)
-- [Start your Azure Stack HCI 20H2 evaluation using nested virtualization](#start-your-azure-stack-hci-20h2-evaluation-using-nested-virtualization)
+- [Interested in AKS on Azure Stack HCI?](#interested-in-aks-on-azure-stack-hci)
+- [Evaluating in Azure](#evaluating-in-azure)
+- [Nested Virtualization](#nested-virtualization)
+- [Deployment of Azure Stack HCI 20H2 nested in Azure](#deployment-of-azure-stack-hci-20h2-nested-in-azure)
+- [Deployment Workflow](#deployment-workflow)
+- [Get started](#get-started)
 - [Product improvements](#product-improvements)
 - [Raising issues](#raising-issues)
 - [Contributions & Legal](#contributions--legal)
@@ -35,25 +39,66 @@ If you're interested in learning more about what Azure Stack HCI 20H2 is, make s
 Why follow this guide?
 -----------
 
-This evaluation guide will walk you through standing up a sandboxed, isolated Azure Stack HCI 20H2 environment using **nested virtualization**, and can run on a **single physical system**, such as a workstation, laptop, or server of you have one, or alternatively, you can run the whole configuration in Azure.  We'll go into more details for this path, shortly.
-
-The important takeaway here is, by following this guide, you'll lay down a solid foundation on to which you can explore additional Azure Stack HCI 20H2 scenarios in the future, so keep checking back for additional scenarios over time.
+This evaluation guide will walk you through standing up a sandboxed, isolated Azure Stack HCI 20H2 environment using **nested virtualization** in a **single Azure VM**. The important takeaway here is, by following this guide, you'll lay down a solid foundation on to which you can explore additional Azure Stack HCI 20H2 scenarios in the future, so keep checking back for additional scenarios over time.
 
 Interested in AKS on Azure Stack HCI?
 -----------
 If you're interested in evaluating AKS on Azure Stack HCI (AKS-HCI), and you're planning to evaluate all the solutions using nested virtualization in Azure, it's certainly tempting to run AKS-HCI on top of an Azure Stack HCI 20H2 nested cluster in an Azure VM, however we **strongly discourage** this approach due to the performance impact of multiple layers of nested virtualization. The recommended approach to test AKS-HCI in an Azure VM using [the official AKS on Azure Stack HCI eval guide](https://aka.ms/aks-hci-evalonazure "AKS on Azure Stack HCI eval guide").
 
-Start your Azure Stack HCI 20H2 evaluation using nested virtualization
+Evaluating in Azure
 -----------
 
-If you have a single physical system, which could be a laptop, desktop, or server, or you have no spare hardware at all, using **nested virtualization** would be a great approach to experiencing Azure Stack HCI 20H2.  You can get more details at the start of the nested path.
+As with any infrastructure technology, in order to test, validate and evaluate the technology, there's typically a requirement for hardware. If you're fortunate enough to have multiple server-class pieces of hardware going spare (ideally hardware validated for Azure Stack HCI 20H2, found on our [Azure Stack HCI 20H2 Catalog](https://aka.ms/azurestackhcicatalog "Azure Stack HCI 20H2 Catalog")), you can certainly perform a more real-world evaluation of Azure Stack HCI 20H2.
 
-![Nested path image](/media/nested.png "Nested virtualization path image")
+For the purpose of this evaluation guide however, we'll be relying on **nested virtualization** to allow us to consolidate a full lab infrastructure, down **onto a single Hyper-V host inside an Azure VM**.
 
-[**Evaluate Azure Stack HCI 20H2 using Nested Virtualization**](/nested/README.md "Evaluate Azure Stack HCI 20H2 using Nested Virtualization")
+*************************
 
 ### Important Note - Production Deployments ###
-The use of nested virtualization in this evaluation guide is aimed at providing flexibility for deploying Azure Stack HCI 20H2 in a lab, or test environment. For **production** use, **Azure Stack HCI 20H2 should be deployed on validated physical hardware**, of which you can find a vast array of choices on the [Azure Stack HCI 20H2 Catalog](https://aka.ms/azurestackhcicatalog "Azure Stack HCI 20H2 Catalog").
+The use of nested virtualization in this evaluation guide is aimed at providing flexibility for evaluating Azure Stack HCI 20H2. For **production** use, **Azure Stack HCI 20H2 should be deployed on validated physical hardware**, of which you can find a vast array of choices on the [Azure Stack HCI 20H2 Catalog](https://aka.ms/azurestackhcicatalog "Azure Stack HCI 20H2 Catalog").
+
+*************************
+
+Nested Virtualization
+-----------
+If you're not familiar with Nested Virtualization, at a high level, it allows a virtualization platform, such as Hyper-V, or VMware ESXi, to run virtual machines that, within those virtual machines, run a virtualization platform. It may be easier to think about this in an architectural view.
+
+![Nested virtualization architecture](/deployment/media/nested_virt.png "Nested virtualization architecture")
+
+As you can see from the graphic, at the base layer, you have your physical hardware, onto which you install a hypervisor. In this case, for our example, we're using Windows Server 2019 with the Hyper-V role enabled.  The hypervisor on the lowest level is considered L0 or the level 0 hypervisor.  On that physical host, you create a virtual machine, and into that virtual machine, you deploy an OS that itself, has a hypervisor enabled.  In this example, that 1st Virtualized Layer is running a **nested** Azure Stack HCI 20H2 operating system. This would be an L1 or level 1 hypervisor.  Finally, in our example, inside the Azure Stack HCI 20H2 OS, you create a virtual machine to run a workload.  This could in fact also contain a hypervisor, which would be known as the L2 or level 2 hypervisor, and so the process continues, with multiple levels of nested virtualization possible.
+
+The use of nested virtualization opens up amazing opportunities for building complex scenarios on significantly reduced hardware footprints, however it shouldn't be seen as a substitute for real-world deployments, performance and scale testing etc.
+
+Deployment of Azure Stack HCI 20H2 nested in Azure
+-----------
+For those of you who don't have multiple server-class pieces of hardware to test a full hyperconverged solution, this evaluation guide will detail using **nested virtualization** in Azure to evaluate Azure Stack HCI.
+
+![Architecture diagram for Azure Stack HCI 20H2 nested in Azure](/deployment/media/nested_virt_arch_ga_oct21.png "Architecture diagram for Azure Stack HCI 20H2 nested in Azure")
+
+In this configuration, you'll take advantage of the nested virtualization support provided within certain Azure VM sizes.  You'll deploy a single Azure VM running Windows Server 2019 to act as your main Hyper-V host - and through PowerShell DSC, this will be automatically configured with the relevant roles and features needed for this guide. It will also download all required binaries, and deploy 2 Azure Stack HCI 20H2 nodes, ready for clustering.
+
+To reiterate, the whole configuration will run **inside the single Azure VM**.
+
+Deployment Workflow
+-----------
+
+This guide will walk you through deploying a sandboxed infrastructure - the general flow will be as follows:
+
+**Part 1 - Complete the pre-requisites - deploy your Azure VM**: In this step, you'll create a VM in Azure using an Azure Resource Manager template. This VM will run Windows Server 2019 Datacenter, with the full desktop experience. PowerShell DSC will automatically configure this VM with the appropriate roles and features, download the necessary binaries, and configure 2 Azure Stack HCI 20H2 nodes, ready for clustering.
+
+**Part 2 - Configure your Azure Stack HCI 20H2 Cluster**: In this step, you'll use Windows Admin Center to deploy an Azure Stack HCI 20H2 cluster - along with a Cloud Witness, a Cluster Shared Volume, and finally, you'll register this cluster with Azure.
+
+**Part 3 - Integrate Azure Stack HCI 20H2 with Azure**: In this step, you'll use Windows Admin Center to register your Azure Stack HCI Cluster with Azure and explore what's presented in the portal
+
+**Part 4 - Explore the management of your Azure Stack HCI 20H2 environment**: With your deployment completed, you're now ready to explore many of the management aspects within the Windows Admin Center.
+
+Get started
+-----------
+
+* [**Part 1** - Complete the prerequisites - deploy your Azure VM](/steps/1_DeployAzureVM.md "Complete the prerequisites - deploy your Azure VM")
+* [**Part 2** - Configure your Azure Stack HCI 20H2 Cluster](/steps/2_DeployAzSHCI.md "Configure your Azure Stack HCI 20H2 Cluster")
+* [**Part 3** - Integrate Azure Stack HCI 20H2 with Azure](/steps/3_AzSHCIIntegration.md "Integrate Azure Stack HCI 20H2 with Azure")
+* [**Part 4** - Explore Azure Stack HCI Management](/steps/4_ExploreAzSHCI.md "Explore Azure Stack HCI Management")
 
 Product improvements
 -----------
@@ -85,4 +130,4 @@ Microsoft, Windows, Microsoft Azure and/or other Microsoft products and services
 
 Privacy information can be found at https://privacy.microsoft.com/en-us/
 
-Microsoft and any contributors reserve all other rights, whether under their respective copyrights, patents, or trademarks, whether by implication, estoppel or otherwise.
+Microsoft and any contributors reserve all other rights, whether under their respective copyrights, patents, or trademarks, whether by implication, estoppel or otherwise.

archive/README.md

@@ -1,6 +1,21 @@
 Evaluate Azure Stack HCI 20H2 using Nested Virtualization
 ==============
 
+Important Note
+-----------
+
+***********************
+This section of the eval guide has been **archived**. If you're looking to evaluate Azure Stack HCI in an Azure VM, the best approach is to use the latest version of the guidance, which you can find here:
+
+* [**Part 1** - Complete the prerequisites - deploy your Azure VM](/deployment/steps/1_DeployAzureVM.md "Complete the prerequisites - deploy your Azure VM")
+* [**Part 2** - Configure your Azure Stack HCI 20H2 Cluster](/deployment/steps/2_DeployAzSHCI.md "Configure your Azure Stack HCI 20H2 Cluster")
+* [**Part 3** - Integrate Azure Stack HCI 20H2 with Azure](/deployment/steps/3_AzSHCIIntegration.md "Integrate Azure Stack HCI 20H2 with Azure")
+* [**Part 4** - Explore Azure Stack HCI Management](/deployment/steps/4_ExploreAzSHCI.md "Explore Azure Stack HCI Management")
+
+If you wish to evaluate Azure Stack HCI on a **single physical system**, you can use the guidance below.
+
+***********************
+
 As with any infrastructure technology, in order to test, validate and evaluate the technology, there's typically a requirement for hardware.  If you're fortunate enough to have multiple server-class pieces of hardware going spare (ideally hardware validated for Azure Stack HCI 20H2, found on our [Azure Stack HCI 20H2 Catalog](https://aka.ms/azurestackhcicatalog "Azure Stack HCI 20H2 Catalog")), you can certainly perform a more real-world evaluation of Azure Stack HCI 20H2.
 
 For the purpose of this evaluation guide however, we'll be relying on **nested virtualization** to allow us to consolidate a full lab infrastructure, down onto a single Hyper-V host, either on-prem, or in Azure. If you do have spare physical hardware, you should be able to follow along and use your own hardware - you can just skip the nested-specific steps.
@@ -10,9 +25,10 @@ The use of nested virtualization in this evaluation guide is aimed at providing
 
 Contents
 -----------
+- [Important Note](#important-note)
 - [Contents](#contents)
 - [Nested Virtualization](#nested-virtualization)
-- [Deployment Options](#deployment-options)
+- [Deployment](#deployment)
 - [Deployment Workflow](#deployment-workflow)
 - [Product improvements](#product-improvements)
 - [Raising issues](#raising-issues)
@@ -21,74 +37,61 @@ Nested Virtualization
 -----------
 If you're not familiar with Nested Virtualization, at a high level, it allows a virtualization platform, such as Hyper-V, or VMware ESXi, to run virtual machines that, within those virtual machines, run a virtualization platform. It may be easier to think about this in an architectural view.
 
-![Nested virtualization architecture](/media/nested_virt.png "Nested virtualization architecture")
+![Nested virtualization architecture](/archive/media/nested_virt.png "Nested virtualization architecture")
 
 As you can see from the graphic, at the base layer, you have your physical hardware, onto which you install a hypervisor. In this case, for our example, we're using Windows Server 2019 with the Hyper-V role enabled.  The hypervisor on the lowest level is considered L0 or the level 0 hypervisor.  On that physical host, you create a virtual machine, and into that virtual machine, you deploy an OS that itself, has a hypervisor enabled.  In this example, that 1st Virtualized Layer is running a **nested** Azure Stack HCI 20H2 operating system. This would be an L1 or level 1 hypervisor.  Finally, in our example, inside the Azure Stack HCI 20H2 OS, you create a virtual machine to run a workload.  This could in fact also contain a hypervisor, which would be known as the L2 or level 2 hypervisor, and so the process continues, with multiple levels of nested virtualization possible.
 
 The use of nested virtualization opens up amazing opportunities for building complex scenarios on significantly reduced hardware footprints, however it shouldn't be seen as a substitute for real-world deployments, performance and scale testing etc.
 
-Deployment Options
+Deployment
 -----------
-For those of you who don't have multiple server-class pieces of hardware to test a full hyperconverged solution, this evaluation guide will detail 2 configurations, both using **nested virtualization**, that should be of interest.
+For those of you who don't have multiple server-class pieces of hardware to test a full hyperconverged solution, this evaluation guide will detail how you can deploy on a single physical system, using **nested virtualization**.
 
 ### Deployment of Azure Stack HCI 20H2 nested on a physical system ###
 
-![Architecture diagram for Azure Stack HCI 20H2 nested on a physical system](/media/nested_virt_physical_ga.png "Architecture diagram for Azure Stack HCI 20H2 nested on a physical system")
+![Architecture diagram for Azure Stack HCI 20H2 nested on a physical system](/archive/media/nested_virt_physical_ga.png "Architecture diagram for Azure Stack HCI 20H2 nested on a physical system")
 
 In this configuration, you'll again take advantage of nested virtualization, but in this case, you'll deploy the whole solution on a single desktop/laptop/server.  On your physical system, you'll run either Windows Server 2016/2019 or Windows 10 Pro/Enterprise/Education, with the Hyper-V role enabled.  On Hyper-V, you'll deploy a sandbox infrastructure, consisting of a Windows Server 2019 domain controller VM, a management VM running Windows 10 Enterprise, and a nested Azure Stack HCI 20H2 cluster.
 
 #### Important note for systems with AMD CPUs ####
 For those of you wanting to evaluate Azure Stack HCI 20H2 in a nested configuration, with **AMD-based systems**, the only way this is currently possible is to use **Windows 10 Insider Build 19636 or newer** as your Hyper-V host. Your system should have AMD's 1st generation Ryzen/Epyc or newer CPUs. You can get more information on [nested virtualization on AMD here](https://techcommunity.microsoft.com/t5/virtualization/amd-nested-virtualization-support/ba-p/1434841 "Nested virtualization on AMD-based systems").
 
-If you can't run the Windows 10 Insider builds on your AMD-based system, it may be a better approach to [deploy in Azure instead](/nested/steps/1b_NestedInAzure.md "Deploy in Azure").  We'll be sure to update this guidance as and when new updates to nested virtualization support become available.
-
-### Deployment of Azure Stack HCI 20H2 nested in Azure ###
-
-![Architecture diagram for Azure Stack HCI 20H2 nested in Azure](/media/nested_virt_arch_ga.png "Architecture diagram for Azure Stack HCI 20H2 nested in Azure")
-
-In this configuration, you'll take advantage of the nested virtualization support provided within certain Azure VM sizes.  You'll first deploy a single Azure VM running Windows Server 2019.  Inside this VM, you'll enable the Hyper-V role, and deploy a Windows Server 2019 domain controller VM, along with a management VM, running Windows 10 Enterprise. This management VM will also run the Windows Admin Center.  Finally, you'll deploy a nested Azure Stack HCI 20H2 cluster, with a minimum of 2 nodes, however the number of nodes will be based on the size of your Azure VM.
-
-To reiterate, the whole configuration (Domain Controller VM, Management VM and Azure Stack HCI 20H2 Nodes) will run inside the single Azure VM.
+If you can't run the Windows 10 Insider builds on your AMD-based system, it may be a better approach to [deploy in Azure instead](/steps/1b_NestedInAzure.md "Deploy in Azure").  We'll be sure to update this guidance as and when new updates to nested virtualization support become available.
 
 Deployment Workflow
 -----------
-This guide will walk you through deploying a sandboxed Azure Stack HCI 20H2 infrastructure.  Many of the steps will be universal, regardless of whether you are deploying in Azure, or deploying on a single physical system, however to accommodate different preferences, we've provided paths for those of you who prefer PowerShell, or GUI (Graphical User Interface, such as Hyper-V Manager, Server Manager etc)-based deployments.
+This guide will walk you through deploying a sandboxed Azure Stack HCI 20H2 infrastructure. To accommodate different preferences, we've provided paths for those of you who prefer PowerShell, or GUI (Graphical User Interface, such as Hyper-V Manager, Server Manager etc)-based deployments.
 
 The general flow will be as follows:
 
-![Evaluation guide workflow using nested virtualization](/media/flow_chart_ga.png "Evaluation guide workflow using nested virtualization")
+![Evaluation guide workflow using nested virtualization](/archive/media/flow_chart_ga_oct21.png "Evaluation guide workflow using nested virtualization")
 
-#### Part 1a - Deploy Hyper-V on a physical system ####
+#### Part 1 - Deploy Hyper-V on a physical system ####
 In this step, on your existing system, that's running Windows Server 2016/2019 or Windows 10 Pro/Enterprise/Education, you'll enable the Hyper-V role and create a NAT virtual switch to enable network communication between sandbox VMs, and out to the internet.
 
-* [**Part 1a** - Start your deployment on a physical system](/nested/steps/1a_NestedOnPhysical.md "Start your deployment on a physical system")
-
-#### Part 1b - Deploy Hyper-V host in Azure ####
-In this step, you'll create a suitable VM in Azure using PowerShell or an Azure Resource Manager template.  This VM will run Windows Server 2019 Datacenter, with the full desktop experience.  On this system, you'll enable the Hyper-V role and accompanying management tools, and create a NAT virtual switch to enable network communication between sandbox VMs, and out to the internet.
-
-* [**Part 1b** - Start your deployment into Azure](/nested/steps/1b_NestedInAzure.md "Start your deployment into Azure")
+* [**Part 1a** - Start your deployment on a physical system](/steps/1_NestedOnPhysical.md "Start your deployment on a physical system")
 
 #### Part 2 - Deploy management infrastructure ####
 In this step, you'll use **either the GUI, or PowerShell** to deploy and configure both a Windows Server 2019 domain controller, and a Windows 10 management VM on your Hyper-V host.  You'll create a Windows Server 2019 Active Directory domain, and join the Windows 10 management VM to this domain.  You'll also install the Windows Admin Center ahead of deploying the nested Azure Stack HCI 20H2 cluster.
 
-* [**Part 2a** - Deploy your management infrastructure with the GUI](/nested/steps/2a_ManagementInfraGUI.md "Deploy your management infrastructure with the GUI")
-* [**Part 2b** - Deploy your management infrastructure with PowerShell](/nested/steps/2b_ManagementInfraPS.md "Deploy your management infrastructure with PowerShell")
+* [**Part 2a** - Deploy your management infrastructure with the GUI](/steps/2a_ManagementInfraGUI.md "Deploy your management infrastructure with the GUI")
+* [**Part 2b** - Deploy your management infrastructure with PowerShell](/steps/2b_ManagementInfraPS.md "Deploy your management infrastructure with PowerShell")
 
 #### Part 3 - Deploy nested Azure Stack HCI 20H2 nodes ####
 In this step, you'll use **either the GUI or PowerShell** to create a number of nested Azure Stack HCI 20H2 nodes.
 
-* [**Part 3a** - Create your nested Azure Stack HCI 20H2 nodes with the GUI](/nested/steps/3a_AzSHCINodesGUI.md "Create your nested Azure Stack HCI 20H2 nodes with the GUI")
-* [**Part 3b** - Create your nested Azure Stack HCI 20H2 nodes with PowerShell](/nested/steps/3b_AzSHCINodesPS.md "Create your nested Azure Stack HCI 20H2 nodes with PowerShell")
+* [**Part 3a** - Create your nested Azure Stack HCI 20H2 nodes with the GUI](/steps/3a_AzSHCINodesGUI.md "Create your nested Azure Stack HCI 20H2 nodes with the GUI")
+* [**Part 3b** - Create your nested Azure Stack HCI 20H2 nodes with PowerShell](/steps/3b_AzSHCINodesPS.md "Create your nested Azure Stack HCI 20H2 nodes with PowerShell")
 
 #### Part 4 - Create your nested Azure Stack HCI 20H2 cluster ####
 In this step, you'll use the Windows Admin Center, on the Windows 10 management VM, to create the nested Azure Stack HCI 20H2 cluster, and perform some post-deployment tasks to validate the configuration.
 
-* [**Part 4** - Create your nested Azure Stack HCI 20H2 cluster](/nested/steps/4_AzSHCICluster.md "Create your nested Azure Stack HCI 20H2 cluster")
+* [**Part 4** - Create your nested Azure Stack HCI 20H2 cluster](/steps/4_AzSHCICluster.md "Create your nested Azure Stack HCI 20H2 cluster")
 
 #### Part 5 - Explore the management of your Azure Stack HCI 20H2 environment ####
 With your deployment completed, you're now ready to explore many of the management aspects within the Windows Admin Center.
 
-* [**Part 5** - Explore the management of your Azure Stack HCI 20H2 environment](/nested/steps/5_ExploreAzSHCI.md "Explore the management of your Azure Stack HCI 20H2 environment")
+* [**Part 5** - Explore the management of your Azure Stack HCI 20H2 environment](/steps/5_ExploreAzSHCI.md "Explore the management of your Azure Stack HCI 20H2 environment")
 
 Product improvements
 -----------