Starting VMs may fail after installation of 10-2023 CU when Veeam RCT is being used -SOLVED-
Dear community, Please consider reading this article https://learn.microsoft.com/en-us/answers/questions/1390624/virtual-machines-failed-to-start-after-installing?page=2#answers in case you are directly affected by the issue, that Hyper-V VMs fail to start, in the certain scenario described below. The issue is not related to VMs not starting on VMware ESXi after applying current CUs. Find remediation instructions for https://kb.vmware.com/s/article/90947 Affected Hosts: Hyper-V Hosts OS: Windows Server 2019 (by community) Windows Server 2022 (by community) Azure Stack HCI 22H2 (experienced myself) Scenario: Gen1 / Gen2 VMs backed up by Veeam using RCT (Change Block Tracking) Not completely confirmed but it seems that unclustered VMs are affected, and clustered VMs are not affected. In a case this morning this caused the unclustered Domain Controllers dedicated for the Azure Stack HCI cluster to fail. edit: 19. Oct. 2023: clustered and unclustered VMs are affected. Reasons: Microsoft has made changes, fixing a long-standing performance issue with Veeam RCT feature, but the fix this can cause a side-effect. The fix is not mentioned in the change log (Windows Update history), despite the criticality of the improvement. https://forums.veeam.com/memberlist.php?mode=viewprofile&u=55718 wrote: https://forums.veeam.com/post500560.html#p500560Oct 09, 2023 10:15 pmThe long awaited 'RCT fix', for the RCT side of this ongoing issue, should be released in the October 2023 Windows update, ie tomorrow!" example of perf. improvements during Veeam backups using RCT from the community: Root cause: directly related to Veeam RCT and CU 10-2023, yet unknown why it happens. Reproducible: yes, 100% in certain scenarios. The https://aka.ms/hci-slack is voluntarily working on the reproducibility in more scenarios to understand the dependencies. Remediation: a. rename or delete MCT / RCT files (quick and dirty). Keep the files if you want Microsoft Support / Veeam Support to engage on this issue. b. uninstall the CU 10-2023 from your cluster (I cannot recommend that for several reasons), using manual suspending of nodes, WUSA and monitor migration and storage replication jobs to be finished before and after restarting nodes. Solution: Deploy Cumulative Update 11-2023, instead of 10-2023 on affected Hyper-V hosts. kudos: ErnieCostaCVLT Jaromir Kaspar Darryl van der Peijl
Feature Request: Azure Stack Storage and Sizing Tools
I would like to bring up that, despite Azure Stack HCI is a growing solution with outstanding features, the current situation for customers and partners is odd to sizing the solution. What we got is in preview everything and not touched for long time, not keeping up with the technology Introducing the all-new azure stack HCI sizing tool (preview)! - Microsoft Community Hub / https://azurestackhcisolutions.azure.microsoft.com/ https://s2dcalc.blob.core.windows.net/www/index.html I hope that the tool will be united. Also the sizing tool requires a Microsoft account instead of a business account which is odd for a business faced solution. It would be amazing, to see more attention. One thing I would wish the most, is a possibility to import LiveOptics data into the sizer tool.Learn about Azure Stack HCI on Microsoft Learn!
Last week the general availability of the new Azure Stack HCI, our new hybrid cloud hyper-converged platform was announced. With the release of this new platform, the team also released a new Microsoft Learn learning path called Azure Stack HCI foundations. In this learning path, you will be introduced to the Azure Stack portfolio and describes basic architecture, core capabilities, and primary use cases of its products. You’ll also learn about the differences and similarities between Azure Stack HCI, Azure Stack Hub, Azure Stack Edge, and Azure. If you want to get an overview of the Azure Stack portfolio or the new Azure Stack HCI 20H2 version, check out my blog posts. The new Azure Stack HCI foundations learning path on Microsoft Learn currently has 4 modules: Introduction to Azure Stack This module introduces you to the Azure Stack portfolio and describes basic architecture, core capabilities, and primary use cases of its products. You’ll also learn about the differences and similarities between Azure Stack HCI, Azure Stack Hub, Azure Stack Edge, and Azure. You can check out the module here. Introduction to Azure Stack HCI core technologies This module introduces Azure Stack HCI technologies. You’ll learn about the core Azure Stack HCI technologies, including Hyper-V, Windows Server software-defined storage, and Windows Server software-defined networking. You can check out the module here. Plan and deploy Azure Stack HCI This module introduces you to planing for and deploying Azure Stack HCI. Content includes identifying suitable workloads, determining the optimal configuration to host these workloads, stepping through the deployment process, validating post-deployment operational status, and evaluating Azure integration options. You can check out the module here. Integrate Azure Arc and Azure Stack HCI In this module, you will learn the fundamentals of Azure Arc and how is it used to bring new capabilities to the management and monitoring of your Azure Stack HCI clusters at scale. You can check out the module here. You can read the full blog post here.MSLab Azure Stack HCI: Waiting until SBL Disks are surfaced.
Hi everyone, Still trying to get an Azure Stack HCI Lab run on my rig. Came far thanks to MSLabs and sorts. Scenario: Azure Stack HCI 22N2 using nested virtualization. Parent OS Windows 11 22H2 Parent Virtualization: Hyper-V Storage HW: 2x Samsung 970 Evo NVMe pooled in Storage Space. S2D Cluster Storage: 4x VHDX each 256 GB, per cluster node (2 cluster nodes) expected behaviour: I hoped that there will be no issues creating a pool. WAC isn't helpful. One message claims everything's alright. but an error in the main screen This is the manual command, since WAC delivers contradictionary results: Enable-ClusterStorageSpacesDirect -Autoconfig 1 -SkipEligibilityChecks -CollectPerformanceHistory 1 -Confirm -Verbose -BusTypesToUse SAS But it its stuck at that point. It used to be possible: https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/storage-spaces-direct-hardware-requirements#virtual-deployment Cleaning up the disks and starting over won't help, so they can be pooled once again. Unfortunately a link from Elden seem to be dead end. https://techcommunity.microsoft.com/t5/windows-server-for-it-pro/enabling-s2d-cluster-in-virtual-test-environment-issue/m-p/84186/highlight/true#M267 Any ideas? (again this is a not a prod. env.) Thanks for your time! ✌️ cc JamesvandenBerg cblackuk1 Darryl van der Peijl John Marlin Thomas-MaurerAzure Stack HCI - performance degradation over time
Dear Community, dear DanCuomo, is there any awareness about the following potential problem with Azure Stack HCI OS 22H2? Hope to find some echo. Problem description: severe Storage NVMe performances degradation over time. Restarting the nodes will remediate the situation. I have heard about an issue that, customer, and partner claim this to be "long standing and a known issue". Also claim there was no solution offered by MSFT support. I got informed about this, and customer agreed to back his claims with futher data, hopefully also with Microsoft SRs involved.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.
Azure Stack HCI Registration Help
We are waiting on arrival on our Azure Stack HCI cluster. In the meantime I have been trying to setup a test environment. The challenge I have is with registering the cluster with Azure. I understand their are specific Azure permissions need for the account that performs the registration. My intention was to register the system on my Visual Studio Subscription. Everything appeared to go ok until what I suspect was my last step. The last step - where I selected my Visual subscription gave me the somewhat expected permission error. Another organization within our college owns the tenant and we'll have to work with them when it comes time to register our production system. Here is where I could sure use some help. Since this permission issue still needs to be hammered out and this is just a test I figured I would try registering it with my personal Azure account. When I try to do that, it errors stating that my personal subscription is not found in the tenant. Which is true.... The problem is I can't figure out how to "unregister the incomplete registration." Everything I see shows the system to be "unregistered." Short of burning my test systems down and restarting, is there anything I can do to reset this registration process? Thanks, JimAzure Stack HCI nedir? (tr-TR)
hibrit operasyonel modele geçmeye hazır olmayan ve şirket içi veri merkezlerinde çalışan Windows veya Linux sunucularını dağıtmak ve yönetmek için geleneksel araçlara ve yöntemlere güvenen birçok müşteri var. Geleneksel şirket içi operasyonel model için daha uygun olan bazı iş yükleri de vardır. Azure Stack HCI, Windows ve Linux tabanlı sanallaştırılmış ve kapsayıcıya alınmış iş yüklerini, kendi veri merkezinizdeki veya bir hizmet sağlayıcısı tarafından yönetilen bir veri merkezindeki HCI cihazınızda çalışmanıza olanak tanır. Donanım açısından bakıldığında, her bir Azure Stack HCI kümesi, hiper yakınsama altyapısı için özel olarak tanımlanmış özel bir işletim sistemini çalıştıran 2 ila 16 arasında fiziksel, doğrulanmış sunucudan oluşur.
