Windows Admin Center Known Problems

  • Commodity
  • 17 minutes to read

Applies to: Windows Admin Heart, Windows Admin Eye Preview

If yous come across an issue not described on this page, delight let us know.

Installer

  • When installing Windows Admin Center using your own certificate, be mindful that if you lot copy the thumbprint from the certificate manager MMC tool, information technology will contain an invalid grapheme at the starting time. Every bit a workaround, type the first character of the thumbprint, and copy/paste the rest.

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

General

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

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

  • If y'all have Windows Admin Center installed as a gateway and your connection listing appears to be corrupted, perform the post-obit steps:

    Alarm

    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 Direction Experience binder under C:\Windows\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft
    3. Reinstall Windows Admin Center

  • If you get out the tool open and idle for a long period of time, you may get several Error: The runspace country is not valid for this functioning errors. If this occurs, refresh your browser. If yous encounter this, send us feedback.

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

Extension Manager

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

Partner extension issues

  • Dell'due south EMC OpenManage Integration extension utilizes APIs provided by Windows Admin Center to push files onto target nodes. This API (e.g. NodeExtensionInstall) but works when the user is a gateway administrator and does not back up non-admin utilize.

Browser Specific Issues

Microsoft Edge

  • If you lot have Windows Admin Heart deployed as a service and you are using Microsoft Edge equally your browser, connecting your gateway to Azure may fail subsequently spawning a new browser window. Attempt to piece of work effectually this issue past calculation https://login.microsoftonline.com, https://login.live.com, and the URL of your gateway every bit trusted sites and allowed sites for pop-up blocker settings on your customer-side browser. For more guidance on fixing this in the troubleshooting guide. [17990376]

Google Chrome

  • Prior to version 70 (released tardily October 2018) Chrome had a bug regarding the WebSockets protocol and NTLM authentication. This effects the following tools: Events, PowerShell, Remote Desktop.

  • Chrome may pop upward multiple credential prompts, especially during the add together connexion experience in a workgroup (non-domain) environment.

  • If you take Windows Admin Center deployed as a service, popups from the gateway URL need to be enabled for whatsoever Azure integration functionality to piece of work.

Mozilla Firefox

Windows Admin Center is not tested with Mozilla Firefox, but most functionality should work.

  • Windows 10 Installation: Mozilla Firefox has its ain certificate store, so yous must import the Windows Admin Eye Client certificate into Firefox to utilise Windows Admin Center on Windows 10.

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 often not supported when using a proxy service.

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

Note

Windows Admin Center requires PowerShell features that are not included in Windows Server 2012 R2, 2012, or 2008 R2. If yous will manage Windows Server these with Windows Admin Heart, you volition demand to install WMF version 5.i or higher on those servers.

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

If it is not installed, you can download and install WMF 5.1.

Role Based Access Control (RBAC)

  • RBAC deployment will not succeed on machines that are configured to apply Windows Defender Application Command (WDAC, formerly known as Code Integrity.) [16568455]

  • To use RBAC in a cluster, you must deploy the configuration to each fellow member node individually.

  • When RBAC is deployed, y'all 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 store. [11818622]

Events

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

  • You may get an mistake that references "bundle size" when exporting large log files.

    • To resolve this, use the following command in an elevated command prompt on the gateway auto: winrm set winrm/config @{MaxEnvelopeSizekb="8192"}

Files

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

PowerShell

  • PowerShell is affected by websocket compatibility when using a proxy service

  • Pasting with a unmarried right-click as in the desktop PowerShell console does non work. Instead you will get the browser'due south context carte, where you lot tin can select paste. Ctrl-Five works as well.

  • Ctrl-C to re-create does non work, information technology will ever ship the Ctrl-C break control to the console. Re-create from the right-click context menu works.

  • When y'all make the Windows Admin Middle window smaller, the last content will reflow, just when y'all arrive larger again, the content may not render to its previous state. If things get jumbled, yous can try Clear-Host, or disconnect and reconnect using the button above the terminal.

Registry Editor

  • Search functionality not implemented. [13820009]

Remote Desktop

  • When Windows Admin Center is deployed as a service, the Remote Desktop tool may fail to load later updating the Windows Admin Centre service to a new version. To piece of work around this consequence, clear your browser enshroud. [23824194]

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

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

  • Some configurations tin can block Windows Admin Center's remote desktop customer with group policy. If you encounter this, enable Allow users to connect remotely past using Remote Desktop Services under Estimator Configuration/Policies/Authoritative Templates/Windows Components/Remote Desktop Services/Remote Desktop Session Host/Connections

  • Remote Desktop is affected by websocket compatibility.

  • The Remote Desktop tool does non currently support any text, prototype, or file copy/paste betwixt the local desktop and the remote session.

  • To do any copy/paste within the remote session, you tin can re-create every bit normal (right-click + copy or Ctrl+C), but paste requires right-click + paste (Ctrl+5 does Not work)

  • You cannot transport the following cardinal commands to the remote session

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

