Powershell errors in local WAC connecting to Azure Local

Question

Powershell errors in local WAC connecting to Azure Local

Matthew Shepard 0

It started with getting Powershell Credssp authentication errors when clicking on a Virtual Machine in our local install of WAC connecting to our Azure Local (HCI). It would still let me manage the Virtual Machine. After trying to edit and correct CredSSP situation, getting intermitten full connection issues now, saying stuff like "Couldn't determine if the cluster supports the SDDC namespace for virtual machines." and "Connecting to remote server [Redacted] failed with the following error message : WinRM cannot complete the operation. Verify that the specified computer name is valid, that the computer is accessible over the network, and that a firewall exception for the WinRM service is enabled and allows access from this computer. By default, the WinRM firewall exception for public profiles limits access to remote computers within the same local subnet. For more information, see the about_Remote_Troubleshooting Help topic."

These errors are coming and going now, seemingly more time of being the error.

Matthew Shepard 0 Reputation points

2025-09-30T22:04:50.7733333+00:00

This is the normal error I have been trying to get fixed with messing with the CredSSP and WinRM settings and group policy to allow credential delegation to the specific hostsnames of the HCI nodes.
Bharath Y P 1,355 Reputation points Microsoft External Staff Moderator

2025-10-27T08:20:15.3666667+00:00
Hello Matthew Shepard,

It seems like you're facing issue with PowerShell CredSSP authentication errors when using Windows Admin Center (WAC) to connect to your Azure Local setup. The messages you're getting suggest issues with WinRM configurations and connectivity to your HCI nodes.

Here are a few steps you can take to troubleshoot and possibly resolve this:

Verify WinRM Configuration: Ensure that WinRM is configured correctly on both your local machine and the HCI nodes. You can run the following command in PowerShell to check the WinRM configuration: winrm quickconfig

CredSSP Settings: You mentioned modifying CredSSP settings. Make sure that both the client and server systems are configured to allow CredSSP authentication for the respective nodes. You can configure CredSSP with the following command on the client: Enable-WSManCredSSP -Role Client -DelegateComputer "<HCI Node FQDN or IP>" And on the server: Enable-WSManCredSSP -Role Server

Check Firewall Rules:The errors hint at potential connectivity issues. Make sure that firewall rules on your network allow traffic through the necessary ports used by WinRM (typically TCP 5985 for HTTP and 5986 for HTTPS). You can run: Get-NetFirewallRule | where { $_.DisplayName -like "*WinRM*" } If necessary, you can enable WinRM firewall exceptions using: enable-psremoting -force

Validate Cluster Support: For the SDDC namespace error, ensure that your cluster supports the Azure Stack HCI features being accessed. Ensure that your HCI nodes are running a supported version (21H2 or later).

Ping and DNS Resolution: Check whether the HCI nodes can resolve and ping each other. DNS resolution issues can lead to connectivity problems Test-Connection <HCI Node FQDN or IP>

Azure Arc Agent:Ensure the Azure Arc agent is installed and correctly configured on your HCI nodes: azcmagent show If the agent isn't installed, you may need to install or update it. Use the commands below to ensure you have the latest version: Install-Module -Name Az.ConnectedMachine -Force -AllowClobber

Hope these steps help you get to the bottom of the issue! If you continue experiencing problems, it might be helpful to check the logs in

C:\ProgramData\AzureConnectedMachineAgent\Log for more detailed error messages or reach out for further investigation.

If you still facing an issue, could you please help us with the below details:

What version of Azure Stack HCI are you currently using?

Have you made any recent changes to the network configuration or group policy settings?

Can you confirm that the necessary firewall ports for WinRM are open and that traffic is allowed?

Are there any specific error codes in the logs that you haven't mentioned?

Feel free to reach out if you need more help!
Bharath Y P 1,355 Reputation points Microsoft External Staff Moderator

2025-10-28T10:10:51.95+00:00

Hello Matthew Shepard, kindly let us know if the solution provided worked for you. If you need any further assistance, please feel free to reach out. Thanks,

1 answer

Your answer

Matthew Shepard 0 Reputation points

2025-09-30T22:04:50.7733333+00:00

This is the normal error I have been trying to get fixed with messing with the CredSSP and WinRM settings and group policy to allow credential delegation to the specific hostsnames of the HCI nodes.
Bharath Y P 1,355 Reputation points Microsoft External Staff Moderator

2025-10-28T10:10:51.95+00:00

Hello Matthew Shepard, kindly let us know if the solution provided worked for you. If you need any further assistance, please feel free to reach out. Thanks,

Answer 1

Matthew Shepard 0

I need to give it a couple more hours, but I think I have the intermitten issue fixed by going to the cluster master and restarting the winrm service, then restarting my WAC server. Still having the CredSSP error pop up, but maybe it is just a non-issue error?

Share via

Powershell errors in local WAC connecting to Azure Local

1 answer

Your answer