Error Occurred While Fetching the Key Please Check the Host and Port Information and Try Again

Skip to main content

Windows Admin Center Known Issues

• Article
• 03/29/2022
• 17 minutes to read

Is this page helpful?

Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services. Privacy policy.

In this article

Applies to: Windows Admin Middle, Windows Admin Center Preview

If you run across an issue not described on this page, please let united states know.

Installer

• When installing Windows Admin Center using your own document, be mindful that if you copy the thumbprint from the certificate managing director MMC tool, it will contain an invalid grapheme at the beginning. As a workaround, type the get-go character of the thumbprint, and copy/paste the rest.

• Using port below 1024 is non supported. In service mode, you lot may optionally configure port 80 to redirect to your specified port.

General

• In the 1910.two release of Windows Admin Center, you may not be able to connect to Hyper-V servers on specific hardware. If you are blocked on this upshot, please download our previous build.

• If you accept Windows Admin Center installed as a gateway on Windows Server 2016 under heavy utilize, the service may crash with an error in the result log that contains Faulting application proper name: sme.exe and Faulting module proper name: WsmSvc.dll. This is due to a bug that has been fixed in Windows Server 2019. The patch for Windows Server 2022 was included the February 2022 cumulative update, KB4480977.

• If you take Windows Admin Centre installed every bit a gateway and your connection listing appears to be corrupted, perform the following steps:

  Warning

  This will delete the connection list and settings for all Windows Admin Center users on the gateway.

  1. Uninstall Windows Admin Center
  2. Delete the Server Management Feel folder under C:\Windows\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft
  3. Reinstall Windows Admin Centre

• If you exit the tool open and idle for a long catamenia of time, you may get several Error: The runspace state is not valid for this functioning errors. If this occurs, refresh your browser. If you lot encounter this, ship us feedback.

• There may be minor variance between version numbers of OSS running in Windows Admin Center modules, and what is listed within the third Political party Software Find.

Extension Manager

• When you update Windows Admin Center, you must reinstall your extensions.
• If you lot add an extension feed that is inaccessible, there is no warning. [14412861]

Partner extension issues

• Dell's EMC OpenManage Integration extension utilizes APIs provided past Windows Admin Middle to push button files onto target nodes. This API (eastward.yard. NodeExtensionInstall) only works when the user is a gateway administrator and does not support non-admin use.

Browser Specific Issues

Microsoft Edge

• If y'all have Windows Admin Center deployed as a service and you are using Microsoft Edge as your browser, connecting your gateway to Azure may fail subsequently spawning a new browser window. Endeavour to piece of work around this issue by adding https://login.microsoftonline.com, https://login.live.com, and the URL of your gateway as trusted sites and allowed sites for pop-up blocker settings on your customer-side browser. For more than guidance on fixing this in the troubleshooting guide. [17990376]

Google Chrome

• Prior to version 70 (released late Oct 2018) Chrome had a problems regarding the WebSockets protocol and NTLM authentication. This furnishings the post-obit tools: Events, PowerShell, Remote Desktop.

• Chrome may pop up multiple credential prompts, particularly during the add connectedness experience in a workgroup (non-domain) environs.

• If y'all have Windows Admin Center deployed as a service, popups from the gateway URL demand to be enabled for any Azure integration functionality to work.

Mozilla Firefox

Windows Admin Center is non tested with Mozilla Firefox, just most functionality should work.

• Windows x Installation: Mozilla Firefox has its ain certificate store, then you must import the Windows Admin Eye Client certificate into Firefox to utilize Windows Admin Center on Windows x.

WebSocket compatibility when using a proxy service

Remote Desktop, PowerShell, Packet Monitoring, and Events modules in Windows Admin Center utilize the WebSocket protocol, which is oftentimes not supported when using a proxy service.

Support for Windows Server versions before 2022 (2012 R2, 2012, 2008 R2)

Note

Windows Admin Middle requires PowerShell features that are not included in Windows Server 2012 R2, 2012, or 2008 R2. If you lot will manage Windows Server these with Windows Admin Center, you volition need to install WMF version five.i or college on those servers.

Type $PSVersiontable in PowerShell to verify that WMF is installed, and that the version is v.1 or higher.

