Fix issues in Windows Admin Center

If you've just created a new Azure account and haven't signed in to the account on your gateway machine, you might experience problems with registering your Windows Admin Center gateway with Azure.

To mitigate this problem, sign in to your Azure account in another browser tab or window, and then register the Windows Admin Center gateway with Azure.

When deploying Azure Kubernetes Service on Azure Local through Windows Admin Center, only the user who set up the AKS host can create Kubernetes clusters.

To work around this issue, copy the wssd folder from the profile of the user who set up the AKS host to the profile of the user who will be creating the new Kubernetes clusters.

You are experiencing deployment issues or want to reset your deployment.

Close all Windows Admin Center instances connected to Azure Kubernetes Service on Azure Local before running Uninstall-AksHci from a PowerShell administrative window.

You may receive an error in either wizard about a wrong configuration.

Perform cluster cleanup operations. These operations might involve removing the C:\Program Files\AksHci\mocctl.exe file.

There are inconsistencies in network field names showing up in the host cluster deployment flow, and the workload cluster deployment flow.

N/A

You will get this error if you have disabled pop-ups. Google Chrome blocks pop-ups by default, and therefore, the Azure sign-in pop-up is blocked and causes the service principal error.

Enable pop-ups.

When switching from DHCP to static IP, Windows Admin Center displayed an error that said the WinRM client cannot process the request. This error also occurred outside of Windows Admin Center. WinRM broke when static IP addresses were used, and the servers were not registering a Service Principal Name (SPN) when moving to static IP addresses.

To resolve this issue, use the SetSPN command to create the SPN. From a command prompt on the Windows Admin Center gateway, run the following command:

Setspn /Q WSMAN/<FQDN on the Azure Local machine> 

Next, if any of the machines in the environment return the message No Such SPN Found, then log in to that machine and run the following commands:

Setspn /S WSMAN/<machine name> <machine name> 
Setspn /S WSMAN/<FQDN of machine> <machine name> 

Finally, on the Windows Admin Center gateway, run the following to ensure that it gets new machine information from the domain controller:

Klist purge 

If you receive an incorrect upgrade notification message "Successfully installed AksHci PowerShell module version null," the upgrade operation is successful even if the notification is misleading.

You can safely disregard this message.

In Stage 2.1: Basic Step Component, you may encounter this error: "Connecting to remote server *** failed with the following error message: Access is denied. For more information, see the about_Remote_Troubleshooting Help topic" when trying to use your credentials for your server node(s).

Make sure that the account/credentials added is an administrative account on the machine. Then verify that PSRemoting is enabled and remote hosts are trusted. You can do this with the following PowerShell commands:

Enable-PSRemoting -Force 
winrm quickconfig 

If you are still encountering issues, see this troubleshooting guide.

Windows Admin Center does not currently have a process to off-board a cluster from Azure Arc.

To delete Arc agents on a cluster that has been destroyed, navigate to the resource group of the cluster in the Azure portal, and manually delete the Arc content. To delete Arc agents on a cluster that is still up and running, you should run the following command:

az connectedk8s delete --name AzureArcTest1 --resource-group AzureArcTest

After a success upgrade, the Windows Admin Center update dashboard still shows the previous version.

Refresh the browser to fix this issue.

When you deploy AKS Arc using Windows Admin Center, and the deployment hangs for an extended period, you might be having Credential Security Support Provider (CredSSP) or connectivity problems.

Try the following steps to troubleshoot your deployment:

1. On the machine running Windows Admin Center, run the following command in a PowerShell window:

      Enter-PSSession <servername>
   

2. If this command succeeds, you can connect to the server and there's no connectivity issue.

3. If you're having CredSSP problems, run this command to test the trust between the gateway machine and the target machine:

      Enter-PSSession -ComputerName <server> -Credential company\administrator -Authentication CredSSP
   

   You can also run the following command to test the trust in accessing the local gateway:

      Enter-PSSession -computer localhost -credential (Get-Credential)
   

For additional CredSSP troubleshooting tips, see Troubleshoot CredSSP.

Sometimes, because of network issues, Windows Admin Center times out during an Arc connection.

Use the PowerShell command Enable-AksHciArcConnection to connect the AKS workload cluster to Azure Arc while we actively work on improving the user experience.

In stage 2.1: System Validation, you may get an error: "The item 'Install-Module' was not recognized as the name of a cmdlet, function, script file, or runnable program".

Check the spelling of the name. If the path is included, make sure the path is correct. Then try again when you install. Complete the PowerShell commands on the node(s) that you are trying to deploy to. Run the following command to resolve the issue (ensure that your PowerShell version is at least 5.1):

Install-Module -Name PowershellGet -Repository PSGallery -Force -Confirm:$false -SkipPublisherCheck

Then run these commands if you encounter any errors from the first command:

Get-PSRepository
Register-PSRepository -Default

Unable to connect Windows Admin Center to Azure because you can't automatically create and use an Azure App ID on the gateway.

Create an Azure App ID, and assign it the right permissions on the portal. Then, select Use existing in the gateway. For more information, visit connecting your gateway to Azure.

