Error adding single node Azure Stack HCI cluster to WAC

Lisa Lownds 66 Reputation points

I initially deployed Azure Stack HCI 21H2 single node and then updated it online to 22H2. I registered Azure Stack HCI with Azure successfully and can manage aspects of the cluster from the Azure portal (I've yet to set up Resource Bridge). I have an instance of WAC running locally and I had previously successfully added the server node into WAC.

However, when I try to add the cluster (using a short name or FQDN) WAC cannot confirm if the cluster is available. I add the cluster anyway and switch credentials (from local) and get this WinRM error. No such issues with the Azure portal. The WAC version is 1.3.2204.19002.

How do I troubleshoot this issue?



Azure Stack HCI
Azure Stack HCI
A hyperconverged infrastructure operating system delivered as an Azure service that provides security, performance, and feature updates.
295 questions
{count} votes

4 answers

Sort by: Most helpful
  1. vipullag-MSFT 25,521 Reputation points

    @Lisa Lownds

    Welcome to Microsoft Q&A Platform, thanks for posting your query here.

    In the past when came across a similar issue after restarting the cluster network everything started working. Please check if the cluster network is up and running on this cluster (user PowerShell or Failover Cluster manager from another Windows Server machine with a desktop).



    Hope this helps.
    If you need further help on this, tag me in a comment.
    If the suggested response helped you resolve your issue, please 'Accept as answer', so that it can help others in the community looking for help on similar topics.

    0 comments No comments

  2. Lisa Lownds 66 Reputation points

    Thank you for the welcome. I've restarted the system (mainly because it is a lab and I don't have it running out of hours). Anyway, I've run Get-ClusterNetwork and it is UP. However, I am still getting the same set of issues e.g. discovery of the cluster doesn't happen and then when I go ahead and add it regardless, I get the WinRM error.

    If I can find the cluster in the first place, then does this suggest an issue with the cluster name and finding the name? I've looked in DNS (not wanting to blame DNS) and there is a record for the cluster name. Yet, this discovery is the first hurdle with WAC. Once overridden, then the WinRM error occurs.

    How do I troubleshoot this?


  3. Badger 56 Reputation points

    I've had a similar issue when all of a sudden my cluster wouldn't discover. DNS is fine, and everything is reachable from everywhere.

    0 comments No comments

  4. Badger 56 Reputation points

    Have you enabled Azure hybrid benefits on this cluster recently? As part of it it enables 2 firewall rules which might cause this to happen. Look for 2 rules with IMDS in their name and disable them, see if that helps.

    0 comments No comments