If information technology is not installed, you can download and install WMF 5.ane.

Part Based Access Control (RBAC)

• RBAC deployment volition non succeed on machines that are configured to apply Windows Defender Application Control (WDAC, formerly known every bit Lawmaking Integrity.) [16568455]

• To utilize RBAC in a cluster, y'all must deploy the configuration to each member node individually.

• When RBAC is deployed, you lot may get unauthorized errors that are incorrectly attributed to the RBAC configuration. [16369238]

Server Manager solution

Certificates

• Cannot import .PFX Encrypted Certificate in to current user shop. [11818622]

Events

• Events are effected by websocket compatibility when using a proxy service.

• You lot may become an error that references "bundle size" when exporting large log files.

  • To resolve this, use the post-obit control in an elevated command prompt on the gateway machine: winrm set winrm/config @{MaxEnvelopeSizekb="8192"}

Files

• Uploading or downloading large files non nevertheless supported. (~100mb limit) [12524234]

PowerShell

• PowerShell is afflicted past websocket compatibility when using a proxy service

• Pasting with a unmarried correct-click as in the desktop PowerShell console does not work. Instead yous volition get the browser'south context menu, where yous can select paste. Ctrl-V works as well.

• Ctrl-C to copy does non work, it will always send the Ctrl-C break command to the console. Copy from the right-click context menu works.

• When you make the Windows Admin Center window smaller, the final content volition reflow, but when you go far larger again, the content may not render to its previous state. If things get jumbled, yous tin effort Clear-Host, or disconnect and reconnect using the button above the final.

Registry Editor

• Search functionality not implemented. [13820009]

Remote Desktop

• When Windows Admin Center is deployed equally a service, the Remote Desktop tool may fail to load after updating the Windows Admin Center service to a new version. To work around this outcome, articulate your browser cache. [23824194]

• The Remote Desktop tool may neglect to connect when managing Windows Server 2012. [20258278]

• When using the Remote Desktop to connect to a car that is non Domain joined, yous must enter your account in the MACHINENAME\USERNAME format.

• Some configurations can block Windows Admin Centre's remote desktop client with group policy. If you encounter this, enable Let users to connect remotely by using Remote Desktop Services nether Computer Configuration/Policies/Administrative Templates/Windows Components/Remote Desktop Services/Remote Desktop Session Host/Connections

• Remote Desktop is affected by websocket compatibility.

• The Remote Desktop tool does not currently support any text, paradigm, or file re-create/paste between the local desktop and the remote session.

• To practice any copy/paste within the remote session, you lot can copy as normal (correct-click + re-create or Ctrl+C), merely paste requires right-click + paste (Ctrl+V does NOT work)

• You cannot send the post-obit key commands to the remote session

  • Alt+Tab
  • Office keys
  • Windows Key
  • PrtScn

Roles and Features

• When selecting roles or features with unavailable sources for install, they are skipped. [12946914]

• If you lot choose not to automatically reboot afterward role installation, we won't enquire once more. [13098852]

• If yous do choose to automatically reboot, the reboot will occur earlier the status gets updated to 100%. [13098852]

Storage

• Down-level: DVD/CD/Floppy drives practise not announced as volumes on down-level.

• Down-level: Some backdrop in Volumes and Disks are not available down-level and then they appear unknown or blank in details panel.

• Downward-level: When creating a new book, ReFS merely supports an allocation unit of measurement size of 64K on Windows 2012 and 2012 R2 machines. If a ReFS book is created with a smaller allocation unit size on downwards-level targets, file system formatting will fail. The new book will not be usable. The resolution is to delete the book and use 64K allocation unit of measurement size.

Updates

• After installing updates, install status may be buried and require a browser refresh.

• You may meet the error: "Keyset does not exist" when attempting to fix up Azure Update management. In this example, please try the following remediation steps on the managed node -

  1. Cease 'Cryptographic Services' service.
  2. Change binder options to show hidden files (if required).
  3. Got to "%allusersprofile%\Microsoft\Crypto\RSA\S-1-five-18" folder and delete all its contents.
  4. Restart 'Cryptographic Services' service.
  5. Repeat setting up Update Management with Windows Admin Middle