If you have workload clusters with Kubernetes version 1.19.9 installed, and then use Windows Admin Center to update them to Kubernetes version 1.19.11, the Kubernetes update page continues to show that the update is still in process. However, if you run Get-AksHciCluster, the output shows that the update is complete, and if you open Windows Admin Center in a new tab, the cluster is updated to 1.19.11 in the Kubernetes clusters list.

You can ignore this issue as the update process did complete.

When you report problems with Windows Admin Center, it's a good idea to attach logs to help the development team diagnose your problem. Errors in Windows Admin Center generally come in one of two forms:

• Events that appear in the event viewer on the machine running Windows Admin Center
• JavaScript problems that surface in the browser console

To collect logs for Windows Admin Center, use the Get-SMEUILogs.ps1 script that's provided in the public preview package.

To use the script, run this command in the folder where your script is stored:

./Get-SMEUILogs.ps1 -ComputerNames [comp1, comp2, etc.] -Destination [comp3] -HoursAgo [48] -NoCredentialPrompt

The command has the following parameters:

• -ComputerNames: A list of machines you want to collect logs from.
• -Destination: The machine you want to aggregate the logs to.
• -HoursAgo: The start time for collecting logs, expressed in hours before the time you run the script.
• -NoCredentialPrompt: A switch to turn off the credentials prompt and use the default credentials in your current environment.

If you have difficulties running this script, you can run the following command to view the Help text:

GetHelp .\Get-SMEUILogs.ps1 -Examples

When running an upgrade in Windows Admin Center, the following error occurred:

Error occurred while fetching platform upgrade information. RemoteException: No match was found for the specified search criteria and module name 'AksHci'. Try Get-PSRepository to see all available registered module repositories.

This error message typically occurs when AKS on Azure Local is deployed in an environment that has a proxy configured. Currently, Windows Admin Center does not have support to install modules in a proxy environment.

To resolve this error, set up AKS on Azure Local using the proxy PowerShell command.

The AKS host cluster deployment fails at system checks with a WinRM service error.

Try applying the solutions suggested in the Manual troubleshooting.

If you have multiple versions of the PowerShell modules installed (for example, 0.2.26, 0.2.27, and 0.2.28), Windows Admin Center may not use the latest version (or the one it requires).

Make sure you have only one PowerShell module installed. You should uninstall all unused PowerShell versions of the PowerShell modules and leave just one installed. More information on which Windows Admin Center version is compatible with which PowerShell version can be found in the AKS on Azure Local release notes..

This error appears when deploying through Windows Admin Center. The package provider requires the PackageManagement and Provider tags. You should check if the specified package has a tag error when attempting a deployment through Windows Admin Center.

This error comes from PowerShell and states that there are internet connectivity issues. PowerShell is trying to install the prerequisites package and is unable to install it.

Check to make sure the server or failover cluster has internet connectivity and then start a fresh installation.

In Stage 2.1: System Validation, there may be an error when you hit install: No match was found for the specified search criteria for the provider 'NuGet'. The package provider requires 'PackageManagement' and 'Provider' tags. Please check if the specified package has the tags. Complete the PowerShell commands on the node(s) that you are trying to deploy to. You will have to manually install the NuGet using the following PowerShell command:

Install-PackageProvider -Name NuGet -Scope CurrentUser -Force

After running that command, close all open PowerShell windows and try again in Windows Admin Center.

In stage 2.1: System Validation, you may encounter this error: `Unable to find repository 'PSGallery'.

Use Get-PSRepository to see all available repositories.` when you click install. Complete the PowerShell commands on the node(s) that you are trying to deploy to. Unregister and re-register the PSRepository in an administrative PowerShell window. Close all PowerShell windows afterward.

Unregister-PSRepository -Name 'PSGallery'
Register-PSRepository -Default

Then uninstall and reinstall PowerShellGet in an administrative PowerShell window. Close all PowerShell windows afterwards.

Uninstall-Module PowerShellGet
Install-Module PowerShellGet -Force

After this, go back to Windows Admin Center and retry.

If you install Windows Admin Center with one account and try to use it with another, you'll get errors.

For CredSSP to function successfully in the Cluster Create wizard, Windows Admin Center must be installed and used by the same account.

This error appears when moving from PowerShell to Windows Admin Center to create an Arc-enabled workload cluster.

You can safely ignore this error. It is part of the validation step, and the cluster has already been created.

Restarting the Azure Local cluster nodes hosting the management cluster and workload clusters may cause the workload clusters to disappear from the Windows Admin Center dashboard.

To work around this issue, pause and drain the nodes before you plan to restart them. Sometimes, the workload clusters may just take longer to appear in the dashboard.

Windows Admin Center will not deploy Azure Kubernetes Service to an environment with separate storage and compute clusters as it expects the compute and storage resources to be provided by the same cluster. In most cases, it will not find CSVs exposed by the compute cluster and will refuse to continue with deployment.

Next steps

• Troubleshooting overview
• Installation issues and errors
• Upgrade known issues

If you continue to run into problems when you're using AKS Arc, you can file bugs through GitHub.