Roles and Features

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

  • If y'all choose not to automatically reboot after role installation, we won't ask once more. [13098852]

  • If you practise cull to automatically reboot, the reboot will occur before the status gets updated to 100%. [13098852]

Storage

  • Down-level: DVD/CD/Floppy drives do not appear every bit volumes on down-level.

  • Down-level: Some properties in Volumes and Disks are not available down-level so they announced unknown or blank in details panel.

  • Down-level: When creating a new book, ReFS only supports an resource allotment unit of measurement size of 64K on Windows 2012 and 2012 R2 machines. If a ReFS volume is created with a smaller allocation unit size on down-level targets, file system formatting will fail. The new volume volition non be usable. The resolution is to delete the volume and use 64K resource allotment unit size.

Updates

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

  • Yous may encounter the error: "Keyset does not exist" when attempting to set upwardly Azure Update management. In this instance, please try the following remediation steps on the managed node -

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

Virtual Machines

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

  • Azure Site Recovery – If Azure Site Recovery is fix on the host outside of Windows Admin Centre, you lot will exist unable to protect a VM from within Windows Admin Center [18972276]

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

Virtual Switches

  • Switch Embedded Teaming (Set up): When adding NICs to a team, they must be on the same subnet.

Computer Management Solution

The Computer Management solution contains a subset of the tools from the Server Manager solution, and so the aforementioned known issues employ, and the post-obit Calculator Management solution-specific bug:

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

  • When you try to manage the localhost, you lot will be prompted to elevate the gateway procedure. If you lot click no in the User Account Control popup that follows, you must cancel the connection attempt and start over.

  • Windows x does not have WinRM/PowerShell remoting on by default.

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

    • Y'all may too demand to update your firewall to let connections from exterior the local subnet with Ready-NetFirewallRule -Proper name WINRM-HTTP-In-TCP -RemoteAddress Whatever. For more than restrictive networks scenarios, please come across how to enable PSRemoting.

Cluster Deployment

Pace one.2

Mixed workgroup machines are currently not supported when adding servers. All machines used for clustering need to belong to same workgroup. If they do not, the adjacent button will be disabled and the following error will announced: "Cannot create a cluster with servers in dissimilar Active Directory domains. Verify the server names are correct. Movement all the servers into the same domain and try once more."

Step 1.4

Hyper-V needs to be installed on virtual machines running the Azure Stack HCI Os. Trying to enable the Hyper-V feature for these virtual machines will fail with the fault below:

Screenshot of Hyper-V enablement error

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

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

Step ane.7

Sometimes servers accept longer than expected to restart after updates are installed. The Windows Admin Center cluster deployment wizard will check the server restart state periodically to know if the server was restarted successfully. However, if the user restarts the server outside of the sorcerer manually, so the wizard does not accept a fashion to capture the server land in an appropriate style.

If you would like to restart the server manually, go out the current wizard session. Subsequently you have restarted the server, you may restart the wizard.

Stage 4 Storage

In stage 4, an error can 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 system are locked past the old cluster object and just 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, y'all tin then run: 
                      get-storagepool go-storagepool -IsPrimordial 0 | remove-storagepool

Notation

If the storage pools are set as readonly which can sometimes happen if the cluster is improperly destroyed, then the user needs to first make sure the storage pools are inverse to editable earlier removing. Run the post-obit earlier the commands above: Get-StoragePool <PoolName> | Set-StoragePool -IsReadOnly $simulated

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

  1. Remove virtual disk: 
                      get-virtualdisk | Remove-VirtualDisk
  2. Remove storage pools: 
                      get-storagepool get-storagepool -IsPrimordial 0 | remove-storagepool
  3. Remove cluster resources: 
                      Go-ClusterResource | ? ResourceType -eq "virtual machine" | Remove-ClusterResource Get-ClusterResource | ? ResourceType -like "*virtual machine*" | Remove-ClusterResource
  4. Cleaning upwardly: 
                      Remove-Cluster -CleanupAD
  5. On all nodes run: 
                      Clear-ClusterNode

Stretch cluster creation

It is recommended to use servers that are domain-joined when creating a stretch cluster. In that location is a network division issue when trying to employ workgroup machines for stretch cluster deployment due to WinRM limitations.

Undo and showtime over

When using same machines repeatedly for cluster deployment, cleanup of previous cluster entities is important to get a successful cluster deployment in the same ready of machines. See the folio on deploying hyper-converged infrastructure for instructions on how to make clean up your cluster.

CredSSP in cluster creation

The Windows Admin Center cluster deployment wizard uses CredSSP in several places. You encounter the fault message There was an fault during the validation. Review error and try once more (this occurs nearly frequently in the Validate cluster step):

Screenshot of cluster create CredSSP error.

