![]() For more information, refer Quickstart for Azure Cloud Shell. This document details how to use Bash in Azure Cloud Shell. Licenses will take a few minutes to be applied on your cluster.Īzure CLI is available to install in Windows, macOS and Linux environments. When Windows Server subscription has been successfully purchased, you can start using Windows Server VMs on your cluster. In the context pane, select Purchase again to confirm. Under the feature Windows Server subscription add-on, select Purchase. In your Azure Stack HCI cluster resource page, navigate to the Configuration screen. Select one of the following tabs based on your preferred method. ![]() You can enable Windows Server subscription through different methods. Windows Admin Center (version 2103 or later) with the Cluster Manager extension (version 2.41.0 or later).Register Azure Stack HCI: All servers must be online and registered to Azure.Install updates: Version 21H2, with at least the Decemsecurity update KB5008210 or later.After setting up AVMA, you can then apply the generic AVMA keys on the client side. When Windows Server subscription is purchased, Azure Stack HCI servers retrieve licenses from the cloud and automatically set up AVMA on the cluster. How does Windows Server subscription work? For the Windows Server subscription fees, see the Add-on workloads (optional) section in the Azure Stack HCI pricing page. Windows Server subscription enables you to subscribe to Windows Server guest licensing on Azure Stack HCI through Azure. ![]() The following table shows the guest operating systems that the different licensing methods can activate: Version For details, see Licensing Windows Server and Pricing for Windows Server licenses. For details, see Pricing for Windows Server subscription.Ĭore licenses. Per physical core/per month pricing, purchased and billed through Azure (free trial within the first 60 days of registering your Azure Stack HCI). No CAL required – included in WS subscription. Key based – for example, KMS/AVMA/enter keys in VM. After it's enabled, you can then apply the generic AVMA keys on the client side. No host-side keys – AVMA is automatically enabled. Need to have both Software Assurance (SA) and WS volume license keys. What versions of WS VMs do you want to use?Įvergreen – all versions up to the latest version.ĭoes this option also allow me to use Windows Server: Azure edition? Where do I want to deploy my Windows Server (WS) VMs? ![]() To use other methods to activate VMs, see Key Management Services (KMS) activation planning.Ĭhoose the licensing option that best suits your needs: Question.One of the most convenient ways is to use Automatic VM Activation (AVMA). ![]() If you are using BYOL, you must use the corresponding keys associated with your license and apply them using your chosen activation method.You can immediately activate VMs against the cluster using generic AVMA client keys. If you are using Windows Server subscription, AVMA is automatically enabled on the host.Bring your own license (BYOL): Apply your existing Windows Server licenses.įor more information, see Compare licensing options.Windows Server subscription: Subscribe to Windows Server guest licenses through Azure.The following figure shows the different Windows Server VM licensing options:įirst, choose one of two licensing options: This article describes general licensing concepts and the new options that are available on Azure Stack HCI. Optionally, Azure Stack HCI offers new licensing models and tools to help simplify this process. You can use any existing Windows Server licenses and activation methods that you already have. Windows Server virtual machines (VMs) must be licensed and activated before you can use them on Azure Stack HCI. Applies to: Azure Stack HCI, versions 22H2 and 21H2 Windows Server 2022, Windows Server 2019 Datacenter Edition and later ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |