Merge branch 'master' of https://github.com/MicrosoftDocs/azure-stack…

…-docs-pr into FromPrivateRepo

azure-stack/aks-hci/adapt-apps-mixed-os-clusters.md

@@ -3,7 +3,7 @@ title: Adapt applications for use in mixed-OS Kubernetes clusters
 description: How to use node selectors or taints and tolerations on Azure Kubernetes Service to ensure applications in mixed OS Kubernetes clusters running on Azure Stack HCI are scheduled on the correct worker node operating system
 author: abha
 ms.topic: how-to
-ms.date: 09/22/2020
+ms.date: 10/20/2020
 ms.author: abha
 ms.reviewer: 
 ---
@@ -35,7 +35,7 @@ For more information on nodeSelectors, visit [node selectors](https://kubernetes
 Windows OS nodes in Azure Kubernetes Service on Azure Stack HCI can be tainted with the following key-value pair. Users shouldn't use a different one.
 
 ```yaml
-node.kubernetes.io/os=Windowss:NoSchedule
+node.kubernetes.io/os=Windows:NoSchedule
 ```
 Run `kubectl get` and identify the Windows worker nodes you want to taint.
 

azure-stack/aks-hci/create-kubernetes-cluster-powershell.md

@@ -125,12 +125,25 @@ If you want to use Windows nodes, the minimum required version is v1.1.8.6.
 
 ## Step 4: Access your clusters using kubectl
 
-To access your Azure Kubernetes Service host or Kubernetes cluster using kubectl, run the following command. This will use the specified cluster's kubeconfig file as the default kubeconfig file for kubectl.
+To access your Kubernetes clusters using kubectl, run the following command. This will use the specified cluster's kubeconfig file as the default kubeconfig file for kubectl.
 
 ```powershell
-Set-AksHciKubeConfig -clusterName
+Get-AksHciCredential -clusterName
+                     [-outputLocation]
 ```
 
+### Required Parameters
+
+`clusterName`
+
+The name of the cluster.
+
+### Optional Parameters
+
+`outputLocation`
+
+The location were you want the kubeconfig downloaded. Default is `%USERPROFILE%\.kube`.
+
 ## Delete a Kubernetes cluster
 
 If you need to delete a Kubernetes cluster, run the following command.

azure-stack/aks-hci/setup-powershell.md

@@ -10,23 +10,33 @@ ms.author: jeguan
 
 > Applies to: Azure Stack HCI
 
-In this quickstart, you'll learn how to set up an Azure Kubernetes Service host on Azure Stack HCI using PowerShell. To instead using Windows Admin Center, see [Set up with Windows Admin Center](setup.md).
+In this quickstart, you'll learn how to set up an Azure Kubernetes Service host on Azure Stack HCI using PowerShell. To instead use Windows Admin Center, see [Set up with Windows Admin Center](setup.md).
 
 ## Before you begin
 
-Before you begin, make sure you have a 2-4 node Azure Stack HCI cluster or a single node Azure Stack HCI. **We recommend having a 2-4 node Azure Stack HCI cluster.** If you don't, follow instructions on how to [here](./system-requirements.md).
+Before you begin, make sure you have a 2-4 node Azure Stack HCI cluster or a single node Azure Stack HCI. **We recommend having a 2-4 node Azure Stack HCI cluster.** If you don't, follow instructions on the [Azure Stack HCI registration page](https://azure.microsoft.com/products/azure-stack/hci/hci-download/).
 
-You will also need to make sure that you have the AksHci PowerShell module installed. The download package that you can find [here](https://aka.ms/AKS-HCI-Evaluate) will have the module in a zip file. Make sure to extract the zip file in the correct location (`%systemdrive%\program files\windowspowershell\modules`), and then run the following command in a PowerShell administrative window.
+## Step 1: Download and install the AksHci PowerShell module
+
+Download the `AKS-HCI-Public=Preview-Oct-2020` from the [Azure Kubernetes Service on Azure Stack HCI registration page](https://aka.ms/AKS-HCI-Evaluate). The zip file `AksHci.Powershell.zip` contains the PowerShell module.
+
+If you have previously installed Azure Kubernetes Service on Azure Stack HCI using PowerShell or Windows Admin Center, run the following command before proceeding.
+
+   ```powershell
+   Uninstall-AksHci
+   ```
+
+**Close all PowerShell windows.** Delete any existing directories for AksHci, AksHci.Day2, and MSK8sDownloadAgent located in the path `%systemdrive%\program files\windowspowershell\modules`. Once this is done, you can extract the contents of the new zip file. Make sure to extract the zip file in the correct location (`%systemdrive%\program files\windowspowershell\modules`).
 
    ```powershell
    Import-Module AksHci
    ```
 
 After running the above command, close all PowerShell windows and reopen an administrative session to run the commands in the following steps.
 
-## Step 1: Prepare your machine(s) for deployment
+## Step 2: Prepare your machine(s) for deployment
 
-First, we'll run checks on every physical node to see if all the requirements are satisfied to install Azure Kubernetes Service on Azure Stack HCI.
+Run checks on every physical node to see if all the requirements are satisfied to install Azure Kubernetes Service on Azure Stack HCI.
 
 Open PowerShell as an administrator and run the following command.
 
@@ -36,7 +46,7 @@ Open PowerShell as an administrator and run the following command.
 
 When the checks are finished, you'll see "Done" displayed in green text.
 
-## Step 2: Configure your deployment
+## Step 3: Configure your deployment
 
 Set the configuration settings for the Azure Kubernetes Service host. **For a 2-4 node Azure Stack HCI cluster, you must specify `MultiNode` in the `-deploymentType`, the `wssdImageDir` and `cloudConfigLocation` parameters.** For a 1 node Azure Stack HCI cluster, all parameters are optional and set to their default values. However, for optimal performance, **we recommend using a 2-4 node Azure Stack HCI cluster deployment.**
 
@@ -55,6 +65,8 @@ Configure your deployment with the following command.
                     [-vipPoolEndIp]
                     [-macPoolStart]
                     [-macPoolEnd]
+                    [-vlanID]
+                    [-cloudServiceCidr]
                     [-wssdDir]
                     [-akshciVersion]
                     [-vnetType]
@@ -118,6 +130,14 @@ This is used to specify the start of the MAC address of the MAC pool that you wi
 
 This is used to specify the end of the MAC address of the MAC pool that you wish to use for the Azure Kubernetes Service host VM. The syntax for the MAC address requires that the least significant bit of the first byte should always be 0, and the first byte should always be an even number (i.e. 00, 02, 04, 06...). The first byte of the address passed as the `-macPoolEnd` should be the same as the first byte of the address passed as the `-macPoolStart`. Default is none.
 
+`-vlandID`
+
+This can be used to specify a network VLAN ID. Azure Kubernetes Service host and Kubernetes cluster VM network adapters will be tagged with the provided VLAN ID. Default is none.
+
+`cloudServiceCidr`
+
+This can be used to provide a static IP/network prefix to be assigned to the MOC CloudAgent service. This value should be provided using the CIDR format. (Example: 192.168.1.2/16). Default is none.
+
 `-wssdDir`
 
 This is a working directory for the module to use for storing small files. Defaults to `%PROGRAMFILES%\AksHci` and should not be changed for most deployments.  
@@ -166,7 +186,7 @@ To reset the Azure Kubernetes Service on Azure Stack HCI configuration, run the
 Set-AksHciConfig
 ```
 
-## Step 3: Start a new deployment
+## Step 4: Start a new deployment
 
 After you've configured your deployment, you must start deployment. This will install the Azure Kubernetes Service on Azure Stack HCI agents/services and the Azure Kubernetes Service host.
 
@@ -176,22 +196,35 @@ To begin deployment, run the following command.
 Install-AksHci
 ```
 
-### Check your deployed clusters
+### Verify your deployed Azure Kubernetes Service host
 
-To get a list of your deployed Azure Kubernetes Service hosts, run the following command. You will also be able to get Kubernetes clusters using the same command after deploying them.
+To ensure that your Azure Kubernetes Service host was deployed, run the following command. You will also be able to get Kubernetes clusters using the same command after deploying them.
 
 ```powershell
 Get-AksHciCluster
 ```
 
-## Step 4: Access your clusters using kubectl
+## Step 5: Access your clusters using kubectl
 
 To access your Azure Kubernetes Service host or Kubernetes cluster using kubectl, run the following command. This will use the specified cluster's kubeconfig file as the default kubeconfig file for kubectl.
 
 ```powershell
-Set-AksHciKubeConfig -clusterName
+Get-AksHciCredential -clusterName
+                     [-outputLocation]
 ```
 
+### Required Parameters
+
+`clusterName`
+
+The name of the cluster.
+
+### Optional Parameters
+
+`outputLocation`
+
+The location were you want the kubeconfig downloaded. Default is `%USERPROFILE%\.kube`.
+
 ## Get logs
 
 To get logs from your all your pods, run the following command. This command will create an output zipped folder called `akshcilogs` in the path `C:\wssd\akshcilogs`.

azure-stack/aks-hci/setup.md

@@ -14,12 +14,17 @@ In this quickstart, you set up Azure Kubernetes Service on Azure Stack HCI using
 
 Setting up involves the following tasks:
 
+* Download Azure Kubernetes Service on Azure Stack HCI
 * Set up Windows Admin Center, if you haven't done so already
 * Install the Azure Kubernetes Service for Azure Stack HCI extension for Windows Admin Center
 * Set up an Azure Kubernetes Service host on the system you want to deploy the Kubernetes cluster to
 
 Before getting started, make sure you have satisfied all the prerequisites on the [system requirements](.\system-requirements.md) page.
 
+## Download Azure Kubernetes Service on Azure Stack HCI
+
+If you haven't already downloaded the preview software, see [evaluate AKS on Azure Stack HCI](https://aka.ms/AKS-HCI-Evaluate). You will be asked to download AKS on Azure Stack HCI as well as Windows Admin Center.
+
 ## Setting up Windows Admin Center
 
 If you haven't already installed Windows Admin Center, see [install Windows Admin Center](/windows-server/manage/windows-admin-center/deploy/install). For public preview of Azure Kubernetes Service on Azure Stack HCI, you must download and run Windows Admin Center on a Windows 10 machine. Only Windows Admin Center desktop mode is compatible with Azure Kubernetes Service on Azure Stack HCI right now. Azure Kubernetes Service on Azure Stack HCI functionality is only available on Windows Admin Center builds 2009 or later.

azure-stack/hci/release-notes.md

@@ -6,7 +6,7 @@ ms.author: v-kedow
 ms.topic: conceptual
 ms.service: azure-stack
 ms.subservice: azure-stack-hci
-ms.date: 10/13/2020
+ms.date: 10/20/2020
 ---
 
 # Release notes for Azure Stack HCI Public Preview
@@ -15,6 +15,47 @@ ms.date: 10/13/2020
 
 This article describes the contents of Azure Stack HCI Public Preview update packages.
 
+## October 20, 2020 Preview Update (KB4580388)
+
+This update includes improvements and fixes for the latest release of Azure Stack HCI.
+
+### Improvements and fixes
+This nonsecurity update includes quality improvements. Key changes include:
+
+- With this update, Azure Stack HCI customers who hold valid Windows Server 2019 Datacenter edition license(s) can use them to conveniently activate virtual machines (VMs) hosted on Azure Stack HCI without having to manage product keys for each VM.
+
+### Known issues in this update
+
+Microsoft is aware of one issue with this update.
+
+#### Symptom
+When using Live Migration to move a VM between Windows Server and Azure Stack HCI operating systems, you may see the error: "Blocked a migration operation for virtual machine <vmname> because VM migration between differing Windows editions is not supported (virtual machine ID)."
+
+Alternatively, this may also cause a Cluster Aware Updating (CAU) operation to fail if any of the VMs are expected to perform Live Migration during CAU.
+
+#### Workaround
+
+Use Quick Migration instead of Live Migration. If using CAU, change the default behavior temporarily so that CAU uses Quick Migration.
+
+Example:
+
+```powershell
+Get-ClusterResourceType "Virtual Machine" | Set-ClusterParameter MoveTypeThreshold 3001
+```
+
+It's recommended that you revert back to the previous `MoveTypeThreshold` value after CAU completes successfully.
+
+For more information, see [Configuring How VMs Are Moved when a Node is Drained](https://techcommunity.microsoft.com/t5/failover-clustering/configuring-how-vms-are-moved-when-a-node-is-drained/ba-p/371848).
+
+### How to get this update
+The October 20, 2020 security update (KB4580388) for [Azure Stack HCI preview](https://azure.microsoft.com/products/azure-stack/hci/hci-download/) is delivered via Windows Update. To install it on your Azure Stack HCI cluster, see [Update Azure Stack HCI clusters](manage/update-cluster.md).
+
+### File information
+For a list of the files that are provided in this update (OS Build 17784.1321), download the [file information for cumulative update 4580388](https://download.microsoft.com/download/2/f/b/2fb766d3-c4c8-4279-8718-8efbd0b6f211/4580388.csv).
+
+   > [!NOTE]
+   > Some files erroneously have "Not applicable" in the "File version" column of the CSV file. This might lead to false positives or false negatives when using some third-party scan detection tools to validate the build.
+
 ## October 13, 2020 Security Update (KB4580363)
 
 This update includes improvements and fixes for the latest release of Azure Stack HCI.

azure-stack/mdc/deployment-overview.md

@@ -13,10 +13,10 @@ ms.workload: na
 pms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: article
-ms.date: 04/09/2020
+ms.date: 10/20/2020
 ms.author: justinha
 ms.reviewer: asganesh
-ms.lastreviewed: 04/09/2020
+ms.lastreviewed: 10/20/2020
 ---
 
 # MDC deployment overview
@@ -31,8 +31,6 @@ The objectives of this guide include:
 - Describe how to install and configure the key components.
 - Validate the customer deployment.
 
-This deployment guide is intended for the Microsoft field professional team that are responsible for deployment of the MDC at the customer site.
-
 Technical experience with virtualization, servers, operating systems, networking, and storage solutions is required to fully understand the content of this guide. 
 The Deployment Engineer must have knowledge of Microsoft Windows Server 2019 with Hyper-V, Azure Stack Hub, Azure, and Microsoft PowerShell.