Forum Widgets
Latest Discussions
Alert emails for Azure Stack HCI health issues?
How do I set up alert emails, when the HCI cluster generates a health fault - like a volume running low on available space? I am running Hci OS 22H2 and using WAC with the Dell plugin to manage. I mean: If I had nothing else to do all day and night, I could sit and stare at WAC and I am sure that something would pop up. But that is not practical. Emails are practical.
Azure Stack HCI & local DHCP
We're replacing our local vSphere infrastructure with Azure Stack HCI. On the vSphere environment we have a DHCP server running that serves ip addresses to our desktops and laptops. Is it possible to run a DHCP server in a VM on Azure Stack HCI? What are the best practices?
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.Starting VMs may fail after installation of 10-2023 CU when Veeam RCT is being used -SOLVED-
Dear community, Please consider reading this articleVirtual machines failed to start after installing Oct 2023 Update (KB5031364) - Microsoft Q&A 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 forVMware here. 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. "stephc_msft wrote: ↑Oct 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 Azure Stack HCI community 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:ErnieCostaCVLTJaromir KasparDarryl van der Peijl
Triggering deployment settings validation failed
I trying to setup a test environment with two Lenovo servers. I have been running several test validations on the cluster and trying to resolve the requriments one by one. But now even my validation wont start - press the "Start validation" button and after a while I receive: Could not complete the operation. 200: OperationTimeout , No updates received from device for operation: [providers/microsoft.azurestackhci/locations/WESTEUROPE/operationStatuses/xxx?api-version=2024-04-01] beyond timeout of [600000] ms Looking in the Activity log I see: -Update DeploymentSettings resources Create failed - Update Deploymentsettings resources Create Started I have no clue that is wrong, am I out of resources ? and what to do ?, anyone
HCI Stack 23H2 WMI - RPC Server is Unavailable
After updating to Solution 10.2405.2.7 I am unable to manage my cluster through the failover manager and unable to run cluster validations due to the error RPC Server is unavailable. I have restarted the nodes, confirmed firewall rules are allowing WMI and RPC, and confirmed DNS. Azure and WAC are reporting no issues with the cluster, I am worried about applying the next solution in case this WMI issue will cause issues with the updates. Any guidance to resolve this fault would be much appreciatedResource planning for Azure Stack HCI
Hi all, I'm currently in resource planning for a small cluster to evaluate it for our projects. Should I always plan double resources for the failover cluster solution for the workloads that are running on the VMs? If it's so, isn't it a kind of over-provisioning? Thank you for your help in advance.