Virtual Machines

• When managing the virtual machines on a Windows Server 2012 host, the in-browser VM connect tool will fail to connect to the VM. Downloading the .rdp file to connect to the VM should still piece of work. [20258278]

• Azure Site Recovery – If Azure Site Recovery is ready on the host exterior of Windows Admin Middle, yous will be unable to protect a VM from inside Windows Admin Center [18972276]

• Advanced features available in Hyper-V Manager such as Virtual SAN Director, Move VM, Export VM, VM Replication are currently not supported.

Virtual Switches

• Switch Embedded Teaming (SET): When adding NICs to a squad, they must be on the aforementioned subnet.

Computer Direction Solution

The Reckoner Direction solution contains a subset of the tools from the Server Manager solution, so the aforementioned known issues apply, and the following Computer Direction solution-specific problems:

• If you lot use a Microsoft Account (MSA) or if yous use Azure Active Directory (AAD) to log on to you Windows 10 machine, you must use "manage-as" to provide credentials for a local administrator account. [16568455]

• When yous try to manage the localhost, you volition be prompted to drag the gateway procedure. If you click no in the User Business relationship Control popup that follows, you must cancel the connection attempt and showtime over.

• Windows 10 does not have WinRM/PowerShell remoting on past default.

  • To enable management of the Windows 10 Client, you must effect the command Enable-PSRemoting from an elevated PowerShell prompt.

  • You lot may also demand to update your firewall to let connections from outside the local subnet with Set-NetFirewallRule -Name WINRM-HTTP-In-TCP -RemoteAddress Whatsoever. For more than restrictive networks scenarios, delight see how to enable PSRemoting.

Cluster Deployment

Footstep one.2

Mixed workgroup machines are currently not supported when calculation servers. All machines used for clustering need to belong to aforementioned workgroup. If they do non, the next button volition be disabled and the following error will appear: "Cannot create a cluster with servers in different Agile Directory domains. Verify the server names are correct. Movement all the servers into the same domain and try again."

Step 1.4

Hyper-V needs to be installed on virtual machines running the Azure Stack HCI OS. Trying to enable the Hyper-Five characteristic for these virtual machines will neglect with the fault below:

To install Hyper-V on virtual machines running the Azure Stack HCI Bone, run the following command:

              Enable-WindowsOptionalFeature -Online -FeatureName 'Microsoft-Hyper-V'                          

Step one.7

Sometimes servers take longer than expected to restart later on updates are installed. The Windows Admin Center cluster deployment magician will check the server restart country periodically to know if the server was restarted successfully. Even so, if the user restarts the server outside of the wizard manually, so the wizard does not accept a fashion to capture the server state in an advisable fashion.

If you would like to restart the server manually, get out the current sorcerer session. Later on you accept restarted the server, you lot may restart the wizard.

Phase 4 Storage

In stage four, an error tin occur if a user has deleted a cluster and has not cleared the storage pools from the cluster. That ways the storage pools that are on the organisation are locked by the onetime cluster object and but the user can manually clear them.

To clear the configuration, the user needs to run:

1. On all nodes run: Clear-ClusterNode
2. Remove all previous storage pools, you tin then run:

                     get-storagepool get-storagepool -IsPrimordial 0 | remove-storagepool                                  

Annotation

If the storage pools are ready as readonly which tin sometimes happen if the cluster is improperly destroyed, and so the user needs to first brand certain the storage pools are changed to editable earlier removing. Run the following earlier the commands above: Get-StoragePool <PoolName> | Set-StoragePool -IsReadOnly $false

To avoid this scenario in the first place, the user will need to run the following:

1. Remove virtual deejay:

                     get-virtualdisk | Remove-VirtualDisk                                  

2. Remove storage pools:

                     get-storagepool get-storagepool -IsPrimordial 0 | remove-storagepool                                  

3. Remove cluster resources:

                     Get-ClusterResource | ? ResourceType -eq "virtual machine" | Remove-ClusterResource Go-ClusterResource | ? ResourceType -like "*virtual automobile*" | Remove-ClusterResource                                  

4. Cleaning up:

                     Remove-Cluster -CleanupAD                                  

