Azure Stack HCI 23h2 upgrade & Azure local Resource
Good evening, After upgrading from 22H2 to 23H2, we encountered an issue where the Azure Local resource in the Azure portal appears as "not connected recently." Additionally, we are not seeing the "Your cluster can be upgraded to the latest version" option, likely due to this connection issue. Despite successful connectivity tests and extensive troubleshooting, the resource remains unsynchronised with Azure. As a result, we tried deleting the Azure Local resource and re-registering the nodes. Now, while both nodes are successfully registered and connected to Azure and passing the Invoke-AzStackHciUpgradeValidation , we are unable to find a way to re-register the Azure Local resource to proceed with the "Install the solution upgrade via Azure portal" step. The only option I see is going through the "Deploy Azure Local" process in Azure Arc. However, I believe this would overwrite existing settings and VMs, causing significant disruption—especially since this is a production cluster upgraded from 22H2. Is there a way to re-register the cluster and restore the Azure Local resource using existing settings, so we can proceed with deploying the rest of the solution upgrade via the Azure portal? Any guidance would be greatly appreciated
AVD on Azure Local: Increase memory of Sessionhosts after Hostpool deployment
Hi there, Is there a best practice for increasing the RAM of the session hosts in an Azure Virtual Desktop host pool? We are using the autoscaler to start and stop VMs on demand. Since this is an automated process, all the settings changed via HyperV-Manager get overwritten, presumably by the host pool template. Can someone confirm that I am on the right track and maybe give me a hint or a how-to on how to change the RAM for my session hosts? Hostpool Type: Pooled Uses Session Host Config: No Thanks in Advance, Maik
Error Depoloying Azure Stack?
I keep getting this message when I try to deploy azure stack Any idea would be appreciated thanks Exception Type 'SetAzureStackHostsPreConfiguration' of Role 'HostNetwork' raised an exception: Stopping execution after intent provisioning failed with [ ProvisioningFailed ] for intent "compute_management" on host "NODE1". Configuration Status: Failed Compute: True Management: True Storage: False at TestNetworkAtcIntentStatus, C:\NugetStore\Microsoft.AS.Network.Deploy.HostNetwork.1.2411.1.8\content\Powershell\Roles\HostNetwork\HostNetwork.psm1: line 1714 at ConfigureHostAdaptersWithNetworkAtcForHosts, C:\NugetStore\Microsoft.AS.Network.Deploy.HostNetwork.1.2411.1.8\content\Powershell\Roles\HostNetwork\HostNetwork.psm1: line 2183 at Set-HostAdaptersWithNetworkAtc, C:\NugetStore\Microsoft.AS.Network.Deploy.HostNetwork.1.2411.1.8\content\Powershell\Roles\HostNetwork\HostNetwork.psm1: line 2315 at Invoke-ConfigureHostAdaptersWithNetworkAtc<Process>, C:\NugetStore\Microsoft.AS.Network.Deploy.HostNetwork.1.2411.1.8\content\Powershell\Roles\HostNetwork\HostNetwork.psm1: line 2586 at Invoke-ConfigureAzureStackHostNetworkingWithATC, C:\NugetStore\Microsoft.AS.Network.Deploy.HostNetwork.1.2411.1.8\content\Powershell\Roles\HostNetwork\HostNetwork.psm1: line 3781 at Invoke-SetAzureStackHostsPreConfiguration, C:\NugetStore\Microsoft.AS.Network.Deploy.HostNetwork.1.2411.1.8\content\Powershell\Roles\HostNetwork\HostNetwork.psm1: line 3916 at SetAzureStackHostsPreConfiguration, C:\NugetStore\Microsoft.AS.Network.Deploy.HostNetwork.1.2411.1.8\content\Powershell\Classes\HostNetwork\HostNetwork.psm1: line 66 at <ScriptBlock>, C:\CloudDeployment\ECEngine\InvokeInterfaceInternal.psm1: line 139 at Invoke-EceInterfaceInternal, C:\CloudDeployment\ECEngine\InvokeInterfaceInternal.psm1: line 134 at <ScriptBlock>, <No file>: line 33Azure Stack HCI Cluster network name changes from "ClusterNetwork1" to "Unused:ClusterNetwork1"
I have configured Azure Stack HCI Stretched Cluster with Network ATC. Strange behaviour i am noticing is with naming of Cluster Network(screenshot 1). e.g. current name is "Cluster Network1", gets changed to "Unused: Cluster Network1". Also Live Migration settings(screenshot 2) keep selecting multiple adaptors by itself even i uncheck all and only keep "LM" on top an checked. Any suggestions or fix to this.
Issues with Azure stack HCI 23H2 and and NVMe Drives 5520 Series
We recently purchased a Lenovo MX630 V3 Integrated System for Azure Stack HCI 23H2 deployment with 16 x 5520 series NVMe drives (Lenovo NVMe part number is 4XB7A13943/SSDPF2KX076T1O and the server model is 7D6U). We are using version 10.2408.0.29 25398.1085 of Azure Stack HCI. In the past few days, we have encountered some weird issues. The storage cluster degraded because the physical disks keep going to "Lost Communication," causing the storage volume to go into detached mode. We are using firmware version Lenovo NVMe 9CV10450, which is approved by Lenovo. I see that the newer driver is 9CV10490, and I was wondering if anyone had a similar experience with these drives and if the August update fixed it. The reason I ask is that using Solidigm driver/firmware is not supported by Lenovo. So far, we have replaced one disk, but when I observed the last problem, it seemed to fix itself.Azure Stack HCI - adding NIC to Network ATC Intent
Hello fellow Azure Stack HCI Admins, I currently have a compute_management Intent for my two node switchless cluster with only one pNIC per node (port1) assigned. I now want to add port2 of each node to the intent for redundancy. (See image) I found this command-set on learn: https://learn.microsoft.com/en-us/azure-stack/hci/manage/manage-network-atc?tabs=21H2&pivots=azure-stack-hci Get-NetIntentStatus -ClusterName <YourClusterName> Update-NetIntentAdapter -IntentName <YourIntentName> -AdapterName pNIC2 Get-NetIntentStatus -ClusterName <YourClusterName> Is that the correct command set to archive that? Or is there another way to do so? I am a bit anxious on running those commands because I already have workloads deployed on that cluster and I don't want to break it. Thanks in advance! :) PS: I chose only one NIC per node because at the time of deployment I only had one ToR switch available.Setup second vswitch for DMZ purpose on azure stack hci cluster
I try to deploy Az stack hci cluster on AX-750 DELL servers, for production purposes in my host network i use dedicated switch for DMZ, so i wish to use a teamming on my 10Gb Dual ports card for production workloads , and another teamming on my 1 Gb dual ports card for DMZ workloads. Does Az Stack HCI support 2 vswitch configurations??
Azure Stack HCI Datacenter Azure Edition - Activation no longer reported correctly in Server Manager
Scenario: different VMs using Windows Server Datacenter Azure Edition (core and GUI), Clustered and unclustered VMs OS: Azure Stack HCI 22H2 Result: Attestation is working as expected, locally, Azure Portal and WAC 2203. Problem: Server Manager locally or remotely does no longer show the activation status correctly. slmgr /sconfig / WMIC shows a correct activation on VMs that are also correctly configured with Attestation Reproducible: yes, in all cases Server Manager Get-CimInstance SoftwareLicensingProduct -Filter "Name like 'Windows%'" | where { $_.PartialProductKey } | select Description, LicenseStatus sconfig Test IDMS Invoke-RestMethod -Headers @{"Metadata"="true"} -Method GET -Uri http://169.254.169.254:80/metadata/attested/document?api-version=2018-10-01 Result: ok UI & Settings app no popup for failed activation on GUI based installation no watermark hints that the VM is not activated (restart may be required if you just attestated and activated it) activation shows up correctly in Settings app This has worked few months ago. Anyone else? Would appreciate a fix for the sake of consistency, as this has worked well in the past.