You can use the post-obit steps to troubleshoot:

  1. Disable CredSSP settings on all nodes and the Windows Admin Middle gateway motorcar. Run the outset command on your gateway machine and the 2nd command on all of the nodes in your cluster:

                      Disable-WsmanCredSSP -Part Client                                  
                      Disable-WsmanCredSSP -Role Server

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

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

  3. Reset group policy propagated data past running the following command on all nodes:

                      gpupdate /force

  4. Reboot each nodes. Later on reboot, examination the connectivity betwixt your gateway motorcar and target nodes, besides as your connectivity between nodes, using the post-obit command:

                      Enter-PSSession -computername <node fqdn>

CredSSP

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

    Screenshot of Updates tool using Cluster-Aware Updating with Cred S S P error.

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

  • The CredSSP session endpoint permission issue is an common CredSSP fault that can be seen when Windows Admin Center runs on Windows client machines. This issue is widely seen when the user who is using Windows Admin Center is non the same user who installed Windows Admin Center on the client machine.

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

    A side by side comparison of the error notification for Cred S S P.

Nested Virtualization

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

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

Note

For virtual switch teaming to be successful in a virtual machine environs, the following command needs to be run in PowerShell on the host soon afterwards the virtual machines are created: Get-VM | %{ set-VMNetworkAdapter -VMName $_.Proper name -MacAddressSpoofing On -AllowTeaming on }

If you are a deploying a cluster using the Azure Stack HCI OS, in that location is an additional requirement. The VM boot virtual hard drive must be preinstalled with Hyper-V features. To do this, run the following control before creating the virtual machines:

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

Back up for RDMA

The cluster deployment wizard in Windows Admin Eye version 2007 does not provide support for RDMA configuration.

Failover Cluster Manager solution

  • When managing a cluster, (either Hyper-Converged or traditional?) you lot may see a beat was non found fault. If this happens either reload your browser, or navigate away to another tool and dorsum. [13882442]

  • An issue can occur when managing a downward-level (Windows Server 2012 or 2012 R2) cluster that hasn't been configured completely. The gear up 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 practice this with PowerShell, enter the command Install-WindowsFeature -Name RSAT-Clustering-PowerShell on all the cluster nodes. [12524664]

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

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

Hyper-Converged Cluster Manager solution

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

Azure services

Azure login and gateway registration

In the 2009 release, you may run into issues logging into Azure or registering your Windows Admin Eye gateway with Azure. The guidance below should help you mitigate these issues:

  • Earlier using any Azure capabilities within Windows Admin Middle, including gateway registration, make sure you are signed into your Azure account in a unlike tab or window. Nosotros suggest signing in through the Azure portal.

  • If you successfully sign into Azure during gateway registration just exercise non encounter visual confirmation on the Azure page of your Windows Admin Centre settings, try navigating to a different page in settings earlier navigating dorsum to the Azure folio.

  • The Azure sign-in pop-up may announced more frequently in this build and may require administrators to grant Windows Admin Middle permissions more than often.

  • If you have already given admin approval for Windows Admin Center in the Azure portal and you are still seeing an error bulletin saying "Need admin approval", endeavour signing into Azure using one of the banners around Windows Admin Center instead of in the Settings folio.

  • If your proxy is mis-configured, then you may get the error message "Fault: Value cannot be null. 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 Heart did non provide prior to version 1910. If you registered your Windows Admin Middle gateway with Azure using a version earlier than Windows Admin Center version 1910, yous volition need to update your Azure Active Directory application to get the correct permissions to use Azure File Sync in the latest version of Windows Admin Middle. The additional permission allows Azure File Sync to perform automated configuration of storage account access every bit described in this article: Ensure Azure File Sync has access to the storage business relationship.

To update your Azure Active Directory app, you tin do ane of ii things

  1. Become to Settings > Azure > Unregister, and and so register Windows Admin Center with Azure again, making sure you choose to create a new Azure Active Directory application.
  2. Become to your Azure Active Directory application and manually add the permission needed to your existing Azure Agile Directory app registered with Windows Admin Center. To do this, go to Settings > Azure > View in Azure. From the App Registration bract in Azure, go to API permissions, select Add together a permission. Roll downward to select Azure Active Directory Graph, select Delegated permissions, aggrandize 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 Center, utilise the aforementioned agent for an on-bounds 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. Because of this limitation, if you wish to prepare up multiple services in Windows Admin Heart, you must fix up Azure Update Management first, and then either Azure Security Eye or Azure Monitor. If you've configured whatsoever Azure direction services that use the Microsoft Monitoring Agent, and and so try to set up Azure Update Direction using Windows Admin Center, Windows Admin Center will but permit y'all to configure Azure Update Management if the existing resources linked to the Microsoft Monitoring Agent support Azure Update Management. If this is not the case you lot have 2 options:

  1. Go to the Control Console > Microsoft Monitoring Agent to disconnect your server from the existing Azure management solutions (like Azure Monitor or Azure Security Heart). Then set up Azure Update Management in Windows Admin Center. After that, yous can become back to set up your other Azure management solutions through Windows Admin Center without issues.
  2. You lot can manually ready the Azure resources needed for Azure Update Direction and then manually update the Microsoft Monitoring Agent (outside of Windows Admin Center) to add together the new workspace corresponding to the Update Management solution you wish to use.