5. On all nodes run:

                     Clear-ClusterNode                                  

Stretch cluster cosmos

Information technology is recommended to utilise servers that are domain-joined when creating a stretch cluster. At that place is a network segmentation outcome when trying to utilise workgroup machines for stretch cluster deployment due to WinRM limitations.

Undo and start over

When using aforementioned machines repeatedly for cluster deployment, cleanup of previous cluster entities is important to get a successful cluster deployment in the aforementioned set up of machines. Meet the page on deploying hyper-converged infrastructure for instructions on how to clean upwardly your cluster.

CredSSP in cluster creation

The Windows Admin Center cluster deployment wizard uses CredSSP in several places. You lot run across the error bulletin There was an error during the validation. Review error and try again (this occurs well-nigh frequently in the Validate cluster stride):

Yous can apply the following steps to troubleshoot:

1. Disable CredSSP settings on all nodes and the Windows Admin Center gateway automobile. Run the first control on your gateway machine and the 2d command on all of the nodes in your cluster:

                     Disable-WsmanCredSSP -Role Client                                  

                     Disable-WsmanCredSSP -Office Server                                  

2. Repair the trust on all nodes. Run the following control on all nodes:

                     Test-ComputerSecureChannel -Verbose -Repair -Credential <account name>                                  

3. Reset grouping policy propagated information by running the following command on all nodes:

                     gpupdate /force                                  

4. Reboot each nodes. Afterward reboot, test the connectivity between your gateway machine and target nodes, equally well every bit your connectivity between nodes, using the following command:

                     Enter-PSSession -computername <node fqdn>                                  

CredSSP

• The Updates tool will sometimes throws the CredSSP error You can't utilise Cluster-Enlightened updating tool without enabling CredSSP and providing explicit credentials:

  

  This error was widely seen when new clusters are created then you try to access the Updates tool for these clusters in Windows Admin Center. This issue is fixed in Windows Admin Center v2110. [36734941]

• The CredSSP session endpoint permission outcome is an common CredSSP fault that can be seen when Windows Admin Center runs on Windows client machines. This effect is widely seen when the user who is using Windows Admin Center is not the same user who installed Windows Admin Heart on the client automobile.

  To mitigate this problem, we have introduced the Windows Admin Centre CredSSP administrators' group. The user facing this problem should be added to this group and so relogin to the desktop computer running Windows Admin Center. Below is an prototype of what the error notification was before (left) and later (right) the modification:

  

Nested Virtualization

When validating Azure Stack HCI OS cluster deployment on virtual machines, nested virtualization needs to exist turned on earlier roles/features are enabled using the beneath PowerShell control:

              Set-VMProcessor -VMName <VMName> -ExposeVirtualizationExtensions $true                          

Note

For virtual switch teaming to be successful in a virtual machine environment, the post-obit command needs to be run in PowerShell on the host soon later on the virtual machines are created: Get-VM | %{ set-VMNetworkAdapter -VMName $_.Name -MacAddressSpoofing On -AllowTeaming on }

If y'all are a deploying a cluster using the Azure Stack HCI Bone, there is an boosted requirement. The VM kicking virtual hard drive must be preinstalled with Hyper-V features. To do this, run the following command before creating the virtual machines:

              Install-WindowsFeature –VHD <Path to the VHD> -Proper noun Hyper-V, RSAT-Hyper-V-Tools, Hyper-5-PowerShell                          

Support for RDMA

The cluster deployment sorcerer in Windows Admin Center version 2007 does not provide back up for RDMA configuration.

Failover Cluster Manager solution

• When managing a cluster, (either Hyper-Converged or traditional?) y'all may encounter a shell was non institute error. If this happens either reload your browser, or navigate away to another tool and dorsum. [13882442]

• An effect tin occur when managing a down-level (Windows Server 2012 or 2012 R2) cluster that hasn't been configured completely. The fix for this issue is to ensure that the Windows feature RSAT-Clustering-PowerShell has been installed and enabled on each member node of the cluster. To exercise this with PowerShell, enter the command Install-WindowsFeature -Name RSAT-Clustering-PowerShell on all the cluster nodes. [12524664]

• The Cluster may need to be added with the unabridged FQDN to exist discovered correctly.

• When connecting to a cluster using Windows Admin Center installed as a gateway, and providing explicit username/password to authenticate, you lot must select Use these credentials for all connections then that the credentials are available to query the fellow member nodes.

Hyper-Converged Cluster Manager solution

• Some commands such as Drives - Update firmware, Servers - Remove and Volumes - Open up are disabled and currently not supported.

Azure services

Azure login and gateway registration

In the 2009 release, you may encounter issues logging into Azure or registering your Windows Admin Center gateway with Azure. The guidance beneath should help yous mitigate these issues:

• Earlier using whatsoever Azure capabilities inside Windows Admin Centre, including gateway registration, brand sure you are signed into your Azure account in a different tab or window. Nosotros suggest signing in through the Azure portal.

• If you successfully sign into Azure during gateway registration but practise not meet visual confirmation on the Azure folio of your Windows Admin Center settings, try navigating to a unlike page in settings before navigating dorsum to the Azure page.

• The Azure sign-in popular-upwardly may appear more ofttimes in this build and may require administrators to grant Windows Admin Center permissions more frequently.

• If you have already given admin approval for Windows Admin Center in the Azure portal and y'all are all the same seeing an error message maxim "Need admin approval", try signing into Azure using one of the banners effectually Windows Admin Middle instead of in the Settings page.

• If your proxy is mis-configured, then y'all may go the fault bulletin "Error: Value cannot be cypher. Parameter name: httpClientFactory." Delight ensure that your proxy is configured correctly by going to Settings page.

Azure File Sync permissions

Azure File Sync requires permissions in Azure that Windows Admin Center did not provide prior to version 1910. If y'all registered your Windows Admin Center gateway with Azure using a version before than Windows Admin Center version 1910, you will need to update your Azure Active Directory awarding to get the correct permissions to use Azure File Sync in the latest version of Windows Admin Centre. The additional permission allows Azure File Sync to perform automatic configuration of storage account admission as described in this article: Ensure Azure File Sync has admission to the storage account.

To update your Azure Active Directory app, y'all can practise one of ii things

1. Go to Settings > Azure > Unregister, so register Windows Admin Center with Azure again, making sure you choose to create a new Azure Active Directory application.
2. Go to your Azure Active Directory application and manually add the permission needed to your existing Azure Active Directory app registered with Windows Admin Heart. To do this, get to Settings > Azure > View in Azure. From the App Registration blade in Azure, go to API permissions, select Add a permission. Coil downward to select Azure Active Directory Graph, select Delegated permissions, expand Directory, and select Directory.AccessAsUser.All. Click Add together permissions to save the updates to the app.

Options for setting up Azure management services

Azure direction services including Azure Monitor, Azure Update Management, and Azure Security Centre, utilise the same agent for an on-premises server: the Microsoft Monitoring Amanuensis. Azure Update Management has a more than limited set of supported regions and requires the Log Analytics workspace to be linked to an Azure Automation account. Considering of this limitation, if you wish to prepare multiple services in Windows Admin Center, you must fix up Azure Update Management first, then either Azure Security Eye or Azure Monitor. If yous've configured whatsoever Azure direction services that use the Microsoft Monitoring Amanuensis, so effort to fix Azure Update Direction using Windows Admin Heart, Windows Admin Center will only allow you to configure Azure Update Management if the existing resources linked to the Microsoft Monitoring Amanuensis back up Azure Update Management. If this is non the case yous have 2 options:

1. Go to the Command Panel > Microsoft Monitoring Agent to disconnect your server from the existing Azure management solutions (like Azure Monitor or Azure Security Center). And then set upwardly Azure Update Management in Windows Admin Centre. After that, y'all tin can get dorsum to set upwardly your other Azure management solutions through Windows Admin Center without bug.
2. You lot can manually set the Azure resource needed for Azure Update Management so manually update the Microsoft Monitoring Agent (outside of Windows Admin Center) to add together the new workspace corresponding to the Update Management solution y'all wish to use.

Feedback

Submit and view feedback for

petersonwithad.blogspot.com

Source: https://docs.microsoft.com/en-us/windows-server/manage/windows-admin-center/support/known-issues